Archive 'subscription' terminology is confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Medium
|
Michael Nelson |
Bug Description
Discussion on IRC:
<noodles> mpt: IMO, when we have the infrastructure that allows us to see quickly which people are using their private access (like a last_download db field that we can filter by etc.) then we could simply create the individual tokens when the team 'subscription' is created.
<noodles> mpt: but until that time, we want to be able to provide the owners of private archives with that information (ie. which users have activated their subscription), hence the current method.
<noodles> (which could be improved so that there's no confirmation etc.)
<mpt> noodles, that would be cool, if it would mean you could get rid of the button. :-)
<mpt> In the meantime, I suggest referring to "have access", "grant access" etc rather than "subscribe", and changing "Confirm" to "Show Me How" or similar that (a) generates the token if it's not generated yet and (b) reveals instructions on adding the PPA to sources.list.
Changed in soyuz: | |
assignee: | nobody → Michael Nelson (michael.nelson) |
milestone: | none → 2.2.7 |
Changed in soyuz: | |
status: | Triaged → In Progress |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
Possibly-incomplete list of places to change the wording: /launchpad. net/people/ +me/+archivesub scriptions
1. The form for a PPA owner to grant access (including <title> and form labels)
2. The message after submitting the form, "You have subscribed <person> to <ppa>"
3. The e-mail message sent out, "New PPA subscription for..." etc
4. https:/
5. The private PPA page itself, if it lists people who have access.