# Helpful Guidelines for New Contributors:

**URL:** <https://talk.openelis-global.org/t/helpful-guidelines-for-new-contributors/1835>\
**Category:** Community\
**Tags:** gsoc2026\
**Created:** [January 10, 2026, 5:55pm UTC](https://talk.openelis-global.org/t/helpful-guidelines-for-new-contributors/1835 "2026-01-10T17:55:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Agaba\_Derrick\_Junior](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/agaba_derrick_junior/32/503_2.png) [@Agaba\_Derrick\_Junior](https://talk.openelis-global.org/u/Agaba_Derrick_Junior)\
**Post date:** [January 10, 2026, 5:55pm UTC](https://talk.openelis-global.org/t/helpful-guidelines-for-new-contributors/1835/1 "2026-01-10T17:55:26Z")

</div>

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

- Read our [Contributor Guidelines](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/239337475/About+OpenELIS+Global)
- Understand our workflow and issue labeling system
- Check existing issues before creating new ones

**2. 🔗 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. 🤝 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. 👥 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. 💡 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

### **💚 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

### **🚀 Ready to Contribute?**

- Browse [Good First Issues](https://github.com/DIGI-UW/OpenELIS-Global-2/pulls)
- Join our [community calls](https://talk.openelis-global.org/t/devdiscussion-break-happening-weekly-every-thursday-at-1700-gmt/242/180)
- Ask questions in [Discussions](https://talk.openelis-global.org/)

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

OpenELIS