governance

Accountabilities

  • translation / international issues
  • General FLO advocacy
  • Outreach to partner organizations
  • General research on related news in FLO, crowdfunding, co-ops etc.
  • Running Board elections (once that is in place)
  • Handling petitions (once in place)
  • Maintaining documentation

Domains

All functions & activities within the Circle

Policy: Permission to impact domains

Normally, you need permission to impact the Domains of other roles via your actions, per Constitution §1.3. However, for the purpose of §1.3, you are automatically considered to have explicit permission to impact all relevant domains via an action, if you share your intent to take that action in advance on the relevant mailing list and no one with a relevant domain asks you not to within 72 hours. Using this approach, you don’t even need to know the relevant domains that you might impact, because domain owners will have a chance to assess that for themselves and tell you.

Policy: Postpone Governance Proposal Crafting

If there is no concrete proposal, and discussion trying to create one goes on for longer than 5 minutes, any participant may table further discussion until the following meeting.

Policy: Asyncronous governance

You are permitted to share and discuss tensions and make proposals via the discuss mailing list. If no valid objection is raised within 72 hours of your proposal, or in the next governance meeting in which the proposal is discussed (whichever is sooner), your proposal shall be adopted as if in a governance meeting.

All proposals accepted in Governance meetings must be aired on the discuss mailing list, and will only go into affect if no valid objection is raised within 72 hours.

Policy: Meeting requirements

Partners are required to RSVP for governance & tactical meetings. Along with a ‘no’ RSVP, you must send any checklist items, metrics, or progress updates you would have shared had you been attending. The secretary may waive this requirement on a case-by-case basis.

Policy: Combined Tactical & Governance Meetings

If two holacracy meetings immediately follow one another, we may skip the closing round of the first & introductary round of the second, and consider them two parts of the same meeting.

Policy: Scrum Tactical Meetings

The Circle’s Tactical Meetings shall include process steps to allow space for iteration review and next iteration planning, using whatever more specific process is defined and published by Scrum Master (which must include the minimum steps required by the Constitution Section 4.3 for Tactical Meetings). The modified Tactical meeting process defined by Scrum Master shall still be facilitated by the elected Facilitator.

Further, Tactical Meetings must be scheduled by Secretary at whatever frequency and duration specified by Scrum Master, and Secretary must use best-effort to schedule Tactical Meetings on whatever target day(s) of the week are specified by Scrum Master.

Circle Resources

Policy: Spending

A partner who wishes to spend money must: (1) check in with Tresurer to ensure that enough money exists, (2) Bring a proposal or spending to a governance meeting and have it be accepted in every other way, and (3) the rep link brings it to the board for review

Lead Link

Purpose

  • Carry out the Snowdrift.coop mission as set by the Bylaws and Board

Accountabilities

  • Structuring the Governance of the Circle to enact the Snowdrift.coop mission
  • Assigning Partners to the Circle’s Roles; monitoring the fit; offering feedback to enhance fit; and re-assigning Roles to other Partners when useful for enhancing fit
  • Allocating the Circle’s resources across its various Projects and/or Roles
  • Establishing strategies for the Circle
  • Defining metrics for the circle
  • Enacting the anchor circle’s Purpose and Accountabilities

The General Manager also holds all un-delegated Circle-level Domains and Accountabilities.

Domains

  • Role assignments within the Circle

Filled by

Aaron Wolf

Rep Link

Purpose

Tensions relevant to process in the Super-Circle channeled out and resolved

Accountabilities

  • Representing Snowdrift class co-op members on the Board of Directors
  • Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Board
  • Providing visibility to the Board into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
  • Removing constraints within the broader Organization that limit the Sub-Circle

Filled by

William “Salt” Hale until 2016-06-01

Secretary

Purpose

  • Organize and record meetings

Accountabilities

  • Scheduling the Circle’s required meetings, and notifying all Core Circle Members of scheduled times and locations
  • Capturing and publishing the outputs of the Circle’s required meetings, and maintaining a compiled view of the Circle’s current Governance, checklist items, and metrics
  • Interpreting Governance and the Constitution upon request
  • Providing other roles with guidance and best practices for Holacracy implementation

Filled by

Stephen Michel until 2016-09-01

Facilitator

Purpose

  • Circle governance and operational practices aligned with the Constitution.

Accountabilities

  • Facilitating the Circle’s constitutionally-required meetings
  • Auditing the meetings and records of Sub-Circles as needed, and declaring a Process Breakdown upon discovering a pattern of behavior that conflicts with the rules of the Constitution

Filled by

William “Salt” Hale until 2016-09-01

Board

Accountabilities

  • Define Snowdrift.coop mission & website purpose

Domains

  • Snowdrift.coop mission

Filled by

The Board has not been created yet. Prior to its creation, Steering Committee acts in its place - Disputes resolved by decision of Aaron Wolf

Development Circle

Lead Link

Purpose

  • Carry out the Snowdrift.coop mission as set by the Bylaws and Board

Accountabilities

  • Structuring the Governance of the Circle to enact the Snowdrift.coop mission
  • Assigning Partners to the Circle’s Roles; monitoring the fit; offering feedback to enhance fit; and re-assigning Roles to other Partners when useful for enhancing fit
  • Allocating the Circle’s resources across its various Projects and/or Roles
  • Establishing strategies for the Circle
  • Defining metrics for the circle
  • Enacting the anchor circle’s Purpose and Accountabilities

The General Manager also holds all un-delegated Circle-level Domains and Accountabilities.

Domains

  • Role assignments within the Circle

Filled by

Bryan Richter

Rep Link

Purpose

Tensions relevant to process in the Super-Circle channeled out and resolved

Accountabilities

  • Representing Snowdrift class co-op members on the Board of Directors
  • Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Board
  • Providing visibility to the Board into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
  • Removing constraints within the broader Organization that limit the Sub-Circle

Filled by

Secretary

Purpose

  • Organize and record meetings

Accountabilities

  • Scheduling the Circle’s required meetings, and notifying all Core Circle Members of scheduled times and locations
  • Capturing and publishing the outputs of the Circle’s required meetings, and maintaining a compiled view of the Circle’s current Governance, checklist items, and metrics
  • Interpreting Governance and the Constitution upon request

Filled by

Facilitator

Purpose

  • Circle governance and operational practices aligned with the Constitution.

Accountabilities

  • Facilitating the Circle’s constitutionally-required meetings
  • Auditing the meetings and records of Sub-Circles as needed, and declaring a Process Breakdown upon discovering a pattern of behavior that conflicts with the rules of the Constitution

Filled by

Architect

Purpose

A core architecture for Snowdrift that enables rapid development and integrity of the codebase

Accountabilities

  • Defining the snowdrift technology stack, including languages, libraries, and frameworks, as well as standards for how, where, and when to use each
  • Prioritizing coding maintenance chores in the backlog
  • Defining code conventions

Domains

Snowdrift technology stack

Policy: Mechanism Ownership pharpend can define snowdrift technology stack in the mechanism library (in accordance with top level standards)

Filled by

Bryan Richter

Code QA

Accountabilities

  • Testing code
  • Code review

Filled by

Bryan Richter

Developer

Accountabilities

  • Implementing user stories, bug fixes, and chores in alignment with:
  • priorities set by Product Manager
  • technical standards and code conventions set by Architect

Note: includes css

Filled by

Bryan Richter Peter Harpending

Interaction Design

Accountabilities

  • Defining page existence, function, and content to fulfill the site purpose as defined by the Board and in accordance with the strategy as defined by Communications
  • Curating user stories

Domains

  • Page list & functions
  • Client-requirement user stories

Filled by

Robert Martinez Michael Siepmann

Visual Design

Accountabilities

  • Managing and publishing design plans and tickets
  • Creating illustrations and relevant designs that follow the design guidelines

Domains

  • Design guidelines
  • Branding

Filled by

Robert Martinez

Operations Circle

Lead Link

Purpose

  • Carry out the Snowdrift.coop mission as set by the Bylaws and Board

Accountabilities

  • Structuring the Governance of the Circle to enact the Snowdrift.coop mission
  • Assigning Partners to the Circle’s Roles; monitoring the fit; offering feedback to enhance fit; and re-assigning Roles to other Partners when useful for enhancing fit
  • Allocating the Circle’s resources across its various Projects and/or Roles
  • Establishing strategies for the Circle
  • Defining metrics for the circle
  • Enacting the anchor circle’s Purpose and Accountabilities

The General Manager also holds all un-delegated Circle-level Domains and Accountabilities.

Domains

  • Role assignments within the Circle

Filled by

Aaron Wolf

Rep Link

Purpose

Tensions relevant to process in the Super-Circle channeled out and resolved

Accountabilities

  • Representing Snowdrift class co-op members on the Board of Directors
  • Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Board
  • Providing visibility to the Board into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
  • Removing constraints within the broader Organization that limit the Sub-Circle

Filled by

Secretary

Purpose

  • Organize and record meetings

Accountabilities

  • Scheduling the Circle’s required meetings, and notifying all Core Circle Members of scheduled times and locations
  • Capturing and publishing the outputs of the Circle’s required meetings, and maintaining a compiled view of the Circle’s current Governance, checklist items, and metrics
  • Interpreting Governance and the Constitution upon request

Filled by

Facilitator

Purpose

  • Circle governance and operational practices aligned with the Constitution.

Accountabilities

  • Facilitating the Circle’s constitutionally-required meetings
  • Auditing the meetings and records of Sub-Circles as needed, and declaring a Process Breakdown upon discovering a pattern of behavior that conflicts with the rules of the Constitution

Filled by

Content Manager

Accountabilities

  • Defining storage location of general documentation (not team specific)
  • Ensuring documentation is adequately findable and up to date

Filled by

Iko ~

Dev Ops

Accountabilities

  • Web server maintenance
  • Mail server maintenance
  • Keeping IRC bot running
  • Tweaking live infrastructure
  • Deploying applications

Domains

  • Backend tech infrastructure

Filled by

Bryan Richter

Checklist Items

Weekly: back up snowdrift databases (civicrm, website, taiga)

Checklist

  • Data backups

Legal

Accountabilities

  • Assuring licensing consistency across project
  • Updating, reviewing, handling any necessary legal enforcement
  • Defining primary Bylaws and other issues
  • Coordinating with Treasurer on taxes and other relevant legal issues

Filled by

Aaron Wolf

Security

Accountabilities

  • Creating guidelines on security issues
  • Creating security documentation
  • Idenfitying where we’re most vulnerable and prioritizing security issues
  • Avoiding money fraud
  • Managing patrons’ financial info
  • Managing patrons’ identity data
  • Mitigating unauthorized access to servers
  • Securing backups
  • Defining access control schemes
  • Mitigating unauthorized account usage
  • on Snowdrift.coop, taiga.io, and any other systems

Domains

Team Security

Standards that ensure backups are secure and control internal authorization (to access domain servers, etc)

User Security

Standards that ensure user data is secure

Filled by

Bryan Richter William “Salt” Hale

Treasurer

Accountabilities

  • Accounting for all income and expenses
  • Writing checks / submitting payments as needed for basic upkeep costs, contract work, travel, promotion, etc.
  • Updating public accounting regularly
  • Filing taxes etc. (in coordination with other officers and board)

Domains

  • Bank accounts
  • Checks
  • Expenses
  • Financial records

Filled by

Aaron Wolf

Outreach Circle

Lead Link

Purpose

  • Carry out the Snowdrift.coop mission as set by the Bylaws and Board

Accountabilities

  • Structuring the Governance of the Circle to enact the Snowdrift.coop mission
  • Assigning Partners to the Circle’s Roles; monitoring the fit; offering feedback to enhance fit; and re-assigning Roles to other Partners when useful for enhancing fit
  • Allocating the Circle’s resources across its various Projects and/or Roles
  • Establishing strategies for the Circle
  • Defining metrics for the circle
  • Enacting the anchor circle’s Purpose and Accountabilities

The General Manager also holds all un-delegated Circle-level Domains and Accountabilities.

Domains

  • Role assignments within the Circle

Filled by

William “Salt” Hale

Rep Link

Purpose

Tensions relevant to process in the Super-Circle channeled out and resolved

Accountabilities

  • Representing Snowdrift class co-op members on the Board of Directors
  • Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Board
  • Providing visibility to the Board into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
  • Removing constraints within the broader Organization that limit the Sub-Circle

Filled by

Secretary

Purpose

  • Organize and record meetings

Accountabilities

  • Scheduling the Circle’s required meetings, and notifying all Core Circle Members of scheduled times and locations
  • Capturing and publishing the outputs of the Circle’s required meetings, and maintaining a compiled view of the Circle’s current Governance, checklist items, and metrics
  • Interpreting Governance and the Constitution upon request

Filled by

Facilitator

Purpose

  • Circle governance and operational practices aligned with the Constitution.

Accountabilities

  • Facilitating the Circle’s constitutionally-required meetings
  • Auditing the meetings and records of Sub-Circles as needed, and declaring a Process Breakdown upon discovering a pattern of behavior that conflicts with the rules of the Constitution

Filled by

Coding Volunteer Liaison

Accountabilities

  • Processing merge requests
  • Volunteer collaboration, Intake, Outreach, Mentorship
  • Communicating status and progress updates to the public
  • Maintain lists of newbie-friendly development tasks ## Filled by

Bryan Richter

Communications

Purpose

  • Communicate the vision to the world

Accountabilities

  • Reviewing media as it is published
  • Publishing updates from other roles/circles on work progress
  • Creating promotional material
  • Coordinating with Visual Design on illustration
  • Managing press material, press releases, assets
  • Interviews/podcasts
  • Representing Snowdrift.coop at events e.g.: speaking at conferences, expos
  • Publishing co-op member newsletter
  • Defining communications strategy

Domains

  • Published Media
  • Press Material

Filled by

Aaron Wolf

Community

Purpose

  • Organize contacts, manage relations with wider network, users, volunteers…

Accountabilities

  • Recruiting Projects
  • Networking with partner organizations
  • Onboarding Volunteers
  • Recruiting volunteers
  • Managing CiviCRM, including entering contact info
  • Obtaining co-op member feedback
  • Making newcomers feel welcome in IRC
  • Moderating IRC

Domains

  • CiviCRM
  • local meetups

Filled by

William “Salt” Hale

Design Volunteer Liaison

Accountabilities

  • Onboarding of design-focused volunteers
  • Volunteer collaboration, Intake, Outreach, Mentorship
  • Communicating status and progress updates to the public

Filled by

Iko ~

Fundraising

Accountabilities

  • Identifying and applying for grant applications
  • Coordinating pre-launch fund-drives / other fundraising

Filled by

Aaron Wolf

Market Research

Accountabilities

  • conducting, analyzing, and presenting research about the broader ecosystem outside of snowdrift.coop, the history of public goods and related concerns

Filled by

Aaron Wolf

User Research

Accountabilities

  • conducting, analyzing, and presenting research about user interactions with the snowdrift.coop site and ecosystem

Filled by

Michael Siepmann

Project Manager

Accountabilities

  • Keeping up with overall progress of the project and providing insight into that progress upon request
  • Advising on use of organizational tools

Filled by

Stephen Michel

Scrum Master

Purpose

Implement, measure, champion, and support agile software development practices

Accountabilities

  • Coaching circle members on Agile/Lean principles and practices as-needed or as-requested
  • Defining and implementing issue tracking (i.e. epics, features, and bugs), and estimating workflow, processes, and policies
  • Defining meeting processes and frequency, and facilitating meetings not required by the Holacracy Constitution

Filled by

Bryan Richter Stephen Michel