I like to call this “drive-by-bugfixing” and this is how it usually happens:
- I have a problem with e.g. xfce4-power-manager, which I’m unable to fix right now
- I check out some random other package (let’s call it “yerba-power-manager”) to check if it can replace xfpm for me
- I find it has a bug. Or two. Actually caused by broken openSUSE patches trying to implement new APIs
- Because it is “an interesting problem”, I fix it them just for fun
- Later I find that I have no use for this package as (for unreated reasons), it does not fix any of my original problems
So far so good. Now I have a fixed package lying around in my
home:seife buildservice repository. Trying to be a good cititzen, I submit it back to the original YERBA desktop project.
Can you imagine what happens next?
Correct! It gets rejected. Why? Because I did not mention all my patches in the changelog.
Come on guys. Policies etc. are all fine, but if you want people helping maintain your broken packages, then don’t bullshit them with policy crap, period.
I had done the heavy lifting last sunday and fixed the bugs, now all that the desktop maintainer would have needed to do would have been to amend the changelog.
And yes, I understand very well that such policies are a good thing to have, and necessary, and if I’m contributing to some subproject on a regular basis, then I of course make sure that I’m following these rules. On the other hand, it’s really easy to discourage the occasional one-time contributor from helping out.
(Names changed to protect the guilty)