As good Drupal citizens, we should use the naming conventions described in http://drupal.org/coding-standards#naming

So I propose that we rename the modules like so:

  • storm -> pm
  • stormexpense -> pmexpense
  • storminvoice -> pminvoice
  • stormnote -> pmnote
  • stormorganization -> pmorganization
  • stormperson -> pmperson
  • stormproject -> pmproject
  • stormtask -> pmtask
  • stormteam -> pmteam
  • stormticket -> pmticket
  • stormtimetracking -> pmtimetracking

These name changes should then be carried through the files, functions, and themes of each module.

CommentFileSizeAuthor
#3 pm-storm-rename.patch1.83 MBjuliangb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

juliangb’s picture

Assigned: Unassigned » juliangb

I have a patch already in progress for this (as you can imagine, it is a big change as the names are everywhere).

Are you talking about any other refactoring (since this is just a renaming)?

n8j1s’s picture

Mostly renaming, but I think the renaming should be deep. Function names, table names, hook names, configuration variables, stylesheets, etc.

juliangb’s picture

Status: Active » Needs review
FileSize
1.83 MB

Here's a patch that should sort out the rename.

juliangb’s picture

Status: Needs review » Fixed

I'm aware that it's pretty hard to test such a big patch.

Tested myself, and committed. Hopefully it will be easier for others to test once committed.

Status: Fixed » Closed (fixed)

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

  • Commit 1fbe1b3 on 7.x-1.x, 7.x-2.x by juliangb:
    Issue #1915300 by juliangb | n8j1s: Refactor Code For PM Namespace.
    
  • Commit 6d28d8f on 7.x-1.x, 7.x-2.x by juliangb:
    Issue #1915300 by juliangb | n8j1s: Refactor Code For PM Namespace.
    
  • Commit 700f5a6 on 7.x-1.x, 7.x-2.x by juliangb:
    Issue #1915300 by juliangb | n8j1s: Refactor Code For PM Namespace.