...
Communicate the change - of voting, that there is changing.
What we want structure to look like, and how we get to that structure. Implementation details make it clear what the nature of the change is. (ugh, bad sentence). Organized in priority order - what has to happen (maybe dependencies). Move to electing members of steering. Once we do that, easier to do everything else. Updating bylaws - from perspective of new steering. There are bylaws on the Samvera Wiki.
Steering asking for evolutionary rather than evolutionary. Coming up with election process - makes everything easier. Putting in place - how to allow people to vote on governance model.
starting from election process for steering - good priority - tied to clear responsibility and distribution of responsibilities -
Each Partner would get a vote (a single vote) -
Every cycle at DuraSpace - one person they talk to about voting -
Agreed on 1 vote per institution - to vote on Steering
AI: Go through and update contact list
Barrier to partnership has been the MOU and CLA and plan of what you want to do and showing that you've got a Samvera instance up and going
How do we figure partners in good standing? Financial contribution
Partners - monetary - in-kind/ encforcement of that - Community manager - checking in with steering, etc.. working with tech coorindator to establish controbutions of FTEs. Did these people actualy do any work?
Steering the option to de-Partner someone? Probably automatic - not make the bar super high. Language "board member has to make a personally significant financial contribution".
"Good standing" notion rather than kicking someone out - take that to Steering. Don't worry about the gap. Enforcement via body of partners?
difference between project mgmt council (PMC) for each project - and component council - should we have separate PMCs as separate for major products - and one PMC for Component group
Group 2 (Simeon, Anna, Ryan: Stable Communications// Coordination Plan)
...