diff options
| author | mjkwiatkowski <mati.rewa@gmail.com> | 2026-02-10 08:14:41 +0100 |
|---|---|---|
| committer | mjkwiatkowski <mati.rewa@gmail.com> | 2026-02-10 08:14:41 +0100 |
| commit | 4d37bbed4a1f745c331ba996fc860d79e3e51e8f (patch) | |
| tree | 69d4e530f1f5a5192f98bb422d46618afb291c23 /CONTRIBUTING.md | |
| parent | 7a078fac132d10933e52edafd0f2527c50c9b1b6 (diff) | |
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index e9e025d1..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,31 +0,0 @@ -# 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. - |
