mirror of
https://github.com/LibreSign/libresign.git
synced 2025-12-18 05:20:45 +01:00
c12f80763cRemoved the content that already stay at documentation page docs.libresign.coop Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
47 lines
2.4 KiB
Markdown
47 lines
2.4 KiB
Markdown
<!--
|
|
- SPDX-FileCopyrightText: 2020-2024 LibreCode coop and contributors
|
|
- SPDX-License-Identifier: AGPL-3.0-or-later
|
|
-->
|
|
Contributing to LibreSign
|
|
=========================
|
|
|
|
Welcome
|
|
-------
|
|
|
|
We really appreciate everyone who would like to contribute to the LibreSign project!
|
|
There are many ways to contribute, including writing code, filing issues on GitHub,
|
|
helping people, assisting in triaging, reproducing, or fixing bugs that people have filed,
|
|
and enhancing our documentation. Also giving a star to the project is a really good way
|
|
to help and donate.
|
|
|
|
Before you get started, we encourage you to read our code of conduct, which describes our community norms:
|
|
|
|
1. [Our code of conduct](CODE_OF_CONDUCT.md), which explicitly stipulates that everyone must be gracious,
|
|
respectful, and professional. This also documents our conflict resolution policy and encourages people to ask questions.
|
|
|
|
Quality Assurance
|
|
-----------------
|
|
|
|
One of the most useful tasks, closely related to triage, is finding and filing bug reports.
|
|
Testing beta releases, looking for regressions, creating test cases, adding to our test suites,
|
|
and other work along these lines can significantly improve the quality of the product.
|
|
Creating tests that increase our test coverage and writing tests for issues others have filed are invaluable contributions to open source projects.
|
|
|
|
If this interests you, feel free to dive in and submit bug reports at any time!
|
|
|
|
> As a personal side note, this is exactly the kind of work that first got me into open
|
|
> source. I was a Quality Assurance volunteer on the Mozilla project, writing test cases for
|
|
> browsers, long before I wrote a line of code for any open source project. —Hixie
|
|
|
|
|
|
Developing for LibreSign
|
|
------------------------
|
|
|
|
**NOTE**: If the project does not have an issue for what you want to do, create an issue first.
|
|
|
|
If you would prefer to write code, you may wish to start with our list of good first issues for [LibreSign](https://github.com/LibreSign/libresign/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22).
|
|
See the respective sections below for further instructions.
|
|
|
|
### Front and backend development environment
|
|
|
|
More information [here](https://docs.libresign.coop/developer_manual/getting-started/development-environment/setup), at the [official documentation](https://docs.libresign.coop/developer_manual/getting-started/development-environment/setup)
|