You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/contributing/contribution_guidelines.rst
+5-21Lines changed: 5 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,17 +18,17 @@ Ways to Contribute
18
18
- Fix typos
19
19
- Improve documentation and testing
20
20
21
-
The best way to report a problem, request a feature, find out if others are working on a similar problem or application, or let us know you'd like to contribute some code is to find the *Issues* tab and check if your problem/suggestion has already been reported. If so, please provide any additional information in the ongoing discussion. Otherwise, feel free to create a new issue and submit your problem or suggestions.
21
+
The best way to report a problem, request a feature, find out if others are working on a similar problem or application, or let us know you'd like to contribute is to find the *Issues* tab and check if your problem/suggestion has already been reported. If so, please provide any additional information in the ongoing discussion. Otherwise, feel free to create a new issue and submit your problem or suggestions.
22
22
23
23
24
24
Requesting a Feature
25
25
--------------------
26
-
Find the *Issues* tab at the top of GitHub repository and click *New Issue* button. Please give your suggestion a clear title and let us know if this is something you'd like to work on and contribute.
26
+
Find the *Issues* tab at the top of GitHub repository and click the *New Issue* button. Please give your suggestion a clear title and let us know if this is something you'd like to work on and contribute.
27
27
28
28
29
29
Reporting a Bug
30
30
---------------
31
-
Find the *Issues* tab at the top of GitHub repository and click *New Issue* button. Give your issue a clear title and describe the steps required to recreate it in as much detail as possible. If you can, include a small example that reproduces the error. More information and minimal examples will help us resolve issues faster.
31
+
Find the *Issues* tab at the top of GitHub repository and click the *New Issue* button. Give your issue a clear title and describe the steps required to recreate it in as much detail as possible. If you can, include a small example that reproduces the error. More information and minimal examples will help us resolve issues faster.
32
32
33
33
34
34
Questions and Help
@@ -39,9 +39,8 @@ Please do not create issues to ask for help. A faster way to reach the community
39
39
Other Resources
40
40
^^^^^^^^^^^^^^^
41
41
- Check out our :ref:`ICESat-2 Open-Source Resources Guide<resource_ref_label>` for a host of tools and code for getting and working with ICESat-2 data
42
-
- The `2019 ICESat-2 Hackweek Tutorial repo <https://github.com/ICESAT-2HackWeek/ICESat2_hackweek_tutorials>`_ and [in progress] `2020 ICESat-2 Hackweek Tutorial repo <https://github.com/ICESAT-2HackWeek/2020_ICESat-2_Hackweek_Tutorials>`_ are great resources for learning basic Python and development skills, learning about ICESat-2 data, setting up a computational environment, and finding and analyzing ICESat-2 datasets.
43
42
- A great set of `interactive tutorials <https://learngitbranching.js.org>`_ for learning and practicing using git
44
-
- Let us know about the helpful tools you've found by posting on our discourse forum as indicated above (`Questions and Help`_)!
43
+
- Let us know about the helpful tools you've found (`Questions and Help`_)!
45
44
46
45
47
46
Adding Examples
@@ -74,22 +73,7 @@ General Guidelines
74
73
75
74
Basic Steps to Contribute
76
75
^^^^^^^^^^^^^^^^^^^^^^^^^
77
-
We encourage users to follow the `git pull request workflow <https://www.asmeurer.com/git-workflow/>`_. In a nutshell, the series of steps required to add new code is:
78
-
(first time only)
79
-
80
-
- Clone the repository
81
-
- Fork the repo to your personal GitHub account
82
-
- Add your fork as a remote
83
-
- Add yourself to `CONTRIBUTORS.rst` (see `Attribution for Contributions`_)
84
-
85
-
(each time you are going to make changes)
86
-
87
-
- Update the development branch
88
-
- Create a new branch
89
-
- Make your changes and commit them to the branch
90
-
- Push your changes to your fork
91
-
- Make a pull request (on GitHub; pull requests will automatically be made against the development branch)
92
-
- Push any additional, relevant changes to the same pull request (this will happen automatically if you push the changes to the same branch from which you made the pull request)
76
+
We encourage users to follow the `git pull request workflow <https://www.asmeurer.com/git-workflow/>`_. For more detailed steps, please see :ref:`How to Contribute<dev_guide_label>`.
0 commit comments