this post was submitted on 24 Jul 2024
4 points (83.3% liked)

Open Source

32298 readers
37 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

Misleading title.

~~If my thing was public in the past, and I took it private, the old public code is still public.~~

That's... How the Internet works anyway.

Edit: See Eager Eagle's better explanation below.

TL;DR - be careful who you allow to fork your private repos. And if you need to take a public repo, which has forks, private, consider archiving the repo and doing all the new work in a new repo. Which is arguably the reasonable thing to do anyway.

Still a misleading title. This isn't a way to break into all or even most of your private repositories.

[–] [email protected] 0 points 6 months ago (1 children)

Im thinking of self hosting Forgejo one day.

[–] [email protected] 0 points 6 months ago (1 children)

sourcehut is much better if you can pay

Edit: Only repo hosters need to pay. Everything else is free.

[–] [email protected] 0 points 6 months ago* (last edited 6 months ago) (1 children)

I want forgejo for its upcoming federation feature tbh.

[–] [email protected] 0 points 6 months ago (1 children)

Considering that git doesn’t need federation, and email is the grandfather of federation, sourcehut has a working version of it this very moment.

[–] [email protected] 0 points 6 months ago (1 children)
[–] [email protected] 0 points 6 months ago

I'd guess because the same argument could be made for the website you're on right now. Why use that when we could just use mailing lists instead?

More specifically: Sure, Git is decentral at its core, but all the tooling that has been built around it, like issue tracking, is not. Suggesting to go back to email, even if some projects still use it, isn't the way to go forward.