On 12/08/2009 07:34 PM, Rafael Schloming wrote:
As there have been no comments or questions on the discussion thread,
I'm going to move this to a vote:
Sorry for jumping in late here, I was away on holiday when the mail was
first sent.
Qualities we look for:
- A candidate must demonstrate an understanding of how our project
is structured and how we work.
Could we make this a bit more concrete/specific?
For me the key to how we work is a collaborative, consensus based
approach to development.
What is meant by project structure here? A knowledge of the different
components and how they are intended to work as a whole? Or an
appreciation of the individuals that work on particular areas (i.e. the
team structure)? Or something else?
- A candidate must communicate openly about work planned/in-progress.
- A candidate must demonstrate expertise in a significant area of
the existing code base.
- A candidate must demonstrate an extended commitment to the
project.
Tests for these qualities:
- contacting the right team members to discuss changes
- actively soliciting feedback for significant changes or new
development
The above is I think a particularly important point. For new features or
components it is vital that there is a clear attempt to build consensus
as to the approach taken. Its also important that other members of the
community be actively encouraged to try it out and that doing this is
made fairly easy.
It's often harder to demonstrate collaboration and consensus based
development on a new component than it is for fixes and enhancements to
existing code (that hopefully already has users and maintainers who will
point out issues or ask questions). However it is especially relevant in
those situations (to prevent accumulating code that does not have users
or maintainers).
- multiple independent contributions over a period of several months
- sponsorship by someone who has worked directly with the candidate
reviewing and committing patches
- detailed positive feedback from those who have worked directly
with the candidate
>
- a record of patches that maintain or improve the quality of the
code without the need for feedback or rework
Please cast your vote below:
[ ] Adopt the above statements as our official committership criteria.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
