Hi Dan, Matthew, and all rocket scientists. Ian is working on a change to ensure teams with Open and Delegated subscription policies cannot be project maintainers or security contacts. As developers, we describe these teams as "closed", but that is not ever defined for users. I came across this problem when I introduced the Delegated team subscription policy. We use "open" and "closed" to describe the control of team membership:
Restricted Moderated Delegated Open
Closed <------------------|-------------> Open
I bet most Lp developers will not know that closed refers to
subscription policy. Well, "subscription policy" is itself, misleading.
"Subscription" implies "notification" in Lp, which is definitely not the
case here.
Both the help file and the interface always says "Moderated or
Restricted" when referring two "closed" teams.
The person-picker uses this text for searching:
"Search for a restricted team, a moderated team, or a person"
I think we want to rename the field:
TeamSubscriptionPolicy => TeamMembershipPolicy
"team subscription policy" => "team membership policy"
I like the terms, "Restricted", "Moderated", and "Delegated". "Open" is
ambiguous since there are three other states. We want to convey that
that membership is unrestricted, permissive, unfettered. Maybe "closed"
is the problem. Maybe we mean gated, guarded, restrained or limited.
--
Curtis Hovey
http://launchpad.net/~sinzui
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
