2 ms·

Obv. feel the same way, which is why I started being the trivial patch monkey which Linus refers to. That's long ago been handed over, but I like to think that

• vertis 8y ago
  I think the other side of this is important as well, shoving a patch or a pull request across for something you use and sharing with them that you're fine if they don't merge it. Probably less with the kernel and more with smaller FOSS it is a way of serving your own needs and also giving back. But there has to be an expectation that the maintainer isn't under any obligation to merge or even evaluate it.
  • RustyRussell 8y ago
    As a maintainer, part of my task is to interface between developers and the code. That generally means responding to submissions somewhat in proportion to the effort the submitter put in. More importantly, I have benefitted so much from senior devs "wasting time" on me, I am obliged to help others now I'm senior.
• anitil 8y ago
  It's good to hear these opinions, and I think that its important work. I've come across a couple 'huh, that doesnt seem right' things in the kernel, but always shied away from trying to contribute because I didn't want to waste people's time
• RcouF1uZ4gsC 8y ago
  It looks Jesper Juhl (the person who asked Linux the question) now manages trivial@kernel.org which is the address for the Trivial Patch Monkey. https://kernelnewbies.org/UpstreamMerge/SubmittingPatches https://kernelnewbies.org/UpstreamMerge/SubmittingPatches This is an awesome example of someone being encouraged to participate when they were starting out, and then helping to make it easier for other newcomers to participate.