PC reviewed Browsers Support statement and endorsed it. There was some support for Owen's ideas of providing some guidance. Owen had proposed in Slack. There is no specific action right now. People should be aware that they should file Jira tickets if there are any.
Continuation of our conversation about Cross-tenant/consortia and tenant checks. Calendar already updated. Olamide Kolawole explained some details in last meeting
I need someone to run this meeting as I'll be out on vacation. Craig will ping Jeremy.
- - Folio Summit - Chairs from each council will be in attendance including Jeremy Huff and Craig McNally
Holiday for many, probably best to not schedule anything
RFC Retrospective
---------------
Tod: There is a meeting following up the Stanford meeting. Pushes on data import. There is representation from ARLEF and from the commercial partners, EBSCO, Knowledge Integration , IndexData and the German consortia.
Jenn et. al.: Why is this not being discussed at WolfCon ? Or we can have 3-hours-lasting meetings at Zoom. Why is this being discussed aside ?
Tod: How can we mobilize resources; how to we mobilize work that is not getting mobilized otherways. It is a response.
Maccabee: I am glad that our governance leaders are there.
Tod: Governance is set up more for influencing than actually directing effort. Various groups insert influence.
5-10 min
TC member roles
All
I believe what we discussed was keeping the liaisons as-is for now. The situation with the chairs was less clear. One idea was to phase a new chair in so there's less disruption once the next terms are up. Let's discuss and decide today.
Chair:
Deputy Chair:
CC Liaison:
CC Liaison backup:
PC Liaison:
PC Liaison backup:
CSP Liaison:
---------------
No change in the liaisons. Marc is CC and PC Liaison backup. Tod is the PC liaison.
Chair / Deputy Chair: We agree on a phased-in approach. No volunteers. We will wait until next year's elections.
Time permitting
Officially Supported Technologies - Upkeep
All
Today:
A workflow for these pages. When do they transition from one state to another. Do we even need statuses at all.
Stripes architecture group has some questions for the Poppy release.
Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how to we pass along that knowledge ? E.g. changes in Nodes and in the UI boxes. How to communicate this ? We have a large number of teams, all have to be aware of it. TC should be alerted that changes are happening. We have a couple of dedicated channels for that. Most dev ops have subscribed to these channels. How can dev ops folk raise issues to the next level of community awareness ? There hasn't been a specific piece of TC to move that along.
Craig: There is a fourth group, "Capacity Planning" or "Release Planning". Slack is the de facto communication channel. There are no objections to using Slack. An example is the Java 17 RFC.
Craig: The TC gets it on the agenda and we will discuss it. The TC gets the final say.
Marc Johnson: We shouldn’t use the DevOps Channel. The devops folks have made it clear that should only be used for support requests made to them.
Jakub: Our responsibility is to avoid piling up technical debt.
Marc: Some set of people have to actually make the call. Who lowers the chequered flag ?
Craig: It needs to ultimately come to the PC at least for awareness. There is a missing piece. Capacity Planning needs to provide input here.
Marc: Stakeholders / Capacity Planning could make that decision. Who makes the decision ? Is it the government or is it some of the body ?
Marc: the developers community, the dev ops community and sys ops will be involved. For example the Spring Framework discussion or the Java 17 discussion. But it was completely separate to the TC decision. It is a coordination and communication effort.
Marc: Maybe the TC needs to let go that they are the decison makers so that they be a moderating group.
Jakub: I agree with Marc. But we are not a system operating group. Dependency management should become in the responsibility of Release management. There are structures in the project for that.
Jason Root: I agree with Jakub and with Marc also. Policies should drive operational/release/support aspects of Folio.
Jason Root: If the idea of “support” is that frameworks are supported, then of course the project should meet that.
Marc Johnson Some group needs to inform OleksAii when a relevant policy event occurs. These documents effectively ARE the manifestation of the policy.
I need someone to run this meeting as I'll be out on vacation. Craig will ping Jeremy.