On Feb 25, 2005, at 9:57 AM, Kees Jongenburger wrote:
I can delay the end of the vote till thursday, after the meeting, so
people can discuss it as mcuh as they like. However if you cannot simply
make up your mind on the simple qyestion whether we should allow people
access to CVS (yes or no), then there is imo no point in continuing at all.
There is a need for the 3rd party stuff on mmbase (MMBOB is the best example i know). We for the next months will not succeed in making rules that everybody will accept, since people are trying to achieve different goals. As long as we don't agree I don't think it is a good idea to put code in the applications module. But 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)
Ill support these 2 ideas (a small delay and this name change) for the following reasons :
I also think its a small step and should not need alot of discussion, the fear is that we will again get into
endless discussion on how things should 'work' inside frameworks. I am a strong believer we need more rules
in the second (non core) layer but also strongly feel that it this will doesn't need to be one way or not at all (unlike the core
that is one way only). The name 'applications' is kind of confusing since it already gives the idea of a framework, this was also the
reason i changed the apps2 project to packaging (a neutral name just based on what it does : packaging).
There will be a need for summarizing what is in cvs (but also leocms). this should happen based on target groups (omroepen , governement, education , fun) . this is where more work is needed.
I also support the idea about subcommunities based in that i feel it will make it alot easer to create these frameworks (rules) this way. We have to except that
in the second layer we will not be able to find a way that makes sense for all users and all areas of interest. allowing people and groups with their own
rule systems inside a packages cvs is the way to go. Having the basic rules (along the lines pierre gave) will allow us to share code between groups or
create a commons for parts that are usefull for all communities.
This is something I can live with for the moment and would get my +1
I would have been happy (and did) to vote +1 on the current call but since there is still alot of thinking on this topic i would not mind making these 2 changes.
Daniel.
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
