|
|
|
# Administrator guide
|
|
|
|
|
|
|
|
## Requesting a project
|
|
|
|
|
|
|
|
Please send an email to Javier.Serrano@cern.ch in order to ask for a
|
|
|
|
project to be created. You will need to specify:
|
|
|
|
|
|
|
|
1. A project name
|
|
|
|
2. Brief description of your project
|
|
|
|
3. Type of license
|
|
|
|
4. Initial team
|
|
|
|
5. Any special requirements
|
|
|
|
|
|
|
|
## OHWR features
|
|
|
|
|
|
|
|
Redmine provides the following modules per Project
|
|
|
|
|
|
|
|
1. Issue management & time tracking (via tickets)
|
|
|
|
2. News module
|
|
|
|
3. Documents module
|
|
|
|
4. Files module
|
|
|
|
5. Wikis (1 per project)
|
|
|
|
6. Forums (can create multiple forums per project)
|
|
|
|
7. Subversion repositories (1 per project)
|
|
|
|
8. Mailing lists (1 per project)
|
|
|
|
|
|
|
|
## Recommended seetup & usage
|
|
|
|
|
|
|
|
We recommend the following usage:
|
|
|
|
|
|
|
|
1. Use the issues tracker to create issues, tasks, milestones and
|
|
|
|
deadlines for your project, and assign it to your team members.
|
|
|
|
Think of issues as "tickets" they allow you to planify tasks and
|
|
|
|
future features, as well as to be used for bug tracking.
|
|
|
|
2. The mailing list is the preferred way of communication, but you can
|
|
|
|
also use forums.
|
|
|
|
3. Use subversion primarily as a source code repository, as well as for
|
|
|
|
storing intermediate versions of rapid-changing documents.
|
|
|
|
4. Use the Documents module for providing "release" versions of
|
|
|
|
Documents; Typically you would show versions 1.0, 2.0 and 3.0 on the
|
|
|
|
Documents section, and all the intermediate steps (1.1, 2.3.1, etc)
|
|
|
|
would be managed via the SVN.
|
|
|
|
5. Similarly, use the Files section for "release" versions of important
|
|
|
|
files, such as binary installation programs, firmware etc. Again,
|
|
|
|
intermediate versions of these should be managed via subversion.
|
|
|
|
6. Use the wiki for storing the information you want to conserve about
|
|
|
|
your project, but for which you don't have specific documents;
|
|
|
|
meeting minutes, informal, high-level descriptions, objectives, etc.
|
|
|
|
7. Use the News section for publishing important events, such as a new
|
|
|
|
exposition or review meeting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Files
|
|
|
|
* [spec_wiki.txt](/uploads/07c53b6284cd6ac2de5331d22f4b7464/spec_wiki.txt) |
|
|
|
\ No newline at end of file |