Difference between revisions of "User:Enus Linden/Project-Wiki-Structure"
Jump to navigation
Jump to search
Enus Linden (talk | contribs) |
Enus Linden (talk | contribs) |
||
| Line 57: | Line 57: | ||
:: [[Pyogp/Documentation/Examples]] | :: [[Pyogp/Documentation/Examples]] | ||
:: [[Pyogp/Documentation/Coding Guidelines]] | :: [[Pyogp/Documentation/Coding Guidelines]] | ||
:: [[Pyogp/In-World-Meetings]] | |||
== Edits for Pyogp Wiki == | == Edits for Pyogp Wiki == | ||
Revision as of 14:14, 23 July 2008
Proposal
The following is a proposal for a stucture for a generic project documentation set on wiki.secondlife.com. Specifically, Pyogp is in need of this like yesterday...
Here is a possible summary of pages and their contents:
Project - main page
- #Overview - 1 to 2 lines, basic description of the project goals and justification, links to related info. Ways to participate: repository location, irc, mailing lists, meeting info.
- #Status - 1 line version, pointers to jiras, link to Project/Roadmap
- #Documentation - outline containing links to supporting docs in the wiki, not the documentation itself. (e.g. Project/Specification)
- #Links - shortcut to Project/Links
- #Licensing - if needed
- Project/Background- more in depth info about the project, essentially a verbose version of the Project#Overview.
- Project/Roadmap - Status at the top. full version of Project#Roadmap, with all known tasks. If Milestones and dates are relevant, this is the right place to say so.
- Project/Links - A comprehensive list of links of all project related wiki pages, plus supporting external resources
- Project/Documentation - a summary page for supporting docs (or just an unnecessary level if not an actual page)
- Project/Documentation/Requirements - description of the requirements for the project, with pointers to external resources as needed
- Project/Documentation/Specification - high level component overview (usage examples as appropriate). Status of the component ought to be indicated, and synced with the Project/Roadmap page)
- Project/Documentation/Specification/Component1(-n) - component details
- Project/Documentation/Specification/Component1(-n)#Overview
- Project/Documentation/Specification/Component1(-n)#Details
- Project/Documentation/Specification/Component1(-n) - component details
- Project/Documentation/Examples - tutorials and the like on usage of Project
- Project/Documentation/{etc}
Example
Using Pyogp as an example, it could look something like this:
- Pyogp#Overview - intro, links to lib and test harness, links to AWG and OGP
- Pyogp#Status
- Pyogp#Documentation
- Pyogp#Links
- Pyogp#Licensing
- Pyogp/Background
- Pyogp/Roadmap - split by library and test harness
- Pyogp/Links
- Pyogp/Links#Project Wiki
- Pyogp/Links#OGP Docs
- Pyogp/Links#Other - (Tao's blog links, Legacy work, etc)
- Pyogp/Documentation
- Pyogp/Documentation/Requirements
- Pyogp/Documentation/Specification
- Pyogp/Documentation/Examples
- Pyogp/Documentation/Coding Guidelines
- Pyogp/In-World-Meetings
Edits for Pyogp Wiki
- reworked Pyogp
- created Pyogp/Background
- created Pyogp/In-World-Meetings