Allow SPs to register an upstream project

For packages that use the new machine-readable copyright file format we should be able to use that to find the matching License in LP: http://dep.debian.net/deps/dep5/.

Perhaps we should have a look at exposing license information (even if it would just be the fulltext of the copyright file) for source packages anyway, at the moment it's not anywhere on the LP pages.

We landed API that exposes the information that was already in the DB. We are now (this week) in the position to add a link the register a project that prepopupates the form and shows the user the copyright file with the paths/URLs highlighted. Project registration could be a 3-click operation with no typing.

On Mon, 2010-07-26 at 16:08 +0000, Curtis Hovey wrote:
> We landed API that exposes the information that was already in the DB.
> We are now (this week) in the position to add a link the register a
> project that prepopupates the form and shows the user the copyright file
> with the paths/URLs highlighted. Project registration could be a 3-click
> operation with no typing.
Ah, nice - I hadn't seen that yet. Rock on!

A brief summary of the expected feature using https://edge.launchpad.net/ubuntu/maverick/+source/mountall as an example:

1. The Upstream connections portlet should have a radio button that allows the user to register the project
    Registered upstream project:
      ( ) diskmount
      ( ) Choose another upstream project
      (*) Register the upstream project

    [Link to Upstream Project]

2. If the user where tp have choosen "Choose another upstream project" (https://edge.launchpad.net/ubuntu/maverick/+source/mountall/+edit-packaging), he may discover that the project is not in launchpad. This page needs a link or action to register the project, may be:
    [Continue] or _Register the upstream project_ or _Cancel_

There was some discussion about putting the message in the project picker, but that means the user has to fail to no registration is an option.

3. The upstream project registration form:
The registration form should prefill the project information with the package information:
    name (project/launchpad id), displayname, summary

I think the form should use the projects/+new multi-step form. The form asks for the three pieces of information to perform a search to ensure there is no duplicate...so the user is really seeing step 2 because "Register the upstream project" submitted the step 1 using the package's information.

Step 2 asks for an optional description, requires a license, and ask if the user if he will maintain the project in Launchpad. There was discussion or using a different form (or setup) that forces the license to "I do not know" and sets the owner to registry admins (the last checkbox). The user can make this decision for himself though, and we want to encourage users to provide the information and take ownership of the project in Launchpad. I do not think we want to change the defaults for step 2 but...

We want to help the user select the real license. The source package page has a link to a view that shows the license and highlights the paths to the common licenses and url of the upstream home page. It would be great if the highlighted copyright could be shown to the user. It might be done with a formoverlay, or using something like an iframe that is scrolled. Most copyright files are easy to read, some are insane. The user is free to see the insane license information and choose the "I do not know" license.

Fixed in stable r11326 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11326>.