>Daniel Carrera wrote: > >> I asked for access but it was denied. I was told that they didn't like >> giving out website access. >> >> I totally understand that if you have a large number of contributors, but >> only a tiny group of committers, then nothing will get done. > >I've been watching this discussion from the side lines, but I hope >nobody will mind if I leap in. > >Why doesn't OOo implement a system like Debian does for its maintainers? >To have access to the Debian site, a person has to be vouched for by an >have their GPG key signed by at least one existing maintainer, find >someone to sponsor them, and serve an apprenticeship to show that they >know not only what they want to do for the project, but also that they >understand the philosophy. The system can be cumbersome, but it does >seem to create a large base of trustworthy people.
It's an interesting idea... Currently, OOo uses a modified version of the Apache structure, with project leads having a lot of autonomy. Each PL controls who is given access to the particular project. This can be modified, of course, but only by the Community Council. The method is: submit the item to [EMAIL PROTECTED] Or, as Daniel is a member of the Community Council, he can present it directly for consideration at the next meeting. Regards Louis > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
