2021-11-03 Meeting notes

Raman Auramau is next in the list, followed by Dennis Benndorf 

• Zak Burke to act as scribe today.

• • Link to acceptance criteria in the TC's GH Repo from the wiki: Zak Burke will do this
  • TC has comment on Jakub Skoczen's document
  • ref data upgrades will be addressed at the PC
  • review the TC charter: still todo

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?

• No progress last week
• Note: CC document framed as "lead" council, though we've been taking it as "who has an active role."
• Working document: TC comments on ... FOLIO Vision, Strategic Objectives and Initiatives...
• Framing document for the cross-council group: Criteria for Accepting Code
• The Friday meetings will be at 11am EST, please join if you can. Contact the above folks if you'd like to attend.

Raman Auramau

Quick update from Raman Auramau?

skipped 2021-11-03

Craig McNally

Jakub Skoczen

• Note this has been renamed from "External Code Submissions" to "New Module Technical Evaluation"
• A proposal for module submission/evaluation/review/acceptance is ready for review by the TC
  • https://github.com/folio-org/tech-council/blob/master/NEW_MODULE_TECH_EVAL.MD
  • The scope of the proposal is a process for acceptance into an official FOLIO release.
  • The subgroup acknowledges that a process also needs to be defined for acceptance into the FOLIO community resources (Hosted reference envs, CI/CD, platform-complete, etc.).  While related, and also important, this is viewed as out of scope for the proposal being reviewed today.
    • We need a volunteer for this, but have none at present.
  • Jakub Skoczen is working on a strawman for the JIRA workflow (closely tied to the new module technical evaluation process): began experimenting with the "Process project" workflow that ships with Jira. Will share with the sub-group this week and present conclusions to the TC on 2021-11-10.
• Acceptance criteria published in the tech-council repo: https://github.com/folio-org/tech-council/blob/master/MODULE_ACCEPTANCE_CRITERIA.MD
  
  • Still need a presence on the wiki that links to this; todo: Zak Burke
• Craig McNally: Review of the new module technical evaluation process draft document
  • Tod Olson: there is a nascent cross-council group working to define the larger picture of module evaluation across councils
  • Tod Olson: So if a dev team wants a module to be included in a new release, they need to go through the PC. Is that correct? Yes.
    • Adam Dickmeiss: what about adding new 3rd party-deps to an existing module? Out of scope.
    • Jeremy Huff: whoops, there is a discrepancy with the acceptance criteria where we specify that code must already be within github.com/folio-org. Marc Johnson: yeah, these two docs need to be reconciled.
  • Philip Robinson: glad to see Jira being used to manage this process.
  • Tod Olson: This looks great! But ... assuming we will look at it iteratively and that it may be tweaked in the future?
    • Yes, we should plan a retro after it's been put through its paces a few times. 
    • This makes some assumptions about input from the PC; Tod Olson will help raise awareness of this within the PC.

Jakub Skoczen

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

Additional Context: 

• 2021-10-13 Meeting notes
• 2021-10-20 Meeting notes
• 2021-10-27 Meeting notes

For Today:

• Review Jakub Skoczen's document and any feedback/questions/comments.
• Marc Johnson: the goal here is "to make a process"? Yes: the task is to specify the process. 
• Owen Stephens: how is evaluating a proposal a decision-making process? Proposals are approved or rejected; this is the decision. This can be made more explicit in the "Goal" statement.
• Motivation: consistency! consistency! consistency! Also, to promote participation in the decision-making process.
  • Marc Johnson: I thought we were trying to define a framework for the process, but achieving consistency is an outcome  of having such a process, so it feels like we're confusing motivation with outcome.
  • High barriers will limit participants; low barriers will reduce consistency; the goal is the middle ground.
  • Owen Stephens: Should the process favor consistency over other things, or are we expecting that the process will increase consistency? We've had presentations from e.g. sysops that demonstrated conflicting priorities among ease of maintenance, feature work, etc; are we saying that consistency is our highest priority?
    • Jeremy Huff: Agreed, we would have to intentionally favor consistency if we want that. Deviating from that would have to be deliberate. Should this priority be captured?
    • Jakub Skoczen: we've added many criteria to our acceptance criteria, but it isn't clear that the project truly will be better off if we add additional criteria, perhaps at the expense of losing a feature that was inconsistently implemented.
• TODO for all: please review and comment on this document! Consider whether the RFC proposal can meet the purpose outlined here.