I'd like to rename an existing project (adsense_injector) to more accurately reflect current and future functionality. Is there a formal process and/or documentation describing how to do this?

I searched D.O. but couldn't find anything.

Thanks.

Comments

mcurry’s picture

mcurry commented

I would like to rename adsense_injector project's 'short project name' to content_injector since that's really what the module can and does do.

Please advise.

mcurry’s picture

mcurry commented
Title: Help change a project's 'short project name'? in Git (and D.O. projects directory). » Proper way to rename a project?
Project: Drupal.org infrastructure » Drupal.org site moderators
Component: Git » Project issues

I found #1060560: Help renaming a module, which recommends removing the old project files from CVS and creating a new project on D.O. -- Still not sure how to proceed.

Edit: I found out how to create a new project, but will await instructions on proper method.

mcurry’s picture

mcurry commented
Title: Proper way to rename a project? » Proper way to change a project's 'short project name'?
mcurry’s picture

mcurry commented
Title: Proper way to change a project's 'short project name'? » Help change a project's 'short project name'? in Git (and D.O. projects directory).
Project: Drupal.org site moderators » Drupal.org infrastructure
Component: Project issues » Git

Seems like this would require renaming the module in Git so.. reassigning to that project.

eliza411’s picture

eliza411 commented
Title: Proper way to rename a project? » Help change a project's 'short project name'? in Git (and D.O. projects directory).
Project: Drupal.org site moderators » Git on Drupal.org
Component: Project issues » Git
Assigned: Unassigned » sdboyer

I'm going to move this into the Git queue where I can get a recommendation from @sdboyer.

eliza411’s picture

eliza411 commented

I talked to sdboyer and killes about this in IRC today.

Here's my understanding:

As you've discovered, it's pretty much impossible to rename projects.

If you do follow the advice you found (to create a new project and mark the old one abandoned) for a module that's had a stable releases, everyone who's installed the stable releases will get the update warning and need to re-install the module to receive security update notices, devs who use the module on a regular basis won't know how to download it from memory any more, docs links and search engine links will be stale, and you'll need to update all your module function prefixes.

In your case, perhaps it is appropriate to deprecate the old module and make a new project given the change in functionality. There's nothing that will stop you from doing so, and it's your decision on whether it is worth the problems it will cause to users of your module, but it should not be undertaken lightly.

eliza411’s picture

eliza411 commented
Assigned: sdboyer » Unassigned

Unassigning

eliza411’s picture

eliza411 commented
Status: Active » Fixed

Marking this as fixed since question is answered (even if it's not an easy answer).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.