| Define meeting schedule (for this year) | | Do we want to meet semi-weekly ? how much synchronous business do we need to do? perhaps doing a beginning-of-year planning session or two to get our goals for 2022. make the above our first agenda item, and meet next week we'll meet when Ingolf sends an invite Ingolf will send either an inivtation or a cancellation each Thursday until 2 PM EST. If Ingolf has sent nothing until Thursday 2 PM he is probably on holiday (he will of course announce his holidays before !!!) or ill. In this case, there will be no meeting, unless someone else sends out an invitation.
Do we want to reserve the weekly meeting spot and cancel if there are no topics ? Shall calendar events be sent once for the whole year (Jan-Dec) ?
|
| Provide input for TC Strategic Objectives : Document library requirements for stability | | As in: TC Strategic Objectives TC comments on CC designation of leading council for FOLIO Vision, Strategic Objectives and Initiatives for PC and TC usage - Google Docs Bullet Point #6 of Strategic Initiatives for near-term. TC sees this as more of a SysOps issue than a TC issue; this is a Service Level Agreement, rather than a Product feature/goal. Should this goal be removed, or can it be rewritten in a way that can be better handled the TC? this would be the group to define requirements this is system dependent, both in terms of system resources as well as anticipated system usage performance metrics are separate from MTBF and MTTR what are the minimum goals ? should this requirement just be dropped? it's important, and the TC is best equipped to manage it should probably be rewritten without MTBF and MTTR, but still capturing 'reliability' concept more time may be required to live with FOLIO in production in order to understand reasonable metrics
Hosting providers identify issues with hosting FOLIO that require development resources to resolve, and report to TC
|