On Thu, 21 Aug 2025 18:44:07 +0100 James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: > > I share my scripts and explain how to do a pull request. How to use > > linux-next and what to and more importantly, what not to send during > > during the -rc releases. > > I'm not sure that covers it. As I read the situation it was more about > how you work with others when there are things in the kernel you'd like > to introduce or change to support your feature. Hence it's really > about working with rather than against the community. What I'm suggesting is to have a program to help newcomers that are taking on a maintainer role. This program can not only teach what needs to be done to be a maintainer, but also vet the people that are coming into our ecosystem. If there's a lot of push back from the individual on how to interact with the community, then that individual can be denied becoming a maintainer. > > > I'm sure others have helped developers become maintainers as well. > > Perhaps we should get together and come up with a formal way to > > become a maintainer? Because honestly, it's currently done by trial > > and error. I think that should change. > > That wouldn't hurt, but that problem that I see is that some fairly > drastic action has been taken on what can be characterised as a whim, > so I think we need some formality around how and when this happens. If it was policy for Kent to work with a mentor before he could send patches directly to Linus, would this have uncovered the issues before they became as large as they had become? -- Steve
