Skip to content

Commit ae87b1c

Browse files
authored
Merge pull request #257 from AR21SM/CONTRIBUTING.md
Improved Contributing.md
2 parents 62a2c0a + 60ab6ea commit ae87b1c

File tree

2 files changed

+98
-25
lines changed

2 files changed

+98
-25
lines changed

CONTRIBUTING.md

Lines changed: 97 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,111 @@
1-
# DISCOVER Handbook Contribution Guide
1+
# DISCOVER Cookbook Contribution Guide
22

3-
NumFOCUS invites the community to make suggestions for improvements to the DISCOVER Cookbook via [pull request (PR)](https://github.com/numfocus/DISCOVER-handbook).
3+
NumFOCUS invites the community to make suggestions for improvements to the DISCOVER Cookbook. This guide outlines how to effectively contribute to this project.
44

5-
# Contibuting
5+
## Table of Contents
66

7-
- [Ways to Contribute](#ways-to-contribute)
8-
- [Ideas, Questions, and Discussions](#ideas-questions-and-discussions)
9-
- [Problems or Issues](#problems-or-issues)
10-
- [Longer Initiatives](#longer-initatives)
11-
- [Content and Design](#content-and-design)
12-
- [Bug Fixes](#bug-fixes)
13-
- [See Also](#see-also)
7+
- [Code of Conduct](#code-of-conduct)
8+
- [Types of Contributions](#types-of-contributions)
9+
- [Ideas, Questions, and Discussions](#ideas-questions-and-discussions)
10+
- [Problems or Issues](#problems-or-issues)
11+
- [Content and Design](#content-and-design)
12+
- [Bug Fixes](#bug-fixes)
13+
- [Pull Request Guidelines](#pull-request-guidelines)
14+
- [Commit Messages](#commit-messages)
15+
- [Review Process](#review-process)
16+
- [Recognition](#recognition)
1417

15-
## Ways to contribute to this repository
18+
## Code of Conduct
1619

17-
The original body of work took place at a series of unconferences and various spurts of energy, today the DISCOVER-cookbook is a living project with numerous contributors. Because it is code to produce a book rather than code for a software library or application, it has different needs than typical open source software systems. Because of these unique needs, we separate various types of contributions:
20+
All contributions should conform to the [NumFOCUS Contributor Code of Conduct](https://numfocus.org/code-of-conduct).
1821

19-
All contributions should conform to the [NumFOCUS Contributor Code of Conduct](https://www.numfocus.org/about/code-of-conduct/).
22+
## Types of Contributions
2023

24+
The original body of work took place at a series of unconferences and various spurts of energy, today the DISCOVER-Cookbook is a living project with numerous contributors. Because it is code to produce a book rather than code for a software library or application, it has different needs than typical open source software systems. Because of these unique needs, we separate various types of contributions:
2125

22-
## Ideas, Questions, and Discussions
23-
Please contribute ideas, questions, and discussions for content or enhancements over in the discussions tab.
26+
### Ideas, Questions, and Discussions
2427

25-
## Problems or Issues
26-
Please add issues on the github issue tracker.
28+
- For content suggestions, feature ideas, or general discussions, please use the [Discussions tab](https://github.com/numfocus/DISCOVER-Cookbook/discussions).
29+
- Before submitting major content changes, we encourage starting a discussion to align with the project’s goals.
2730

28-
## Longer Initiatives
31+
### Problems or Issues
2932

30-
## Content and Design
31-
While content is the heart of the project, the quality of the content needs to remain high. Due to a high volume of generated text being submitted for review, content takes longer to review and approve. We value these contributions but just understand that it will take time to add. Please start an idea in the discussions, then move to making an issue once there is approval for the content to be added to the book. After that issue is made we feel free to open a pull request against the repository to begin the review process.
33+
- Submit issues on the [GitHub issue tracker](https://github.com/numfocus/DISCOVER-Cookbook/issues) with clear, detailed descriptions.
34+
- Include steps to reproduce (for bugs) or context (for enhancements).
35+
- Use appropriate labels/tags to categorize the issue.
36+
- Check if a similar issue already exists before creating a new one.
3237

33-
## Bug fixes
34-
For issues with other elements of the book, first make sure an [open an issue](https://github.com/numfocus/DISCOVER-handbook/issues) and tracking can occur on the issue. Then open a a pull request](https://github.com/numfocus/DISCOVER-Cookbook/pulls).
38+
### Content and Design
3539

36-
## See Also
40+
While content is the heart of the project, the quality of the content needs to remain high. Due to a high volume of generated text being submitted for review, content takes longer to review and approve. We value these contributions but understand that thorough review is necessary.
3741

38-
- [How to write a git commit](https://cbea.ms/git-commit/)
42+
- Start with an idea in [discussions](https://github.com/numfocus/DISCOVER-Cookbook/discussions).
43+
- Once the community approves, create an [issue](https://github.com/numfocus/DISCOVER-Cookbook/issues).
44+
- Only then submit a PR referencing the approved issue.
45+
46+
47+
### Bug Fixes
48+
49+
For technical issues with the book:
50+
51+
- **Check for existing issues** in our [issue tracker](https://github.com/numfocus/DISCOVER-Cookbook/issues).
52+
- **Create a new issue** if none exists, with clear reproduction steps.
53+
- **Reference the issue** in your pull request.
54+
- **Test your changes locally** following our [build instructions](README.md) before submitting.
55+
56+
## Pull Request Guidelines
57+
58+
When submitting pull requests:
59+
60+
- Reference related issues (`Fixes #123` or `Related to #123`).
61+
- Ensure you've built and tested the book locally.
62+
- Your PR description clearly explains the changes.
63+
- You are open to feedback and respond to review comments.
64+
65+
## Commit Messages
66+
67+
Write clear, concise, and descriptive commit messages following this format:
68+
69+
**Format:**
70+
```
71+
<Brief summary of changes (Aim for 50 characters max)>
72+
73+
<More detailed explanation if needed>
74+
75+
[Reference relevant issues, e.g., Fixes #123]
76+
```
77+
78+
**Examples:**
79+
```
80+
Fix typo in introduction section
81+
82+
Corrects a minor spelling mistake in the introduction
83+
of the documentation.
84+
85+
Fixes #42
86+
```
87+
**For more guidance, check out** [How to Write a Git Commit](https://cbea.ms/git-commit/).
88+
## Review Process
89+
90+
- **Technical fixes** generally receive faster review.
91+
- **Content additions** undergo more thorough review by subject matter experts.
92+
- **Revisions** may be requested before merging.
93+
- **Final approval** comes from designated maintainers.
94+
95+
## Recognition
96+
97+
This project follows the [all-contributors specification](https://allcontributors.org/). Contributors are recognized in the Contributors section of the [README.md](README.md) file with emoji indicating their contribution types:
98+
99+
- 📖 Documentation
100+
- 💻 Code
101+
- 🤔 Ideas, Planning & Feedback
102+
- 👀 Reviewed Pull Requests
103+
- 🚧 Maintenance
104+
- 💬 Answering Questions
105+
- 🖋 Content
106+
107+
We value all forms of contributions and are grateful for your help in making events more diverse and inclusive.
108+
109+
---
110+
111+
Thank you for contributing to the DISCOVER Cookbook! Your efforts help create more welcoming and inclusive spaces in the scientific computing community.

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ To contribute changes:
6767

6868
### For More Information
6969

70-
See the `contributing.md` for a detailed guide on how to contribute.
70+
See the [contributing.md](CONTRIBUTING.md) for a detailed guide on how to contribute.
7171

7272

7373
## How to run the book locally

0 commit comments

Comments
 (0)