Greater Los Angeles Drupal Governance Policy (old draft)

You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

This governance policy went into effect on April 21, 2013, and this wiki page is here for historical purposes. See the meeting minutes from the governance meetup at http://groups.drupal.org/node/289988#comment-912503 for details.

This wiki document is a formal proposal for the governance policy of the Greater Los Angeles Drupal group (formerly Downtown Los Angeles Drupal). It should be considered a draft until further notice and is editable at http://groups.drupal.org/node/230018/edit

So long as this is a wiki document on groups.drupal.org, it is editable by a growing number of members of the larger Drupal community. We ask our neighbors that the following policy be written by its group members and not by the larger community.

Discussion is welcome from all interested parties and that discussion should take place in the comments below rather than inline in the document itself.

Table of Contents

Shared Goals and Values

The Greater Los Angeles Drupal group is dedicated to fostering the Drupal software and its community. It is our hope that this governance policy helps encourage trust in our group and its leadership by the public and the members of our group.

Our leadership team endeavors to actively empower and support volunteers and attendees in the Greater Los Angeles Area, and to provide resources (venues, guidance, equipment, raffle prizes, etc.) and an open governance model with consistency, transparency and accountability.

We strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members. If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of a positive return on that investment and being recognized, in an appropriate manner, for your contribution.

The best and quickest way to invest yourself and improve the group is to volunteer. If you want want more meetups in your area, organize one and post it! If you want more presentations on web accessibility, give it yourself! If you got lost on the way to the meetup and want better directions, write it up and post it!

Having consistency, transparency and accountability are vital for our group's health, but more important and more powerful is volunteering. The Greater Los Angeles Drupal group provides unlimited opportunities and encouragements for its members to volunteer, as well as the tools to help them.

Discuss our shared goals and values HERE

Code of Conduct

At all times, our members are asked and expected to abide by the Drupal Code of Conduct, which outlines our shared values around conduct within our community:

We do not tolerate harassment of group members in any form. If you feel threatened or violated as a result of bullying, intimidating, harassing, abusive, discriminatory, derogatory or demeaning conduct, please notify a group organizer immediately. Likewise, please notify a group organizer immediately if you notice that someone else is being subjected to such behavior.

Discuss our code of conduct HERE

Transparency

As a Drupal user group, we will naturally use our group site at http://groups.drupal.org/node/219129 for a large portion of our online infrastructure. Most if not all of our decisions are made online in our group site and in person at our meetups. Whenever possible, our meetups are broadcasted via video conference so that as many people can attend and participate as possible.

For governance meetups (i.e. meetups that involve the group's membership structure, physical and online resources and the sharing of those resources), we will post in our group site at http://groups.drupal.org/node/219129 the date, place, time and agenda of those meetups at least 2 weeks in advance (whenever possible), as well as any subsequent minutes.

Discuss our need for transparency HERE

Accountability

We are here to promote Drupal and foster the Drupal software and community. In other words, we are here for you and depend on your feedback and criticism in order to better provide what our group's members need and want.

There are several mechanisms for our members to share suggestions and complaints. In addition to open governance meetups, we have a discussion forum at http://groups.drupal.org/node/add/story?gids[]=219129 for public discussions and an organizers [at] drupal [dot] la email address if our members wish to contact the group organizers privately.

Discuss our need for accountability HERE

Conflict Management and Resolution

We don't want to focus on negative things, but sometimes negative things happen. One of the responsibilities of our user group's leadership team is to deal with conflict. If we're asked to speak on behalf of a member involved in an incident, we will do that with the best interests of the community at heart. If there is a disciplinary incident, we are prepared to do that as well. We prefer the former.

In the event of a conflict, the parties involved agree to manage and resolve their conflict professionally and privately between themselves as to not impact the larger group. If the parties involved cannot find resolution, we will offer to bring in an outside facilitator that all interested parties can agree upon to help guide the resolution process.

If the parties involved can't agree to a facilitator within a reasonable period of time, or the conflict resolution process fails (as determined by the facilitator), these parties automatically agree to a cooldown period. A reasonable cooldown period may be 1 month, 3 months or 6 months, depending on the severity of the incident and as agreed to by the Greater Los Angeles Drupal group organizers.

During a cooldown period, the parties involved agree to stop volunteering or working together on shared projects or events. The parties involved may also be prevented from attending, speaking, organizing, sponsoring or volunteering at user group events, including meetups, camps and conferences.

Discuss conflict management and resolution HERE

Definition of Roles

Member

When this document refers to the word "member", we mean a person who has attended our events in the Greater Los Angeles Area, has joined this group and is listed in the member list at http://groups.drupal.org/og/users/219129, simply identifies as a member of this group, or any combination of the above.

There are no membership dues and there is no secret handshake.

Volunteer

This is an open-source community that exists based on the actions of its volunteers. Anyone who contributes to this group as a member, presenter, organizer, etc. is by the nature of their actions a volunteer in our community.

We strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members.

Organizer

When this document refers to the word "organizer", we mean a group administrator who listed in the "Group organizers" list on the right-hand side of this page. In this context, organizers are event organizers as well as moderators of the group's content and membership and are considered the group's "leadership team".

These organizers have access to a set of tools for community building and content curation including OG Vocab, OG Panels and other OG-specific functionality (including content editing and OG broadcast), which enables them to make their volunteer efforts more effective.

If you'd like to join this list of volunteers, talk with any of the organizers listed in the "Group organizers" list, join the discussion in the comments below or at any of our governance meetings or post a request to our group site at http://groups.drupal.org/node/add/story?gids[]=219129 (this process is similar to the maintainer request policy for projects on Drupal.org at https://drupal.org/node/251466).

Again, there are no membership dues and there is no secret handshake. We may ask, however, that you make consistent and positive contributions to this group so that the group organizers can get to know you.

If an organizer is no longer directly involved in the running of the group or has acted in a way that negatively impacts the the larger group, they may be demoted to "member" status by another organizer.

Discuss our definition of roles HERE

Comments

christefano's picture

In the next few days, we're going to be going a little nuts editing this document and discussing it in the comments. This will potentially generate a lot of email notifications that will be sent out to group members.

At any time during — or in advance of — our editing spree, please take a moment to fine-tune your notifications:

  1. Go to your user account at http://groups.drupal.org/user
  2. Click the "Notifications" tab for your account
  3. Click the "Subscriptions" sub-tab (see attached screenshot)
    • Click the "edit" link next to the subscription for this thread and change the "Send interval" or "Status" settings to your liking (see attached screenshot), or:
    • Click the "drop" link to delete your subscription to this thread

At any time, you can resubscribe or unsubscribe to this thread by clicking the "Subscribe from: This post" or "Unsubscribe from: This post" node links (i.e. the links that appear at the bottom of the wiki document).

If any of these steps don't work for you, please open a support issue in the groups.drupal.org issue queue at http://drupal.org/project/issues/groupsdrupalorg or ask me privately. Any subsequent comments will hopefully be about this governance document and not how groups.drupal.org does or doesn't work.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Shared Goals and Values

mrjeeves's picture

Our leadership team endeavors to actively empower and support volunteers and attendees in the Downtown Los Angeles area, and to provide resources (venues, guidance, equipment, raffle prizes, etc.) and a governance model with consistency, transparency and accountability.

At all times, our members are asked and expected to abide by the Drupal Code of Conduct, which outlines our shared values around conduct within our community:

Chris.

Focus on business

mrjeeves's picture

I feel that we need to emphasize our desire to attract sponsors that can benefit from the members of the group that are either looking for developers, or to become a developer. There are many potential ways to approach this.

Chris.

Agreed. In the most general

christefano's picture

Agreed. In the most general sense, I think we should be attracting business of all kinds (not just sponsorships) by providing consistency and predictability in our group's leadership.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Policies

mrjeeves's picture

So I'm almost wondering if this would be a good place to link to a sort of "Policy of Involvement" document, or some similarly named document that would detail the exact effect that becoming a "sponsor" would provide. Both as an advertisement for sponsorship, and as a reference page for those wanting to help bring sponsors to our events.

Chris.

Ways to get involved

christefano's picture

This document doesn't explicitly mention sponsors, but I'm okay with that. We have a "Return on Investment" section that is very inclusive and says:

If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of a positive return on that investment.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

The "Shared Goals and Values"

christefano's picture

The "Shared Goals and Values" section is now back in the document. I split its content across the "Shared Goals and Values" and "Code of Conduct" sections.

I also took a liberty and added a new line that hasn't been discussed yet:

The Downtown Los Angeles Drupal group is dedicated to fostering the Drupal software and its community.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Consistency

mrjeeves's picture

The organizers of the group strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members.

If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of a positive return on that investment.

Chris.

Purpose?

mrjeeves's picture

I'm not entirely sure what the purpose of this section is. What role does play in governance? Is this a statement of promise from the organizers? Possibly some kind of expansion of the goals?

Chris.

Lets just cut to the chase

mrjeeves's picture

Lets just cut to the chase and call this whole section "Return on Investment"

Chris.

UPDATE

mrjeeves's picture

This has been added back to the document as the "Return on Investment" section.

Chris.

I am still confused by this section

Stew-bee's picture

When i read the term "Return on Investment" my first thought was a monetary return and I do not think that is what we mean.

I would suggest for the second paragraph something a long this line:

"If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of being recognized by the group, in an appropriate manor, for your contribution. This may range from a public thank-you, being listed as an event organizer, all the way to becoming a group organizer."

Thanks for the suggestion, Stew!

christefano's picture

Thanks for the suggestion, Stew! I think this is about "community engagement" more than anything else and per your comment on volunteering at http://groups.drupal.org/node/230018#comment-910343 I've moved it into our "Shared Goals and Values" section.

I've also rolled part of your suggested text back into the document:

We strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members. If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of a positive return on that investment and being recognized, in an appropriate manner, for your contribution.

(Emphasis mine.)

I believe we need to be somewhat careful about listing the ways that members may be recognized for their contributions and I didn't add add the specific examples you suggested. We may face a situation when someone says, "hey, I'm not being recognized!" and they'll point to this document for the grounds for claiming credit or being added as a group organizer.

My thoughts around this come from times when people actually added themselves as organizers to events that they didn't actually organize, complained publicly for not being asked to be a group organizer, and so on. This document shouldn't give anyone with these kinds of tendencies or inexperience of community management the tools they need to misappropriate the group and its resources.

What do you think, Stew?


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Looks Great

Stew-bee's picture

The update expresses what I was trying to get at. And you are right about not being as explicit when it comes to recognition.

Thanks

Great, I'm glad this

christefano's picture

Great, I'm glad this works.

Per our discussion at last week's GLAD governance meetup (and subsequent Downtown Drupal meetup), we're re-freezing the document. If there are no more changes to the document in the next 2 weeks, we'll publish it on April 21st (2 weeks from your comment).

Thank you for this contribution!


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Volunteering

Stew-bee's picture

I think we might want to talk more in the Governance Policy about how the key to success of the group is volunteering. And at the same time point out that a member can have increased input and influence over the group by volunteering. Expanding this section might be the place to put this info.

The best and quickest way to improve the group is to volunteer. You want more meet-ups in the valley, organize one and post it. You want more presentations on accessibility, give it yourself. Got lost on the way to the meet-up and want better directions, write it up and post it.

Having a group with transparency and accountability are virtual for the its health. But more important and more powerful is volunteering. And The GLAD Group provides unlimited opportunities and encouragements for its members to volunteer. And the tools to help them.

I agree 100% with all of

christefano's picture

I agree 100% with all of this. I've lifted these paragraphs and placed them (with a few minor edits) into the "Shared Goals and Values" section:

   http://groups.drupal.org/node/230018#shared-goals-and-values


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Transparency

mrjeeves's picture

Most if not all of our decisions are made online in our group site at http://groups.drupal.org/node/219129 and in person at our meetups. Whenever possible, our meetups are broadcasted via video conference so that as many people can attend and participate as possible.

As a Drupal user group, we will naturally use groups.drupal.org for a large portion of our online infrastructure.

For governance meetups (i.e. meetups that involve the group's membership structure, physical and online resources and the sharing of those resources), we will post in our group at http://groups.drupal.org/node/219129 the date, place and time of those meetups at least 2 weeks in advance, as well as the meeting agenda and minutes.

Chris.

For starters...

mrjeeves's picture

I feel that at the very least, these links should be reformed to showcase our new link http://groups.drupal.org/dtla

Chris.

Proposed rewrite

christefano's picture

As a Drupal user group, we will naturally use our group site at http://groups.drupal.org/dtla for a large portion of our online infrastructure. Most if not all of our decisions are made online in our group site and in person at our meetups. Whenever possible, our meetups are broadcasted via video conference so that as many people can attend and participate as possible.

For governance meetups (i.e. meetups that involve the group's membership structure, physical and online resources and the sharing of those resources), we will post in our group at http://groups.drupal.org/dtla the date, place and time of those meetups at least 2 weeks in advance, as well as the meeting agenda and minutes.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

UPDATE

mrjeeves's picture

This has been added back to the document

Chris.

2 weeks notice might be

christefano's picture

2 weeks notice might be ideal, but looking back at the governance conference calls that we've had recently it strikes me that we didn't set the agendas for those calls until a few days in advance.

I propose that we change "at least 2 weeks in advance" to "in advance whenever possible". What do you all think?


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

The "Transparency" section

christefano's picture

The "Transparency" section has been updated with feedback from this discussion.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Accountability

mrjeeves's picture

Our group organizers and moderators are here to promote Drupal and foster the Drupal software and community. In other words, we are here for you and depend on your feedback and criticism in order to better provide what our group's members need and want.

We are working on ways to provide mechanisms for our members to share suggestions and complaints.

Chris.

Details, details, details.

mrjeeves's picture

I feel that we should have some form of link or other direction regarding our plans for this movement. In the interest of transparency, I feel that we should refrain from saying are we working on something without actually linking to that 'something'.

Chris.

or delete this section until

oseldman's picture

or delete this section until there's something concrete?

I'm actually not opposed to

mrjeeves's picture

I'm actually not opposed to this

Chris.

Here are some

christefano's picture

Here are some possibilities:

  1. We could create a project on Drupal.org for the Downtown Los Angeles group and utilize the issue queue for handling support requests, complaints and so on. All feedback and criticism would be public for all the world to see.
  2. We could ask that when members have feedback and criticism that they post a discussion topic here at http://groups.drupal.org/dtla
  3. We could have a separate site (whether it's Meetup.com, DowntownDrupal.org or another site is immaterial at this point) that has a contact form. This utilizes non-Drupal.org infrastructure but makes it possible for members to contact the organizers privately if they wish.
  4. We could officially request that OG Contact be installed on groups.drupal.org. I don't know if this will go anywhere but it's worth a shot.

There are probably more, but I'd like to put in place a method of being contacted rather than delete the section.

You know… looking at this list, I propose that we consider enacting all four options.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Here, here.

mrjeeves's picture

I agree that we should enact all four solutions, though I would like to propose that there be a universal introduction to these "interaction points" that is displayed prominently at each point to help foster interaction, rather than distraction from the various possible methods.

This may be a point towards having an organizers [at] downtowndrupal [dot] org email that can be used to alert the group when someone is attempting to provide feedback

Chris.

Excellent suggestion

oseldman's picture

Excellent suggestion Chris, and thanks to Christefano for getting this set up already.

Should a link to this email be provided on the group's main page? On the governance wiki? Both?

The "Accountability" section

christefano's picture

The "Accountability" section is now back in the document:

   http://groups.drupal.org/node/230018#accountability

We've implemented 3 of the 4 suggested approaches so far. The one we haven't created yet is a public project and issue queue on Drupal.org, which I think is still a good idea.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Conflict Management and Resolution

mrjeeves's picture

In the event of a conflict, the parties involved agree to manage and resolve their conflict professionally and privately between themselves as to not impact the larger group.

If the parties involved cannot find resolution, we will — as a group who cares about our membership — offer to bring in an outside facilitator that all interested parties can agree upon to help guide the resolution process.

If the parties involved can't agree to a facilitator within a reasonable period of time, or the conflict resolution process fails (as determined by the facilitator), these parties automatically agree to a cooldown period. During this period, the parties involved agree to stop volunteering or working together on shared projects or events.

Chris.

UPDATE

mrjeeves's picture

This section has been added back to the document.

Chris.

What should this cooldown

christefano's picture

What should this cooldown period be? 3 months? 6 months? 1 year?

As an aside, there's a discussion about a "conflict resolution team" for the Drupal community at http://drupal.org/node/1561772 that's probably worth paying attention to.

I'm okay with adding that as an option later to this section, but I don't believe we should default to it as the only course of action.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

We discussed the definition

christefano's picture

We discussed the definition of a "cooldown period" at this week's governance meetup and the wording we collaborated on has been proposed at http://groups.drupal.org/node/230018#comment-894688


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Definition of Roles

mrjeeves's picture

Member

When this document refers to the word "member", we mean a person who has attended events in the Downtown Los Angeles area, has joined this group and is listed in the member list at http://groups.drupal.org/og/users/219129, simply identifies as a member of this group, or any combination of the above.

There are no membership dues and there is no secret handshake.

Volunteer

This is an open-source community that exists based on the actions of its volunteers. Anyone who contributes to this group as a member, presenter, organizer, etc. is by the nature of their actions a volunteer in our community.

Organizer

When this document refers to the word "organizer", we mean a group administrator who listed in the "Group organizers" list on the right-hand side of this page. In this context, organizers are event organizers as well as moderators of the group's content and membership and are considered the group's "leadership team".

These organizers have access to a set of tools for community building and content curation including OG Vocab, OG Panels and other OG-specific functionality (including content editing and OG broadcast), which enables them to make their volunteer efforts more effective.

If you'd like to join this list of volunteers, post a request to our group at http://groups.drupal.org/node/add/story?gids[]=219129 (this is similar to the co-maintainer request policy for projects on Drupal.org). You may also talk with any of the organizers listed in the "Group organizers" list, join the discussion in the comments below or at any of our governance meetups.

Again, there are no membership dues and there is no secret handshake. We may ask, however, that you make consistent and positive contributions to this group so that the group organizers can get to know you.

If an organizer is not active, is no longer directly involved in the running of the group, or has acted in a way that negatively impacts the the group, they may be demoted to "member" status by another organizer. We are working on ways to provide an open and transparent mechanism for this process.

Chris.

For the "how to become a

oseldman's picture

For the "how to become a group organizer" i think we should put an emphasis on "talk with organizers" and "join the discussion" and then mention the more formal process of creating a node with the official request to be added.

Add this to organizers

mrjeeves's picture

The organizers of the group strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members.

Chris.

Here is a proposed revision

christefano's picture

Here is a proposed revision of the "Definition of Roles" section. Changes are italicized and incorporate the feedback in the above comments at http://groups.drupal.org/node/230018#comment-754153 and http://groups.drupal.org/node/230018#comment-754178

I also removed the "We are working on ways to provide an open and transparent mechanism for this process" sentence as I believe we have this open and transparent mechanism already via our open conference calls and the publishing of the meeting minutes.

Also taken out is the "not active" part of "If an organizer is not active or is no longer directly involved in the running of the group". Not being directly involved is the same as not being active.

Member

When this document refers to the word "member", we mean a person who has attended events in the Downtown Los Angeles area, has joined this group and is listed in the member list at http://groups.drupal.org/og/users/219129, simply identifies as a member of this group, or any combination of the above.

There are no membership dues and there is no secret handshake.

Volunteer

This is an open-source community that exists based on the actions of its volunteers. Anyone who contributes to this group as a member, presenter, organizer, etc. is by the nature of their actions a volunteer in our community.

The organizers of the group strive to provide consistent guidance and support as well as the consistent recognition of volunteer efforts of group members.

Organizer

When this document refers to the word "organizer", we mean a group administrator who listed in the "Group organizers" list on the right-hand side of this page. In this context, organizers are event organizers as well as moderators of the group's content and membership and are considered the group's "leadership team".

These organizers have access to a set of tools for community building and content curation including OG Vocab, OG Panels and other OG-specific functionality (including content editing and OG broadcast), which enables them to make their volunteer efforts more effective.

If you'd like to join this list of volunteers, talk with any of the organizers listed in the "Group organizers" list, join the discussion in the comments below or at any of our governance meetings or post a request to our group at http://groups.drupal.org/node/add/story?gids[]=219129 (this is similar to the maintainer request policy for projects on Drupal.org at https://drupal.org/node/251466).

Again, there are no membership dues and there is no secret handshake. We may ask, however, that you make consistent and positive contributions to this group so that the group organizers can get to know you.

If an organizer is no longer directly involved in the running of the group or has acted in a way that negatively impacts the the larger group, they may be demoted to "member" status by another organizer.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

The "Definition of Roles"

christefano's picture

The "Definition of Roles" section has been moved back to the document:

   http://groups.drupal.org/node/230018#definition-of-roles


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

deleted

oseldman's picture

deleted
comment didn't show up as a reply

About this Group

mrjeeves's picture

If you make a positive investment of yourself in this group as a member, presenter, organizer, volunteer, etc., you have a reasonable expectation of a positive return on that investment.

Chris.

Is this about the group or the goals?

mrjeeves's picture

I'm kind of confused as to how this 'describes' the group. It feels more like a goal of the group to me, rather than a purpose. In that vien of thought, What is our purpose? Or more precisely, how is our purpose different here than on the main page of the group? Please elaborate.

Chris.

This section is really about

christefano's picture

This section is really about stating one of the group's shared values. I think by explicitly defining this shared value at the outset, we can help steer the direction of the group culture by acknowledging credit from the very beginning.

We can also use this definition to "fall back on" when in doubt or when the group leadership shifts as organizers become busy or step back from organizing and new organizers come in.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

I've removed the "About This

christefano's picture

I've removed the "About This Group" section from the document. I believe it was erroneously added while this document was being restructured last year.

The group's mission at http://groups.drupal.org/dtla works for me. More importantly, the values around participation and returns on investment are already included in the "Return on Investment" section:

   http://groups.drupal.org/node/230018#return-on-investment


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

We've recently banned a

christefano's picture

We've recently banned a member of the community and the experience around that may be instrumental in how this document speaks to our code of conduct and expectations around professionalism. I'm posting this comment to make a note of it so that we can discuss this at a future time.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

I suggest that we include the

christefano's picture

I suggest that we include the Drupal Code of Conduct by referencing it in this governance policy. My understanding is that this is a given since this code of conduct already applies to our user group and events.

That said, its purpose is to state the shared values and principles around behavior and it's fairly toothless when it comes to enforcement. For that, I've already proposed a policy around conflict resolution and management here:

   http://groups.drupal.org/node/230018#conflict-management-and-resolution

As far as the DrupalCon Code of Conduct goes, although it isn't finalized I do want to recognize the same need for an enforcement policy at our events. In its current form, the "When we need it, we ask for help" section looks especially relevant here. I'd like to incorporate something like that that in our governance policy.

We'll probably need a separate location where the contact information for the individual points of contact are listed. My preference is to use a wiki page here on groups.drupal.org so that any domain name or external website isn't a variable in case a conflict involves anyone who has access to that domain name or external website.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Over the weekend I caught up

christefano's picture

Over the weekend I caught up with someone who I met and got to know at events I helped organize in 2011. I learned that another member of the Drupal community had been stalking her and this was the reason she hadn't been back to our events.

It's too late to address what happened then, but having a framework for dealing with incidents like this in the future is a big priority for me. I've taken people aside in the past (to either talk with them or direct them to leave) and I have no problem doing it again, but I'd like to have this document be the framework for others when I or others aren't available in the moment.

I think the Conflict Management & Resolution section looks great, but it focuses on general disagreements and not immediately actionable behavior such as bullying and harassment.

So, I'd like to borrow the below section from the current draft version of the DrupalCon Code of Conduct and have placed it in our document under Code of Conduct.

We do not tolerate harassment of conference participants in any form. If you feel threatened or violated as a result of intimidating, harassing, abusive, discriminatory, derogatory or demeaning conduct, please immediately notify a conference staff member. Likewise, please immediately notify a staff member if you notice that someone else is being subjected to such behavior.

… and include the word, "bullying", and replace "conference participants" with "group members" and "conference staff member" with "group organizer". Please review:

   http://groups.drupal.org/node/230018#code-of-conduct


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

WordPress, one of our

christefano's picture

WordPress, one of our neighboring open source communities, recently underwent an incident when the WordCamp Foundation banned a company and its associates from "speaking, organizing, sponsoring or volunteering" at WordCamps:

   http://thenextweb.com/insider/2013/01/23/wordpress-org-bans-themeforest-...  

Without getting into the details of why they were banned, I'd like to simply borrow this wording — prevented from "speaking, organizing, sponsoring or volunteering" (but not attending) at events — when censuring those who misbehave egregiously.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Can we have a meeting on

christefano's picture

Can we have a meeting on Wednesday, February 27th, between 5-6pm, to finalize this policy and publish it?

   Link: http://groups.drupal.org/downtown-los-angeles/governance
   Short URL: http://ex.tl/ZMd  


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Per today's governance

christefano's picture

Per today's governance meeting, the wording at http://groups.drupal.org/node/230018#comment-886353 will be included to describe the "cooldown" period in our Conflict Resolution and Resolution section:

   http://groups.drupal.org/node/230018#conflict-management-and-resolution


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Conflict Resolution and Management

christefano's picture

Here is the proposed wording, following discussion at this week's governance meetup:

We don't want to focus on negative things, but sometimes negative things happen. One of the responsibilities of our user group's leadership team is to deal with conflict. If we're asked to speak on behalf of a member involved in an incident, we will do that with the best interests of the community at heart. If there is a disciplinary incident, we are prepared to do that as well. We prefer the former.

In the event of a conflict, the parties involved agree to manage and resolve their conflict professionally and privately between themselves as to not impact the larger group. If the parties involved cannot find resolution, we will offer to bring in an outside facilitator that all interested parties can agree upon to help guide the resolution process.

If the parties involved can't agree to a facilitator within a reasonable period of time, or the conflict resolution process fails (as determined by the facilitator), these parties automatically agree to a cooldown period. A reasonable cooldown period may be 1 month, 3 months or 6 months, depending on the severity of the incident and as agreed by the Downtown Drupal group organizers.

During a cooldown period, the parties involved agree to stop volunteering or working together on shared projects or events. The parties involved may also be prevented from speaking, organizing, sponsoring or volunteering at user group events, including meetups, camps and conferences.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

The "Conflict Management and

christefano's picture

The "Conflict Management and Resolution" section has been moved back to the document:

   http://groups.drupal.org/node/230018#conflict-management-and-resolution


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Okay, almost everything we

christefano's picture

Okay, almost everything we discussed at this week's governance meetup has been merged and / or added to the main document:

   http://groups.drupal.org/downtown-los-angeles/governance  

The document reads much better now! I'm going to take a break from this for a while and try to come back to it with some fresh eyes.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

This looks pretty good to me.

christefano's picture

This looks pretty good to me. I made a couple minor changes to the voice used in the document and now it's slightly less wordy. The change log is here:

   http://groups.drupal.org/node/230018/revisions

I also added a line to this document that describes the document itself:

It is our hope that this governance policy helps encourage trust in our group and its leadership by the public and the members of our group.

What say you, friends, colleagues, organizers and fellow Drupaleros?


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  
nodiac's picture

Hi There -

I would consider that it's important to be able to ban inflammatory people from events.

Hope this is helpful...

Exaltation of Larks
Founder
http://www.larks.la  
Droplabs
Robot Coordinator
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Dragonslayer
http://drupal.la  

This has been included in the


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

This policy is now in effect.

christefano's picture

This policy is now in effect. Congratulations, everyone!

I posted a comment on the meeting minutes from our last governance meetup. It describes the process for how the document was reviewed and eventually published:

   http://groups.drupal.org/node/289988#comment-912503

Now that the policy is being put into practice, I copied it from the wiki page and into an OG Panels page that is editable only by our group organizers. This wiki pages is being saved as-is for historical purposes.


Exaltation of Larks
Founder, CEO
http://www.larks.la  
Droplabs
Founder, Lead Burrito Analyst
http://droplabs.net  
Greater Los Angeles Drupal
Organizer, Drupal Adventure Guide
http://drupal.la  

Greater Los Angeles Drupal (GLAD)

Group events

Add to calendar

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: