...
Attendees
- Jeremy Huff
- Ian Walls
- Maccabee Levine
- Jenn Colt
- Zak Burke
- Raman Auramau
- Jakub Skoczen
- VBar
- Ingolf Kuss
Discussion items
| Time | Item | Who | Notes | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 min | Scribe | All | Jeremy Huff is next, followed by Marc Johnson | ||||||||||||||||||||
| 10 min | TCR Board Review | All |
| ||||||||||||||||||||
| 5-10 min | Liaison Updates |
| |||||||||||||||||||||
| 15 min | Technical Council Sub Groups Updates | All | Topics to discuss:
Today: Controlling AWS Hosting Costs: Maccabee Levine this work is 90% done. The only remaining work to be done is a communication piece which is scheduled to be done next month. Maccabee Levine will bring an update at the close of September. Distributed vs. Centralized Configuration: No subgroup members were in attendance. Architecture Review: Jenn Colt Unsure how to proceed given the application formalization discussion and potential groups to explore this topic which were suggested at WolfCon. Jeremy Huff believes that there is both a governance aspect to the architectural changes proposed by VBar and technical aspects. He feels that this subgroup could focus on the technical aspects, and any new subgroup might be scoped to the governmental implications. Maccabee Levine agreed with Jeremy Jenn Colt We need to agree upon the purpose of the Architecture Review group Jeremy Huff Agreed with Jen that the purpose of the group needed to be defined more clearly Owen Stephens We were under some pressure at the Tri-Council meeting to have an actionable response to the proposed architectural changes. It is more important that the work is done in the timeframe which we committed to, than that a particular group of people does the work. We can be flexible about who does the work. This group most likely needs to be broken down into specific areas of focus. Jakub Skoczen agreed that we give this group a more focused goal and that we may possibly need multiple focused groups. Jenn Colt There will be RFC on these topics, and maybe this group can contend with those. Jeremy Huff Agreed with this thought. What if the first deliverable for this subgroup was a recommendation for the specific goals of the group moving forward and other possible groups that may be formed to address the architecture topic? Jenn Colt felt that could work, and suggested contacting Craig McNally for clarity on future RFC. Breaking Changes: No volunteers were forthcoming. Jeremy Huff described the needs of the group, and that the main focus of the next phase was to determine how breaking changes should be communicated in the FOLIO community. Zak Burke volunteered as a group member. Jeremy Huff suggested that we may need to assign people to the task of organizing the group. Zak Burke expressed a willingness to help in producing training and communication of the results of the subgroup, upon its conclusion. Jeremy Huff brought up a question of order: Can the TC create subgroups without a quorum? Maccabee Levinesuggested that the subgroups should be created and that the TC could decide later if they should be removed. Translation Sub Group: Jeremy Huff given the discussions at wolfcon, it seems possible that we may need a translation subgroup. Should we create one? Maccabee Levine suggested that a first step would be to reach out to the vendor who created the recent TCR. Jeremy Huff Suggested that community engagement should be a top priority for the translation subgroup. Owen Stephens the kware folks have shown their interest, but there are many others, and we should cast a wide net in gathering community engagement Zak Burke we have had difficulty in the past getting stakeholders from the wider community on the topic of multilingual approaches. Jeremy Huff Suggested "engagement with the community", "define functional and non-functional requirements", and "shepherd one or more rfc" as goals for the group. Jeremy Huff called for volunteers, Zak Burke volunteered for membership Maccabee Levine suggested that this might be a cross-council group No owner was found. Potential sub-group for non-technical response to the Platform and Application formalization proposal: Jeremy Huff do we need a sub-group for this? Maccabee Levine suggests that the timeframe may recommend not using the subgroup. Jenn Colt had a question about the scope. She is concerned that the questions about implications may encourage a change in governance that may not be required. Jeremy Huff agreed with this concern Maccabee Levine also agreed that the list brought forward by the TC should not be considered recommendations. He also expressed the opinion that some of the possible ways in which the application architecture changes might impact governance may be desired by some people. Jeremy Huff expressed that his goal behind pursuing identifying these implications is to encourage the other councils to have conversations/decisions in place before the changes are made. He feels that something like VBar proposal is likely to take place at some point, but that these changes are going to demand that we make some decisions on governance. He wants the decisions to be preemptive and not reactionary. Jeremy Huff asked Jenn Colt if she would want to participate in the discussion. He has agreed to reach out to the volunteers and organize a meeting time. | ||||||||||||||||||||
| < 5 min | Decision Log | All |
| ||||||||||||||||||||
| < 5 min | RFCs | All / Jenn Colt | This PR was approved | ||||||||||||||||||||
| < 5 min | All | Standing agenda item to review/discuss any requested or required changes to officially supported technology lists
| |||||||||||||||||||||
| 10 min | Decision on Jeremy's Schedule Conflict | All | Options discussed:
Jenn Colt pointed out that swapping the Monday and Wednesday meetings would allow us to plan the extended meetings on the same week that they occur, and that this could be beneficial.Jeremy Huff agreed. It was decided that swapping the Monday and Wednesday was preferable, and all voting members agreed on this, but we did not have a quorum and it was decided to defer until more TC members could weigh in. | ||||||||||||||||||||
| 10 min | Review of Tri-Council Meeting | All | Complete Notes: 2023-08-25 Tri-Council Meeting Tom Cramer's excelent summary:
This was reviewed and no new details were added. | ||||||||||||||||||||
? | Continued Discussion on Process Concerns in the wake of Vince's presentations | All | Questions/concerns were raised in #tc-internal about what the next steps are (after WOLFcon) for the topics recently presented by Vince...
Today: | ||||||||||||||||||||
| Zoom Chat | placeholder. | ||||||||||||||||||||||
Topic Backlog | |||||||||||||||||||||||
| Discuss during a Monday session | Officially Supported Technologies - Upkeep | All | Previous Notes:
Today Notes: | ||||||||||||||||||||
...