Incorrect. You DO need to use the webmaster queue. Somebody did this outside of the normal process. We also normally don't delete content from Drupal.org, instead preferring to unpublish it or assign it to Abandoned Modules so that somebody else can inherit it. -- Cameron Eagans http://cweagans.net On Tue, Apr 17, 2012 at 11:37, Joel Farris <joel@transparatech.com> wrote:

Oh, so we don't *need* to use the webmaster's issue queue after all. ;) -- Joel Farris Transparatech.com "There are no mysteries here."

On Apr 17, 2012, at 6:20 AM, Robin Monks wrote:

...

Hi James,

Both projects have now been removed: •

...

• Issue Screenshot? has been deleted. • Issue Kill project has been deleted. • Git repository enqueued for deletion. • Project Ariel has been deleted. • Git repository enqueued for deletion. • Project Caliban has been deleted.

• Thanks for releasing the names back; and best of luck with your projects in future. /Robin

-- Robin Monks Developer of spiffy things. http://robinmonks.com

...

On Tuesday, 17 April, 2012 at 10:17 AM, James Benstead wrote:

Thanks Robin - yes, please delete those projects.

...

On 17 April 2012 14:12, Robin Monks <devlinks@gmail.com> wrote: Hi James,

I just need a final confirmation you want these projects deleted, and I'll proceed with the deletion for you.

Thanks, /Robin

Yeah; I got a bit too helpful; apparently there is one care where there is a reason to the steps (namely preventing account spoofing). Although, I still don't see the argument in not deleted totally empty projects; which there are a decent amount of. If there's code, sure, save it. If it's empty, someone else can make a new project anyways so there's no loss. /Robin -- Robin Monks Developer of spiffy things. http://robinmonks.com On Tuesday, 17 April, 2012 at 3:18 PM, Greg Knaddison wrote:

Well...

http://drupal.org/node/1536822

Cheers, Greg

On Tue, Apr 17, 2012 at 1:37 PM, Joel Farris <joel@transparatech.com (mailto:joel@transparatech.com)> wrote:

...

Oh, so we don't *need* to use the webmaster's issue queue after all. ;) -- Joel Farris Transparatech.com (http://Transparatech.com) "There are no mysteries here."

On Apr 17, 2012, at 6:20 AM, Robin Monks wrote:

...

Hi James,

Both projects have now been removed: •

...

• Issue Screenshot? has been deleted. • Issue Kill project has been deleted. • Git repository enqueued for deletion. • Project Ariel has been deleted. • Git repository enqueued for deletion. • Project Caliban has been deleted.

• Thanks for releasing the names back; and best of luck with your projects in future. /Robin

-- Robin Monks Developer of spiffy things. http://robinmonks.com

...

On Tuesday, 17 April, 2012 at 10:17 AM, James Benstead wrote:

Thanks Robin - yes, please delete those projects.

...

On 17 April 2012 14:12, Robin Monks <devlinks@gmail.com (mailto:devlinks@gmail.com)> wrote: Hi James,

I just need a final confirmation you want these projects deleted, and I'll proceed with the deletion for you.

Thanks, /Robin

-- Director Security Services | +1-720-310-5623 Skype: greg.knaddison | http://twitter.com/greggles | http://acquia.com

Note: if the project in question is a sandbox project, you're free to delete it yourself if it's empty or obsolete, without any intervention from the webmasters or infra team. When you do this, the Git repo for the sandbox, and *all* related content (e.g. issues) will also be deleted. The hope is that you're not going to delete a sandbox project that still has a bunch of useful issues. In that case, the intention is that you're going to move those issues to a more appropriate queue first (e.g. back into the issue queue for the parent project). See https://drupal.org/node/1077884 for more. Cheers, -Derek (dww)