docs belong in wiki not app-mvhub/doc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MVHub |
Confirmed
|
Medium
|
Sam Antonaccio |
Bug Description
A merge request is too much overhead for updating the docs.
A lot of docs are notes or rough specifications which also aren't part of the project (yet)
Except for the READMEs , move docs to http://
Probably best to:
1) start with (1) merge request for each type of doc
checklist/ (howto ?)
specification
rough note
2) get feedback/approval on formatting / description for prototype
3) repeat 1-2 till done
4) do the rest of docs to spec developed above
ideally create a table of contents page something like:
<h1> Developer </h1>
<link> bzr worklflow </link> sequences of version control / launchpad commands, used every day
<link> adding a external library </link> How to be sure a library your new code depends on is included in project
Changed in mvhub: | |
assignee: | Roger Wieand (roger-wieand) → Sam Antonaccio (jacque-anton) |