2022-11-09 Meeting notes
Date
Attendees
- Craig McNally
- Ankita Sen
- Jeremy Huff
- Maccabee Levine
- Jenn Colt
- Marc Johnson
- Mark Veksler
- Ingolf Kuss
- Florian Kreft
- Zak Burke
- Jakub Skoczen
- VBar
- Radhakrishnan Gopalakrishnan
- Raman Auramau
- Ian Walls
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
1 min | Scribe | All | Ankita Sen is next followed by Tod Olson |
- | TCR Board Review | All | No news. |
- | RFCs | All | No news. |
10-15 min | Technical Council Sub Groups Updates | All | Last week:
Today: Technical Council Goals/Objective Tod Olson - Subgroup had not met since sometime but burning issues, and both medium and long term goals and objectives on table. The sense of how TC would like to review or refine these kinds of prioritisation is missing. Craig McNally - Have put an agenda item today to discuss the finer things and next step. Translations Subgroup Zak Burke - No update this week, expecting updates after the bug fest. Documenting the conclusions are still on the table, check-in after 2 weeks. Controlling AWS hosting costs Mark Veksler - no updates for this week. Waiting for a demo from Kitfox team about cost explorers. Check in Breaking Changes Subgroup Ankita Sen - Finishing up the RFC with all the discussions and agreed on decisions in it. Yet to still discuss about communicating the changes. Planned absence of members from 15-29.11 so next check in first week of December. Improved TCR process Jeremy Huff - Kickoff meeting was done successfully and few points discussed, initial steps are taken to satisfy goals 1. and 2., already have volunteers and regular scheduled meeting set-up weekly on Thursdays. Tech Council Charter Revision Craig McNally - No kickoff yet. ADR process improvements Radhakrishnan Gopalakrishnan - met with Craig and kicked off. Craig McNally - A plan is in place and added extra week to finish timeline. |
10 min | Goals and Objectives | Last week: Sounds like this subgroup might be ready to wrap up soon. Allocating some extra time outside of the subgroup updates for them to present/shared deliverables, etc. See Technical Council Goals & Objectives - DRAFT Today: Refining the objective and goals and getting feedback from the rest of the community. How to proceed and what are the next steps? Agreed: Next step is to leave feedback about the Defined goals and objectives in the document's wiki comment section. Tod Olson - Made a few changes. How would the TC like to proceed? Would they like to give feedback to the Subgroup's work or want the subgroup to meet again? Inline comments as feedback source should be fine. Having some inputs about priorities in the feedbacks is requested. Craig McNally - Maybe a little bit of both should be done, feedback from the rest of the group and then refining a little more into which issues are more pressing than others. What the common goals are objective should be agreed on, insights from rest of the community needed. How to proceed? Jenn Colt - Are these Goals and Objectives for the Technical Council or for FOLIO? Marc Johnson - How are they different from each other? Jeremy Huff -Defining these will impact overall FOLIO processes. Also, which format shall the feedback on the working group's deliverables shall be provided with? Marc Johnson - The next step should be TC members giving the working group deliverable valid feedbacks. Feedbacks welcome on the wiki comment section. | |
5-10 min | Tools/Dependencies Versions | Previous:
Today:
Put on agenda next week. | |
10-15 min | Things FOLIO could do better | All | Today: What are the next steps? How do we proceed? Out of time Last week: From Tom Cramer in #tech-council:
Previous Notes:
|
* | Topic backlog | All | Review/introduce/triage unprioritized items, and if there's time start discussion items. |
Topic Backlog | |||
? | Communicating Decisions | Craig McNally / All | 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?
Notes: |
How can/should the TC weigh in on the architectural impact of new modules? | Introduce the topic
| ||
10 min | Consolidated Decision Log | All / Maccabee Levine | Today:
Last Week: What, if anything should we do with the Decision log in the Technical Designs and Decisions wiki 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.
|
Optimistic Locking interfering with batch update in inventory | Conversation started in slack:
Topic has been addressed. Core team has agreed to implement as separate API that disables optimistic locking. See also Bulk Operations redesign, different issue but seems related. | ||
Ease of Installing FOLIO | All / Ian Walls | From last week:
Today:
| |
Revisiting FOLIO Governance | All / Ian Walls | Slack discussion: Revisiting FOLIO Governance |