Community priority tickets for the Platform team

Owned by Ken Omondi
Jul 26, 2021
1 min read

Background

Community priority tickets are those that have been identified as key to the community and OpenMRS as a platform. The tickets have been curated. They can be accessed from here Community Development Status


Strategy

The Platform team will work on the community priority tickets and will use the following strategy:

  • Identify and encourage developers to work on such tickets. Through slack and talk posts such as this
  • Review associated PRs


Problem

In the process of reviewing the PRs, the following issues have been observed:

  • A PR that has no action for the past 1 year. An automated bot will automatically close such. e.g. What should be done to the associated ticket? Should we still maintain it as a community priority ticket?
  • A PR whose assignee has not provided feedback for the past 3 months. At least 3 reminders have been sent and yet no response has been provided.
  • A PR whose reviewer has not provided feedback. At least 3 reminders have been sent, and no response has been provided.

Solution/ Ideas

How can the platform team deal with the issues covered by the above scenarios?