I would like to take over the 'console' project namespace on Drupal.org

+1 from me! Last version of the theme is for D4.7.

https://drupal.org/project/console

I think it is safe to say that this namespace can be taken over.

Since there is no way to change the project's short name, 'taking over namespace' will mean complete deletion of the theme. I'd love to have a few more comments, +1s from site maintainers before I do it.

I think this really should be handled as an unsupported project process. i.e. post an issue in the queue, wait 2 weeks, etc. https://drupal.org/node/251466

Given that this request sat for months in the issue queue of console and that the project owner wasn't active in over six years I thought we were fine enough. However I've contacted the owner via mail. If there is no response within a week or so I think we can proceed here.

Sorry I didn't notice that the issue had started in the console queue. I do think given the fact that the repo will be deleted that an email to the maintainer is a good idea. In an ideal world, the theme code would be moved to a different project (console_theme? as a sandbox) just for historic purposes (e.g. someone like ken rickard decides to go back in the history to learn something).

That is a good point greggles. Should we make the creation of such a preservation sandbox a requirement for taking over once used namespaces? Or can we do this wihtout burdening the person overtaking the namespace?

Well, someone has to do it and that's either the person applying for the namespace or a "webmaster" or someone else. I think it makes most sense to make it the responsibility of the person applying for the namespace.

@jmolivas, please create a sandbox that contains the code from the current console project and a description that makes sense.

Might sound too idealistic but guess that the original creator of console project deserves to keep credit in the commits history. So guess that it makes sense to sync the current console project repository to the new sanbox. Also, no need to link the sandbox to the current console project, since it is going to change.
Does it makes sense?

Just noticed that it looks like @jmolivas has not permission to promote a sandbox to full project, so guess he needs to create a sandbox of his new console project, push the code from github there and make a full project application: https://drupal.org/node/add/project-issue/projectapplications

A link to the application should be pasted here.

I believe Jesus has done all the things:

• Posted an issue in the original queue
• Moved that issue here
• Left a "tell" in irc for the maintainer
• Used the Contact form
• Created a sandbox as request
• Maintained the original commit history

I'm going to assign him maintainer status on the theme.

Marking fixed.

I don't think the actions were actually taken to delete the current project and then let jmolivas create the new one which I think will be necesary to turn a theme into a module.

But I think #16 is right that last step is git vetted user status.

Also, commit history was not preserved, compare both:

https://drupal.org/node/99695/commits
https://drupal.org/node/2185069/commits

Thanks @jmolivas!

So the next step is to delete the current console **theme** project, so @jmolivas can create the new console **module** project.

I moved the issues and links associated with console to the sandbox and deleted the console theme so that jmolivas can create the module project.

Looks like this is now fixed. Thanks everyone for your help.