2021-09-30 Product Council Meeting notes

LDP App - clarifying the current state of this as there is some confusion.  

There is still some confusion over the outcome of TC's evaluation of the LDP app -- most recently it (the confusion) was surfaced in the Scrum of Scrums today. So, I'd like to recap (because there is an old Russian saying, "repetition is the mother of learning")

1. The PC asked the TC to evaluate whether the LDP app is technically compliant for inclusion in the Kiwi release
2. Despite the lack of any identified urgency, the TC expedited the definition of inclusion criteria to accommodate this request -- a formalization of community established norms that have been in existence for ~2 years.
3. The LDP app was formally reviewed, but failed to meet all the established criteria (as is required)
4. However, the TC agreed to establish a one-time, limited set of acceptance criteria for provisional acceptance into Kiwi -- to be met by October 6
5. The TC will confirm that the LDP app has met the limited set of criteria and deadline for provisional inclusion into Kiwi
6. Provisional acceptance would only be for Kiwi, and the LDP app is expected to pass the full set of criteria to remain in Lotus
7. Although the TC decided to extend a deadline, it is not actually within the TC's authority to establish release-related milestones -- it is the Capacity Planning's team responsibility.
8. To avoid repeating this situation in the future, it is highly recommended that the Product Owner for the LDP app to join the product_owners channels and attend the regular PO meetings. This is a forum for all of the FOLIO POs to be on the same page wrt definition of done, acceptance criteria, and other product development/releases-related topic
9. Deployment of the LDP App into Kiwi bugfest hasn't been scheduled due to resource constraints, however it can still be included in Kiwi release and can still be tested in other environments (snapshot).
10. TC's and PC's decisions re: LDP inclusion in Kiwi have not been overruled.

Juniper upgrade slowness -  https://issues.folio.org/browse/MODINVSTOR-774 describes an issue that is causing Juniper upgrades to take a long time.  We want to make sure PC is aware of this and see if we can come up with any recommendations for next steps or actions

This item came from the last CC meeting: Action item: PC needs to keep a list of existing apps and their state of maintenance, their status of integration (tight or just loosely), developer team, responsibility, connected MoU's about maintenance . Can we assign this to a small group to get started.