Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
src/core - for core src/lib - for internal libraries src/modules - for module
Feel free to propose other variants or express your opinion regarding the proposed options.
Cheers, Daniel
2013/5/7 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
among the topics discussed just before the last major release series (4.0.x) was one about restructuring the source code tree. It started mainly as a proposal to move source code belonging to core in a dedicated folder, but there could be more variants. It's time start discussing if we do it, and if yes, how.
Here is what I could collect so far.
a) no change, keep like it is
b) move source code of core in a dedicated folder named 'core'
c) move all source code in a folder named src, with following sub-structure
+1 for c.
-- With best regards, Peter Lemenkov.