Mark Veksler No updates from the Cap Planning team
External code submissions - Jakub Skoczencreated the GitHub repo
5 min
Security Team Personnel Changes
All
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.
Two questions:
Any objections to the team's selection? None raised at the meeting.
Any objections to the process we used for member replacement? If not, the security team will document the process so it's clear how this should be handled going forward. No objections raised, so the security team will document the process.
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.
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.
Zak Burke asked whether TC should distinguish between internal submissions and external.
Jakub Skoczen created the new GitHub repo for the TC.
The Capacity Planning Team has determined that we should proceed with the caching approach. The feature UXPROD-3317 "Improve checkout performance by caching data" and 19 stories with priority P1 (linked from the UXPROD-3317 feature) have been created.
Upgrade/Migration Script Performance
All
We've run into situations where migration/upgrade scripts take a very long time to complete, which is problematic. The TC should consider defining some criteria around this... Possibly a phased approach over the course of the next few releases?
Overlaps with the acceptance criteria topic as it applies to modules already part of the official FOLIO release.
Time permitting
TC charter review
All
Action items
Jakub Skoczen to create a Tech Council repo and move Acceptance Requirements document