Skip to content

Commit 2eadbd5

Browse files
authored
Merge pull request #357 from NASA-IMPACT/contributing-file-new
Contributing file for dev
2 parents 5a74c9f + c0b0fa5 commit 2eadbd5

1 file changed

Lines changed: 56 additions & 0 deletions

File tree

contributing.md

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Contributing File
2+
3+
# Welcome to pyQuARC!
4+
This page is meant to help you learn how you can contribute to pyQuARC! We are passionate about NASA's Open Science initiative and are open to a variety of contributions. Read below to find ways that you can contribute to our project, either through reporting bugs, suggesting new features, or even directly editing the code yourself.
5+
6+
## How you can contribute to pyQuARC:
7+
8+
1. **Report a Bug:** for when you find something within the code that does not respond the way you expected/wanted it to.
9+
* To start you will need to proceed to the [**Issues** tab](https://github.com/NASA-IMPACT/pyQuARC/issues) within the pyQuARC Github page.
10+
* From here, look for the green button on the right side of the page labeled **New issue**.
11+
* Select **Bug Report** from the list that appears, so that you can create a report to help us improve an aspect of pyQuARC.
12+
* The page you are directed to will provide a prompt to add a title and explain how to fill in the bug you want to report.
13+
* If you change your mind about reporting a bug, there is a white button on the bottom right of the page labeled **Cancel** where you can either decide to keep editing or close and discard your issue.
14+
* Beneath the description box, select "Issue Type" and "Bug".
15+
* When you are finished describing the bug you wish to report, you can click the big green button at the bottom of the page labeled **Create**. This will make your Issue visible to all pyQuARC contributors, and pyQuARC developers will automatically be assigned to the Issue and notified.
16+
* You can see your new issue if you return to the **Issues** page of the pyQuARC GitHub and look for your title followed by the red __bug__ tag.
17+
18+
2. **Suggest a New Feature:** for when you think of something that could enhance pyQuARC for other users.
19+
* Suggesting a new feature is very similar to reporting a bug. You will start at the [**Issues** tab](https://github.com/NASA-IMPACT/pyQuARC/issues) within the pyQuARC Github page.
20+
* Select the green **New Issue** button found on the top right side of the page.
21+
* From the menu that appears, select **Feature Request** so that you can suggest an idea for our project.
22+
* The page you are directed to will provide a prompt to add a title and explain how to make a new suggestion.
23+
* If you change your mind about making a feature request, there is a white button on the bottom right of the page labeled **Cancel** where you can either decide to keep editing or close and discard your issue.
24+
* Beneath the description box, select "Issue Type" and "Feature".
25+
* When you are finished describing your suggestion, you can click the big green button at the bottom of the page labeled **Create**. This will make your Issue visible to all pyQuARC contributors.
26+
* You can see your new issue if you return to the **Issues** page of the pyQuARC GitHub and look for your title followed by the green __new check__ tag.
27+
28+
3. **Directly Contribute to PyQuARC Content:** for when you want to directly edit the code to add checks or new features.
29+
* Fork the repository
30+
* To edit the code, you will need to first create your own 'fork' of the repository. A fork is a new repository that shares code and visibility settings with the original repository and allows you to create your edits. Read more about Forks [here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo).
31+
* To create your fork of pyQuARC, return to the [**Code**](https://github.com/NASA-IMPACT/pyQuARC) tab of the pyQuARC GitHub.
32+
* On the top right of the page, select the **Fork** tab.
33+
* Under the "Owner" dropdown menu, select yourself as the owner of the new forked repository.
34+
* The fork name will default to 'pyQuARC'. If you wish to name your fork something different, edit the 'Repository Name' field.
35+
* You can set an optional description in the 'Description' field below.
36+
* Make sure the checkbox next to 'Copy the master branch only' is selected.
37+
* Click **Create fork** when you are finished to create your fork!
38+
* After completing the steps above, you should be on a new page titled the same as your new fork, with "forked from NASA-IMPACT/pyQuARC" beneath the title. You have successfully created a fork of pyQuARC!
39+
* Clone your fork locally
40+
* Now we will store the files locally on your computer so you will be able to edit the code. Click the green dropdown button labeled **<> Code**.
41+
* Under the **HTTPS** tab, copy the link to the repository.
42+
* Open a Python terminal in your preferred coding location.
43+
* Change your working directory to wherever you want your cloned pyQuARC repository to be stored.
44+
* Type '__git clone__' and then paste the URL you copied a few steps above.
45+
* Press **Enter** and your local clone of pyQuARC will be created! You can now explore all of the files on your local computer.
46+
* Create a new branch and make your desired changes.
47+
* Create a PR
48+
* Once your changes are made, push your commits.
49+
* You can then open a Pull Request (PR) on the [**Pull requests** tab](https://github.com/NASA-IMPACT/pyQuARC/pulls) within the pyQuARC Github page.
50+
* Set the base repository to "NASA-IMPACT/pyQuARC" and the base to "dev".
51+
* Fill out a title and description, then submit!
52+
* Feedback may be provided on your PR. Once it is approved, a pyQuARC team member will merge your changes.
53+
54+
## Thank you for your interest in pyQuARC!
55+
We appreciate your interest in pyQuARC! Everyone is encouraged to help improve pyQuARC, and we welcome your comments, suggestions, and new ideas!
56+
Please contact earthdata-support@nasa.gov with any questions.

0 commit comments

Comments
 (0)