WOLFcon will tentatively be in Chicago August 22-24.
PC:
PO recruitment: Khalilah Gambrell spoke about the needs and a success story from the WOLFcon drive, defining clear expectations is key. There is a need to make the role appealing, so benefits to individuals and institutions are apparent.
Council updates
Support SIG: how move bugs forward when there is no longer a development team? Khalilah is thinking about a proposal.
How to accommodate when an institution reaches out with developers? Video from 2017 is out of date. Likely involves lead PO. (But this seems like lumping more work onto one person.) Noted that TC has a bullet about onboarding in draft charter. (See resulting TC Slack conversation.)
Meeting notes 01.03.2023:
CC:
Craig McNally - Need a bit more details on Second-phase resourcing group will start mentioned in the CC updates
Maccabee Levine - First phase evaluated a no. of resources and models that FOLIO community might operate under a lightly centralized model and this second phase which is defined will do a bit more work on distinguishing this with the current situation in the community and a few other tasks which are at the moment TBD... Marc Johnson might be able to expand on that..
TC Goals and Objectives - Skip the updates, will be discussed later as part of the agendas today.
Translations Subgroup - No updates. Craig McNally will reach out to Zak Burke to get status updates.
Controlling AWS hosting costs - Craig McNally - Peter was invited today to talk about the recent $5000 jump in hosting costs and provide some insights. Peter Murray - Major costs seems to be driven by Full stacks of FOLIO using EKS clusters, and other services such as RDS(for database), OpenSearch and so. A number of teams are using these installations and the recent cost jumps came from installing a 4th environment which stays on 24/7.(Teams- Bulk-edit, firebird,folijet and spitfire). Even though cost monitoring is being done by Peter but he has is no control over what the developers are doing with those environments and he is not as involved with this part of the project as he was during the early FOLIO days. Craig McNally - The last update was provided by Mark Veksler on the kubecost tool developed and rolled out by the Kitfox team was providing more insight into what exactly was driving up those costs. Peter Murray - kubecost is a good tool for determining the costs being incurred by the scratch environments because the resources are within on single cluster and namespaces are allocated to those teams working in the scratch environments but the recent costs are driven from individual full FOLIO environments which are being spun up. Jenn Colt - What is the process of spinning these full FOLIO environments? According to Jenn's knowledge there should be overlap in these environments, eg. bulk-edit is the same as firebird(?). Peter Murray - There is no oversight. Historically these teams have been given AWS admin rights so there is currently no request process for spinning up these environments as such and no strict access control on these folio accounts. In the early stages this approach was good but probably this is not a good approach anymore. Craig McNally - This topic needs to be revisited again. Jeremy Huff - It would be the TCs job to encourage the project to adopt some procedures around this issue. Craig McNally - The agenda topic with Mike Gorrell about how Project Finances are being managed will overlap with Jeremy Huff 's question. If enough is not discussed in the agenda, this topic can be added as an agenda item next week.
Breaking changes - Jeremy Huff - Draft PR is in, few people were absent so one more meeting is needed before we finally submit it next week. Craig McNally - Olamide Kolawole 's RFC has been moved to Public review recently, so can this RFC wait untill the one in progress is done and the process is improved or do we want to go on paralelly? Jeremy Huff - Willing to start the RFC review parallelly to keep the momentum of the subgroup going. Marc Johnson - We might get more RFCs so in general it's not advisable to wait since each of these takes months to complete.
TCR Process improvement - Jeremy Huff - Good discussion last meeting. Almost at the end of triaging all the feedback we got from the community. Maybe doing another round of retrospection with the reviewers might do good. Craig McNally -More discussions to follow next week.
Tech Council Charter Revisions - Craig McNally - CC has already approved. Jenn Colt - Did some grammatical correction and is looking for a consensus to promote the draft Charter to the Actual charter page. Craig McNally - Reviews are done and moved to main document page. Subgroup closed.
Kafka partitions RFC - Craig McNally - Had moved on from DRAFT RFC to the PUBLIC REVIEW phase, and this subgroup was for the draft rfc so can this subgroup be closed? TBD... How the Public Review can be notified to the people(message in which slack channel)
Craig McNally - Let's catch up with other topics next week and elaborate on them.
Jeremy Huff 's breaking changed RFC will be reviewed starting next week.
Jeremy Huff - For https://github.com/folio-org/rfcs/pull/6 Subgroup, do we let the members of the Subgroup meet one last time to decide the Slack channel for communicating, then the subgroup can be wrapped up. Next week further discussion.
Conversation about how funding decisions are made in the CC, and what role the TC plays in that decision making process, if any at all.
If the TC perceives a need for specific resources, how is that conveyed to the CC?
5 min
WOLFcon Volunteers
All
From slack:
Mike Gorrell Hello. Another WOLFcon is being planned (tentatively August 22-24 in Chicago), and we want the FOLIO community to be ready. In order to achieve this we need Volunteers to help plan WOLFcon. Please consider chipping in and join the#folio-wolfcon-planning-group
Take a look at the decision log, migrated decisions
Are any adjustments required?
Do any of these require additional discussion?
Next steps?
Communication about the consolidated decision log? Where? When? Who will do this?
Topic Backlog
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?
This was brought to my attention earlier today... https://blog.nlnetlabs.nl/open-source-software-vs-the-cyber-resilience-act/ While it's still just a proposal, I think FOLIO should keep an eye on, and maybe even try to get ahead of in anticipation of this. I will add it to the agenda for next week's meeting. This is a short read that does a decent job of laying it all out. Please take a look prior to next Wednesday. Thanks!
Have folks had a chance to read through any of this?
What, if anything do we think the TC should do about this?
Raise awareness among other councils?
Seek legal advice in anticipation of this being passed?
Is there anything else we want to do to be more prepared for this in the event it does get passed?
Primary task the Tc would take on by making FOLIO easier to get up and running. Would also reduce AWS costs so that the money coming from Membership groups can be flowed to other aspects of FOLIO. Tc is the best equipped group to decide on how to make installing and deploying Folio easier and cheaper.
Craig McNally - Brainstorming open ended session with Ian Walls and then discuss further before or after WOLFcon depending on the brainstorming session. Ian Walls and Tod Olson to frame the topics of discussion for the brainstorming.
Today:
Probably defer, but keep on the agenda so we don't lose track of this...
Ian Walls - should be best discussed in cross council meeting possibly at WOLFcon. Idea to was bring this up at a high community level not necessarily the Pc or TC. Doesn't need to be on TC agenda next week. Aspects to be discussed at WOLFcon.