Mozdev.org

Project Creation Documentation

Current manual steps:

-- I'm subscribed to the new-projects@mozdev.org list and each new project request comes in as a new email message. I copy the contents of each message into a text file and label each one as unconfirmed. I don't do anything else to a request until I get a response back from the person who submitted the request (note that going forward we'd like to automatically confirm any requests from existing owners).

-- If a project request is incomplete or not appropriate for mozdev, then I'll mail the person back. Often I'll ask for a more detailed description and will update the project's information when the person writes me back. Very many requests though are dropped after mailing the person back because they're not related to Mozilla. There's a set of canned responses on the admin project.

-- Once a project has been confirmed and is ready to be created, I create an email to send back to the new-projects list. I format the information for each project that needs to be created in the following way:

username email "Full Name" projectname "project description"

or for a project request from an existing owner:

existing owner: username
project name: projectname
description: description

There are plenty of examples of this in the new projects list archive. Look for a subject like: "3 new projects -- 2008/01/15".

-- After this email is sent off, I wait until Pete runs the script on his end. There are several steps that need to happen once the projects are created.

-- If a project requests Bugzilla, then I need to manually create a Bugzilla account for the person if they don't already have one. I also need to give this new account the correct Edit bugs privilege. A Bugzilla product needs to be manually created and the requested components need to be manually added.

-- If a project requests that other people be added as committers, then those accounts need to be manually created, manually added to the project and the people need to have their account information emailed to them. There's a canned message that I use that has blanks for the relevant information.

-- I might be missing something, but this is the bulk of it.

An automated system needs to take care of all of this. Ideally there'd be a page that tracks all open requests and their confirmed status. There should be options for approving projects or contacting the person with a set of responses or deleting requests. After a project is created, I shouldn't have to do anything other than browse the project site to make sure everything is set up correctly.