This is what I think the summary of the call yesterday for @akanter and others:
- PCC members have decided that our focus is on what functionally we are building, and not how it is built technology-wise. We will have to work closely with the technical advisory (decision?) committee in prioritizing work to ensure feasibility.
- PCC members agreed it is our job to be the connection to the on the ground implementations and service providers out there to bring all of the functional requests, needs, problems to the queue to be prioritized.
- PCC members agreed it is NOT our job to manage the process of how things get built or to find/assign resources to the work. That is the job of the operations team.
- PCC members agreed that as our first task, we will gather all of the information from all sources in the OpenMRS ecosystem to have a list of work to be prioritized. We will work on a process to lead the community in the prioritization. At the latest, we would like that to happen at the implementer’s meeting in Mozambique.
We have started a #product-change slack channel for communication between those who are participating day to day in this work.
PCC members from yesterday please feel free to correct that or add to it! @mseaton @wanyee @jennifer @mksd @dkayiwa @c.antwi
Notes: https://notes.openmrs.org/2019-10-09-Product-Change-Committee