On Mon, Aug 17, 2015 at 09:14:34AM +0200, Miroslav Suchý wrote: > > I don't know if this has changed in he new age of having crazy human > > coding machines, but the last time i looked it was extremely difficult > > to see someone's sponsor and to generate statistics on sponsorship > > activities. I had some tooling a very long time ago which was used to > > stir up a whole pile of flames surrounding the handling of inactive > > sponsors. > > Although I think too, that right way is to sponsor somebody via Package Review, I enhanced my script to show direct > sponsorship - which means that this information is available in FAS :) > Mind that this information is not (yet?) linked to that BZ reviews, so I show BZ reviews *and* independently sponsorship > in FAS. Without information if this was result of some Package Review. There is this process to become a co-maintainer. I think this is quite useful: The way this is intended (IMHO), is, to get an upstream developer becoming a package maintainer for the specific component. That person at first might not be the best person to maintain an rpm package. But this person knows the software quite well. -- Matthias Runge <mrunge@xxxxxxxxxxxxxxxxx> -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
