Skip to end of metadata
Go to start of metadata
Date
31-Mar-2021
Attendees
Discussion items
Time | Item | Who | Notes |
|---|
| New Tech Council Chair needed | | The TC should elect a new Chair.
|
| Define technical approach to keeping data across apps in sync | TC | This is an introduction to the problem outlined in
FOLIO-1331
-
Getting issue details...
STATUS
The community seems to be in need of a standard solution to this problem. Thoughts? Suggest this be added to the list of future topics. |
| Unified list of expectations relative to testing items that should be part of Definition of Done | Anton | Review Anton's recommendation |
| Agenda items for future meetings | TC | The following items are agenda topics for future meetings - how to prioritize Top 3: - Status of Spring Way (can leverage this discussion to determine process for approving new technology
Create a unified list of expectations relative to testing items that should be part of Definition of Done (note Anton Emelianov (Deactivated)is preparing a recommendation to be reviewed on 2021-03-31)- Process/details on what is expected and required in order for code to be contributed by a team to FOLIO
Others: - OK to upgrade our AWS support from "Basic" to "Developer", which would add about $300/month to the FOLIO AWS bill (3% of monthly spend) to address the Confluence problem (painful details are in a comment on FOLIO-2867).
- Technical approach to keeping data across apps in sync
- Guidelines for which modules re part of official releases
- Tech Debt review (periodic)
- Definition of Reference/Default Data Types
- How to approve new technology that has been asked to be added as "approved" for FOLIO
- Technical review of code/system quality
- Review of Architectural design process
- Review of architectural blueprint / potential items
- Establish and manage a policy around changes that might impact our budget
|