There are several ways to contribute to RISCOSS project

1. Give us your feedback
2. Testing
3. Documentation
4. Contribute Code
5. Contribute Models

Give us your feedback

Use the feedback option in the public deployment or send us a an email to [email protected]

Testing

Test new RISCOSS versions and report bugs opening issues in the corresponding GitHub repository. It is important to report bugs correctly giving the sufficient detail to reproduce them.

This repository defines a set of labels that are used to differentiate 3 kinds of issues:

1. "bug": bugs/malfunctions
2. "enhancement": new features or improvements
3. "question" or "help wanted": asking for assistance

It is recommended to use always one of these 3 labels to characterise the issue.

Besides these labels, this repository also include 2 in order to indicate that the issue is special:

1. "blocking": a critical issue, something to be handled as soon as possible.
2. "nicetohave": a low priority issue.

At some point, a (non-help for assistance) issue can be closed without include any modification in the code, in this case the issue will be labelled using:

1. "duplicate": there are more than one issue concerning the same fact. In this case, the person closing the issue will include the reference of the issue that is kept as a comment (e.g. #13).
2. "invalid" or "wontfix" if the issue is discarded. In this case, the person closing the issue will include the reason as a comment.

Documentation

If you think that something can be improved, open a issue in the corresponding GitHub repository.

If you consider that something is missing, you can also add new pages following the instructions from the corresponding repository. All the repositories contains a How to contribute tutorial.

#C ontribute Code In order to separate the contributions from the different developers groups (see RISCOSS Ecosystem above), there are several repositories in the GitHub where RISCOSS developers can contribute.

• Developers interested in the riscoss corporate version (except the Risk Analysis Engine) and the user interface, can contribute to RISCOSS/riscoss-corporate.
• Developers interested on analysis techniques (Risk Analysis Engine) can contribute to RISCOSS/riscoss-risk-analyser.
• Risk Data Collector developers can contribute adding new data collectors to RISCOSS/riscoss-data-collector.

All the repositories contain a How to contribute tutorial with specific instructions.

Contribute Models

Risk and goal modelers can contribute to the RISCOSS knowlegde base adding new risk and goal models to RISCOSS/riscoss-risk-modeling

riscoss-risk-modeling repository contains a How to contribute tutorial with specific instructions.