Conversation

Notices

1. muesli (fribbledom@mastodon.social)'s status on Tuesday, 12-Sep-2023 07:16:15 UTC muesli

   @pfm

   Until there's a federated replacement? Nope.

   • FIGBERT (figbert@fosstodon.org)'s status on Tuesday, 12-Sep-2023 07:31:35 UTC FIGBERT

     in reply to

     • muesli
     • pfm 🧘

     @fribbledom @pfm definitely work in progress here with things like forgefed, but…

     also perhaps no need to reinvent the wheel. git is already federated.

     the question worth asking here could be “what does the ux look like for a forge that leans into git’s decentralized nature?”

   • muesli (fribbledom@mastodon.social)'s status on Tuesday, 12-Sep-2023 07:31:35 UTC muesli

     in reply to

     • pfm 🧘
     • FIGBERT

     @FIGBERT @pfm

     Git is fine. What needs to be federated are issues, PRs and discussions.

   • muesli (fribbledom@mastodon.social)'s status on Tuesday, 12-Sep-2023 08:31:53 UTC muesli

     in reply to

     • Baggypants
     • pfm 🧘

     @Baggypants @pfm

     I guess email is federated, yes, but it's really not the UX I'm looking for when working on issues & PRs.

     While I do run my own gitea instance for some things, switching to another unfederated platform seems futile to me. The only thing that would achieve is forcing users & contributors of my software to sign up for yet another account to participate.

   • Baggypants (baggypants@mstdn.social)'s status on Tuesday, 12-Sep-2023 08:31:54 UTC Baggypants

     in reply to

     • muesli
     • pfm 🧘

     @fribbledom @pfm There's been attempts like https://sourcehut.org/ where it uses email for managing issues, mailing lists for discussions and pull requests and the like. email is kind of federation I suppose. Saying "I don't want to leave this unfederated problematic platform for another less-problematic unfederated platform" seem like a weird take to me, though I'm probably missing something.

   • muesli (fribbledom@mastodon.social)'s status on Tuesday, 12-Sep-2023 16:13:46 UTC muesli

     in reply to

     • Ruby Rhod
     • pfm 🧘
     • FIGBERT

     @feld @pfm @FIGBERT

     git-bug is great, but it requires write-access to the repository to participate.

   • Ruby Rhod (feld@bikeshed.party)'s status on Tuesday, 12-Sep-2023 16:13:47 UTC Ruby Rhod

     in reply to

     • muesli
     • pfm 🧘
     • FIGBERT
     you mean like this?
     
     https://github.com/MichaelMure/git-bug
   • muesli (fribbledom@mastodon.social)'s status on Tuesday, 12-Sep-2023 16:46:51 UTC muesli

     in reply to

     • Ruby Rhod
     • pfm 🧘
     • FIGBERT

     @feld @pfm @FIGBERT

     As you say, spam will be everywhere. There is spam on GitHub as well. You'll deal with it.

     Unlike a world-writable repo, which would be super concerning on multiple levels.

   • Ruby Rhod (feld@bikeshed.party)'s status on Tuesday, 12-Sep-2023 16:46:52 UTC Ruby Rhod

     in reply to

     • muesli
     • pfm 🧘
     • FIGBERT
     well, I don't know what the answer is. Put it in another repo and give the world write access? Then you gotta deal with spam.
     
     Same with everything else.
     
     We make federated git forge happen? Same problem. There will be tons of spam. So then what do you do? Start whitelisting who is allowed to federate activities?
     
     Now we're back to square one.