More Manpower is needed

[sils]

Hey @erickwilder ,

so far we seem to be able to keep up with new PRs barely, maybe we should think about putting a note in the README asking for more people who would like to help us. There are at least some regular contributors who might actually have an interest in helping us out.

How's your opinion on this?

Lasse

[etanol]

I'm in, although there some issues that prevent me from being more involved:

• I'm switching jobs with a relocation involved, so until the second half of october I'll be quite busy
• I don't know much about your current release strategy or backporting policy
• I also find it difficult to know what needs the most attention first

Hopefully, you could write some comments about the last two items in this issue.

[sils]

@etanol I invited you with write access to the org. Thanks for stepping up. Terms are quite easy :)

• You obviously do as much as you want.
• As for releases we'll set up an automated pipeline. This'll be cool. You'll see! (See also https://github.com/python-babel/babel/issues/194)
• We're still trying to get a hold on everything so we also don't know what needs attention. The most important thing is to address new PRs as fast as possible, we should leave a reply (even if it is "I don't have time this week but review will be done next week") within 24 hours of the submission of a PR. For a biggger picture I just set up https://waffle.io/python-babel/babel - there the Pending Review column is the most important one. Apart from that we need to bring the PR count down to zero, make sure bugfixes are properly backported to the 2.x-maintenance branch and then we can look into what issues are the most pressing matters. That's my current vision at least.

[sils]

@etanol maybe you can join https://gitter.im/python-babel/babel and we can coordinate a bit?

[StanFromIreland]

@akx I guess this is a duplicate of #479

(Some triaging is necessary, a lot of noise in the bug tracker :-( )