Improving our processes for new contributors.

Parag Nemade panemade at gmail.com
Tue Jul 21 13:41:34 UTC 2015


Hi,

On Tue, Jul 21, 2015 at 6:14 PM, Miroslav Suchý <msuchy at redhat.com> wrote:

> Dne 11.7.2015 v 23:38 Jonathan Underwood napsal(a):
> > Thoughts from the COPR folks?
>
> I like the idea of adding Copr as intermediate step for new contributors.
> Copr is outer ring of Fedora and it definitely
> make sense for newbies to go from outer ring to ring0. Step by step.
>
> Additionally we have in plan to run fedora-review consequently after each
> build, which hopefully will lead to better
> quality of spec files and resulting RPMs.
>
>
> Regarding long wait for sponsor: We have little over 120 sponsors right
> now. And there is little over 210 reviews
> waiting for sponsors.
> If every sponsor would take 2 reviews right now, the queue would be empty.
> So our current process still can work.
> However I am aware that sponsoring somebody is very irregular task. I am
> sponsor too. It happen that I sponsor 2
> contributors in one month, but sometimes there are months where I focus on
> something else and I forgot on my sponsor
> duties. I assume other sponsors have it similar.
> I would welcome if somebody can write cron script which would mine data
> from BZ and send me email that:
>
> Dear sponsor,
> it seems that you did not sponsor anybody for 3 months. We have 120 new
> contributors waiting for sponsor.
> Please consider taking some bug from:
>   https://bugzilla.redhat.com/show_bug.cgi?id=177841
>
> Sincerely your Watchmen
>
>
What above is said is from sponsor side. I will suggest similar for
contributor side. Implement a script which search FE-NEEDSPONSOR package
review bugs where package has not already under review. This script will
check package submission date and then submit a comment every month till 3
months like

Dear contributor,
Its one/two/three month since this package review is submitted and you are
in need of a sponsor. Have you started reviewing other packages reviews? if
yes please post the link to your reviews in the next comment.
Have you also run fedora-review on your package submissions? if yes and
found any issues in review.txt then try to fix them or ask on devel list or
#fedora-devel irc channel for help.

something like this. This will make sure contributor realize what he need
to do next after his submission. Thus, contributor will not loose interest
in packaging.

Regards,
Parag.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20150721/8822be77/attachment.html>


More information about the devel mailing list