Ubuntu Universe Contributors

[Emmet Hikory]

Stefan Potyra wrote:
> On Monday 21 April 2008 15:51:37 Soren Hansen wrote:
>  > On Mon, Apr 21, 2008 at 03:37:31PM +0200, Stefan Potyra wrote:
>  > >> The reason it's not named something like that is to maintain some
>  > >> sort of separation between the team name and the privileges that come
>  > >> with it. It's entirely possible that the members of the contributors
>  > >> team will be granted more privileges than simply being allowed to
>  > >> upload to REVU. When this happens, a team name like "revu-uploaders"
>  > >> will be confusing at best.
>  > >
>  > > erm..., you wouldn't want to have such a team as an open team then, or
>  > > am I missing s.th. again?
>  >
>  > Why not?
>
>  well, if you want to use this team to grant privileges, it seems
>  counterproductive to me, if anyone could just grab the privileges by joinging
>  the team. Or am I missing s.th. again?

    Consider the possibility that there exists a set of privileges
that are both normally open to all after self-election, would be
useful for those interested in becoming involved with development, and
can be controlled through a Launchpad group (either directly or
indirectly).  Having this set of privileges collected into a single
group allows would-be members of the development effort to gain all
appropriate access with a single membership, rather than having to
track down each specific permission group individually.

    Further, such a team allows for a single, accurate, label to
indicate those so interested, and further provides an answer to the
frequently asked question "What do I have to do to get involved in
development>", that being to join the team, and dig in.  This may be
perceived as an improvement over the current answer, to simply get
started, with new developers seeking additional permissions one-by-one
as they discover things they are unable to do without membership in
the several relevant permission-granting teams.

-- 
Emmet HIKORY