> I'd also personally bump the docs to high so that > people can start > ramping up to get involved more closely with the doc > effort. >
> benr. Ben, We are trying to break down documentation into more discrete tasks that can be managed, tracked and achieved. So far, we've broken the project into four areas, based in large part on our perception of community need: * Open source man pages: universally, this seems to be the area of highest priority. * OpenSolaris documentation project: This refers to formulating and setting up the processes and framework for the development of open source documentation for OpenSolaris. This includes the decision-making around format for source, style guidelines, standards for technical review, the submission process, the posting process, versioning , archiving, issues of standards, licensing, ownership, tools recommendations. *Open Solaris Resource Portal: this is the development of a single-point portal for OpenSolaris resource documentation. This is a location that will aggregate the resources available for OpenSolaris, including articles, blogs, project materials, specs, developer guides, etc. These resources may or may not be open source. *Open source Solaris documentation: open source Solaris documentation for OpenSolaris Resource limitation forces us to set priorities. While open sourcing Solaris documentation is important, we sense that there is higher community interest in being able to contribute new documentation, independent of the documentation that currently supports Solaris. And the decisions to be made and processes and structures to put in place for the doc project are integral to the latter initiative. Sue Weber, Program Manager-Solaris Documentation Nevada, Express, Trusted and OpenSolaris (650) 786-5467 x85467 [EMAIL PROTECTED] This message posted from opensolaris.org _______________________________________________ opensolaris-code mailing list [email protected] https://opensolaris.org:444/mailman/listinfo/opensolaris-code
