...
- Call for additional items
- Julie
- Resourcing and survey results
- Presenting the survey results at a Partners call
- Nabeela
- Perhaps we can discuss the Partner call
- Marketing Working Group
- Mention of some help from the Roadmap Council in updating the pages
- Julie: Assigned certain pages from the last meeting
- Julie
- Action items from the previous meeting
- Hyrax WG meeting rescheduled
- There is potentially a new Hyrax Product Owner identified, but there are scheduling concerned
- Julie Hardesty is looking to start this in July, hitting 20% stride by Connect 2020
- Serve in this role for two years, with the second year involving the preparation for nominating the successor PO
- This will be discussed with the community during Virtual Connect
- There needs to be some clarification addressing that Julie cannot begin to ramp up focus until at least July
- Julie Hardesty is looking to start this in July, hitting 20% stride by Connect 2020
- Component Maintenance WG
- James is going to serve as the representative for the WG
- Mark could continue to be a Product Owner representative for the WG, with James serving as the developer representative
- Prefer to keep Mark
- James provided a history of the Core Component WG
- (This will be drafted)
- Roadmap Council is there to facilitate with community coordination from the WG
- Parter Meeting Recap
- Three goals were shared with Partners f
- Survey
- Asks put to Partners
- Some discussions regarding reinterpretations
- For the ask, assumed that we were discussing the contribution model
- Code recommendation
- Tom Cramer: Overall goals and objectives vs. the vision of the community
- Roadmap
- Are we actually working towards a roadmap?
- Are we building a roadmap?
- Are we actually working towards a roadmap?
- We might need a massive change to the charter
- Rename to the "Roadmaps Council"
- There is this constant problem of assuming that this council is chartered to create a single roadmap for the entire community
- This is not the chartered purpose of this group
- This needs to be clearly stated
- The community does not empower us to establish a single roadmap
- There also isn't interest from the community in empowering us to do so
- We are more of a clearing house, "air traffic control"
- If Partners do not understand this, then the rest of the community likely does not understand any of this either
- Renaming
- "Samvera Roadmaps Coordination Committee"
- "Roadmap Clearing House"
- If we continue to keep the "roadmap" term in the name, we still are left with the assumption that we have a roadmap
- If there is a contingency of partners who do want to define a roadmap, this will need to be clearly identified and this will need to be addressed
- Three goals were shared with Partners f