This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
content:dev:techdoc [20/05/2014 19:24] Andrew Bettison [Format] "basic Markdown" -> "standard Markdown" |
content:dev:techdoc [21/05/2014 01:05] (current) Andrew Bettison [Where to find technical documents] remove link to Batphone LICENSE.md |
||
---|---|---|---|
Line 2: | Line 2: | ||
Technical documentation includes: | Technical documentation includes: | ||
- | * release notes | + | * protocol and API specifications |
- | * build, test and installation | + | * instructions for developers: |
- | * privacy and data retention policies | + | * documents accompanying specific versions: release notes, credits, |
- | * architectural | + | |
- | * API documentation | + | ==== Where to find technical documents ==== |
- | * names of contributors | + | |
+ | All technical documentation resides in [[git|Git]] source code repositories: | ||
+ | |||
+ | [[: | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | [[: | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | [[: | ||
+ | * [[https:// | ||
+ | * [[https:// | ||
==== Format ==== | ==== Format ==== | ||
Line 16: | Line 35: | ||
* Markdown has the benefit that it can be read as plain text, but can be made richer and more interactive by rendering it to [[http:// | * Markdown has the benefit that it can be read as plain text, but can be made richer and more interactive by rendering it to [[http:// | ||
* Both standard and GitHub Flavoured Markdown are supported by the [[http:// | * Both standard and GitHub Flavoured Markdown are supported by the [[http:// | ||
- | |||
==== Copyright and licensing ==== | ==== Copyright and licensing ==== | ||
Line 43: | Line 61: | ||
* [[http:// | * [[http:// | ||
- | ==== What belongs | + | ==== Why is technical documentation kept in Git repositories? |
- | All [[: | + | |
- | | + | * It **must be updated** as new software versions are produced, |
- | * it **must be updated** as new software versions are produced, | + | * **Prior versions** must be available, just like source code, |
- | * **prior versions** must be available, just like source code, | + | * It is produced and reviewed by the **same developers** who work on the source code, |
- | * it is produced and reviewed by the **same developers** who work on the source code, | + | * It is core Intellectual Property, and thus requires explicit **copyright assignment or licensing**, |
- | * it is core Intellectual Property, and thus requires explicit **copyright assignment or licensing**, | + | * Authorship |
- | * authorship | + | * GitHub [[https:// |
- | * GitHub [[https:// | + | |
- | Some good examples of technical documentation are: | + | ==== What belongs in the Developer Wiki? ==== |
- | * [[https:// | + | |
- | * [[https:// | + | |
- | * [[https:// | + | |
- | ==== What belongs in the Wiki ==== | + | The [[:|Serval Project |
- | + | ||
- | The [[wiki|Serval Project Wiki]] contains documents that are **not closely tied to specific software versions**, such as: | + | |
* orientation and introductory material | * orientation and introductory material | ||
* general Serval Project practices and policies | * general Serval Project practices and policies | ||
- | * general information for developers and contributors, | ||
* road map and other long-term planning material | * road map and other long-term planning material | ||
+ | * general information for developers and contributors, | ||
* lists of useful resources | * lists of useful resources | ||
+ | |||
+ | The Developer Wiki **MUST NOT** contain copies of technical documents whose definitive source is a Git repository, because such copies will not be maintained and will fall out of date, leading to confusion and poor community engagement. | ||
+ | |||
+ |