Line 42: |
Line 42: |
| | | |
| Core SME Server and community documents will be made available in plain text format. | | Core SME Server and community documents will be made available in plain text format. |
− | - SME Server Release Notes
| + | * SME Server Release Notes |
− | - SME Serve changelogs
| + | * SME Serve changelogs |
− | - SME Server User's Guide
| + | * SME Server User's Guide |
− | - Ruffdog's Contract with the Community
| + | * Ruffdog's Contract with the Community |
− | - This Constitution and ancillary documents
| + | * This Constitution and ancillary documents |
− | - Any general guidance, policies, procedures, volunteering, etc. documents as they are created
| + | * Any general guidance, policies, procedures, volunteering, etc. documents as they are created |
| | | |
| These documents will be made available in a location that can be reached without extensive gui navigation, such as an ftp repository (using the mirrors). | | These documents will be made available in a location that can be reached without extensive gui navigation, such as an ftp repository (using the mirrors). |
Line 54: |
Line 54: |
| | | |
| For distribution into the predominately gui-based computing environments worldwide, core documents will be available in .pdf format | | For distribution into the predominately gui-based computing environments worldwide, core documents will be available in .pdf format |
− | - SME Server User's Guide
| + | * SME Server User's Guide |
− | - The introductory web pages
| + | * The introductory web pages |
− | - Any SME Marketing specific documents
| + | * Any SME Marketing specific documents |
| | | |
| It is not necessary for these documents to be available before the release of a new version of SME Server | | It is not necessary for these documents to be available before the release of a new version of SME Server |
Line 63: |
Line 63: |
| | | |
| Within the guidelines stated above, A web site will be created and maintained by appropriate subteams. At a minimum the website: | | Within the guidelines stated above, A web site will be created and maintained by appropriate subteams. At a minimum the website: |
− | - will allow users to find and install contribs, and participate in their testing
| + | * will allow users to find and install contribs, and participate in their testing |
− | - will allow users to find and apply howtos and participate in their testing
| + | * will allow users to find and apply howtos and participate in their testing |
− | - will clearly separate contribs and howtos, wherever they are stored
| + | * will clearly separate contribs and howtos, wherever they are stored |
− | - Provide documentation for every contrib, even if it's only “rpm -Uvh ...”
| + | * Provide documentation for every contrib, even if it's only “rpm -Uvh ...” |
− | - Allow users to post content to the web site, whether through wiki or articles
| + | * Allow users to post content to the web site, whether through wiki or articles |
− | - Allow users to link to documentation hosted on external sites
| + | * Allow users to link to documentation hosted on external sites |
− | - Provide descriptions of how to participate in testing, documentation, dev, FAQs, website, etc.
| + | * Provide descriptions of how to participate in testing, documentation, dev, FAQs, website, etc. |
− | - Provide sufficient forums in General-purpose, defined subject matter, and global languages
| + | * Provide sufficient forums in General-purpose, defined subject matter, and global languages |
| | | |
| It is expected that the website will be built using a CMS portal that supports multiple domains and is maintainable by our Hosting Provider, such as Social MPN. | | It is expected that the website will be built using a CMS portal that supports multiple domains and is maintainable by our Hosting Provider, such as Social MPN. |