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 Cool beans, Drew builds rad stuff. :) Fingers crossed!
Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.