Comment by skydhash
7 hours ago
That looks like a whole load of work. The thing thay is not defined is why I should do it.
Also forge are already fragmented. I use OpenBSD and the software in ports comes from all over the web. You got the forges, web links,… As far as collaboration go, you can always send an email to the person. Up to them to accept it. If I care that much, I will publish a blog post or share it via the community’s channel.
Those articles look like linkedin-style post to work on your brand or for some internet points.
I think these articles are meant for people who entered the developer ecosystem after GitHub became ubiquitous, because those developers basically only ever known GitHub, and some even see GitHub and Git as synonyms.
The rest of us who started developing before GitHub, or been around communities that self-host their infrastructure, we're already used with everything being spread all over the place, this place accepts patches via email, this one wants a URL to a pastebin containing the patch, others use GitLab, some the public service, others self-hosted, and so on.
I don't think this sort of article is for us, but for the former mentioned usergroup.
> this place accepts patches via email, this one wants a URL to a pastebin containing the patch
I for one would never contribute to a project that requires one of the above. I know some will shoot back with "but Linux!", but that's the exception that proves the rule.
And projects that want emailed patches might consider it a good filter for the sorts of contributors they want.
I think that's exactly why they keep their existing workflows :)
> I for one would never contribute to a project that requires one of the above.
They’re not exactly begging for your contribution, are they? It’s very much voluntary. They’re just stating how to communicate with them.
> The thing thay is not defined is why I should do it.
Most of the reasons seem to boil down to "X bad", where X is some combination of Github, Microsoft, America, and AI