Hard to disclaim maintainership of a project you're registering

If we let people create projects initially owned by "registry", the user won't be able to set any more details about the project.

So we'd need to consider whether there are any actions outside of the "new project" form that a "nobody-in-particular" user would want to set, and then work out how permissions should be handled for that.

This relates to driver-by-project creation. I think this scenario though overlaps with barry's guided-project-registration.

The workflow for registering a project via the "Also affects" mechanism on a bug now sets the maintainer to be the registry team. This change went into affect within the last two cycles.

According to your comment, this is fixed. According to your status change, it is invalid. I have retested this on staging, and it seems to be neither. My steps:
1. Go to an Ubuntu bug report that is not marked as affecting upstream, e.g. <https://bugs.staging.launchpad.net/ubuntu/+source/ebox-network/+bug/411470>.
2. Choose "Also affects project".
3. Try to select a project that is not in Launchpad yet.

There is no interface element anywhere on the page suggesting that you can register a project. And entering an unregistered ID returns the error: "There is no project in Launchpad named 'eboxify'. Please search for it as it may be registered with a different name." Again, there is no indication that you can register the project.

And from the projects page:
1. Go to <https://staging.launchpad.net/projects/+new>.
2. Enter the initial details of the new project, and choose "Continue".
3. Choose "No, this is a new project" [sic].
4. Try to specify that you are not the maintainer of the project.

What happens: There is no interface element anywhere on the page for doing this.

We talked about adding about adding a button or checkbox to to this workflow for users to state they are not the maintainer. I suggested the "[x] I am not the owner". Barry and Martin did not like this because to complicated the form and the use is ambiguous.

Why is the user registering a project if he is not the owner? If it is to file a bug, he can do it from the bug page and he will not not the owner. The only other use case that we know of is registering a project to mirror code, and we want to add this feature.

Since we fixed the bug scenario, there are very few users giving up projects. So Barry and Martin's point may be correct.

I agree this bug cannot be closed until the code use case of covered. If there are other use cases, I think we should reconsider adding a checkbox (or an action button) that lets the user clearly state he is not the owner.

By "he can do it from the bug page" do you mean "he will be able to do it from the bug page in the future"? I don't see how to do it now.

Perhaps translations is another use case. A project's maintainers don't use Launchpad at all, but the Fooish and Barinese translators of that project both decide they want to use Launchpad for their translations. The Barinese translators get to Launchpad first, and ... what do they do?

Matthew,

The previous reference to being able to register a project from the bug page "Also affects" link is done by:
1) Selecting "Also affects".
2) Performing a search for a project that does not exist.
3) When the search fails there will be an option to "Register it" that will take you to
https://bugs.staging.launchpad.net/ubuntu/+source/ebox-network/+bug/411470/+affects-new-product
4) At the end of processing the registration through this form, the ownership of the project is set to the Registry Admins team and the license is set to "I don't know".

Matthew please replicate the steps at least as far as #3 and provide some feedback. I'm concerned you didn't see the 'Register it' link originally.

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