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.
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.