This just means that the IICM tries to avoid some chaos that could happen when a distributed developer community is launched. Dino V3 as the predecessor is provided to give you a feeling where it should go. The reason why we decided to launch the community in this early stage was to give everybody the chance to take part in the design too, rather than just extending an already existing system. And even this was not only the idea of the former Dino team - several developers who heard about Dinopolis wanted to take part in the development from the very beginning. The Dinopolis Software Development Philosophy Dinopolis software has to meet high quality standards.
All code written has to be well designed and well implemented.
Design and implementation both have to be well documented, otherwise there is a great danger of developing a monster due to the complexity of the goals that shall be achieved. Another reason for having to meet high quality standards can be found in projects that want to use Dinopolis for their purposes. One of the projects for example is a platform for distributed medical patient records. At the moment there are design-rules and coding standards existing that were mandatory for the members of the former Dino project. We know that we cannot force anybody to accept these standards and we are also aware that the standards are not complete.