- Slack: tc-evaluation-process
- Meeting Time: Every week on Tuesday, 11AM - 12PM EST
- Zoom Meeting ID: 830 2941 7442
- Zoom Link: https://openlibraryfoundation.zoom.us/j/83029417442?pwd=amdndnBLd1loMlFET1Z3RU8yWEh6UT09
Agenda and Minutes
2022-2-22:
Review:
- Previous TC discussions: 2021-10-13 Meeting notes, 2021-10-20 Meeting notes, 2021-10-27 Meeting notes, 2021-11-10 Meeting notes
- Draft Document: Technical decision making process in FOLIO
- RFC process: https://github.com/folio-org/rfcs
- Development process: https://dev.folio.org/guidelines/development-design-review/
- Tech Lead: Technical Designs and Decisions
- FOLIO Developers: https://dev.folio.org/
Define:
- Scope
- Audience
- Goals
- Approach
2022-03-01
Feedback on RFC process:
Action Item: To recommend that TC should implement RFC process to improve consistency and standardization of decision making. TC should promote the process to stakeholders in the FOLIO community, provide some clarification on when the process is required, solicit feedback, and make adjustment to the process in the next months before WOLFcon.
Discussion: How to design and implement the decision-making process so we can encourage participation and ensure consistency/standardization?
This subgroup will lead the effort in soliciting feedback, improving the RFC process, and recommending additional venues for encouraging participation during the RFC piloting.
2022-03-08
Recommendation to TC on piloting RFC process:
- The subgroup agreed that the RFC process (https://github.com/folio-org/rfcs) is well written and TC could use it as the council's formal decision making process to improve consistency and standardization, as well as ensure consensus.
- We acknowledge the definition of "substantial changes" will and should be evolving as the FOLIO community grows. The categories outlined currently are good enough to start with:
- Any changes to the Folio infrastructure including Okapi and Stripes
- The addition or removal of conventions, patterns and protocols that are key to the interoperability of Folio components.
- The removal of features that already part of a Folio release.
- Any change required for integration with systems external to Folio
- Changes that require the coordination between multiple Folio components or services.
- A new feature which might be considered redundant to existing features.
- We recommend TC to pilot the RFC process.
- Select a request that is already submitted for TC review
- Work with one dev team on a change that's in planning process
- Go through the RFC life cycle for those two change requests
- Revise the process and recommend additional tools
Discussion:
- Approaches: pilot RFC process within TC, invite dev team to participate, clarify decision categories that are required to go through RFC process, and explore additional tools.
- Need TC instruction so the subgroup can focus on one or two concrete things:
- Piloting RFC process
- Define "substantial change" categories
- Tools for providing feedback before formal RFC process
2022/03/15
To do list:
- TC-internal: collect current/incoming changes that need TC decision for piloting RFC process
- Authentication Token Architecture (this has been proposed by Steve Ellis on Nov 21, see 2021-11-10 Meeting notes , seems there were no actions performed by TC since that time)
- Cross-application Data Sync proposal (as a topic of Cross-app data synchronization working group ; the proposal is not ready yet as per Mar 15 - still at least a few weeks of work)
- Authentication Token Architecture (this has been proposed by Steve Ellis on Nov 21, see 2021-11-10 Meeting notes , seems there were no actions performed by TC since that time)
- TC-internal: collect suggestions on tools/process for TC to provide feedback before a formal RFC process