Jörn Nettingsmeier wrote:
hi andreas!
currently, we have the modules split into
* modules
* modules-core
* modules-legacy
* modules-optional
i would like to have an explicit definition of what that means, ideally
as a README in the src/ directory.
what were your intentions when you re-organized them?
I put the modules which I extracted from the core in the modules-core
directory. My idea of this "category" is that it contains a basic
set of modules which all other modules can rely on. Actually I'd like
to split up the core into modules entirely, this would be the purpose
of the "core modules". IMO it would be nice if a dependency to a core
module wouldn't have to be declared explicitly.
I used the modules-legacy directory for the 1.2 task stuff, which
is deprecated and will probably not be 100% functional anymore
(e.g. the scheduler).
i have a problem with the "modules" dir which contains the majority of
modules right now. apparently they are not "core" and they are not
"optional"... (my first thought was a module can be either one or the
other.)
+1
IMO we should move them either of these categories.
can you just dump your criteria into a README with lazy consensus on, so
that others can adhere to them when preparing patches?
Sure, as soon as we agreed on something reasonable :)
as to the module declarations, i have added some annotations to
bugzilla, please review.
Thanks, I'll take a look at it.
IIRC Michi coined the contents of the module descriptor, I guess
he can explain his intentions better than me :)
Thanks for your comments!
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
