Skip to content

Latest commit

 

History

History
53 lines (38 loc) · 1.97 KB

File metadata and controls

53 lines (38 loc) · 1.97 KB

Contributing

PyHAT depends on periodic and uncertain funding, often via grants. Therefore, community involvement is essential to PyHAT's long term support. Every little bit helps and credit will always be given. You can contribute by emailing the team with feedback, posting to our Issues page, or developing code.

Non-USGS code developers need to contact us, as is mentioned on the code.usgs.gov webpage,

A USGS employee must submit a form to request an external collaborator account on their collaborator's behalf. For additional details on this process, the USGS employee may contact GS Help Git by email,

which is: gs_help_git@usgs.gov.

Reporting bugs, providing feedback, and requesting features

Please see our Issues page and check to see that your concern is not already addressed by an existing Issue. If so, you add additional information.

When reporting new bugs, include:

  • Your operating system name and version
  • Relevant details about your local setup
  • Detailed steps to reproduce the bug
  • Associated error messages
  • Links to related input data files
  • Steps you took to troubleshoot
  • The severity of the issue
    • Is there a workaround? Does it completely impede your workflow?

When requesting new features...

  • Keep the scope as narrow as possible.
  • Explain in detail how the feature would work.
  • Articulate the broader relevance of the feature to the user base.
    • This helps us prioritize feature requests.

Write Documentation

Feel free to contribute to or make suggestions on our install instructions, doctrings, markup files, or the compiled documentation.

Get Started!

Once you have developer access on the repository, meet with the development team to become familiar with our git development workflow; it may evolve over time.