<p dir="ltr">+1 from me!</p>
<div class="gmail_quote">On Jun 26, 2014 5:51 PM, "Sandro Mani" <<a href="mailto:manisandro@gmail.com">manisandro@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
>From time to time, I see trivial patches posted in bugzilla which end up sitting there because the maintainer is too busy / gets bombarded with tons of bugzilla mails and misses that particular one / whatever reason. As a packager, sometimes it seems very hard to get such trivial patches applied. What you can do is<br>
<br>
- You can keep pinging bugzilla<br>
- You can apply for commit rights, which might be excessive for just this one patch, and still requires the maintainer to answer.<br>
- You can start the non-responsive maintainer procedure, even if you know perfectly well that the maintainer is still active. Or you might suspect that the maintainer is inactive, but you'd rather not have to wait for an entire month, because this one bug is blocking your work.<br>
- You can start asking on irc for a proven packager to jump in and hope a proven packager is online and has time at that moment.<br>
- You can post on -devel, though again, unless someone has time right now it gets forgotten an people move on.<br>
- Repeat the above n times until someone shouts at you and flags your email as spam :)<br>
<br>
So wondering, if there is a way we can improve the situation. One idea which comes to mind would be something like "trivial patch policy"<br>
- after i.e. one week of inactivity one can flag such a bug as a trivial bug. You can only do so if you are a packager and post a patch (which also updates the SPEC, so just a matter of apply patch, fedpkg commit & build).<br>
- for anything else than packaging issues, the patch may only be a well justified upstream commit backport<br>
- a proven packagers gets notified about the issue, validates the patch and if ok fires the update. The entire thing might work similar to how a New Package / Package Change request works, by posting something like this to the bug:<br>
Trivial Patch Request<br>
=====================<br>
Patch[branch]:<br>
Patch[other_branch]:<br>
Reason:<br>
Upstream commit:<br>
Submitter:<br>
<br>
<br>
>From my experience such situations do not occur too frequently, but when they happen, they can be hard to deal with.<br>
<br>
Comments?<br>
<br>
Thanks,<br>
Sandro<br>
<br>
-- <br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org" target="_blank">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" target="_blank">http://fedoraproject.org/code-<u></u>of-conduct</a></blockquote></div>