| Time | Item | Who | Notes |
|---|
| 5-10 min | Improved Handling of Reference Data During Upgrades | | - The sub-group has completed it's objectives and produced the following deliverables:
- JIRA Feature and Spike:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-3111 |
|---|
|
/ | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | FOLIO-3215 |
|---|
|
- Formalized Recommendation: Improved Handling of Reference Data During Upgrades
- Next Steps:
- The SysOps SIG will be given an update on July 23 (Tod Olsonand Wayne Schneider)
- Ask Capacity Planning to find some resources to work on the Spike/PoC (Mark Veksler)
- Idea is that is a real PoC, module would be split off into it's own storage so should be able to peacefully co-exist in the dev team's scratch environment.
|
| 5-10 min | Transition Plans for TC members? | All | - Newly elected TC members will take affect on July 14
- Questions:
- Does the meeting time still work for everyone?
- TC self-governance...
- Who will be the convener? Rotating responsibility? Full set of officers? etc.
- Need to list the specific responsibilities:
- See Tech Council Charter
- what is the business of the TC and what does the TC need to do to conduct that business and have a suitable record?
- What does the decision making process look like? Voting? Lazy Consensus? Something else?
- Get something agreed to and written down (on the wiki)
- Review relationship with PC and CC, see FOLIO Governance Model
|
| 1 min | Convener for next week? | All | Tod Olson volunteered. Thank you! |