Archive subscriptions URL should be "shareable"

Bug #522144 reported by Julian Edwards
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

The current URL schema for an archive subscription looks something like this:

https://launchpad.net/~$USER_NAME/+archivesubscriptions/$ARCHIVESUBSCRIPTIONID

where the number at the end is an internal archive ID. However this is not "shareable" between users because we can't do this:

https://launchpad.net/people/+me/+archivesubscriptions/2784

This is because the subscription that it refers to is actually a page for a token that may not exist yet, and it normally gets generated when a user first visits the page via a POST form.

Once fixed, we can take the following actions when someone visits the URL:
 * if I have access to the PPA and I have a token, I get to manage my subscription to it
 * If I have access but I don't have a token, it will activate the token
 * if I don't have access, I'm politely told that
 * if the PPA doesn't exist, I get told that nicely too!

We should also make the URL a bit more readable and use something like this:

https://launchpad.net/people/+me/+archivesubscriptions/~soyuz-team/ppa

instead of the ID string.

Tags: lp-soyuz p3a ppa
tags: added: p3a ppa
Changed in soyuz:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Julian Edwards (julian-edwards) wrote :

When the work is finished to present a list of installable binary packages on the user-facing PPA page, we can make that page available to subscribers and put the sources.list entry with the token right in that page.

description: updated
Revision history for this message
Mark Shuttleworth (sabdfl) wrote : Re: [Bug 522144] Re: Archive subscriptions URL should be "shareable"

Thanks Julian, that's a much better statement of the problem and success
criteria.

description: updated
Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

On 04/01/12 03:52, Robert Collins wrote:
> - https://edge.launchpad.net/people/+me/+archivesubscriptions/~soyuz-
> - team/ppa
> + https://launchpad.net/people/+me/+archivesubscriptions/~soyuz-team/ppa

Please drop the ~ from the team name, it's not needed if the only thing
that can refer to is a person ;-)

Mark

Revision history for this message
Robert Collins (lifeless) wrote :

On Wed, Jan 4, 2012 at 9:00 PM, Mark Shuttleworth
<email address hidden> wrote:
> On 04/01/12 03:52, Robert Collins wrote:
>> - https://edge.launchpad.net/people/+me/+archivesubscriptions/~soyuz-
>> - team/ppa
>> + https://launchpad.net/people/+me/+archivesubscriptions/~soyuz-team/ppa
>
> Please drop the ~ from the team name, it's not needed if the only thing
> that can refer to is a person ;-)

There has been talk of doing project PPAs, which would mean that there
is room for both persons and projects in that url space. I think it
would be considerably safer to use the same url component we use in
the main part of the web UI to refer to that object.

-Rob

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

On 04/01/12 08:25, Robert Collins wrote:
> On Wed, Jan 4, 2012 at 9:00 PM, Mark Shuttleworth
> <email address hidden> wrote:
>> On 04/01/12 03:52, Robert Collins wrote:
>>> - https://edge.launchpad.net/people/+me/+archivesubscriptions/~soyuz-
>>> - team/ppa
>>> + https://launchpad.net/people/+me/+archivesubscriptions/~soyuz-team/ppa
>> Please drop the ~ from the team name, it's not needed if the only thing
>> that can refer to is a person ;-)
> There has been talk of doing project PPAs, which would mean that there
> is room for both persons and projects in that url space. I think it
> would be considerably safer to use the same url component we use in
> the main part of the web UI to refer to that object.
>

I asked some time ago that project and person names be mutually
exclusive, is that not yet done? I know there are some historical
collisions, but I did ask, years ago, that they be exclusive going
forward so we could move to a single namespace. Please do that as a
dependency of this work. It's a trivial change on the new name
validation functions.

Mark

Revision history for this message
Robert Collins (lifeless) wrote :

I'm not sure if that is done or not. I don't think it is; yes it can
be done before this bug is addressed.

Revision history for this message
Robert Collins (lifeless) wrote :

bug 656272 is the one to take the first step in unifying the namespaces.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.