How would decentralization work for an issue tracker? The issues have to be stored somewhere.
Comment on Organic Maps migrates to Forgejo due to GitHub account blocked by Microsoft.
twice_hatch@midwest.social 2 months agoThe issue tracker is usually the concern
xigoi@lemmy.sdf.org 2 months ago
WhyJiffie@sh.itjust.works 2 months ago
naturally on the instance that hosts the repo
pinball_wizard@lemmy.zip 2 months ago
The issues should be central, but it would be nice for my reputation as a contributor to migrate between instances.
lemmydividebyzero@reddthat.com 2 months ago
Yeah, that was my point in the first comment… But not only that…
The development with multiple people is decentralized, yes…
But even, if I add 3 remotes to my repo (1 to GitHub, 1 to Forgejo instance A and 1 to Forgejo instance B), guess what happens, if you don’t have an account on each of these… Try pushing code or making a pull request and see how it fails, because you are not authenticated…
xigoi@lemmy.sdf.org 2 months ago
SourceHut encourages an e-mail based workflow that does not require anyone but the repository owner to have an account. In fact, that’s how Git originally worked before GitHub enshittified it.