2023-04-05 Meeting notes

PC: No meeting since the last TC.

Technical Council Sub Groups Updates

AWS: Maccabee Levine a first meeting is on the calendar

Distributed vs Centralized Configuration: Craig McNally we will need to find a new leader for the Distributed vs Centralized Configuration subgroup Radhakrishnan Gopalakrishnan will need a replacement. No volunteers were forthcoming. We might defer finding a leader until after the elections. Vijay's name was removed. We will revisit this next week.

Onboarding documentation: Craig McNally Should we wait on forming a group until after the elections? Jenn Colt Should we create a documentation subgroup? We may not want to have a standing subgroup. Craig McNally Feels that we should have shortlived well-defined subgroups. Maccabee Levine maybe this should be a subgroup to the documentation sig. Jenn Colt That group is mostly focused on docs.folio, which has high overhead. Do we have two classes of documentation? The TC sidebar needs cleanup, which Radhakrishnan Gopalakrishnan started, maybe we should have a subgroup for cleaning up our wiki presence?

Craig McNally A subgroup may be overkill for updating the wiki presence

Marc Johnson is in favor of case-by-case volunteers to clean up the sidebar. He also does believe that we do have multiple forms of documentation, docs for those who use FOLIO, and another for those who contribute to it. Docs.folio is not aimed toward contributors.

Jeremy Huff maybe we should ask a volunteer to approach the documentation sig and ask if they have the capacity for onboarding documentation. Maccabee Levine volunteered for this, he agrees that it is important to reach out to these groups. 

Craig McNally if we are going to do the work, we might as well track it as a subgroup, Maccabee Levine has become the owner of the onboarding documentation subgroup and will be reaching out to find additional members.

Tod Olson there is a documentation-wg slack channel, and it seems like it is a subgroup of the support sig. They maybe an additional place to start when reaching out.

Today:

Craig McNally changes are being made to this list without the TC being consulted

Jeremy Huff maybe we should put a disclaimer at the top of the document that stated that the TC is responsible for updating that page

Craig McNally That may work, but it does not address all of the concerns. Maybe we need a reminder to create new pages for new releases

Florian Gleixner Maybe we should add a header that expresses the status, instead of "draft draft draft" Marc Johnson agrees. 

Marc Johnson The versions are likely to change over time, so we need a process to support that

Jeremy Huff There are multiple purposes behind this list, which leads to differing levels of granularity

Craig McNally The differences are present in places where it is important to the build processes

Marc Johnson Some of these differences are due to different people editing this. We should put controls in place for editing

Craig McNally We can put a disclaimer that says don't edit this page, leave a comment instead

Jeremy Huff The granularity of the spring modules is excessive for the purpose of new module technical evaluation but may be needed for other purposes. This posses a conflict.

Craig McNally Maybe we can change the presentation and use verbal framing to avoid this conflict

Marc Johnson Agrees with Craig's suggestion, as does Jeremy Huff 

Craig McNally We should:

      1) add a section at the top with some clarifying comments on how this is used and updated

      2) Change the wording of the spring module enumeration to imply that the modules listed are examples

      3) Add dates to our calendar to create new pages for each release

Florian Gleixner volunteers to make a draft header for the next meeting 

Tod Olson Would we also want to be explicit about the purposes of this document? Craig McNally yes

Topic Backlog

A process was proposed for how to keep these pages up-to-date, we need to revisit and put some processes into place.  As it stands right now, we have members of the community making changes w/o consulting the TC.

• Managing Tools/Frameworks/Dependencies Version - v0.2 DRAFT
• Officially Supported Technologies