Pierre van Rooden wrote:
According to teh rules we need a maven project, with assigned cvs
access, before code can be checked in.
I suggest you make a project proposal with goals etc (there is an
example docbook template in the documentation tree) so we can make this
an official project?
According to the guidelines my changes are a hack. And because they are
guidelines I didn't follow all the steps to commit my hack. I assumed
there would be a positive outcome on a majority vote for a maven build
system based on earlier communication (dev meeting and mailinglist).
Projects are for finding other like-minded people and defining the scope
of what is required. I think the requirements are clear for a long time
and the poeple, who wanted it, were working on it in the speeltuin.
The only thing that is mising is documentation.
Nico
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
