Voting starts in March for the Drupal Association Board election.
Currently, drupal.org users are allowed to create an unlimited number of "sandbox" repositories to hold experimental modules, code forks, and not-yet-published modules waiting for approval.
Once created, a sandbox project cannot be deleted. This pollutes the project namespace, as it is not possible to register a project whose name conflicts with a sandbox.
In fact, the only practical difference between sandbox projects and full projects is that the latter are allowed to have release nodes, and appear in the main project issue drop-down. See Sandbox (experimental) projects.
For this reason, many developers have resorted to using (e.g.) github for initial or experimental code development. @todo: explain why this is bad.
Many users have requested the ability to delete drupal.org sandboxes that are no longer relevant or which were never intended to be promoted to full projects.
- Users should be able to delete their own sandbox projects, which would also delete any associated issues, comments, git repos, etc.
- A warning should be added to sandbox pages stating that any content posted there may be lost if the sandbox is deleted.
- Sandbox names should not conflict with full project names.
The necessary code changes needs to be discussed, tested, reviewed, approved, committed, and deployed.
User interface changes
An additional "Delete" button for user sandbox projects.
Original report by Snugug
I would like to see the ability to delete projects from our Git sandboxes. This currently does not exist, but would make a very good feature to avoid clutter in projects.
PASSED: [[SimpleTest]]: [MySQL] 253 pass(es). View