Sponsor shortage

[Kevin Fenzi]

So, I'll reply here, but I'm replying in general to the thread not the
last post in particular. ;) 

This topic seems to come up from time to time and we never really
"solve" it, but a mix of old and new ideas here I think has some
promise:

* There's movement to make an app for new package reviews and move it
  out of bugzilla. I think this would help us out allowing more
  automation and not showing sponsors things that aren't ready yet
  (unless they want to look at them) and also allow submitters more
  visibility into where they are in the process. 

* I like the idea of suggesting to new submittors that they maintain
  their new package in a copr and keep it up to date with upstream
  changes, and review suggestions. I think that would give them more
  practical experence in maintaining and also show to sponsors that
  they are willing to do that work.

* The co-maintainer path I think is a good one for some people, but I
  am not sure how to really give it more visibility. I think my hope
  when we added that was that there would be people who would be active
  in reporting bugs/providing patches for some packages and would be
  natural to add as co-maintainers, but I am not sure this has really
  happened. 

Anyhow, just some early morning thoughts... back to coffee.

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20150713/30615cb0/attachment.sig>