> A maintainer who "doesn't care" if their infrastructure is proprietary is not doing a good job.
This isn't to mention also the issues regarding code ownership, where GitHub now trains their Co-Pilot AI on code under any license.
> Note that GitLab is not really the answer to this problem. It's open core, subservient to its investors, and pulls a lot of stupid shit like this.
Even if GitLab pulled out on their payed-tiers now, it's too late. This has been coming for years with the paid version of GitLab features vs the free version, which always ran behind on functionality.
We are currently considering our options to move away from GitLab. Ideally we look for tickets, merge/pull requests, CI and the ability to allow the public to contribute.
@ddevault We have been looking at SourceHut at an alternative. Specifically some questions for you:
1. Will you have a non-email merge/patch system for SourceHut in the near future [1]? The problem isn't so much for our team, but to encourage external people to help with our project who are used to the likes of GitHub and GitLab.
2. With regards to pricing for SourceHut, how will the pricing look in the future [2]? We have a small project that could pay per person/group, but would struggle to pay what GitLab are asking [3]. GitHib pricing is better, but obviously your code then becomes the product.
Great work in any case, I really enjoy seeing your blog updates.
[1] https://drewdevault.com/2022/07/25/Code-review-with-aerc.htm...
[2] https://sourcehut.org/pricing/
[3] https://about.gitlab.com/pricing/