Jörn Nettingsmeier wrote:
Andreas Hartmann wrote:
<module xmlns="http://apache.org/lenya/module/1.0";>
<id>org.apache.lenya.modules.jackrabbit</id>
<depends module="org.apache.lenya.modules.repository"/>
<depends module="org.apache.lenya.modules.jcr"/>
<package>org.apache.lenya.modules</package>
<version>0.1-dev</version>
<name>Jackrabbit Repository Module</name>
<lenya-version>@lenya.version@</lenya-version>
<description>Jackrabbit JCR Implementation (see
org.apache.lenya.modules.jcr Module)</description>
</module>
how about adding a maintainer field with a name and email address for
optional, user-contributed modules?
that way, lenya committers will know who to contact if a module gets
broken due to core changes, or is suffering from bit-rot.
Fine with me for non-core modules, if the field is optional since we
have code collective ownership.
it might even make sense for core modules. in theory, the maintenance
burden of those should be divided among the entire committer community,
but it's certainly nice to be able to find out who has the best insight
and the "grand architectural vision" concerning a particular module.
I see the danger that people rely on a particular person to fix a bug.
That's why I'm rather -1 for explicit code ownership.
-- 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]
