... | ... | @@ -81,36 +81,17 @@ We recommend the following usage of the OHR project functionality: |
|
|
'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
|
|
|
a bit ugly at the bottom of a page.
|
|
|
Specific documents (in the form of pdf or .doc) such meeting
|
|
|
Specific documents (in the form of pdf or .doc) such as meeting
|
|
|
minutes, informal, high-level descriptions, objectives can also be
|
|
|
put as Documents. Make sure that via the wiki pages you are directed
|
|
|
put in a wiki page, for example called 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
|
|
|
important files, such as binary installation programs, drivers,
|
|
|
schematics, gerber files, firmware etc. Again, intermediate versions of
|
|
|
these should be managed via subversion.\] *not existing anymore since
|
|
|
move to OpenProject; please use a dedicated 'Document'*.
|
|
|
|
|
|
One alternative to the use of the Documents and Files modules is to have
|
|
|
a dedicated documentation wiki page with links to important files in the
|
|
|
SVN repository. This has the advantage of not duplicating files and the
|
|
|
disadvantage of a (potentially) less intuitive navigation experience for
|
|
|
the occasional visitor.
|
|
|
|
|
|
## Adding new users
|
|
|
|
|
|
New users should apply for an account with the
|
|
|
[Register](https://www.ohwr.org/account/register) link (top-right of the
|
|
|
screen). They will have to be approved by an administrator (Javier).
|
|
|
|
|
|
An administrator can register new users via the following link:
|
|
|
<https://www.ohwr.org/users/new>
|
|
|
|
|
|
If you are not an administrator and need to create lots of new users,
|
|
|
please [open a ticket](https://www.ohwr.org/work_packages/new) on
|
|
|
ohr-support. You will need to specify the user names and email addresses
|
|
|
there - an attached text file is recommended.
|
|
|
New users should apply for an account with one of the ohwr administrators.
|
|
|
There is no way to register yourself. Note that anyone, even without an account, can read all information. Registering does not give you access to more data.
|
|
|
|
|
|
Once approved, users can be given roles on a project via the project's
|
|
|
Settings / Members tab by a project manager.
|
... | ... | @@ -121,32 +102,29 @@ When a project manager adds a user, he has to set the *Role*. These are |
|
|
the current Roles in ohwr:
|
|
|
|
|
|
- **Administrator** - can do everything
|
|
|
- **Manager** (of a project) - can do everything, but only in a
|
|
|
certain project
|
|
|
- **Maintainer** (of a project) - can do everything, but only in a certain project
|
|
|
- **Developer** (of a project) - like manager, except: manage
|
|
|
documents, create forums, manage wiki pages and manage news.
|
|
|
- **Reporter** (of a project) - Only able to create new issues and
|
|
|
read-only rights on the rest.
|
|
|
- **Reporter** (of a project) - only able to create new issues and read-only rights on the rest.
|
|
|
- **Guest** - can read. Not used on ohwr.org as all projects are accessible for everyone without needing a login.
|
|
|
|
|
|
## Repositories
|
|
|
|
|
|
- [Policies about Repository
|
|
|
Use](https://www.ohwr.org/project/white-rabbit/wikis/Repository)
|
|
|
Use](https://www.ohwr.org/project/ohr-support/wikis/Repository-use)
|
|
|
gives ideas how large repositories with many contributors can be
|
|
|
handled.
|
|
|
|
|
|
### Git
|
|
|
|
|
|
If you have requested it, your project will include a *git* repository.
|
|
|
Actually Git is the most used repository type that is also more flexible
|
|
|
than SVN
|
|
|
See the [dedicated wiki page](Git-Repositories) for details.
|
|
|
A project will include a *git* repository.
|
|
|
Anyone wanting to commit changes to a project will have to be
|
|
|
authenticated as a developer or manager on that project.
|
|
|
Notably for older projects the page [Gitlab migration of ohwr faq](Gitlab-migration-of-OHWR-FAQ) may give you useful information.
|
|
|
|
|
|
## Forums
|
|
|
|
|
|
Each project has it's own forum. E.g., this OHR Support project has the [forum https://forums.ohwr.org/c/ohr-support](https://forums.ohwr.org/c/ohr-support).
|
|
|
Each project has it's own forum. For example, this OHR Support project has the [forum https://forums.ohwr.org/c/ohr-support](https://forums.ohwr.org/c/ohr-support).
|
|
|
|
|
|
# Other
|
|
|
|
... | ... | |