I can live with a packages module (in CVS) where different developer groups can create a working space (based on interests). Those interest groups may create there own rules and sub projects within the group (and keep out of the core and applications modules)
We have that. It is called speeltuin. Because I taste that you don't want any rules in that module except whatever people who check in their code makes up? If you want even more freedom that speeltuin grants, use source forge for all I care. We need to facilitate but we do need to apply some community rules.
I think adding another module with all kinds of stuff is going to just make another speeltuin filled with whatever people like to dump there.
If any of these code bits is useful in any way, nobody is going to find it.
We can ofcourse rename speeltuin to packages. I don't care about the name.
If you desire a packages module that follows the standard rules (as proposed in my vote) but explicitly for 3rd party stuff, then that may be possible, but I don't much see the point of yet another module besides the applications module.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Anything worth doing is worth overdoing." _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
