Helpful Guidelines for New Contributors:

Community
1

1. :open_book: Start with the Wiki & Documentation
Before jumping into code, please take time to:

  • Read our Contributor Guidelines
  • Understand our workflow and issue labeling system
  • Check existing issues before creating new ones

2. :link: Always Link Issues to PRs
When submitting a pull request:

  • Mention the issue number you’re addressing (e.g., “Fixes #123”)
  • This helps maintainers track progress and avoids duplicate work
  • If no issue exists yet, create one first and discuss the approach

3. :handshake: Practice Collaborative Patience

  • Check if someone is already working on an issue before starting
  • Communicate in issue threads before coding to avoid duplicates
  • Be patient with reviews – our maintainers volunteer their time
  • Use the OpenELIS workflows - use OpenELIS Pull request Template

4. :busts_in_silhouette: Review Others’ Work Too
Great communities grow when everyone participates! Consider:

  • Reviewing other PRs (even with “LGTM” or thoughtful questions)
  • Testing proposed changes
  • Offering help to fellow contributors

5. :light_bulb: AI as Assistant, Not Replacement
We encourage using AI tools for:

  • Code explanations and learning
  • Debugging assistance
  • Documentation help

However, we value mentor-guided growth :

  • Submit work that reflects your understanding
  • Use AI as a learning aid, not a code generator
  • Be ready to explain and discuss your implementations

:green_heart: Why These Guidelines Matter:

  • Avoid duplicate effort so we focus energy on diverse problems
  • Maintain code quality through proper tracking and review
  • Build relationships through communication and mutual support
  • Grow your skills with hands-on, mentored experience

:rocket: Ready to Contribute?

We’re excited to have you here and look forward to building better healthcare systems together – one collaborative contribution at a time.

OpenELIS

2 Likes