... | @@ -41,13 +41,14 @@ Redmine provides the following modules per Project |
... | @@ -41,13 +41,14 @@ Redmine provides the following modules per Project |
|
|
|
|
|
We recommend the following usage of the OHR project functionality:
|
|
We recommend the following usage of the OHR project functionality:
|
|
|
|
|
|
1. Use the **Wiki** for storing the information you want to conserve
|
|
1. Use the **Wiki** for storing all information you want to conserve
|
|
about your project, but for which you don't have specific documents;
|
|
about your project. As the wiki is the entry place for most people
|
|
meeting minutes, informal, high-level descriptions, objectives, etc.
|
|
into the project, so it's good have some standard sections: Project
|
|
Also, the wiki is the entry place for most people into the project,
|
|
description, an image, Specification, Project information, Contacts,
|
|
so it's good to have a quick intro and a status table in it. Here's
|
|
Status. Having the same look-and-feel for all projects helps the
|
|
an [example](https://www.ohwr.org/project/spec/wiki) (sample source
|
|
readers too.
|
|
code at attachment:spec\_wiki.txt).
|
|
Here's an [example](https://www.ohwr.org/project/spec/wiki) (sample
|
|
|
|
source code at attachment:spec\_wiki.txt).
|
|
For images on the wiki site we usually create a Document called
|
|
For images on the wiki site we usually create a Document called
|
|
'images'. From the wiki pages you can then point to the files that
|
|
'images'. From the wiki pages you can then point to the files that
|
|
you put there. So no images attached to the wiki page as that looks
|
|
you put there. So no images attached to the wiki page as that looks
|
... | @@ -88,7 +89,11 @@ We recommend the following usage of the OHR project functionality: |
... | @@ -88,7 +89,11 @@ We recommend the following usage of the OHR project functionality: |
|
For images on the wiki site we usually create a Document called
|
|
For images on the wiki site we usually create a Document called
|
|
'images'. From the wiki pages you can then point to the files that
|
|
'images'. From the wiki pages you can then point to the files that
|
|
you put there. So no images attached to the wiki page as that looks
|
|
you put there. So no images attached to the wiki page as that looks
|
|
a bit ugly at the bottom of a page.
|
|
a bit ugly at the bottom of a page.
|
|
|
|
Specific documents (in the form of pdf or .doc) such meeting
|
|
|
|
minutes, informal, high-level descriptions, objectives can also be
|
|
|
|
put as Documents. Make sure that via the wiki pages you are directed
|
|
|
|
to these Documents too, as most users will only see the wiki pages.
|
|
8. Similarly, use the **Files** section for "release" versions of
|
|
8. Similarly, use the **Files** section for "release" versions of
|
|
important files, such as binary installation programs, drivers,
|
|
important files, such as binary installation programs, drivers,
|
|
schematics, gerber files, firmware etc. Again, intermediate versions
|
|
schematics, gerber files, firmware etc. Again, intermediate versions
|
... | @@ -236,7 +241,7 @@ Please read its comments and configure it properly before using it. |
... | @@ -236,7 +241,7 @@ Please read its comments and configure it properly before using it. |
|
|
|
|
|
-----
|
|
-----
|
|
|
|
|
|
19 April 2016
|
|
4 August 2016
|
|
|
|
|
|
|
|
|
|
|
|
|
... | | ... | |