> PMC membership has nothing to do with technical mastery of the codebase, > which is why I cringe every time I see people talking about what "the bar" > should be. It's about trust. If you trust someone to work the gears on a > release, > that has considerable impact on the well-being of a project, and personally > meets my definition of "belongs on the PMC".
We have a new PMC member who hasn't done much (if any) work on the actual code base of Wicket, but runs an awesome twitter account [1] posting new projects and applications using our framework, posting job listings etc. We wanted him to continue to do so and acknowledged that he found sites and jobs we were not doing, so it was only logical to ask him to become a PMC member and our true social manager! We *trust* him to do good with the twitter account and wanted to give him the official seal of trust by inviting him to the PMC. If and when he finds time to contribute in other ways, we will be welcoming. Martijn [1] https://twitter.com/apache_wicket --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
