[core-workflow] Tracker workflow proposal

[Nick Coghlan]

On 22 Apr 2014 00:06, "Ezio Melotti" <ezio.melotti at gmail.com> wrote:
> What if we can't keep them manageable?
> There's a fine line between managing to handle all the incoming issues
> and having issues start leaking in and giving up on the goal of
> keeping the queues empty.  When your queue has 3 issues, well, you
> could just take a look now and make it empty, but you don't quite have
> time right now for looking at 5 issues... Maybe later (or tomorrow, or
> during the weekend) you will have more time.  I think many of you had
> something similar happening with your mail inbox (or new year
> resolutions, or similar things).

Then that becomes data folks like me, Toshio Kuratomi, Jesse Noller and Van
Lindberg can take to our respective management chains to say "Hey, we have
this critical upstream dependency that needs more developer time to keep up
with its workload, can we have a hiring req, please".

That's the other advantage of setting up core development as clearly being
a service role for the rest of the community - it's a way to bring full or
part time paid development into the picture without generating resentment
amongst volunteer contributors, by specifically tasking the paid developers
with ensuring that roadblocks are cleared out of the paths of volunteers.

Where Tim Peters used to say "we read Knuth so you don't have to", the
ideal of paid open source development for me is "paid staff do the
boring-but-necessary bits so volunteers don't have to". (I think payment is
also appropriate for essentially "on call" roles like the security response
team)

Cheers,
Nick.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20140422/883b9af7/attachment.html>