# Contribution guidelines for LibreHealth

**URL:** <https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642>\
**Category:** Development\
**Tags:** toolkit, ehr, radiology, issue, pull-request\
**Created:** [September 28, 2018, 4:12am UTC](https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642 "2018-09-28T04:12:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![muarachmann](https://forums.librehealth.io/user_avatar/forums.librehealth.io/muarachmann/32/2291_2.png) [@muarachmann](https://forums.librehealth.io/u/muarachmann)\
**Post date:** [September 28, 2018, 4:12am UTC](https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642/1 "2018-09-28T04:12:43Z")

</div>

Hey all, I have been viewing/opening issues, making PRs for quite sometime now and its really mixed up. I saw something similar in another org and think we could adopt same. I think we should adopt a standard procedure for

- Submiting a PR e.g a valid name, what it fixes. and generally PR should fix a known issue(that is before making a PR, we must first create and issue)
- Creating issues: a valid name, what the issue is all about, steps to encounter the issue , issues for discussions , screenshot, whether or not you would like to work on the issue etc etc.

Some sort of template for both issues/pull request.

I would love to have your ideas/thoughts

---

<div class="post-metadata">

**Author:** ![r0bby](https://forums.librehealth.io/user_avatar/forums.librehealth.io/r0bby/32/1781_2.png) [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Post date:** [September 28, 2018, 8:08am UTC](https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642/3 "2018-09-28T08:08:55Z")

</div>

I merged your posts into one. See [this](https://help.github.com/articles/about-issue-and-pull-request-templates/) for EHR – which is what you contribute to the most, so GitHub issue/PR templates will work. Additionally, each project will likely want to set their own guidelines. That’s where these policies should happen.

We could probably leverage [gitmate](https://gitmate.io/) to ensure these requirements are met.

---

<div class="post-metadata">

**Author:** ![muarachmann](https://forums.librehealth.io/user_avatar/forums.librehealth.io/muarachmann/32/2291_2.png) [@muarachmann](https://forums.librehealth.io/u/muarachmann)\
**Post date:** [September 28, 2018, 4:04pm UTC](https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642/4 "2018-09-28T16:04:25Z")

</div>

@teryhill, @tony, @Trodrige , @judywawira, @downey here is a sample issue i made.

> <https://github.com/LibreHealthIO/lh-ehr/issues/1246>
>
> \*\*What issue is all about:\*\*
> The calender gets open when the medication field o…utcome - resolved is selected from the dropdown which is undesirable
> 
> \*\*Steps leading to issue:\*\*
> Select a patient \> Go to medication \> Add new \> Click on the dropdown for outcome \> select resolved
> 
> \*\*Screenshots\*\* 
> !\[screenshot from 2018-09-27 21-26-01\](https://user-images.githubusercontent.com/16350814/46172894-c0b5cb80-c272-11e8-952e-eec2ca59cc50.png)
> 
> \*\*Errors from log files or console if any\*\*
> None
> 
> \*\*Would you like to solve this issue\*\*
> No, any first time contributor can be assigned to this

---

<div class="post-metadata">

**Author:** ![r0bby](https://forums.librehealth.io/user_avatar/forums.librehealth.io/r0bby/32/1781_2.png) [@r0bby](https://forums.librehealth.io/u/r0bby)\
**Post date:** [September 28, 2018, 11:27pm UTC](https://forums.librehealth.io/t/contribution-guidelines-for-librehealth/2642/5 "2018-09-28T23:27:02Z")

</div>

I know I’ve tried to influence how projects were run in the past and it backfired…I think projects should be able to mandate how issues/PRs are submitted. Discuss this with the EHR folks 🙂

We can of course suggest things at the organization level…but ultimately I don’t think LH itself should mandate how things are reported unless we have a universal issue tracker, which we do not.