Follow

Fedizens, great news!

The project which allows code to interoperate on the is selected for the 2nd phase of the DAPSI program. The project has rebranded to forgefriends.org

is both Community and project on an important mission: To unite coders online, and make stronger bonds in the world and to the benefit of the .

@gitea is first in adding code. They're your forge friend!

Your help is vital!

1/2

Both and are doing all they can to open up a walled garden ecosystem where is increasingly captured in proprietary full-service platforms.

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. is for everyone 💞

Join the community now. Raise your voice. Write articles. Revamp the site. Brainstorm ideas.

Donate!

2/2

@humanetech So good to see it happening. This is probably the most exciting thing I've seen in months in #FreeSoftware world.

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:

drewdevault.com/2018/07/23/Git

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?

@puer_robustus @humanetech Git is 25% of what runs a github/gitlab/gitea project. And people don't like mailing lists.

@clacke

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?

@puer_robustus Because generated hypertext provides the context, structure and connections a flat pile of text can't. Affordances to take action without using a special client and configuring it just so. Previews of the consequences of your actions before you take them.

It's very cool if someone can open issues, close issues, connect a review comment to three specific lines, run blame on those lines to see where the previous version came from all with sending some specially formatted emails and all without leaving Mutt or Emacs, but that's always going to be a 1% power user interface.
I know git in and out, I have ssh keys set up, I can manage three branches at the same time with git rebase, but if there's a trivial merge conflict I can resolve right there on the web, I will use that instead of fetching and checking out my colleague's branch, merging it and pushing it.

I edit my source code in a text terminal with tmux and vi, but I also keep a browser with nine tabs of source code open, because there are so many neat tools there connected to just where they need to be.

@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.

@Literally @clacke @puer_robustus

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.

@humanetech @Literally @clacke All of you have valid points. Mail can be horribly abused, a web interface is more intuitive and comes with some bells and whistles mail will never provide.

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.

@humanetech @Literally @clacke For all of the convenience (i.e. not strictly necessary but helpful) features you mention, it can of course be worthwhile to still go ahead with forge federation.

As long as we can all work together, all is good ;)

@puer_robustus @Literally @clacke

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 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".

@humanetech @puer_robustus @Literally Right! ForgeFriends or a native ForgeFed implementation can allow someone to use the amazing email workflow that their home forge supports while contributing to a project on another forge that doesn't support it. Everybody wins!
first they came for our mailboxes,
and turned them into bugged-web mail,
hardly suitable for software development,
and their lusers learned that all email sucks

then they came for the software forges,
and because email had been made to suck,
point&click recentralizing interfaces dominated,
bottlenecking the preexisting git federation

then we who resisted were left alone,
faster, better, and lonelier, pestering aside,
by hostile email monsters that ostracize us,
and by blinded prisoners who pull us in
Sign in to participate in the conversation
Mastodon

The original server operated by the Mastodon gGmbH non-profit