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?
I considered @codeberg and #sourcehut, but that solves a problem we don't really have: the hosting part. We already have a gitea instance, it works and is maintained anyway.
Sourcehut has a CI setup, which we are still evaluating: our gitea needs work still to get a drone.io CI running.
Sourcehut or Codeberg might lower the participation barrier a little, but I presume that anyone on #sourcehut or #codeberg also has a GH account, but not vice-versa.
@flockingbird after Microsoft bought github, many people dropped their account or refuse to access it if they have one. The people using sourcehut or codeberg would much more likely be in that set.
As noted in the other thread, if discoverability is the concern, then following the Linux model might make sense (with pointers/direction to the official non-gh instance).
@flockingbird also, the people looking for a LinkedIn alternative will align with those avoiding github for the same Microsoft reason.
@flockingbird
Just wanted to second what has already been outlined thrice:
If your target audience is people wanting a libre alternative to linkedin then they probably won't like to learn it's hosted on github (I know because I fit that description 😬)
Also, email contributions mean no account needed, and that's cool 👍
@keverets