Our #foss project team is *very* motivated to do the right thing, and we need your input and help 🙏
1st question: What's your preferred forge?
@dachary @activitypub I suggest nixing #Gitea because there are already many decent public gitea instances, but not many of the other packages: https://git.sdf.org/humanacollaborator/humanacollabora/src/branch/master/forge_comparison.md
And this mention on #codeberg where @6543 is a Gitea team member: https://codeberg.org/Codeberg/Community/issues/397
@humanetech @cj @dachary @clacke ah, just realized I gave a snap answer w/out knowing what fedeproxy.eu is doing. Some of the work could be done by incorporating this tool: https://github.com/MichaelMure/git-bug Periodically running "git bug bridge pull" would import the bug reports into git. From there, it would just be a matter of using a git command to get the new reports which could then feed Mastodon.
Oh no didnt noticed, to les time and thousands of emails from github (i just delete them) ...
The grade to manage what mails you will recive in github is ... bad
Thabks for the ping
Or does a fedeproxy-user create all the issues / PRs / etc. on the remote server? If that’s the case, isn’t that gonna be confusing if half of the participants in a conversation have the same username and avatar?
@tastytea when forges do not implement federation, a proxy needs a user on every federated forge, indeed. It could either be users that you happen to control because you already have accounts on all of them. Otherwise fedeproxy needs to create an account for this purpose. It would be confusing if multiple users are merged into a single one, you are correct. Fedeproxy will need to create a different account for every federated users. Does that sound sensible to you ?
@dachary I don’t think fedeproxy could create accounts automatically, because of captchas. So I would have to create the account manually. At this point I could just use the remote forge directly. I don’t see the benefit in creating an extra step.
@dachary @tastytea @dachary IMO the most relevant question dachary could ask is what forges are most hated considering the goal is to liberate data. And for that, I put gitlab.com as the most hated & most useless since we must solve a CAPTCHA just to read existing bug reports. #Gitlab.com is the most inaccessible forge of all forges even pretending to be "public". It's the max security prison of all prisons.
@dachary @tastytea Since I can't file bug reports on gitlab.com, I find the corresponding pkg on Debian or Ubuntu bug trackers and file it there-- but then I get complaints because the bug should be reported upstream (where the pkg is jailed in github or gitlab.com). Plz consider solving that problem with fedeproxy.
@dachary @tastytea Note this survey as well: https://infosec.exchange/@bojkotiMalbona/104637098084869887
If this indeed happens, my bet is on Amazon, as an extension to their whole AWS shebang.
@humanetech @resist1984 @dachary @tastytea Yes, it's only a matter of time before Gitlab exits and merges with one of the BigTech companies.
But the planet-brain question is why we always become so dependent on these corporate intermediaries. Are our development tools not deficient if we always have to rely upon sites like Github/lab to collaborate on software?
Also, I don't think returning to mailing list workflows is viable. We need to be doing something better.
@bob @humanetech @resist1984 @tastytea On the bright side there is progress. Twenty years ago (SourceForge / Savannah time) the problem was different: self-hostable forge software was difficult to install and the user experience was not great. Today we can build on quality forge software, establish a federation and free ourselves from centralized services.
I think the benefit comes afterwards, as you don't have to remember to manually track a million remote repositories. Many of which you forget about after a while. You get to collaborate with them from your own forge, or check your #fedeproxy account to get an overview of anything you are interested in, with activity feeds, topic lists, etc. Many cool features are possible. It would be interesting to find a first MVP that offers an exciting first start. There's the challenge.
Github because I like git and for the social aspects and the good documentation and the nice UI
I try to use #SourceHut as much as I can. The stripped-down nature of it is quite refreshing. Things always feel fast and snappy with it.
I mostly use #GitHub for eyeballs now. I hate to admit it, but it's still a very convenient way to collaborate and discover new projects.
> What's your preferred forge?
This list gives an idea, additions welcome:
There is evidence that Free Software developers routinely cross reference issues (inserting URLs in commits messages or in issue comments) located on different forges. This is a heartbreaking case of federation done manually.
@fedeproxy should implement that first.
The poll results are at https://forum.fedeproxy.eu/t/poll-results-what-is-your-preferred-forge/135
A newer server operated by the Mastodon gGmbH non-profit