Drupal.org

Per-issue repositories

Allow individual issues to be turned into Git repositories, which allows everyone working on an issue to collaborate in one spot.

Submitted by

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

Voting

26 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

Derive project documentation and/or descriptions from git

We currently keep docs on d.o and in version control. Since docs are tied to code, I feel that the authoritative source should most naturally our git repositories. The suggestion would be to investigate how we can start deriving some degree of docs from files we commit to VCS, ideally written in a simple markup language like markdown. Obviously this would require other very significant efforts in regards to UI changes ...more »

Submitted by

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

Voting

6 votes