Page Comparison

 Florian Gleixner , Tod Olson is next, followed by Ankita Sen 

All

No news.

No news.

All

TC Council Goals: Extra Item on Agenda.

Translation Subgroup: No update

Controlling AWS hosting costs: No update

Breaking Changes: Ankita has posted a draft, the subgroup reviews the draft.

Improving TCR Process: Jenn is working on getting a retroboard up for evaluation of the TCR process.

Tech Council Charter Revisions: Jenn will take over ownership of this group.

ADR process improvements: Some changes in the ADR space, but still WIP. Feedback welcome.

Tod Olson / Radhakrishnan Gopalakrishnan 

Last week:

Sounds like this subgroup might be ready to wrap up soon.  Allocating some extra time outside of the subgroup updates for them to present/shared deliverables, etc.

See Technical Council Goals & Objectives - DRAFT

Refining the objective and goals and getting feedback from the rest of the community. How to proceed and what are the next steps?

Agreed: Next step is to leave feedback about the Defined goals and objectives in the document's wiki comment section.

Tod Olson - Made a few changes. How would the TC like to proceed? Would they like to give feedback to the Subgroup's work or want the subgroup to meet again? Inline comments as feedback source should be fine. Having some inputs about priorities in the feedbacks is requested.

Craig McNally - Maybe a little bit of both should be done, feedback from the rest of the group and then refining a little more into which issues are more pressing than others. What the common goals are objective should be agreed on, insights from rest of the community needed. How to proceed?

Jenn Colt - Are these Goals and Objectives for the Technical Council or for FOLIO? Marc Johnson - How are they different from each other?

Jeremy Huff -Defining these will impact overall FOLIO processes. Also, which format shall the feedback on the working group's deliverables shall be provided with?

Marc Johnson - The next step should be TC members giving the working group deliverable valid feedbacks. Feedbacks welcome on the wiki comment section. 

Radhakrishnan Gopalakrishnan 

Previous:

• Tools/dependency versions - Radhakrishnan Gopalakrishnan took on this topic as a project. There is also a proposal Managing Tools/Framework Dependencies currently in Draft stage with feedbacks as latest as 02.08.2022.
• Radhakrishnan Gopalakrishnan advised that he was meeting with Marc Johnson on Friday to resolve outstanding questions and that this work should be ready for next week
• Radhakrishnan Gopalakrishnan - Need to review as group, get some feedback and close it. Version 1 was reviewed and certain things finalised but later discussion revealed a different approach was needed. Reviewed in today'S meeting for active feedback and discussion about the topic.
• Jeremy Huff - Concerns about the list of Officially Supported Technologies - this document was created for the new module technical evaluation , it was intended for another purpose so rolling it out into central processes might cause issue.
• Marc Johnson - Officially Supported Technologies is not a secondary document of this process, the point of the process is to have a list of things Folio as an application officially supports which is essentially like this exact document.. Radhakrishnan Gopalakrishnan agrees.

Put on agenda next week.

Today: Radhakrishnan Gopalakrishnan hard to get this done without having a separate meeting. Craig will send out a doodle poll for a separate meeting.

Previous Notes:

From Tom Cramer in #tech-council:

Since September, the CC, PC and TC have canvassed many community members on “what are things that could be better about FOLIO?” This came out of discussions at WOLFcon in Hamburg about what the priorities were for advancing & investing the project. 20+ council members interviewed 60+ informants from the community, producing a list of 175 items.

These items can be found in a grouped list that sorts the input into 13 different categories. This is a rich gauge of where many community members find the project--I recommend reading through this doc all at once to capture the gestalt. (~15 min)

A synthesis of all the input can be found in this presentation. The last three slides contain some specific and actionable opportunities for the FOLIO councils to consider and adopt as priority items around which to organize community effort.

• Asked all members to review the more detailed list on their own
• Reviewed presentation, a lot of feedback on "run on a laptop" point
  • Seen as barrier to contributing
  • Better management of dependencies between modules might help

Today:

• what are the next steps here?
• CC dedicated a meeting on this topic.
• A cross council chair meeting for coordinating action items shall be set up.

Craig McNally 

From Kristin Martin in #tech-council:

Hello @here The work of the Functional Evaluation for new FOLIO Modules Group has completed and we are ready to share our work with the Councils for feedback, and hopefully a path for adoption. We have written an overview of the entire evaluation process here, in the document titled, “Evaluation Process for New FOLIO Modules.” This document, if approved, would become a wiki page under the Product Council space that covers the full evaluation workflow for new modules, under the current system of flower releases for FOLIO. Criteria for how the PC would evaluate modules is included in this document, which also links to the Technical Council’s technical review process. Finally the document provides a link to a proposed MOU for module contributors to sign. We would like to present this process to the three councils for discussion and welcome comments and feedback in the documents directly.

• Let's all take a look and familiarize ourselves with this.
• Kristin will be joining us on the 11/30 to present and discuss (allocating 30-40 minutes)

Craig McNally /All

From Craig McNally in #tech-council:

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?

Craig McNally / All

One open question from the ADR improvements subgroup is how we should communicate decisions out to relevant groups/members of community?  We've discussed adding a stakeholders section to the ADR template, which will help, but we thought we might ask the TC if there are other ideas we should be considering...  Creating (yet another) slack channel for this purpose?  Post something to particular slack channels?  etc.

Today:

Maccabee Levine no new Slack channel. Posting to relevant channels should be enough.

Marc Johnson better post to specific channels like #development

Craig McNally Decision Records in Confluence are here. Part of the decision could be to find the relevant Slack channels for posting the decision. A newsletter for folio exists, but it may be the wrong target audience.

Marc Johnson Newsletter is a "marketing tool"

Craig McNally Interesting idea could be a developer focused newsletter.

Marc Johnson 

All / Maccabee Levine 

Last Week:

What, if anything should we do with the Decision log in the Technical Designs and Decisions wiki space?  Is it worth consolidating those decisions with the TC's ADRs?  Should we cross-reference?  Clarify the scope of these decisions, and whether or not decisions should still be made/logged here?  

See discussion in #tech-council for additional details.

• Craig McNally Decision log left when Tech Leads group fell apart with new governance structure.  Are decisions still made or logged in that space?  Where does this lie in the backlog.
• Maccabee Levine Motivations are to have a single list of decisions, to build developer-buy in and solve the longstanding issues with what decisions TC has authority to make.  Also to know what we have to keep updated vs archive.
• Craig McNally By consensus, added to the middle/bottom of the list.

Today:

Marc Johnson : Decision about Optimistic Locking: this is done. Optimisting locking can be used using the API. Bulk/Batch APIs especially for migration should use Optimistic concurrency control.

Tod Olson 

All / Ian Walls 

From last week:

• Ease of installing/deploying FOLIO - Ian Walls , Marc Johnson , Jeremy Huff
  •  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...

All / Ian Walls 

Slack discussion:  Revisiting FOLIO Governance 

• • 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.
  • See also:  messages to PC and CC council channels