<br><br><div class="gmail_quote">On Sun, May 29, 2011 at 6:53 PM, Gonzalo Odiard <span dir="ltr"><<a href="mailto:gonzalo@laptop.org">gonzalo@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I am not so sure this is a solution.<br>I think we need active maintainers, not only bugs fixes. <br>IMHO we need a MIA ("missing in action") or "non responsive maintainer" policy.<br>We have hundred of pending tickets, from months or years ago. <br>
And when we start to work in a abandoned activity, there are not a clear way to request <br>access to git or aslo (aslo is easier than git)<br>Debian have policies [1] point 7.4, and teams [2] to manage MIA,<br>Fedora have a Non responsive maintainers policy [3].<br>
Probably, we can change the time lapses, but the general idea is the same.<br><br>Gonzalo<br><br><br>[1] <a href="http://docs.huihoo.com/debian/manuals/developers-reference/ch-beyond-pkging.en.html" target="_blank">http://docs.huihoo.com/debian/manuals/developers-reference/ch-beyond-pkging.en.html</a><br>
[2] <a href="http://wiki.debian.org/Teams/MIA" target="_blank">http://wiki.debian.org/Teams/MIA</a><br>[3] <a href="http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers" target="_blank">http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers</a><br>
<br><br></blockquote><div>I tend to agree more with Gonzalo here, </div><div>although I think that we'll need both policies in the long run,</div><div>as we have been experiencing, the key to solve some activities problems (as Gonzalo depicted) is a MIA policy. Debian overall process is very well described, we can follow it but changing time frames. </div>
<div><br></div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="gmail_quote"><div><div></div><div class="h5">On Sat, May 28, 2011 at 11:46 AM, Sascha Silbe <span dir="ltr"><<a href="mailto:sascha-ml-reply-to-2011-2@silbe.org" target="_blank">sascha-ml-reply-to-2011-2@silbe.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div></div><div class="h5">
Hi!<br>
<br>
I would like to propose adopting the Debian Non-Maintainer-Upload (NMU)<br>
process [1] for Fructose. Individual activity authors would also be<br>
encouraged to allow their activities to be NMU'ed following this policy.<br>
The sections I'd consider applicable to Sugar Labs are 5.11.1, 5.11.2<br>
(read debian/changelog as Release Notes) and 5.11.4. Since the version<br>
number rules are different in Sugar, the NMU should append ".1" instead<br>
of "+nmu1" (e.g. "123.1" for an NMU based on the maintainer release<br>
"123").<br>
<br>
A few key points:<br>
- NMUs are only to be done for bug fixes<br>
- all bugs that get fixed by the NMU must have been reported in the BTS<br>
[2]<br>
- the maintainer must have been given sufficient time to act (rule of<br>
thumb: 2-10 days depending on the severity of the bug that gets fixed)<br>
<br>
The Infrastructure Team [3] would be authorised to manage permissions<br>
on git.sl.o and a.sl.o as needed for the NMU to happen.<br>
<br>
Since Sugar Labs lacks an equivalent of the Debian New Maintainer<br>
process [4], I would like to add a requirement that the uploader has<br>
successfully gone through review for a Sucrose (Glucose + Fructose)<br>
package at least once and their patch been included in mainline. Note:<br>
Patch author and uploader can be different persons.<br>
<br>
Sascha<br>
<br>
[1] <a href="http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu" target="_blank">http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu</a><br>
[2] <a href="https://bugs.sugarlabs.org/" target="_blank">https://bugs.sugarlabs.org/</a><br>
[3] <a href="https://wiki.sugarlabs.org/go/Infrastructure_Team" target="_blank">https://wiki.sugarlabs.org/go/Infrastructure_Team</a><br>
[4] <a href="http://www.debian.org/devel/join/newmaint" target="_blank">http://www.debian.org/devel/join/newmaint</a><br>
<font color="#888888">--<br>
<a href="http://sascha.silbe.org/" target="_blank">http://sascha.silbe.org/</a><br>
<a href="http://www.infra-silbe.de/" target="_blank">http://www.infra-silbe.de/</a><br>
</font><br></div></div><div class="im">_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></div></blockquote></div><br>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br>