Drupal.org

Build a new front-end user experience for Project Applications

Currently, the 'new project application' process (which fronts the 'create full project' permission on d.o) is initiated by applicants creating a issue in the 'projectapplication' issue queue. There are a number of 'sanity' checks which are then manually performed by reviewers, which would be better if automated and addressed during the application process (and before an issue is created). These checks may include repository ...more »

Submitted by

Related *.drupal.org issue/discussion : http://drupal.org/node/1409778

Voting

12 votes

Drupal.org

Enforce Project shortname naming conventions

I would like to see (and maybe this isn't super important) that project shortnames follow a static convention. Although the suggestion is "project_name" where the underscore represents a space between words (in the full title), there are many modules which ignore it. There are even instances where module names don't quite match up to their purpose. This makes it easier to remember the shorturl for retrieving a module, ...more »

Submitted by (@wjaspers)

Related *.drupal.org issue/discussion : http://drupal.org/node/1513636

Voting

2 votes

Drupal.org

Integrate PAReview.ventral.org w/ official Drupal testing infra

The automated PAReview tool hosted at ventral.org provides automated 'code style review' reviews for new project applications submitted into the "Full Project Approval" process, and provides both Coder and Drupal CodeSniffer review results. While this tool has revolutionized the coding style portion of project application reviews, the next step is to migrate it onto 'official' Drupal infrastructure, and integrate it ...more »

Submitted by

Related *.drupal.org issue/discussion : http://groups.drupal.org/node/214443

Voting

6 votes