Fedizens, great news!
Your help is vital!
You know this, and we complain about it here on fedi. But too few people act! The "tragedy of the commons" is on all of us.
@gitea and Forgefriends ..
Not just techies can participate. #SocialCoding is for everyone 💞
Join the community now. Raise your voice. Write articles. Revamp the site. Brainstorm ideas.
I hope people will finally find a good reason to move away from GH. I've stopped maintaining my personal projects on GH for years now. But I feel annoyed when I have to login to nonfree GH just to post an issue/PR.😠
@humanetech Probably the real tragedy is that all open source exists in service of Big Tech. And for it to be "commons" it would need protection from the hidden corporate violations instead. So be careful what you wish for.
@humanetech While I appreciate the effort people put into allowing forges to federate, I think Drew DeVault has a valid point:
Git *as such* is already federated and decentralized. And with it's built-in email support it's incredibly resilient and efficient. So instead of putting a lot of effort and time into federating forges, we might want to focus on making the email based git workflow more widely known & accessible?
Granted, code collaboration does not happen exclusively in actual code. However, mailing lists can power bug trackers & discussions.
Why do you feel like people dislike mailing lists? Because of the tool as such? Or because Github/Gitlab/Gitea have popularized the pull request based collaboration workflow?
@clacke @humanetech @puer_robustus I didn’t know about the email thing until this week, and am otherwise very familiar with git and the various platforms people use with it. The big draw of GitHub is how searchable it is, the ability to raise issues and +1 them, and similar social features in which email falls short.
Same for me. Email is not doing it for me, and the last couple of years I've been minimising its use. In all the companies I've worked email was a big productivity loss imho with all kinds of crazy CC-ing and forwarding that formed some kind of hidden communication layer and creating all kinds of miscommunication where everyone has different perception of what's going on.
And also mailing lists I never found intuitive. But maybe I lacked the proper tools.
My point is that it is possible to collaborate with others on coding projects with git + email in a federated and decentralized way already, *without* having to add another layer of complexity by introducing forge federation.
Ah, yes. I think that is a better approach. A best of both worlds that can entice people to use an email flow. Forges offer an ever expanding set of integrated features that ease software development, making their use more compelling.
What the #Forgefriends project can achieve is openness, level playing field, where no one is excluded from stuff that only exists in one walled gardens or the next.
I call the vision behind this "United Software Development".
The original server operated by the Mastodon gGmbH non-profit