blob: 36cd5cb55b98dbd96ae61757aa8f253b396ddb10 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
---
title: Contributing
hide_title: true
sidebar_label: Contributing
---
# Contributing to OpenDC
First of all, thank you for wanting to contribute to OpenDC!
You can contribute in various meaningful ways:
* Report a bug through [GitHub issues](https://github.com/fabianishere/atlarge-research/issues).
* Propose new functionality for using this project.
* Contribute improvements to the code and documentation.
* Provide feedback about how we can improve the project.
* Help answer questions on our [Discussions](https://github.com/atlarge-research/discussions) page.
## Want to report a bug or suggest a feature?
Please file an issue! First, have a look if someone has already filed an issue addressing your concern. If there already
is such an issue, feel free to comment on the issue to show your support for it, or to add additional information that
might be helpful. You can also just react with a thumbs-up 👍 to the issue, to indicate that you'd be interested in its
resolution. This can help us prioritize what we spend our development time on.
If you can't find an issue that fits your problem or feature request, open a new one. Describe actual and expected
behavior, and be as detailed as you can. We'll get back to you asap!
## Want to contribute code?
That's great! If you want to contribute to this
repository, [fork it](https://github.com/atlarge-research/opendc/new/master) and submit a pull request here when you're
ready! Be sure to describe *what* you changed and *why* you changed it, to help us understand what your contribution is
about.
A quick note on commit messages: Please follow common Git standards when writing commit messages,
see [this post](https://cbea.ms/git-commit/) for details.
|
