if you use gitlab/github, you will loose contributions from the people not wanting to use gitlab/github.
github has received the most contributions because it is the primary work area, not because of your users like github most.
I had issues open on gitlab and yerbamate for months, and advertised all three. Very few issues opened. PRs are still open on all three, but the only PRs have been from me and nutomic. So unfortunately no one is using them, although they do exist. Most people are still using github.
yeah I noticed gitea doesn’t eat their own dog food, which reflects poorly on them.
Luckily we aren’t limited to Gitea. You can avoid Github and Gitlab.com and use a 3rd party instance of a Gitlab installation. In that case there is no ethical issue and likely to functionality issue either b/c I believe the Gitlab s/w package is feature rich.
I will make it simple, we are not going to move the main repo away from Github for now. There is no point arguing about this, or trying to convince us. If the situation for code hosting changes in the future, we will reconsider our opinion.
Also lazy users are perhaps not the ones making significant contributions to the project anyway, because they’re lazy.
Consider as well that when Github/Gitlab.com force me through hoops as a Tor user, not only am I too lazy to solve CAPTCHAs and do Github email re-verifications but I also feel like those efforts feed unethical systems which is even more anti-motivational. I will not dance for them – and as a consequence I often do not report bugs that I discover if the project is on Github or Gitlab.com.
When a project uses Gitlab.com or Github, I’ll usually report the bug in some unconventional place (IRC, a forum, Mastodon, etc). I have little confidence that it gets spotted by someone who then actually transcribes the bug into a bug tracking/triage system. For some projects there is no suitable means of communication (they only use Twitter or Facebook or some exclusive walled garden).
deleted by creator
I had issues open on gitlab and yerbamate for months, and advertised all three. Very few issues opened. PRs are still open on all three, but the only PRs have been from me and nutomic. So unfortunately no one is using them, although they do exist. Most people are still using github.
You can issue PRs here if you don’t want to use github or gitlab: https://yerbamate.dev/dessalines/lemmy
As far as issue tracking, I don’t really want to migrate all the issues, until a federated issue tracking system gets mostly working.
Btw even Gitea is still using Github for their primary repo.
https://github.com/go-gitea/gitea/issues/1029
yeah I noticed gitea doesn’t eat their own dog food, which reflects poorly on them.
Luckily we aren’t limited to Gitea. You can avoid Github and Gitlab.com and use a 3rd party instance of a Gitlab installation. In that case there is no ethical issue and likely to functionality issue either b/c I believe the Gitlab s/w package is feature rich.
I will make it simple, we are not going to move the main repo away from Github for now. There is no point arguing about this, or trying to convince us. If the situation for code hosting changes in the future, we will reconsider our opinion.
deleted by creator
deleted by creator
deleted by creator
Concur with u/fruechtchen.
Also lazy users are perhaps not the ones making significant contributions to the project anyway, because they’re lazy.
Consider as well that when Github/Gitlab.com force me through hoops as a Tor user, not only am I too lazy to solve CAPTCHAs and do Github email re-verifications but I also feel like those efforts feed unethical systems which is even more anti-motivational. I will not dance for them – and as a consequence I often do not report bugs that I discover if the project is on Github or Gitlab.com.
You can also report bugs here on this site.
When a project uses Gitlab.com or Github, I’ll usually report the bug in some unconventional place (IRC, a forum, Mastodon, etc). I have little confidence that it gets spotted by someone who then actually transcribes the bug into a bug tracking/triage system. For some projects there is no suitable means of communication (they only use Twitter or Facebook or some exclusive walled garden).