2023-06-28 Meeting notes
Date
Attendees
- Craig McNally
- Jeremy Huff
- Ingolf Kuss
- Maccabee Levine
- Zak Burke
- Florian Gleixner
- Marc Johnson
- Olamide Kolawole
- Tod Olson
- Jakub Skoczen
- VBar
- Jenn Colt
- Mark Veksler
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
1 min | Scribe | All | Jeremy Huff is next, followed by Maccabee Levine |
5-10 min | TCR Board Review | All |
TCR-27 Zak Burke Based on the criteria he feels that the module does not pass. These are minor things that could be remediated fairly easily. He has recently written up the report and will touch base with the development team and see what they want to do. Craig McNally Should this go into review? Marc Johnson We need to be consistent in how we handle this because in the past we have iterated with teams Maccabee Levine agrees with Maccabee Levine and feels that he and Zac should iterate with the team to resolve these minor issues. Also some of the comments pertained more for TC process improvements Craig McNally How can we change our approach to utilize the rejection mechanism as part of our iterative process |
5 min | Liaison Updates |
| |
5-10 min | Technical Council Sub Groups Updates | All | Controlling AWS: Maccabee Levine they have not met and will update Breaking Changes: Jeremy Huff The RCS will be ready for a vote next week TCR Improvements: Jeremy Huff The video is in progress and will be done this week Distributed vs Centralized Configuration Florian Gleixner created a doodle poll but needs to coordinate with members still Architectural ReviewJenn Colt Initial meetings are discussing topic priorities |
1 min | Decision Log | All | |
5 min | RFCs | All |
Today:
Jenn Colt no update on the cleanup processes Craig McNally please add cards to the retro board |
1 min | WOLFcon Planning |
Craig McNally Has heard that there are more sessions proposed then there are slots for presentations Tod Olson and Maccabee Levine confirmed this Mark Veksler How will decisions be made, which sessions will be accepted Tod Olson This has not been determined yet Marc Johnson Cautions against combining sessions, as the widening of scope may inhibit the ability of the session to come to a useful conclusion | |
5 min | Officially Supported Technologies | All | (New) Standing agenda item to review/discuss any requested or required changes to officially supported technology lists Craig McNally this happened this week in a Slack conversation between Marc Johnson and Julian Ladisch concerning the removal of Java 11 from the Officially Supported Technologies |
5 min | Upcoming Meetings |
| |
15-20 min | Debrief from last week's meeting in Chicago | Craig McNally There were four of us there from the TC, Craig McNally Tod Olson , Jakub Skoczen and Jeremy Huff . Craig McNally gives a summary of the events of the meeting:
Marc Johnson Why are we announcing this summary? Are we intended to discuss these things? Marc Johnson is really pleased that people are having these conversations. It is important to acknowledge that the private nature of the meeting presents challenges to topics like transparency. Jeremy Huff No new group was formed, it was an attempt to facilitate an efficient conversation between informed individuals Maccabee Levine Appreciates the fact that the summary was shared and echoed the need for transparency, and feels that WolfCon would be a great venue for these conversations Marc Johnson The TC is often put in a position to review proposals that have already been invested in significantly. He would encourage us to not delay in discussing these new technical proposals Craig McNally Would VBar be willing to go over the concepts during a Monday discussion session of the TC Jenn Colt Does the Architecture group need to be put on hold until after these things can be discussed? Jeremy Huff It would be good for the Architecture subgroup to be informed about these topics prior to the meeting, but this does not need to take a long time Marc Johnson Feels that the group should wait for the TC to get all the technical data concerning Application Descriptors Jenn Colt Are we rubber-stamping predetermined decisions? Jeremy Huff No, we should do a technical evaluation of any proposal put before council. Jenn Colt Is evaluating VBar 's proposal the scope of the Architecture group Jeremy Huff does not think so, only that the architecture group should be mindful of the proposal as potential development in FOLIO VBar This conversation is going to take some time Craig McNally asked VBar to share a link to the proposal | |
Topic Backlog | |||
Discuss during a Monday session | Officially Supported Technologies - Upkeep | All | Previous Notes:
|
Action Items
- VBar to provide link to previous document discussing Formalizing Applications for Folio: https://docs.google.com/document/d/1W1Pknn84cNd8esuv2BCzYXZunnZ66jNb9gQOhvSiQ78/edit?usp=sharing