The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)? Andreas
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
+1 on this... i would say a dedicated zope3-modules folder and a dedicated zope2-modules folder (well, i don't care what the names are either, but some toplevel containing folders). - Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com ServerZen Hosting -- http://www.serverzenhosting.net News About The Server -- http://www.serverzen.net
On Thursday 22 December 2005 14:26, Rocky Burt wrote:
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
+1 on this... i would say a dedicated zope3-modules folder and a dedicated zope2-modules folder (well, i don't care what the names are either, but some toplevel containing folders).
-1. We had this before and decided against it. Please discuss such important issues that concern Zope 3 on zope3-dev. Regards, Stephan -- Stephan Richter CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
-1 Let's keep the SVN repo structure as flat as possible. Note that I think a project's name should be the dotted name of the Python package (if one such package exists), so it should be Products.CompositePage/ Products.PluginRegistry/ Products.PluggableAuthService/ Products.Zelenium/ instead of CompositePage/ PluginRegistry/ PluggableAuthService/ Zelenium/ Why? Because it's a pattern we're following with other package projects already: zope.file zope.formlib ... zope.testing Also, what is "Zope-Products"? Seems like it's a bag for historical baggage. In that case it can go because that baggage is still in revision history on older release branches... Philipp
Philipp von Weitershausen wrote:
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
-1
Let's keep the SVN repo structure as flat as possible.
Note that I think a project's name should be the dotted name of the Python package (if one such package exists), so it should be
Products.CompositePage/ Products.PluginRegistry/ Products.PluggableAuthService/ Products.Zelenium/
instead of
CompositePage/ PluginRegistry/ PluggableAuthService/ Zelenium/
Why? Because it's a pattern we're following with other package projects already:
More importantly, imo, it reflects that actual name of the real subject of the project. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
On Dec 25, 2005, at 12:48 PM, Philipp von Weitershausen wrote:
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
-1
Let's keep the SVN repo structure as flat as possible.
Note that I think a project's name should be the dotted name of the Python package (if one such package exists), so it should be
Products.CompositePage/ Products.PluginRegistry/ Products.PluggableAuthService/ Products.Zelenium/
instead of
CompositePage/ PluginRegistry/ PluggableAuthService/ Zelenium/
+1 Zac
On Dec 27, 2005, at 9:57 AM, Zachery Bir wrote:
Let's keep the SVN repo structure as flat as possible.
Note that I think a project's name should be the dotted name of the Python package (if one such package exists), so it should be
Products.CompositePage/ Products.PluginRegistry/ Products.PluggableAuthService/ Products.Zelenium/
instead of
CompositePage/ PluginRegistry/ PluggableAuthService/ Zelenium/
+1
(er, that was to Philipp's idea, not Andreas') Zac
--On 25. Dezember 2005 18:48:22 +0100 Philipp von Weitershausen <philipp@weitershausen.de> wrote:
Andreas Jung wrote:
The top-level directory structure on svn.zope.org appears a bit messy to me. There we have the folders for the "large" projects CMF, Zope, Zope3 and lots modules that possibly don't belong there. Wouldn't it make sense to move them into a dedicated Zope3-modules folder (or choose another name)?
-1
I am fine if this is intended behaviour. As Stephan pointed out there has been a discussion on this issue but I was not aware of that discussion so I asked about it :-)
Also, what is "Zope-Products"? Seems like it's a bag for historical baggage. In that case it can go because that baggage is still in revision history on older release branches...
Yes, I will remove this again..it does not make sense Andreas
participants (6)
-
Andreas Jung -
Jim Fulton -
Philipp von Weitershausen -
Rocky Burt -
Stephan Richter -
Zachery Bir