Page Comparison

Philip Robinson is next in the list, followed by Jakub Skoczen

• Mark Veksler  No updates from the Cap Planning team
• External code submissions - Jakub Skoczencreated the GitHub repo

Mike Gorrell is stepping down from his role on the FOLIO Security team.  Jakub Skoczen has be nominated by the team to fill his spot.  A formal process for this hasn't been defined yet, but we wanted to raise this here for awareness and to give folks a chance to weigh in on the choice.

Ian Walls/All

• Discussion ran longer than the time originally budgeted.
• mod-inventory-update eval for Lotus... https://folio-project.slack.com/archives/CAQ7L02PP/p1634659952419300, https://github.com/folio-org/mod-inventory-update
• Ongoing work on Acceptance Criteria and Processes (submission, evaluation, etc.)
  • Has the Acceptance Criteria v1.0 been published somewhere yet?  What about references/links in other places.
    • Will pick a Github repo and deposit it later (Jakub)
    • Charlotte Whitt said it would be helpful to have an official wiki page for the criteria. Anton Emelianov (Deactivated) agreed, and the page should list the sequence of steps for a new module to be accepted for release. Craig McNallymentioned that the TC has been working this for a while and will continue to focus on it.
  • Agree on short and long term goals, will continue to work on:
    
    • Define processes for submission, evaluation, review, feedback, acceptance
    • Improve the AC with more verifiable criteria, links to supporting documentation, etc.
    • Time frame: Ian Walls and Jakub Skoczen will take a look at Lotus dates and inform the team next week
      • Ian Walls needs clear timelines from the release team, otherwise the feature has to wait until the following release. Ian needs an addition to the timeline that explicitly states which date is the TC external code review deadline.
      • Anton Emelianov (Deactivated) will join the Friday meeting focusing on a resolution to this.
      • Timeline: Lotus (R1 2022)
  • Zak Burke LDP approval came to TC from PC and would expect future requests to come from PC rather than directly from contributors. Owen Stephens  and Brooks Travis agreed. Charlotte Whitt said the module has already been approved by the PC.
  • VBar there's a race condition where we have a series of incoming technical review requests, but the processes haven't been finalized. We should have a moratorium on evaluations temporarily until the processes are complete. Craig McNally agreed. Jeremy Huffasked does that mean no new modules can get through until the process is finished?
  • Brooks Travis considers modules hosted on the project GitHub as approved by the PC. The PC is going to get a handle on what gets added to the project GitHub. This is the distinction between the LDP app and mod-inventory-update, and mod-inn-reach. His understanding of what the PC wants is the TC's recommendations as to the viability of external contributions, but the decision is still PC's.
  • Marc Johnson feels that the TC is mixing up at least 2 processes: accepting modules into the community, and including them in the official distribution.
  • Owen Stephens noted in chat that the PC said it wanted LDP app to be part of the FOLIO product, but that may not be relevant. There should be some kind of sign-off process from PC. Brooks Travisagreed and suggested that it be raised at PC again to clarify the process for acceptance. Owen Stephensclarified that he was making his point generally, not questioning whether the PC sign-off happened for mod-inventory-update in particular.
  • Zak Burke asked whether TC should distinguish between internal submissions and external.
  • Charlotte Whitt mentioned that Kirstin Kemner-Heek will attend, as PC rep and as stakeholder for mod-inventory-update.

Jakub Skoczen  created the new GitHub repo for the TC.

Follow-up from previous meetings...

Previous notes:

From Mike Gorrell:

I have created a clean copy of what the Community Council created to identify which FOLIO Goals/Objectives were under the purview of the CC. We also took a stab at what thought would be handled by PC or TC. Please feel free to give us feedback/etc. https://docs.google.com/document/d/17jVxW2XEK2bRSpXG9_FvdVtgqDfCTeKKM5h49IIhmRw/edit#heading=h.m2gdb67ibe1x. and use for your planning purposes.

Update from Tod Olson, Jeremy Huff, Craig McNally who met to discuss this last Friday.

• The Friday meetings will be at 11am EST, please join if you can.

Deferred last week due to insufficient TC attendees.

Back in July we asked Zak Burke to create a reminder for us to discuss this... 

This is a carry-over from last week.

• The tech leads group not being a decision making body
• Whether it's realistic and/or desirable for the TC to make every technical decision
  • There was some overlap here with the external code submission topic

Related - in the wake of last week's slack vote:

• Revisit voting rules:
  • quorum: 8 (tie is no, so minimum 5 votes to pass)
  • simple majority: yes
  • of vote casted (including abstentions): yes
  • Abstain: Yes
  • Delegate: Yes
  • voting via slack: No, it has to be in person only
• Future for Tech Leads Group?  Who makes technical decisions, how?

Brainstorming on how to make technical decisions. 

Additional Context: 2021-10-13 Meeting notes

• Actions from last week:
  • VBar can commit to re-present the RFC process next week
  • Jakub Skoczen will try to define what we are trying to accomplish → See here

Marc Johnson

Follow-up from previous meetings...

Proposal from Marc Johnson: https://wiki.folio.org/display/~marcjohnson/Check+Out+Performance

Marc Johnson was asked to make a proposal for checking out performance; draft document is available by the first link above. Feedback is appreciated

There's a link to PTF analysis from the first mentioned doc

Julian Ladisch