[QGIS-Developer] 32 by 3.2?

[Matthias Kuhn]

I'm superhappy to see it was worth the effort and having the queue down
to a manageable size it feels indeed much better to review pull requests!

I am also taking this as an opportunity to reflect on the current state
of the project. I think we have seen an incredible improvement
concerning stability and processes recently. Pull requests are the
standard, the amount of unit tests and reliability of the CI
infrastructure is constantly improving, we have a very active reviewing
process (it's a nice job to learn and improve skills by the way, anyone
interested in helping here is welcome. It's worth getting started, just
pick your pull requests!). In short, we have done a leap forward!
A huge applause for the project which I think has proven to be mature
and ready for any infrastructure.

I'm also in favor of having some automation on the pull request in place
to make stalled pull requests move forward and closing them after a time
of inactivity. This will help to shift some of the responsibility away
from reviewers towards pull request authors, and if done in a polite way
clearly stating reasons and possible steps I think this does not have
any bad impact. Even more, it frees some resources on reviewer side
which may be better invested on active pull requests where motivation is
high to advance things.

If I am not wrong the proposal to trade things for sponsorship levels
has been scheduled for the next PSC meeting? I think this is a topic
which requires very careful evaluation!

Thanks
Matthias

On 06/22/2018 07:25 AM, Paolo Cavallini wrote:
> Hi all,
> 
> Il 22/06/2018 01:20, Nyall Dawson ha scritto:
>> On Thu, 21 Jun 2018 at 23:07, DelazJ <delazj at gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> Congratulations to all the cleaners! I can see that GitHub had for a moment reported 32 issues today and I'm pretty sure it'll go lower.
>>
>> Yep - we're now floating around the 32 +/- 4 mark, depending on the
>> time of day. I think we can declare this campaign a success and all
>> have a virtual beer together!  Seriously, this is a tremendous effort
>> consider that we had > 150 open requests just a short while ago. It
>> presents us much better as a friendly, welcoming project who value new
>> contributions.
>>
>> So where to from here? I've given it some thought, and here's my
>> current thinking:
> 
> I agree fully. How to implement this? IMHO, shared responsibility do not
> work well for this kind of task. We had the same issue with plugin
> management, with too many falling into cracks.
> I believe we need a PR manager, who gives the initial feedback and
> forward each PR to the most appropriate dev, or back to the proposer.
> This boils down, as for other unsexy tasks, to how to motivate people.
> Until now several people had taken one or more of them as a volunteer
> work. Now we have some proposal to trade this kind of things with an
> explicit sponsorship level. Other proposals will be most welcome.
> In any case, it is clear that providing adequate motivation and
> incentives is vital to the project, I'm not sure volunteering can last
> forever and it can cover all our needs.
> All best wishes.
>