Skip to content
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.

Latest commit

 

History

History
70 lines (50 loc) · 2.79 KB

CONTRIBUTING.rst

File metadata and controls

70 lines (50 loc) · 2.79 KB
Raw

If you would like to contribute to the CSV2IATI project, you can....

  • Send us feedback about your user experience. Contact details at: https://github.com/IATI
  • Report bugs
  • Request new features
  • Contribute code or documents to improve the application. See the list of specific tasks below.

How to report a bug or request a feature

If you are able to work with GitHub then please "Create an issue". The issue tracker for CSV2IATI is used to log issues for both this code and the CSV2IATI-backend code.

Before creating a new issue check to see if the issue already exists. If not then please do report it. If you have permissions to assign the issue to people and milestones then try to select suitable options.

If you are not comfortable working with GitHub, but would still like to contribute, then talk to us. Details at: https://github.com/IATI

How to contribute code and documents

How we use branches in this repository

  • master represents our main development branch
  • once a version of the software is released it is given it's own version_ branch. Those branches can be bug fixed if needed.
  • Other branches represent development work or bug fixes.

Submitting changes

  • Fork this repository (if you haven't previously)
  • Make sure you're working on top of an up to date copy of IATI's master branch
    • Create a branch named after the work you're doing (if you're targeting a specific issue, start the branch name with the issue number e.g. 42-feature-name)
  • Do your work
    • If your work addresses a specific issue, reference that issue in your commit message by starting the commit message with [#issue number] e.g. [#64]
  • Create a pull request

Specific Tasks:

Deployment

If you find any issues in deploying your own version of the code we'd love to hear about it and try to improve our deployment documentation.

User Interface

Can you improve the user interface? Can you make it look 'nicer'?

Documentation

We would welcome any improvements to how the code or the application is documented.

Statistics

Can you check that the generated statstics are telling us what we think they are telling us? Do you have other tests/statistics that we could be generating?

Unit Tests

Can you improve the unit testing to make deployment more robust?

Fix a Bitesize issue

We mark some of issues as 'Bitesize'. Generally these will help ease you into the code and help you find your way around.

Talk to us

We'd love to hear from you. Details at: https://github.com/IATI

For general guidance on contributing to IATI Code please see http://iatistandard.org/developer/contribute/