Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Date

Attendees

Goals

Discussion items

TimeWhatWhoNotes
10 minReview feedback on the Governance Review document Steering has reviewed; review their feedback; make any relevant changes.
30 minDiscuss potential paths forward for developing a governance model recommendation

Two paths to consider:

  1. Map the components of the proposed models to desired attributes.
    1. Review the desired attributes listed in the Governance Review document;
    2. Divide the working group up and map components of the proposed models to attributes.
    3. Synthesize components of the models to develop a proposed model
  2. Draft a small solution and grow
    1. Divide the working group up and assign an attribute
    2. Sub-groups develop a model based on one desired attribute
    3. Come back together to synthesize.
10 minWrap up and confirm action items


Action items

  •  

Notes

We did get our document in on time.  We're leaving the document open for review.  Still encouraging people to make comments other places.  

Potential paths forward for consideration:

The next stage is to draft a proposed model - by February 16th

1)Can map components from Porposed models that are out there to list of desired attributes - we can divide that up, synthesize components into one model

2) each team take one desired attributes and come up with a model to match the attribute


Can he a cohesive, unified model with a piecemeal process?

People hated the ALA model but is the Red Cross/ Apache model may be better

Evviva - ALA is really top heavy 

Develop models in pairs? - more cohesive approach - 

We may have more wiggle room - getting something to partners meeting and getting it to people prior to the partner's meeting

Do we know the problems that we're trying to sort out? - The attributes are a polite way of saying what the issues are.  

  • Roadmaps often aren't community defined.  
  • Stable communication isn't taking place.
  • Formal contributions from partners aren't always clear.  
  • Relationships between groups aren't clearly articulated.  Ex:  difference between Steering and Partners

There is a reason Michele is here.  He wasn't part of prior conversations.  

Might make sense to break up along lines - based on why we're here.  3 of each kind.  In order to address anxiety issues - we'll need to go back to Steering via Mark.  Once we're in teh covo, it'll be more clear how to use Mark.

  • Community not in governance group (avviva, nabeela, simeon)
  • Community in governance group (maria, michele, anna)
  • Facilitating the group (carolyn, ryan, rosy)

Drafting  a model based on those desired attributes - each group has one attribute and will design a model based upon that attribute

Plan to address anxiety - just table that until we're getting plans out.  Think about it as we're writing out our models.  

"clearly articulated relationships" tied to "new roles"

Given Evviva's schedule - 

  •  
  • No labels