Considering to move from a selfhosted gitea to Github with flockingbird. Sourcecode, issues, wiki/documentation.
* Discoverability: We're just more visible on GH than on "some random website".
* Participation barrier: you probably have a GH account, but certainly no account yet on our instance.
* Defacto standard: external systems like CI, support etc all require github.
It feels a bit like giving in, but the benefits seem to outweigh the idealistic stance.
What do you think?
@flockingbird Rather than asking whether "the benefits outweigh the idealistic stance" (a framing that, I'd argue, prescribes the answer) I would instead consider what problems you will have to solve (make a concrete list!) if you do the idealistic thing and whether you think they can be dealt with, given your resources.
@freebliss Thanks for the suggestion.
We did that. And the outcome was clear: go for Github.
But that makes me unconfortable and feels like "giving up on free, decentralised web". Yet such a "feeling" is hard to place in a concrete list.
Hence the request for some other viewpoints here. Sorry if the "framing" comes over as such: it was an honest request for input on a matter that is important to us, yet hard to quantify; if at all.
@flockingbird I see. Well if you seriously "did the math" then even if it feels bad you should go with github! :), because anything else will, according to your considerations, hinder your project so much that it's of no help to the cause anyway. Failing idealistically is failure. If I misread things and you wanted feedback on your bullet points, mine would be that I would consider Discoverability and Participation Barrier both moot: Any serious and viably attractive project should and will (I believe) succeed without the extra discoverability GH provides, if it does not the proposition or marketing is probably too weak (note that this is no judgement on your project, I don't know it (yet)). Likewise any serious and determined contributor - the ones a project really needs - will not be hindered by having to register somewhere (my feeling anyway) and one shot "drive-by" contributions are probably negligible in the big picture. One shot issues/bugreports might be a relevant factor though, I concede to that.
@flockingbird I didn't mention these two points earlier because I guess your (or anyone's) evaluation on this will probably be decided in the realm of CI requirements anyway, this is where the real prohibitive factors can occur :)
@flockingbird Cool beans, Drew builds rad stuff. :) Fingers crossed!
@freebliss I'm still evaluating the hosted CI on #sourcehut . If that works, it might be the best option.