I had the talk  about Fedora Sponsorship process at Flock. And we had
very interesting follow-up discussion.
We come up with several improvements, which should be easy to implement
and may improve the process a lot. I am posting it here so more people
can see that and join the discussion.
a) Sponsoree (who apply for package maintainer status) is required to
create Copr project and maintain the package there until he get the
package into Fedora. This should show his endurance to sponsors. It will
improve the morale of the sponsoree as the package is immediately ready
for other users. And it is not wiped after 14 days as scratch builds in
b) fedora-review is run automatically by some bot/script just after
review have been submitted.
c) Create wiki page with list of sponsors willing to accept new
sponsoree. And list area of expertise of sponsors (e.g. java, python,
IoT...). This will make for sponsoree easier to find right sponsor.
Because we have some sponsors, who are active but are not willing to
accept new sponsoree right now.
d) When sponsors is not active for 2 years [*] - that means not just in
sponsoring work, but there is no activity in BZ, koji, wiki and any
other Fedora service at all (guessed by reading log of fedmsg), then his
sponsor status is removed. We will assume that the sponsor is gone for good.
e) When the package review is still not assigned to anybody after 3
months [*], then 3 [*] random sponsors are added to CC and asked to
proceed with the review despite the fact that it likely doesn't belong
to their area of expertise. This should helps us to get rid of stalled
review, which are waiting for ages to get some sponsor.
Those are the ideas which came up at Flock. Please comment this. And if
we come to some conclusion, I can pass it to FeSCo for approval.
Please note that the data in this presentation is based only on
data I was able to gather and I am aware the it does not reflect 100%
the reality. But it approximately gives us the order of magnitude of the
reality and approximately ratio.
[*] I just made up this number. Feel free to discuss appropriate interval.
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys