Le 09/04/2014 18:19, Chad a écrit :
No. I've thought the OpenStack policy is rude to contributors.
If your personal review queues are too spammy you should be more aggressive about removing *yourself* from the change.
I disagree without you that it is rude. I find them warmly welcoming new contributors even when they definitely lack python skill (my case a few months ago, that has improved thanks to their reviews).
OpenStack is slightly different.
- They have a policy to have each patch to be approved by two different people. Which mean most of the code would usually at least get one review when some of our code barely has one author.
- I believe most OpenStack contributors are professional software developers being paid to contribute to OpenStack. That is their duty. Whereas we have a tons of volunteers (which is a good thing) which cant always afford to reply to all the reviews in a timely manner or sometime have no clue what they are doing (no offense there).
- They also use http://status.openstack.org/reviews/ , that ranks patches per project and priority of the bug attached to it.
- They have WIP to let people open a change that is never abandoned. Much like a Gerrit draft but public :)
We also host a bunch of repositories that most senior folks have no interest in. Our collections of extensions can probably be cleaned up and the one for which we have no interest (as a community) should be hosted elsewhere.
Finally, removing yourself from changes would not prevent you from seeing the bit rotting changes when you list all open changes for a set of repositories. On integration/* I keep them open as TODO item and there is only a handful of them so that remains manageable.
I would not mind participating in a triage to clean up the oldest patches or at least contact the various authors and ask them to continue or abandon their patches. That could even be automatized, and abandoning automatically with a nice message would have the same effect.
Hey, we can even replace Abandon with Expire if that sounds less rude.