Define documentation strategy
Registered by
brian.pedersen
Can we aim to have only an install guide, or do we need windows specific documentation ?
Blueprint information
- Status:
- Not started
- Approver:
- GNOME Do Windows Port Team
- Priority:
- High
- Drafter:
- GNOME Do Windows Port Team
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
03.07.2008 brian.pedersen>
Can we aim to have only an install guide, or do we need windows specific documentation ?
03.07.2008 Krisztian Gyuris>
Only install guide is ok, I think.
03.07.2008 Nick Parker>
As far as documentation goes, I am thinking that we can put some content up on a website (possibly using Launchpad again?) to benefit two distinct groups, end users and plugin developers. The documentation can start to be formalized a little later on, once things stabilize enough.
(?)
