|State of QA for new releases||resulting from discussion at 2023-09-28 Product Council Agenda and Meeting Notes|
After a discussion about release management and timing, CSPs, etc, Khalilah Gambrell suggested that we have members of the EPAM team at an upcoming PC meeting to talk about the state of QA.
|Platform & Application Formalization Questions from the Technical Council||follow up from WOLFCon 2023|
|is this for re-architecting subgroup or PC in general? will start in subgroup.|
|Retrospective report on new CSP process||Oleksii Petrenko says this will happen in Nov or Dec after the Poppy release.|
Time zone inclusiveness
|Follow up from WOLFCon what can the PC do this year discussions. |
It seems we can find a time that works for US ET and Australia/China (7:00 PM Boston, 8:00 AM Beijing, 9:00 AM Canberra) , or Berlin with China/Australia (2:00 PM Beijing, 4:00 PM Canberra, 8:00 AM Berlin) but finding one that will work for all would be problematic. The best is probably 7 AM Boston, 7 PM Beijing, 9 PM Canberra, 1 PM Berlin. It would be even earlier/later for some of us and other regions may join if we can find a suitable time. Should be consider alternating times once or twice a month? https://www.timeanddate.com/worldclock/meetingtime.html?iso=20230928&p1=43&p2=33&p3=57&p4=37
|Entities Management followup. Will reach out to the MM-SIG||Feedback from MM SIG conveners regarding final report from the Entity Management Working Group|
2023-08-31 Metadata Management Meeting notes
|Should the MM SIG take over Entity Management work (or at least be the lead), should it be a new SIG, under another group, etc.? Then it was pointed out how much MM SIG already has responsibility for and that there are other groups like Acquisitions and ERM that would have a big stake in this as well. |
Waiting for co-convener Felix Hemme to return from vacation to start a larger conversation.
but PC notified and had an initial discussion on
|Flower release schedule - release dates and/or decreasing the number of annual releases, and how this fit in with the re-architectural decisions.||Follow up from later than expected Quesnalia release date, feedback currently being gathered|
|Establish criteria for newly developed apps and code contributions|
In coordination with Technical Council and Community Council, what is PC's criteria for accepting contributed code. What alternatives exist if a contribution is not accepted; what does it mean if something is not accepted. In the context of the LDP inclusion discussion, the PC identified the need for its own criteria for accepting apps into the reference environments. For instance, does an app meet the style guidelines? And later in the meeting, is there a support commitment from the developers?
FOLIO Scope Criteria Group formed, meeting starting in December 2021. Update in June.
|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||From 2021-09-30 Product Council Meeting notes||The Product Owners have created a Team vs module responsibility matrix. Harry is developing a simplified version on a single slide as well as a list of orphaned apps and modules. Having a list of orphaned areas is useful for when an organization joins FOLIO and wants to work on something. It is possible to have orphaned modules that don't in turn orphan an app (the single sign-on module is an example). There is another category of apps for which a team performs periodic maintenance but there is no active development (updating dependencies, for instance). An additional acceptance criteria for contributing code could be a memorandum-of-understanding to support the code for an explicit period of time. What is the maintenance commitment for code contributed by established partners?|
|Identifying priorities for development for FOLIO||From 2021-10-14 Product Council Meeting Notes||Anya Arnold, Martina Schildt, Tod Olson and Jana Freytag volunteered to work on a group to look at the issue of feature ranking.|
|Update on Data Sync Working Group||From Brooks Travis|
Ways to synchronize data across FOLIO apps. Group work started in August under App Interaction.
Originally wanted to present November 18, moving back to December 2, then to December 9
Will provide discuss on Feb. 10 SIG Conveners
|Release planning||From Martina Schildt||What is the release management planning/process. Talk to release manager regarding release process and where could improvements come in. This could be combined with report on BugFest. Invitation to Anton and|
|Support SIG Community Developer||from Anya Arnold||Need to recruit new developer|
|Need full support for GDPR||from Martina Schildt|
Have Privacy SIG report on GDPR needs and how that work can be slotted into FOLIO development - discussion postponed - check again on
|Need for additional Product Owners||from Jesse Koennecke||Jesse is discussing needs with Khalilah|
|Translation of documentation|
from Martina Schildt
|Managing upgrades so that implemented libraries to take advantage of new functionality||from Kristin Martin|
|FOLIO Technical Pain Points|
from Tod Olson
Part of the TC Goals & Objectives process has been to identify technical pain points within FOLIO that impede development and operations. We plan to look at underlying causes, come to agreement on some remedies, and use this to inform our priorities. Like any form of technical debt, these will require resources to address, but will pay dividends if addressed well.
See: FOLIO Technical Pain Points - DRAFT (in progress)
|UI Customization rather than Permissions||from 2022-05-12 Product Council Meeting notes||Start plan for when to do all of the planned Features for the customization of FOLIO. There are a bunch of things that we want to bring to FOLIO put together in a plan as a theme in the Roadmap.|