Integrating Project Wizard into Project Request Process

I've recently been working on getting FizzyPop ready to be included in our project request process (bug#19617).  I should be able to create a "simpler" frontend for Mozdev now that has a lot of the normal required fields (like project name, author, contributors, etc) already filled out.  The primary thing we need to figure out is where it best fits in our signup process.  The current process is typically:

  1. Submit project request
  2. Confirm email address
  3. Wait for admin approval

We'd like to get people working on their projects a little sooner and hopefully lead to more active projects.  I'm thinking we should offer the wizard as soon as you finish the project request so you can download a package to work on.  Another choice would be to submit this template project to their CVS as soon as the project is approved.  This would add delay before you could start working on the project, though.
What do others think?  Would it be better to give the user something to do immediately, or have a more functional CVS tree waiting for them when the project is approved?

Reply

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img>
  • You may quote other posts using [quote] tags.
  • Lines and paragraphs break automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".
  • You can use BBCode tags in the text. URLs will automatically be converted to links.

More information about formatting options