I can see how this looked, but no, I wasn't granting anyone access by fiat, the granting of karma followed proper voting procedures. The thing we're working on is identifying sub-projects and determine which commiters will have access to each sub-project. The consensus was that until we actually have sub projects, we would continue as we did under Jakarta ... voted onto the team means access to all the code.
On 4/24/06, Justin Erenkrantz <[EMAIL PROTECTED]> wrote: > On 4/13/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > We've succesfully moved the SVN repository out from under the Jakarta > > project. Howard Lewis Ship has taken over responsibility for granting > > SVN access karma to Tapestry team members. > > I imagine that the intent is right, but this phrasing is a little off. > So, let me try to restate what should be going on here to ensure that > we're all on the same page here. > > The new Tapestry PMC as a whole has the responsiblity for granting > karma to new committers to Tapestry. Once a new committer is approved > by the PMC, the PMC Chair (in this case, Howard) is responsible for > executing that decision by twiddling the SVN karma or filing the right > request forms with [EMAIL PROTECTED] However, the PMC Chair shouldn't be > adding > or removing committers without consulting the rest of the PMC first. > > Other than that, looks fine to me. Keep up the good work! -- justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
