34 ms·
The thing is, a lot of the barriers would be pretty easy to solve - especially, move from cgit and mailing lists to GitLab - hell even a self-hosted Community E
by mschuster91 3y ago
The thing is, a lot of the barriers would be pretty easy to solve - especially, move from cgit and mailing lists to GitLab - hell even a self-hosted Community Edition instance would be enough. Having merge requests with detailed annotation threads instead of patch series on mailing lists is just so much a better experience for everyone, but it seems like many of the core contributors have so grown into their paths they literally cannot see the sunlight at the horizon any more.
- aragilar 3y agoBut that wouldn't change needing to support an older gcc, nor change the "no breaking userspace" rule. CI won't run on every platform (nor all the different hardware that's out there). Random PRs will be just as ignored as random patches (probably more so if the idea is to increase the volume of contributions). A "build it and they will come" attitude only works if you're ready for the volume, if not (and based on the original discussion, the problem is lack of maintainer time), then it just adds more work.