~launchpad-pqm/launchpad/devel

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
<html>
  <head>
    <title>Team subscription policy</title>
    <link rel="stylesheet" type="text/css"
          href="/+icing/yui/cssreset/reset.css" />
    <link rel="stylesheet" type="text/css"
          href="/+icing/yui/cssfonts/fonts.css" />
    <link rel="stylesheet" type="text/css"
          href="/+icing/yui/cssbase/base.css" />
  </head>
  <body>
    <h1>Team subscription policy</h1>

    <p>
      There are four kinds of policy that describe who can be a member and
      how new memberships are handled. The choice of policy reflects the need
      to build a community versus the need to control Launchpad assets.
    </p>

    <dl>
      <dt>Open</dt>
      <dd>
        Membership is open, no approval required, and subteams can be open or
        closed. Any user can be a member of the team and no approval is
        required. Subteams can be Open, Delegated, Moderated, or Restricted.
        Open is a good choice for encouraging a community of contributors.
        Open teams cannot have PPAs.
      </dd>

      <dt>Delegated</dt>
      <dd>
        Membership is open, requires approval, and subteams can be open or
        closed. Any user can be a member of the team via a subteam, but team
        administrators approve direct memberships. Subteams can be Open,
        Delegated, Moderated, or Restricted. Delegated is a good choice for
        managing a large community of contributors. Delegated teams cannot
        have PPAs.
      </dd>

      <dt>Moderated</dt>
      <dd>
        Membership is closed, requires approval, and subteams must be closed.
        Any user can propose a new member, but team administrators approve
        membership. Subteams must be Moderated or Restricted. Moderated is a
        good choice for teams that manage things that need to be secure, like
        projects, branches, or PPAs, but want to encourage users to help.
      </dd>

      <dt>Restricted</dt>
      <dd>
        Membership is closed, requires approval, and subteams must be closed.
        Only the team's administrators can invite a user to be a member.
        Subteams must be Moderated or Restricted. Restricted is a good choice
        for teams that manage things that need to be secure, like projects,
        branches, or PPAs.
      </dd>
    </dl>
  </body>
</html>