...
- Update the term components council to roadmap council
- Update the overview section to talk about the documentation we've generated being available to future working groups
- Add a qualifier to say July or end of summer at the latest
- Remove the requirement for in person once per year
- “Will elect a Chair and Chair-Elect from among their membership” And let Steering sort out how in the bylaws.
- Roadmap Council is solution bundles and core components and other components as identified by the Steering Group (Avalon, Hyrax, metadata, etc.)
Other action items
Meeting Notes
...
Resolved what happens when a PO steps away
When a PO steps away, Partners will acknowledge and we'll find a replacement PO
Support Simeon’s comments about Components Council making language stronger?
Goes back to re-naming of Components to Roadmap Council
Left avalon and SIGAHR separate - Components Council and COmmunity Roadmapping Group
Practically be Sr. folks who will be on the roadmap council. Technical coordinator will oversee the coordination of
Things from the Core Components as decided by CCMWG and Solution Bundles as Designated by Steering
- Roadmap Council is name
- Solution Bundles and Community Owned Components and other Components Identified by the Steering Group
Will be responsible for roadmaps
Standing Working Groups? Do we need this?
New framework allows for rechartering - so we don't need "Standing" Working groups in new format