> main goal of the wiki as I understand it - should be to serve the > project and not the ooo end user. Certainly in the end, the project > serves the end user. But the project's requirements are rather > different from the end user's requirements. Therefore, any wiki content > which is valuable for the end user should be "outsourced" to a better > place. This could of course be a second wiki. But at least the two > should be clearly separated as long as they stay in the same wiki.
The Wiki is growing VERY fast. Both developers and end users are coming to the Wiki for information. The Documentation project has around 3000 pages alone on the Wiki aimed at both end user and developer. There is no reason we can't have both in the same Wiki... a free-for-all playground for development projects, and a more structured section for end users. What's really missing right now is the critical guidance for both parties. New developers don't have a clue where to start, and end users can get lost in the maze. The Main page is a good place for us to start with helping sort that out. Combine a simple and clear path for each group to follow and use Project landing pages to guide new users/developers through the project. C. -- Clayton Cornell [email protected] StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
