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
We welcome contributions from the community to help improve GeodePy! Whether you're fixing bugs, adding new features, or enhancing documentation, your input is valuable. Open source projects live and die based on the support they recieve.
4
+
We welcome contributions from the community to help improve GeodePy! Whether you're fixing bugs,
5
+
adding new features, or enhancing documentation, your input is valuable. Open source projects
6
+
live and die based on the support they recieve.
5
7
6
8
This document outlines some of the guidlines and advice for contributing to GeodePy.
7
9
8
10
Code of Conduct
9
11
----------------
10
12
11
-
By participating in this project, you agree to abide by the `Python Software Foundation Code of Conduct <https://policies.python.org/python.org/code-of-conduct/>`_. Please read it to understand the expectations for behavior when contributing to this project.
13
+
By participating in this project, you agree to abide by the
14
+
`Python Software Foundation Code of Conduct <https://policies.python.org/python.org/code-of-conduct/>`_.
15
+
Please read it to understand the expectations for behavior when contributing to this project.
16
+
17
+
Coding Style Guide
18
+
------------------
19
+
20
+
GeodePy uses `Black <https://github.com/psf/black>`_ to keep coding style consistent while still being accessable to all.
21
+
Black uses `PEP 8 <https://peps.python.org/pep-0008/>`_ coding style, an industry standard for python code. Before
22
+
any commits to GeodePy ensure Black has been used.
23
+
24
+
.. _code:
25
+
26
+
Code Contributions
27
+
------------------
28
+
29
+
When contributing code please follow these steps:
30
+
31
+
1. Fork the repository on `GitHub <https://github.com/GeoscienceAustralia/GeodePy>`_.
32
+
2. Run tests on current code to ensure it works on your system (See :ref:`Testing <testing>`)
33
+
3. Create tests that demonstrate your bug or feature.
34
+
4. Make changes, ensuring coding sytle guide is abided by.
35
+
5. Run all tests again including one added and ensure all tests pass.
36
+
6. Send a Github Pull Request to the repository's **master** branch
37
+
38
+
Our project maintainers have the last word on if contributions are suitable or not. If your contribution is rejected dont despair!
39
+
Following the guidlines above will give you the best chance of getting accpeted.
40
+
41
+
Documentation Contributions
42
+
---------------------------
43
+
44
+
Documentation imporvements are always welcome! We understand that good documentation is important for all users of a package.
45
+
The documentation files can be found in the docs/ folder. They are written in `reStructedText <http://docutils.sourceforge.net/rst.html>`_,
46
+
and use `Sphinx <http://sphinx-doc.org/index.html>`_ to generate the documentation.
47
+
48
+
When contributing documentation please follow the style of current documentation, having a semi-formal yet friendly approach.
49
+
Ensure any code in documentation is well commeneted to ensure parameters are well understood.
50
+
51
+
Bug Reports
52
+
------------
53
+
54
+
We welcome all bug reports! Before you raise one though please check the `GitHub issues <https://github.com/GeoscienceAustralia/GeodePy/issues>`_,
55
+
both open and closed, to confirm the bug hastn been reported before. If you do submit a bug report ensure that the bug is clearly described,
56
+
giving the situation that caused the bug and some repeatable code for testing.
57
+
58
+
Feature Requests
59
+
----------------
60
+
61
+
If you believe a feature is missing, feel free to raise a feature request. Keep in mind that being an open source project requested features may
62
+
or may not be implemented. If there is a feature you really need consider creating it yourself and :ref:`submitting the code <code>`.
0 commit comments