Date
6-Jan-2021
Attendees
- Mike Gorrell
- Jakub Skoczen
- Zak Burke
- spampell
- Jeremy Huff
- Marko Knepper
- Mark Veksler
- Marc Johnson
- VBar
- Craig McNally
- Ian Walls
- Tod Olson
Discussion items
| Time | Item | Who | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Texas A&M Representation on Tech Council | Stephen took a new role at A&M last June and had stayed on FOLIO through 2020 but the time has come for him to transition from FOLIO activities. Jeremy Huff will be the new representative from Texas A&M for the Tech Council | ||||||||||
| FOLIO Governance | FOLIO Stakeholders have approved the new governance model and we'll be communicating specifics to the Product Council tomorrow. | ||||||||||
| Scratch Environments - process for making uniform changes | Jakub |
What should our process be for vetting requests related to reference or scratch environments - especially if they involve increasing the AWS costs. Two aspects: 1) Process to review/approve additions/changes if they can fit within the Budget. Requires TC to be tracking actuals and understand where the actuals are relative to budget. Bottom Line: DevOps need to get TC approval for changes that will increase infrastructure costs. 2) Process to request increasing the budget - TC needs to be able to "make the case" for the increase. Action: Mike Gorrellto document current budget, prior requests and approvals for the TC. We will also need to establish an "accounting" process so that we know what's been budgeted and what's being consumed (therefore what's left of the budget). Comment: we should invest in a tool to help understand cloud costs (A&M uses Cloudability). | |||||||||
| Permissions Architecture and management | Mike | Should there be a centralized control of how permissions are setup and managed Reference
Discussion: There are guidelines and guidance around permissions, although not specifically for "action based" ones. What Vega did was based on discussions (not done in a vacuum)... and we encourage teams to make localized decisions when necessary to continue to make progress on features. Documentation and discussion can/should still happen, but won't necessarily hold up the team. Also discuss the complications/difficulty in dealing with permissions during an upgrade. Craig volunteered to get with the FOLIO Implementers to get their thoughts on recent/upcoming changes. |