<div dir="ltr"><div class="gmail_default" style="font-family:times new roman,serif;font-size:large"><span style="font-family:arial,sans-serif;font-size:small">On Tue, Jul 21, 2015 at 8:44 AM, Miroslav Suchý </span><span dir="ltr" style="font-family:arial,sans-serif;font-size:small"><<a href="mailto:msuchy@redhat.com" target="_blank">msuchy@redhat.com</a>></span><span style="font-family:arial,sans-serif;font-size:small"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dne 11.7.2015 v 23:38 Jonathan Underwood napsal(a):<br>
<span class="">> Thoughts from the COPR folks?<br>
<br>
</span>I like the idea of adding Copr as intermediate step for new contributors. Copr is outer ring of Fedora and it definitely<br>
make sense for newbies to go from outer ring to ring0. Step by step.<br>
<br>
Additionally we have in plan to run fedora-review consequently after each build, which hopefully will lead to better<br>
quality of spec files and resulting RPMs.<br>
<br>
<br>
Regarding long wait for sponsor: We have little over 120 sponsors right now. And there is little over 210 reviews<br>
waiting for sponsors.<br>
If every sponsor would take 2 reviews right now, the queue would be empty. So our current process still can work.<br>
However I am aware that sponsoring somebody is very irregular task. I am sponsor too. It happen that I sponsor 2<br>
contributors in one month, but sometimes there are months where I focus on something else and I forgot on my sponsor<br>
duties. I assume other sponsors have it similar.<br>
I would welcome if somebody can write cron script which would mine data from BZ and send me email that:<br>
<br>
Dear sponsor,<br>
it seems that you did not sponsor anybody for 3 months. We have 120 new contributors waiting for sponsor.<br>
Please consider taking some bug from:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=177841" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=177841</a><br>
<br>
Sincerely your Watchmen<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Miroslav Suchy, RHCA<br>
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
devel mailing list<br>
<a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/devel</a><br>
Fedora Code of Conduct: <a href="http://fedoraproject.org/code-of-conduct" rel="noreferrer" target="_blank">http://fedoraproject.org/code-of-conduct</a></div></div></blockquote></div><br><div class="gmail_default" style="font-family:'times new roman',serif;font-size:large">In principle, I agree that Copr is probably a good proving ground, but Copr needs a lot of work right now to make that doable. It's extraordinarily slow right now, and builders don't have the level of availability needed to support it being part of the review process. It needs to become as good as OpenSUSE's Open Build Service and Canonical's PPAs before we can have any serious usage of it for this kind of work.</div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Neal Gompa (FAS: ngompa)</div></div>
</div><font face="yw-402608bc37fe50adb11a5899295781aeb83d248d-f50f319bfb1fac305d9cc7f1d235c2af--o" style="display: none;"></font></div>