Recent searches
Search options
"[…] Instead of accepting my [#LinuxKernel] patch or guiding me towards a better solution, he went ahead and implemented his own fix, giving me credit only for reporting the issue […]
My first contribution to the [#Linux] #kernel was a really frustrating and discouraging experience, dealing with people who do not think it’s important to get proper recognition for your work. […]"
https://ariel-miculas.github.io/How-I-got-robbed-of-my-first-kernel-contribution/
1/ Side note: I sometimes wonder if…
2/…patches from new or rare contributors should have some kind of tag to indicate things like
(1) I have no interest in learning how to do things better, I just want it fixed; I'm thus happy if someone dramatically changes the patch or writes a better one.
(2) I'd really like to learn how to do this properly, hence would be grateful if someone could guide me somewhat.
Why? Well, misunderstandings here can be annoying and a waste of time for both sides (and lead to situations like the above).
Of course it's silly and over complication. But at the same it makes something explicit that in an ideal world might be wise for everyone to make explicit, as people will forget to spell it out (and maintainers will forget to ask which of the two it is).