A constitution is a set of rules: do's and don'ts. Is that what you want? It is a regulatory mechanism to control behaviour. It sits between Law ands no Law at all. It is a formality commonly associated with corporations.
So far I don't see any reason for current behaviour to change. Your founding principles seem quite sound to me. Why the panic? Perhaps your current Strategic Plan could be a bit more flexible. But there are all sorts of sub-forums which can deal with superficial issues. I suggest a cool down period, and agreement to disagree on particulars only. But never a compromise on principle: they are either right or wrong. If a better principle emerges then drop the old one and take on the new. Otherwise let the opponents prove their point.
Earnie Boyd at MinGW-Msys is a good example of control by principle.
Regards and rosuccess Justin
---- Casper Hornstrup ch@csh-consult.dk wrote:
Just code, don't talk works fine...when you are a two people project.
ReactOS isn't a two people project anymore. We need a fair way to settle disagreements and we need a way to remember the decisions we make. Fair meaning that everyone has equal opportunity to influence the decision. We need a constitution.
Casper
-----Original Message----- From: ros-general-bounces@reactos.org [mailto:ros-general-bounces@reactos.org] On Behalf Of Tim Jobling Sent: 16. oktober 2005 22:55 To: ros-general@reactos.org Subject: Re: [ros-general] Wait a second...
I chime in even less than Richard, but I have to say I whole heartedly agree with his sentiment.
Perhaps we should take a lesson from the early history of this project and get back to letting the code talk for it's self.
Reactos started at with an "emphasis on results -- on written code rather than endless talk". Famous words, I'm sure we have all read 100 times, but now seems like a really good time to remind everyone of them.
Kind regards, Tim Jobling
ros-general mailing list ros-general@reactos.org http://www.reactos.org/mailman/listinfo/ros-general