Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
You can use other forges, but they have the exact same issues as GitHub. You need to make an account, you need to accept terms of service and if they feel like it (or are forced by a court) they'll ban you and your repository.
git send-emailexists. So it's not like you absolutely can't contribute to projects that are hosted on GitHub.At some point in the future gitlab will get federation, but that's not a solution for now. It'll take a while.
Total noob here when it comes to all things git, but can't you simply host git in a privately owned server? I thought I saw that when installing some packages on my Synology NAS.
Yes, but how are you gonna accept pull requests? You need a frontend and a frontend needs an account.
Of course, all of these alternative forges (gitea, forgejo, gitlab) can be self hosted on your own private server.
Yes, but the requirement of said frontend are very small.
Not required at all actually. For example, mirror a github repo in gitea. You'll see all the commits, their messages, and who made them. Yet that gitea instance isn't accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a "real" account.
Would you call that open source? A read only gitea instance?
If you want to get away from GitHub a mirror won't cut it, it has to be the main dev platform.
You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don't have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn't require accounts. You could email someone your git diff's and it will function the same.
I feared as much, because the same could be said about your comment above.
I already mentioned
git send-emailin my comment. But the ux of that is terrible. So if you want good UX you're in account hell, having to create a new profile for every hosting site.You can have a nice, terms of service free but read only forge, or you have terms of service and account bullshit or you can have the dev experience of git send email. Choose one of the three and until we have federation they are all terrible in some aspect.