Hi all,
  I have been thinking about what should be the criteria for PMC
members for ZK. I do not have much experience with PMC member criteria
for other projects except for Hadoop. In Hadoop we indirectly imply
that a PMC member be a superset of a committer. Meaning more
responsibilities than a committer, more responsibility towards project
direction, more responsibilities towards projects day to day
activities.


 and here is what I had in mind for ZK (mostly explicitly stating what
we have in Hadoop):

A PMC member should be able to get involved in the day to day
activities of the project
   - by day to day activities I imply
      -  release discussions
     -  code reviews/ could be any kind - documentation/ others (does
not imply a deep understanding of the project), should be willing to
contribute on any part of the project
     -  should be willing to work with new contributors and mentor
them (mostly a superset of committer).
  - works well with other PMC members

By the above I imply that a PMC member has a greater set of
responsibilities that a committer and should be able to review (any
contribution) and contribute towards ZK releases.

What do others think?

thanks
mahadev

Reply via email to