Rename app/code to app/modules

[colinmollenhour]

It seems that with all of the module components being moved into the app/code directories that the name "code" for this directory is far too specific and "modules" would be more appropriate.

[ArnaudLigny]

👍

[sshymko]

Internally it's already named Mage_Core_Model_Dir::MODULES.

[amenk]

👍

[andreasemer]

👍 :-)

[waynetheisinger]

👍

[sankalpshekhar]

👍

+1

[robouk]

👍

[RahulKachhadia]

👍

[kandy]

It maybe better to rename the "app/modules" in the "vendor"?

[tzyganu]

http://martinfowler.com/bliki/TwoHardThings.html

[fooman]

I support @kandy's suggestion - currently I do not see a reason to use the app/code/ location (except maybe historical reasons). If we could move all modules into the composer vendor directory (vendor/) this would be a consistent and permanent location for all modules without having to copy/symlink non-core extensions into the app/code directory when installing additional extensions.

[alankent]

There was a big proposed directory structure change that did not make it before dev beta - too big/risky. One of the challenges at present is all modules are located by looking for app/code///etc/module.xml (I think). So all modules need to be under the same directory. With the new config.php approach (the list of modules is created by setup script, not at runtime) one idea being played with was to include the path name of each module root directory in config.php as well. Then modules could be located in different places more easily without extra overhead per http request. (There would be more overhead when setup is run, but that does not matter so much.) That would make it easier to put modules under app/code (or better app/modules) as well as vendor/.

Oh, themes into a 'themes' directory instead of 'design' was another possible change.