Sounds like this subgroup might be ready to wrap up. Allocating some extra time outside of the subgroup updates for them to present/shared deliverables, etc.
Radhakrishnan Gopalakrishnanadvised that he was meeting withMarc Johnsonon Friday to resolve outstanding questions and that this work should be ready for next week
Since September, the CC, PC and TC have canvassed many community members on “what are things that could be better about FOLIO?” This came out of discussions at WOLFcon in Hamburg about what the priorities were for advancing & investing the project. 20+ council members interviewed 60+ informants from the community, producinga list of 175 items.
Asynthesis of all the input can be found in this presentation. The last three slides contain some specific and actionable opportunities for the FOLIO councils to consider and adopt as priority items around which to organize community effort.
Previous Notes:
Review the presentation together?
Ask all members to review the more detailed list on their own?
Reviewed presentation, a lot of feedback on "run on a laptop" point
Seen as barrier to contributing
Better management of dependencies between modules might help
Today:
What are the next steps? How do we want to proceed?
*
Topic backlog
All
Review/introduce/triage unprioritized items, and if there's time start discussion items.
One open question from the ADR improvements subgroup is how we should communicate decisions out to relevant groups/members of community? We've discussed adding a stakeholders section to the ADR template, which will help, but we thought we might ask the TC if there are other ideas we should be considering... Creating (yet another) slack channel for this purpose? Post something to particular slack channels? etc.
20 min
WOLFcon Hot Topics
All
An overview was provided of the "hot topics" at WOLFcon. It seems clear that the TC ought to be involved in these discussions/efforts; what is the best way to participate?
What, if anything should we do with the Decision log in theTechnical Designs and Decisionswiki space? Is it worth consolidating those decisions with the TC's ADRs? Should we cross-reference? Clarify the scope of these decisions, and whether or not decisions should still be made/logged here?
See discussion in #tech-council for additional details.
Craig McNally Decision log left when Tech Leads group fell apart with new governance structure. Are decisions still made or logged in that space? Where does this lie in the backlog.
Maccabee Levine Motivations are to have a single list of decisions, to build developer-buy in and solve the longstanding issues with what decisions TC has authority to make. Also to know what we have to keep updated vs archive.
Craig McNally By consensus, added to the middle/bottom of the list.
Optimistic Locking interfering with batch update in inventory
The Data Migration subgroup of SysOps has been struggling with how optimistic locking has interfered with batch update in Inventory. They've asked me to bring it to TC to see if there's a way to push this forward. The current open ticket is MODINVSTOR-924 Batch update with optimistic locking disabled. (This was split off from MODINVSTOR-910.)
Topic has been addressed. Core team has agreed to implement as separate API that disables optimistic locking.
Primary task the Tc would take on by making FOLIO easier to get up and running. Would also reduce AWS costs so that the money coming from Membership groups can be flowed to other aspects of FOLIO. Tc is the best equipped group to decide on how to make installing and deploying Folio easier and cheaper.
Craig McNally - Brainstorming open ended session with Ian Walls and then discuss further before or after WOLFcon depending on the brainstorming session. Ian Walls and Tod Olson to frame the topics of discussion for the brainstorming.
Today:
Probably defer, but keep on the agenda so we don't lose track of this...
Ian Walls - should be best discussed in cross council meeting possibly at WOLFcon. Idea to was bring this up at a high community level not necessarily the Pc or TC. Doesn't need to be on TC agenda next week. Aspects to be discussed at WOLFcon.