Gregory's Server@raulinbonn @lina @desttinghim to be honest - my bigger hope would be that he actually sets rules around "If there has already been a consensus in the kernel to accepting a project, and part of that project falls on your lap for review - you either have to review it in good faith or hand it to someone else who will.". Because like - folks like Neal are right, this has definitely been a problem in many areas of the kernel for a while. I'm all for thorough review of patches but I've seen/had discourse sent to me that was clearly just "I have a disdain for rust and am buying time", or sometimes literally just "I have a disdain for rust and I will bother you because you sent patches related to rust"
|
3 comments
 @Lyude @raulinbonn @lina @desttinghim It's a big part of why @AsahiLinux has made no progress on upstreaming in over a year. The people who worked on it have become really demoralized due to lack of support from... well, anybody in the kernel community, even with @torvalds using it for a brief time. (I don't even know if he still does or if he cares about it anymore...)  @Conan_Kudo @Lyude @lina @desttinghim @AsahiLinux @torvalds So particularly frustrating because the DRM subsystem had room for improvement given the bugs Lina was looking into. Estability/quality improvements there would benefit way more than just Asahi Linux and the Mac devices |
@raulinbonn @lina @desttinghim It even extends outside of just being obstinate - subsystems like input have become pretty difficult to get a lot of work into simply because there's not enough maintainers, yet despite this being a problem for ages now I've seen basically no effort from the single maintainer there to actually bring in new maintainers when other subsystems like DRM very rarely ever have only single maintainer for anything