4 ms·

"That circle"? You make it sound like an exclusive club for the elite. This isn't supposed to be a popularity contest. Linus' attitude is very material. Kernel

by NBJack 3y ago

"That circle"? You make it sound like an exclusive club for the elite. This isn't supposed to be a popularity contest. Linus' attitude is very material. Kernel leadership sets the stage for other contributors to do the same, good or bad.

jacquesm 3y ago
Linus' attitude has nothing to do with it, he wasn't part of this exchange at all. And yes, it's an exclusive club, hence people trying to become a part of it.
- mfru 3y ago
  Open source software development is not an exclusive club. If you contribute to open source software you are an open source contributor. Stop gatekeeping.
  - jacquesm 3y ago
    Security patches are the last place (especially tiny ones) where you want to make a stand for proper attribution of four line patches, the rest got properly credited. Note that the OP misrepresented the nature of the exchange with the kernel maintainer and that puts their motivation about the whole thing in doubt. Nobody got robbed. OP still has contributed code, the LKML lists are proof of that and if you think that in the future every such patch should carry an automatic 'Suggested-by' or 'Coauthored-by' tag then you could propose that. But for now this is the maintainers call and by sending mail to the LKML you play by their rules. That's not gatekeeping, that's just reality, and yes, kernel maintainers are an in-group whether we like it or not. My take on that is that if I had stuff that gets included that I couldn't care less about the attribution because what they give me is so much more than I'll ever be able to give back. Of course everybody is welcome to their own motivations, but you send unsolicited patches with the hope that they'll be used, if you get credit that's great but then the patch had better be ready to run as is and preferably for something a bit more substantial.
carapace 3y ago
Um, Kernel maintainers are an exclusive club for the elite. Seriously, I'm not even trying to be funny or edgy or anything. The hierarchy roughly goes: users -> script kiddies -> programmers -> compiler writers -> kernel devs.

by NBJack 3y ago

jacquesm 3y ago

Linus' attitude has nothing to do with it, he wasn't part of this exchange at all. And yes, it's an exclusive club, hence people trying to become a part of it.

mfru 3y ago
Open source software development is not an exclusive club. If you contribute to open source software you are an open source contributor. Stop gatekeeping.
- jacquesm 3y ago
  Security patches are the last place (especially tiny ones) where you want to make a stand for proper attribution of four line patches, the rest got properly credited. Note that the OP misrepresented the nature of the exchange with the kernel maintainer and that puts their motivation about the whole thing in doubt. Nobody got robbed. OP still has contributed code, the LKML lists are proof of that and if you think that in the future every such patch should carry an automatic 'Suggested-by' or 'Coauthored-by' tag then you could propose that. But for now this is the maintainers call and by sending mail to the LKML you play by their rules. That's not gatekeeping, that's just reality, and yes, kernel maintainers are an in-group whether we like it or not. My take on that is that if I had stuff that gets included that I couldn't care less about the attribution because what they give me is so much more than I'll ever be able to give back. Of course everybody is welcome to their own motivations, but you send unsolicited patches with the hope that they'll be used, if you get credit that's great but then the patch had better be ready to run as is and preferably for something a bit more substantial.

carapace 3y ago

Um, Kernel maintainers are an exclusive club for the elite. Seriously, I'm not even trying to be funny or edgy or anything. The hierarchy roughly goes: users -> script kiddies -> programmers -> compiler writers -> kernel devs.