Wiki Team Launchpad permissions (was Re: Proposal: Create product for each derivative's documentation)

[Nathan Handler]

In my opinion, there are two main things that a user should need to
accomplish prior to being granted access to the bzr branch.

1) The user has interacted with many members of the team.

This is a very key point. We are not just individuals contributing
patches; we are a team working together to improve the documentation.
As a result, I strongly feel that interaction with the team should be
a strong requirement that people need to meet before being granted any
elevated privileges.

2) The user has demonstrated knowledge of the relevant skills and processes

If the user is going to be able to commit to the main bzr branch
without going through a sponsor, we want to ensure that they know what
they are doing. Otherwise, we will end up wasting time fixing their
mistakes. While evaluating whether or not to grant a user membership,
we should encourage all current team members who have sponsored a
patch for that user to provide feedback.

These two points are subjective. There is no set number of users you
need to interact with or certain number of error-free patches you need
to submit. This is the way that it should be. Take a look at any of
the other restricted Ubuntu teams (i.e. ubuntumembers,
ubuntu-bugcontrol, motu, etc.). If the user is doing a good job of
interacting with the team, then the team will be able to accurately
judge if the user is ready to gain access to the bzr branch.

Nathan