> In order to be be granted committer rights, I think these > requirements have to be met: > 1 - specific intentions. If you don't plan to use them for a > specific purpose, it's better to wait until you do.
What do you mean with 'them'? The cvs-write-rights or the voting-rights? Cvs I could agree. > 2 - proven trackrecord and commitment. There are a number of > ways to achieve this: participation on the > developers-mailinglist, attending developers meetings, > submitting bugreports and bugfixes, etc. IMO it shouldn't matter a lot in how much you contributed to the community. A commitor should know enough about MMBase to make decisions which will improve it. Contributing to the community is one of the ways to proof that you know MMBase. Ronald knows easily 10 times as much of MMBase then I did at the moment I became a commitor. I became a commitor when I worked on a project at the VPRO. I knew MMBase only from a few months at the VPRO and a 'small' project at Vodafone. Ronald has worked on many projects with MMBase this year and has seen the 'mess' he will step into. Most of his mmbase work was to adapt MMBase to let it meet the customer requirements. I am confident that he knows enough to get the voting-rights. As a committor you have to get more involved and share your knowledge. I have no doubts that he will. Nico ---------------------------------------------------- This message transmitted on 100% recycled electrons.
