About

The documentation team is a group of individuals passionate about accurately and efficiently representing ideas and solutions in written format for consumption by anyone within or outside the OpenMRS community.  Our role as the documentation team Our purpose is to ensure all OpenMRS products (Wiki, Website, GitBook) are well-documented with concise, updated information by sharing and the OpenMRS community resources are structured in a way that is easy to understand and flows for ease of traceability and onboarding new community members.

Our purpose is to:

• Ensure the OpenMRS platform is well documented with accurate information.
• Share and implement the best documentation practices.

Active Projects

1. Team and Squad Project Pages

Current Status: VERY ACTIVE

Agenda and Notes

There is a Documentation Team Roadmap that outlines current and future tasks. To learn how to navigate this roadmap, click here. 

To find meeting notes, go under the Documentation Team Meeting Notes tab on the sidebar. 

OpenMRS Meeting and Connection Information

Excluding OpenMRS Holidays, the Documentation Team has bi-weekly meetings on Tuesdays at 2:00-2:30 PM UTC, or 10:00-10:30 AM EST.

You can find a full list of time conversions here.implementing the best documentation practices.

Active Projects

Team and Squad Project Pages

Current Status:

Status
colour Green title VERY ACTIVE

How does this project fit in with the strategy?

As a community-driven organization, it is essential that new and current members can access information on what each squad and team is working on. This led to the need to create wiki project pages that give an overview of ongoing projects. 

Our overall goal is to ensure that all community members are informed, up-to-date and aligned with the community happenings.

Current Project Pages:

• Quality Assurance Support Team
• OpenMRS Dictionary Manager Squad 

Getting Started Guides

Current Status:

Status
colour Yellow title ACTIVE

How does this project fit in with the strategy?

Getting started guides help new members understand how the community works, navigate through the extensive documentation, and identify their areas of expertise so they can contribute. 

How to Join

The Documentation Team is always welcoming new members in our efforts. Technical writers and communicators who can express complex information in a simple and understandable manner are  especially encouraged to join.

Interested individuals can attend our weekly meetings (excluding holidays) via UberConference on Thursdays at 10:30 pm IST | 8 pm Nairobi | 7 pm Cape Town | 5 pm UTC | 1 pm Boston | 10 am Seattle. New members can introduce themselves by stating their name, occupation, and how they would like to contribute improving OpenMRS' documentation.

For further information, please contact grace nakiguli

Useful Team Resources

Talk: https://talk.openmrs.org/ 

Documentation Team Slack Channel (#docs): https://app.slack.com/client/T03U4PGDY/C02BF27V85C 

Jira Board: https://issues.openmrs.org/projects/ONBOARDING/issues/ONBOARDING-7?filter=allopenissues 

Documentation Team Meeting Notes

OpenMRS GitHub: https://github.com/openmrs

Collaboration Opportunities Dashboard: https://wiki.openmrs.org/pages/viewpage.action?pageId=261718040 

OpenMRS YouTube: https://www.youtube.com/c/OpenMRSorg/videos

Meet the Team

Jennifer Antilla - @jenniferDirector of Community

Grace Potma - @grace Director of Product

Grace Nakiguli - @gracebish

Bret Studer - @bstuder99 Technical Writer

Kaylin Bracey - @kaylinbracey Technical Writer

Christine Gichuki - @christine QA Technical Project Manager

Hadijah Kyampeire - @hadijah315 Software Engineer

Daniel Kayiwa - @dkayiwa 

Edwin Jomo - @eddjomo 

Juliet Wamalwa - @jwnasambu 

Kakumirizi Daud - @kdaud 

Nelson Guya - @nelsonkimani63 

Herbert Yiga Mulindwa - @Herbert Yiga Mulindwa

Looking to Join?

...