2024-05-20 Meeting notes

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

Maccabee Levine

Tod Olson

Jakub Skoczen

Craig McNally

Jenn Colt 

• CC: Maccabee Levine 
  • No meeting this week.
• PC: Tod Olson
  • Introduction of Developer Advocate
  • Discussion of how to get better data in the snapshot and test environments
    • 2024-05-16 Product Council Agenda and Meeting Notes
      • Need updated data, appropriate for newer functionality
      • smaller data sets for dev environments that still allow range of testing
      • Note that different institutions use different features and cannot rely on data from just one site to test all functionality
      • ideas on updating from contributors and anonymizing data
      • PC bringing together a small group to figure out next steps, unclear if there is a TC stake here
    • Slide deck: Better sample data in Reference environments
• RMS Group: Jakub Skoczen
  • Positive feedback to adding reminder about architectural changes with TCR require to release schedule, will be added to Ramsons document for Sunflower release
• Security Team: Craig McNally
  • Processing backlog, many false positives or vulnerabilities that do not apply in our use case
• Tri-council Application Formalization: Jenn Colt
  • Was off last couple weeks
  • VBar is preparing an overview of Eureka, providing big picture for general audience.

• 22 May 2024 - Dedicated Discussion - Communicating Breaking Changes
• 27 May 2024 - Regular TC Meeting
  • Holiday in the US & UK - Cancel Monday and use Wed as regular meeting
• 29 May 2024 - Use as regular meeting for this week, due to Monday holiday
• 03 Jun 2024  - Regular TC Meeting
• 05 Jun 2024 - Alternate time meeting for China and Australia topics?

All

All

• Go Language: When will we do the final review?
  • Next Monday 27 May 2024 - Jakub not available
• Application Formalization: When will we do the final review?
  • The following Monday 03 Jun 2024 

Jeremy Huff

• Jeremy Huff:
  • Advertise Communicating Breaking Changes PoC Demo update
  • Reach out to Australia and China for topics
  • Add developer suggested topics to our backlog
    • Done.

Nothing new

Craig McNally doesn't mind staying on as co-chair to aid in transitioning to new TC leadership once Jeremy leaves this summer.  

Jenn Colt would like to volunteer, but she's up for re-election.

It seems it might be best to wait until after the elections, but it cannot hurt for those interested to speak up now. Jenn willing to be a backup until elections and next formal assignment of officers.

Standing agenda item to review/discuss any requested or required changes to officially supported technology lists

Need volunteer to update calendar, especially milestones on OST page. Also reach out to Peter Murray to see if we have access to the old calendar to check what milestones we had put there.

Previous Notes:

• 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 about the Poppy release.

Zak: A handshake between developers, dev ops and the TC. Who makes that decision and how do 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 dev ops folks have made it clear that it 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 TC 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 parts of the body ?

Marc: the developers community, the dev ops community and sys ops are 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 decision makers so that they be a moderating group.

Jakub: I agree with Marc. But we are not a system operating group. Dependency management should be 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.

Craig: This is a topic for the next Monday session.

Craig to see if Oleksii Petrenko could join us to discuss the process for updating the officially supported technologies lists.

Possible topic/activity for a Wednesday session:

Discuss/brainstorm:

• Ideas for the type of developer-facing documentation we think would be most helpful for new developers
• How we might bring existing documentation up to date and ensure it's consistent 
• etc.