On 9/5/05, David Crossley <[EMAIL PROTECTED]> wrote: > Noel J. Bergman wrote: > > David Crossley wrote: > > > > > I suggest that we go further and make it a requirement > > > of graduation from the Incubator that the project > > > already has some people helping at infra@ > > > > That can only apply if there are ASF Members willing to do it, because we > > don't give apmail or root access to non-Members. And not everyone wants or > > feels competent to manage the tasks. > > > > What tasks did you have in mind? > > Anything. Even just answering other users queries. > That will relieve the other infra people to attend > to the new project's core needs. > > I want to instill at the beginning that we all > need to look after our own ASF - love your Infra. > If you want to participate in a project, then be > prepared to assist with the general infrastructure. > > Leave the rest of this account creation type stuff > to the main infra people ...
it's important that every project has committers who are familiar with the apache infrastructure. for example, release management requires knowledge of infrastructure policy which can (at the moment) only be gained by subscribing to the list. so IMO all release managers should subscribe and read the infrastructure list. podlings are going to need release managers. it's better for them to volunteer early so that they have time to (subscribe and) learn. therefore, i'd say that all podlings should have some committers who are subscribed to infrastructure. (hopefully, where they are there, they might find time to submit some documentation patches ;) it's also a question of culture. incubation needs to acclimatize projects to the way that the apache infrastructure team works. the best way to learn this is by subscribing to the infrastructure list. they need to know where to look for information and (if the information is missing) that the right attitude is to volunteer to patch the documents once someone answers the question. a few pmc'er with reasonable knowledge of the apache infrastructure and where to find information are vital in reducing the number of questions that need to be posted to infrastructure. IMHO some of the difficulties with infrastructure have been to do with the slowness of the flow of people from jakarta through to infrastructure. it should be a natural progress from pmc'er to release manager through to being active on the infrastructure list to helping out the infrastructure team. IMO this postive flow needs to be established early for new projects. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
