2021-09-08 Meeting notes
Date
Attendees
- Craig McNally
- Brandon Tharp
- Ian Walls
- James Fuller
- Jeremy Huff
- jpnelson
- jroot
- Raman Auramau
- Steffen Köhler
- Tod Olson
- Owen Stephens
- VBar
- Marc Johnson
- Ingolf Kuss
- Zak Burke
- Philip Robinson
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
1 min | Scribe | All | Philip Robinson is scribe, followed by Jakub Skoczen |
5 min | Review outstanding action items | All |
|
20 min | External Code Submissions |
| |
30 min | SysOps SIG representative(s) | Per Tod Olson:
Likely to require additional discussion as well as a subgroup and/or time slots in coming weeks. How should we move this forward? Brandon Tharp the TC should decide how to lean on the FOLIO community to resolve the issues, and advocate for architecture change. Jeremy Huff One restriction is that the TC does not allocate developer time. The most we can do is advocate and lobby for a strategy that the TC would promote. Define goals of how FOLIO should be, where things currently fall short, how to head off future technical debt as well as remove the current debt. Zak Burke A challenge is that we don't have an "NFR" SIG or library to advocate for non-functional requests. FOLIO is more motivated by SIGs and Libraries who are mostly feature-driven. James Fuller This feels like a Risk Tolerance situation. If the risk for a module release is very small, I think the folks would be more likely to update more frequently. With the historical risk during an update, currently people are update-adverse. Marc Johnson The topic of failures in operations that require changes of persistent state in multiple modules has been attempted to be addressed a few times and we haven’t made much progress on doing so (possibly because it changes the nature of the integration patterns). One of the challenges we have is that the community quite often expresses stances that aren’t compatible with each other e.g. some folks want more smaller modules others want less larger ones. Ian Walls FOLIO needs to have official 'releases' from a marketing, training and documentation perspective. but that can also exist with the ability to deploy bug fixes in modules without having to re-roll a completely new release. Owen Stephens The discussion at the PC concluded with 3 next steps:
The SysOps SIG has suggested and advocated for NFR work in the past, but it always gets ranked at the bottom and never prioritized. SysOps also has no PO. | |
Time permitting (likely deferred) | Technical Decision Making Process | All | (this was deferred) This is a carry-over from two weeks ago week. It was a tangent of the min.io/S3 conversation that started to delve into topics of
NOTE: We need to frame this conversation and agree upon what we're trying to accomplish and how much time we want to dedicate to it before diving in. |
Time permitting (likely deferred) | TC charter review | All | (this was deferred) |