Skip to content

Latest commit

 

History

History
32 lines (22 loc) · 1.67 KB

CONTRIBUTING.md

File metadata and controls

32 lines (22 loc) · 1.67 KB

Introduction

First off, thank you for considering contributing to the FHIR Workflow Capability. It's people like you that make the FHIR Workflow Capability such a great tool. Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.

What kinds of contributions are we looking for.

All contributions that fit with the goal of the Workflow Capability are welcome. That includes documentation, bug triaging, and writing tutorials!

[source: Elasticsearch] Need more inspiration? [1] Devise [2] Geocoder (“known issues”)

Getting started

  1. Create your own branch in the code
  2. Do the changes in your branch
  3. If you like the change and think the project could use it:
    • Be sure you have followed the code style for the project.
    • Send a pull request describing the requested change.

How to report a bug

Explain security disclosures first!

If you find a security vulnerability, do NOT open an issue. Email [email protected] instead.

Tell your contributors how to file a bug report.

When filing an issue, make sure to answer these five questions:

  1. What version of Java are you using (java --version)?
  2. What operating system and processor architecture are you using?
  3. What did you do?
  4. What did you expect to see?
  5. What did you see instead?