Skip to content

Commit f5f4138

Browse files
committed
How to contribute
1 parent 8b79bdc commit f5f4138

File tree

1 file changed

+36
-1
lines changed

1 file changed

+36
-1
lines changed

CONTRIBUTING.md

Lines changed: 36 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,36 @@
1-
# How to Contribute
1+
# How to Contribute
2+
3+
How to Contribute to Our Collection of Research Software Quality Indicators
4+
5+
Thank you for your interest in contributing to our collection of research software quality indicators! Your contributions play a crucial role in improving the comprehensiveness and effectiveness of our project. Here's how you can get involved:
6+
Accessing the GitHub Repository:
7+
8+
Our project is hosted on GitHub. If you're viewing this guide on our website and would like to contribute, you can access the GitHub repository by following this link: [Link to GitHub Repository](https://github.com/inab/FAIRsoft_indicators)
9+
10+
1. Familiarize Yourself with the Project:
11+
12+
Before contributing, take some time to familiarize yourself with our project and its goals. Browse through the repository where the indicators specification "lives" to understand the existing indicators and their documentation.
13+
14+
2. Explore Existing Issues:
15+
16+
Check the repository's [issue tracker](https://github.com/inab/FAIRsoft_indicators/issues) for existing issues related to the indicators. These issues may include suggestions for new indicators, discussions about existing ones, or requests for clarification.
17+
18+
3. Submitting a New Issue:
19+
20+
If you have an idea for a new indicator or would like to suggest improvements to an existing one, you can submit a [new issue](https://github.com/inab/FAIRsoft_indicators/issues/new). Please provide as much detail as possible, including the rationale behind your suggestion and any relevant references.
21+
22+
4. Participate in Discussions:
23+
24+
Engage in [discussions](https://github.com/inab/FAIRsoft_indicators/discussions) on existing issues by sharing your thoughts, providing feedback, or offering solutions. Your input can help refine and clarify the indicators, ensuring they accurately reflect best practices in research software quality.
25+
26+
5. Proposing Changes:
27+
28+
If you're comfortable with Git and GitHub, you can fork the repository, make your proposed changes, and submit a pull request. Be sure to follow any guidelines or conventions outlined in the repository's contributing guidelines.
29+
30+
31+
6. Spread the Word:
32+
33+
Help us reach a broader audience by sharing our project with others who may be interested. Whether through social media, academic networks, or research communities, spreading awareness can attract more contributors and enrich our discussions.
34+
35+
36+
Thank you for being part of our community!

0 commit comments

Comments
 (0)