There is no project to make. What should a project do?
Define standards. defined how dependencies will
be Handeld, define if a project may use the bugtracker , where
communication about the project is to be taken place and how vendors
can create distributions containing there code

This is fine as a project, but applies also to existing code, so I would think it is separate from the discusison whether we relax the requirements on what code should 'do' before we propose it for addition in the CVS.
I am fine with starting a project for this, but we do need a policy change before I want to fully discuss stuff like this, else we are doing it for naught.


We only vote on a rules change.
We also vote on accepting stuff we did not yet define

The vote specifically states that any addition has to be voted on sepearately.
So we are not voting to accept any code, we are voting on allowing new code to be proposed for addition without requiring that it is 'core' code that should be mainmtained by the community.


--
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

Reply via email to