On Feb 24, 2005, at 9:43 AM, Pierre van Rooden wrote:
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.
Well if we start a project for this do the people who wish to handle this as a project put in the time to work on it ? Say 3 full days within the next 3 weeks ? I would be willing to put 3 of my days into this who else is willing ?
Also what worries me is that if we need more than 3 or 4 basic constraints people will keep putting their code somewhere else. I for one will _not_ follow 25 rules with demands that almost no current code even passes. People will more and more dump it on sourceforge and we and the users will have a harder time to find and use things.
The messages on the list the last 2 days will end up in 2 camp's one for open it up and one for a very closed and controlled way. This will not be fun fight and i am sure the screaming will start soon since i doubt we can come to a agreement.
Daniel.
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
