Last updated November 16, 2013.

After contributing a useful and working module or theme as a sandbox project, you may go through a one-time approval process to get permission to promote it (and future projects) to a full project.

As successful completion of the project application process results in the applicant being granted the "Create Full Projects" permission, there is no need to take multiple applications through the process.

The application review volunteers will analyze your code to ensure you are writing secure code, following the coding standards, generally following best practices, familiar with proper usage of the Drupal APIs, and promoting collaboration over competition (i.e., not duplicating functionality already available in other modules). For more details, read what to expect during a review.

Here is the process:

  1. Obtain basic Git access and Create a sandbox project for your code.
  2. Get your project into a state you feel is release-ready. Ideally, you would commit the project early and have a track record of several weeks/months of commits so that application reviewers can get an idea of your development and maintenance style.
  3. Have a look at the Project application checklist and try to resolve common issues.
  4. Once ready, create a new issue in the Project Applications queue [Note: Do NOT edit that page! Create a new issue.]
  5. Fill out the issue form:
    • Component: 'module', 'theme' or 'feature' (depending on the application)
    • Category: task
    • Status: needs review
    • Title:
      • [D?] Your project name
      • Use [D6], [D7] or [D8] to specify which Drupal version your project uses.
      • e.g. [D8] Unicorn Integration
    • Description:
      1. A detailed description of what your project does, including how it is different from other, similar projects, if applicable.
      2. For themes it's helpful to include a screenshot.
      3. A link to your project page.
      4. A direct link to your git repository (git clone ...).
      5. A list of links to reviews of other project applications that you did.

  6. Reviewers will then examine your code and provide feedback over the coming days/weeks (again see What to Expect). Please be patient, and make the changes requested of you.
  7. As the application process is fully volunteer driven, many of our most active reviewers use the review bonus program to prioritize which applications they review. This program gives priority to those who are also helping to review other applications. Participation is not mandatory, but it does provide a significant fast-track through the applications process. Due to limited resources, it could otherwise take a number of weeks between reviews of your own application. To participate in the Review Bonus program, review three other project applications and reference them in your own application. We are a community and we help each other, so we are counting on you!
  8. Once given the sign off, you will be granted permissions both to create full projects and to promote your sandbox projects to full projects.

    Once this comes into place there is no need to submit project applications for review as at this stage you are considered a trusted contributor. This makes it unnecessary for you to add to the project application queue but you should promote your projects to full projects when they are ready.

Comments

When filling out the issue form, the direct link to your git repository (git clone ...) mentioned in step 4 of part 6 above can be copied directly from an auto generated link on your Sandbox project 'Version Control' tab.

To generate the link, ensure that the Non-maintainer? checkbox in the 'Version to work from' dialog is checked. Next click the 'Show' button.

When the page has reloaded the panel immediately below titled, 'Setting up this repository locally for the first time' contains an http link.
'http://git.drupal.org/sandbox/..name../n..#######.git' for some ..name.. and value n..###.

This is the link you should use as the direct link in your issue form.

Ben Greenaway
- Drupaling TZO-DDNS, amongst others....

Also, in order to be notified when someone responds to your review request you will need to set the notification settings - this step is entirely missing from the guide above.

Once you have submitted your issue to the Project Application issues project, navigate to http://drupal.org/project/issues/projectapplications.
Click on the link to E-mail notifications.
On the page 'Manage e-mail notifications for Drupal.org Project applications issues' select the radial button to send e-mail for issue you follow and click 'Save'.

Check if you are automatically a follower of the issue you've created - idk, but then if you aren't you need to click 'Follow' on your issue page and then you will receive notification once someone had reviewed your module.

Thanks.

Ben Greenaway
- Drupaling TZO-DDNS, amongst others....

I have check email notification option please review again

A k Rawat

I keep getting this message when I set the Needs Review.

Git clone command for the sandbox is still missing in the issue summary,
please add it. Please follow https://drupal.org/node/1011698 [1] to fill out
your issue summary.

But I can't figure out where on that page the information to find the syntax for the Git clone command.

Can anyone help?

Fred