Governance vs. Charter

Toshio Kuratomi a.badger at gmail.com
Tue Nov 5 19:21:44 UTC 2013


On Tue, Nov 05, 2013 at 12:45:31PM -0500, Deborah Rieden wrote:
> Hello,
> 
> At the meeting today we discussed "Governance" vs "Charter".
> I just wanted to make clear what my understanding of this.
> 
> Governance (how we operate) defines 
> - the members in this group
> - how to fill membership openings
> - how we make decisions (voting, email, etc)
> - how we modify our "Governance"
> This is similar to the Cloud wiki [1].
> 
> Charter (what we do) defines
> - what we are supposed to be doing
> This is what we need to come up with.
> 
> Is this similar to what you are thinking?
> 

+1

For our governance document, here's the draft I promised at the meeting:
https://fedoraproject.org/wiki/User:Toshio/Env_and_Stacks_Governance

Things of note:
* Based on the Cloud WG but with differences
* Under membership, I changed unanimous consent to "When a position in the
  group becomes available, we will call for volunteers and then fill the
  position according to which volunteer the existing members feel is most
  suitable."  I tried to choose wording that preserved most of the same
  spirit but got rid of the word unanimous which can be dangerous if there's
  a limited pool of volunteers and none of them are satisfactory to
  everyone.
* Making Decisions:
  * I added a note that we'll have more meetings during this
    initial phase but afterwards will move to being like the Cloud WG anddo
    business on the mailing list instead.  I gave us a January 2014 deadline
    for that as it is when other WG deliverables are due (please correct that
    if I have my dates wrong).
  * I added that the two meeting times would be on Tuesday at 13:00UTC and
    16:00 UTC.  Need to add something that shows which weeks are which (and
    what happens when we skip for holidays).  That can be a link to
    a different page, though.  Also update that if we decide that 13:00 UTC
    is not the alternate meeting time that we want (drieden and I would be
    unable to attend [or only sporadically]; slavek will be unable to attend
    the 16:00UTC meeting time).
    : http://whenisgood.net/fedenvstk/results/q3gmp7
  * I changed the impact of abstentions.  Instead of an abstention being
    equivalent to a -1 (as it didn't help to reach +5) abstentions serve to
    decrease the number of positive votes needed to pass something.  Since
    we will have to (if we're going to take on the role of incubating fresh,
    unknown ideas) deal with things that we don't have a lot of personal
    knowledge of, it seemed particularly important that we allow this.
  * Adapted voting procedures to work with a mailing list.  The cloud WG
    assumed a trac instance would be available to vote in.  I think that
    voting in tickets might be a good reason to have trac even if we don't
    use it for anything else.  It would be easier to keep track of than what
    I came up with for voting on the mailing list, at least.

> [1] https://fedoraproject.org/wiki/Cloud/Governance
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/env-and-stacks/attachments/20131105/0e5c84ee/attachment.sig>


More information about the env-and-stacks mailing list