28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
|
## How to contribute to ckanext-harvest
|
||
|
|
|
||
|
|
#### **Did you find a bug?**
|
||
|
|
|
||
|
|
* **Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/ckan/ckanext-harvest/issues).
|
||
|
|
|
||
|
|
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/ckan/ckanext-harvest/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible.
|
||
|
|
|
||
|
|
#### **Did you write a patch that fixes a bug?**
|
||
|
|
|
||
|
|
* Open a new GitHub pull request with the patch.
|
||
|
|
|
||
|
|
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
|
||
|
|
|
||
|
|
* Make sure to update the CHANGELOG.rst in the "Unreleased" section with your bugfix
|
||
|
|
|
||
|
|
#### **Do you intend to add a new feature or change an existing one?**
|
||
|
|
|
||
|
|
* Open a new issue on Github and start writing code
|
||
|
|
|
||
|
|
* Make sure to update the CHANGELOG.rst in the "Unreleased" section with your change
|
||
|
|
|
||
|
|
* If you are unsure about the change, wait for feedback on the issue or post to the [ckan-dev mailinglist](https://lists.okfn.org/mailman/listinfo/ckan-dev)
|
||
|
|
|
||
|
|
#### **Do you have questions about the source code?**
|
||
|
|
|
||
|
|
* Ask any question about how to use ckanext-harvest on the [ckan-dev mailinglist](https://lists.okfn.org/mailman/listinfo/ckan-dev)
|