GitHost.io will be shut down on June 1, 2019. At that point this instance will be unreachable and all data will be irrevocably deleted. More details at https://about.gitlab.com/gitlab-hosted/#githost-is-shutting-down-on-june-1st-2019

Commit 38965049 authored by Stephen Michel's avatar Stephen Michel

Merge branch 'overhaul' into 'master'

update governance doc format and overall structure

Closes #8, #7, and #5

See merge request !7
parents 484983ec a185f848
- 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
- Define Snowdrift.coop mission & website purpose
- Snowdrift.coop mission
The Board has not been created yet. Prior to its creation, Steering Committee acts in its place
- Disputes resolved by decision of Aaron Wolf
- 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
### Snowdrift technology stack
**Policy: Mechanism Ownership**
pharpend can define snowdrift technology stack in the mechanism library (in accordance with top level standards)
A core architecture for Snowdrift that enables rapid development and integrity of the codebase
- 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
- Circle governance and operational practices aligned with the Constitution.
- 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
- Page list & functions
- Client-requirement user stories
- 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.
- Role assignments within the Circle
- Carry out the Snowdrift.coop mission as set by the Bylaws and Board
- 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
Tensions relevant to process in the Super-Circle channeled out and resolved
- Managing and publishing design plans and tickets
- Creating illustrations and relevant designs that follow the design guidelines
- 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
William "Salt" Hale _until 2016-09-01_
- Circle governance and operational practices aligned with the Constitution.
## Purpose
Circle governance and operational practices aligned with the Constitution.
## Filled by
### Term
## 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
## Purpose
Maintain a "well-oiled" team
## Filled by
## Accountabilities
- Deciding to bring on new partners
- Resolving conflict amongst partners
- Looking after Partners' wellness (ie, not overworked, not feeling useless,..)
## Purpose
The Lead Link holds the Purpose of the overall Circle.
## Filled by
## Accountabilities
- Structuring the Governance of the Circle to enact its Purpose and Accountabilities
- 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 priorities and Strategies for the Circle
- Defining metrics for the circle
- Removing constraints within the Circle to the Super-Circle enacting its
- Purpose and Accountabilities
The Lead Link also holds all un-delegated Circle-level Domains and Accountabilities.
## Domains
Role assignments within the Circle
## Purpose
Keeping us out of jail
## Filled by
Aaron Wolf
## Accountabilities
- Defining and reviewing Bylaws
- Coordinating with Treasurer on taxes
- Updating, reviewing, handling any necessary legal enforcement
## Purpose
Making sure that snowdrift.coop has a consistent and recognizable visual style.
## Filled by
Robert Martinez (mray)
## Accountabilities
- Mainintaing visual style guidelines
- Reviewing media we publish for alignment with our visual style
## Domains
### Branding
#### Brand Guidelines
You may publish materials that use Snowdrift.coop branding as long as you follow the brand guidelines.
## Purpose
Writing text for effective communication
## Filled by
Aaron Wolf
Michael Siepman
## Accountabilities
- Replacing lorem ipsum text (on the website, on flyers, etc)
- Managing text assets (https://wiki.snowdrift.coop/about)
## Purpose
Creating designs and assets for publishing
## Filled by
Robert Martinez (mray)
iko ~
## Accountabilities
- Creating promotional material (flyers, stickers, t-shirts, etc)
- design / shwag / whatever
- Managing visual assets
- Deciding on the look and feel of infrastructure customizations
## Purpose
Customizing applications to suit Snowdrift.coop's unique needs.
## Filled by
fr33?
## Accountabilities
- Deciding on platforms that would best support the circle's needs.
- Customizing those platforms (front and/or backend) to fit snowdrift.coop.
## Purpose
Circle governance and operational practices aligned with the Constitution.
## Filled by
### Term
## 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
## Purpose
Generate funds for cases when the mechanism is not yet sufficient
## Filled by
Aaron Wolf
## Accountabilities
- Identifying and applying for grants
- Coordinating pre-launch fund-drives / other fundraising
## Purpose
The Lead Link holds the Purpose of the overall Circle.
## Filled by
## Accountabilities
- Structuring the Governance of the Circle to enact its Purpose and Accountabilities
- 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 priorities and Strategies for the Circle
- Defining metrics for the circle
- Removing constraints within the Circle to the Super-Circle enacting its
- Purpose and Accountabilities
The Lead Link also holds all un-delegated Circle-level Domains and Accountabilities.
## Domains
Role assignments within the Circle
## Purpose
Handle connections with individuals or projects looking to create a stronger bond with Snowdrift.coop
## Filled by
William "Salt" Hale
Aaron Wolf (wolftune)?
## Accountabilities
- Recruiting partner projects
- Growing & directing volunteer community
- Managing CiviCRM, including entering contact info
- Networking with partner organizations
- Maintain https://wiki.snowdrift.coop/community/how-to-help
## Purpose
Trust-building (showing the public that we've done our homework)
## Filled by
Aaron Wolf
## Accountabilities
- conducting, analyzing, and presenting research about the broader ecosystem
outside of snowdrift.coop, the history of public goods and related concerns
## Purpose
Foster community engagement
## Filled by
William "Salt" Hale
Jason "JazzyEagle" Harrer?
## Accountabilities
- Decide on and enforce rules
- [IRC] Channel welcomer
- Publishing co-op member newsletter
- Obtaining co-op member feedback
\ No newline at end of file
## Purpose
Networking to increase credibility (through connections), brand recognition, and website traffic.
## Filled by
Salt
wolftune
## Accountabilities
- Representing Snowdrift.coop at events e.g.: speaking at conferences, expos, other organizations
- Giving talks
- Interviews/podcasts
- Publishing blog
- Press releases
## Purpose
Establish the snowdrift.coop brand; attract interest and continue to engage with the existing community.
## Purpose
Within the Super-Circle: the Rep Link holds the Purpose of the Sub-Circle.
Within the Sub-Circle: Tensions relevant to process in the Super-Circle channeled out and resolved.
## Filled by
## Accountabilities
- Removing constraints within the broader Organization that limit the Sub-Circle
- Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Super-Circle
- Providing visibility to the Super-Circle into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
- 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
## Purpose
Steward and stabilize the Circle’s formal records and record-keeping process.
## Filled by
### Term
## 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.
## Domains
### All constitutionally-required records of the Circle
## Purpose
Deploying and maintaining infrastructure to support the circle.
## Filled by
Bryan Richter
## Accountabilities
- Deploying the site regularly
- Keeping software up to date
- Domain stuff
- Web server maintenance
- Mail server maintenance
- Keeping IRC bot running
- Tweaking live infrastructure
- Deploying applications
## Domains
### Backend tech infrastructure
## Purpose
Making sure that we have a cohesive vision and that published materials communicate it effectively
## Filled by
Aaron Wolf
## Accountabilities
- Defining communications strategy
- Reviewing media we publish for alignment with our vision
## Domains
### Official/published materials
../Website Circle/Outreach cross link.md
\ No newline at end of file
### All functions & activities within the Circle
## Purpose
**Policy: Permission to impact domains**
Successful crowdmatching platform
## Strategies
Prioritize features according to our [roadmap](https://tree.taiga.io/project/snowdrift/epics/).
## Domains
### All functions & activities within the GCC
#### **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**
#### **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**
#### **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.
You are permitted to share and discuss tensions and make proposals via the team 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**
#### **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**
#### **Policy: Combined Tactical & Governance Meetings**
If two holacracy meetings of the same circle immediately follow one another, the facilitator may skip the closing round of the first & introductary round of the second.
### Circle Resources
**Policy: Spending**
Any partner may spend money if they: (1) check in with Tresurer to ensure that enough money exists, (2) In a tactical meeting, following the governance process, pass a proposal for spending, and (3) have it approved by the board (the rep link will bring the proposal to the board after step 2).
## Purpose
Within the Super-Circle: the Rep Link holds the Purpose of the Sub-Circle.
Within the Sub-Circle: Tensions relevant to process in the Super-Circle channeled out and resolved.
## Filled by
## Accountabilities
- Removing constraints within the broader Organization that limit the Sub-Circle
- Seeking to understand Tensions conveyed by Sub-Circle Circle Members, and discerning those appropriate to process in the Super-Circle
- Providing visibility to the Super-Circle into the health of the Sub-Circle, including reporting on any metrics or checklist items assigned to the whole Sub-Circle
## Purpose
Implement, measure, champion, and support agile software development practices
## Filled by
- Bryan Richter
- Stephen Michel
## Accountabilities
- Coaching circle members on Agile/Lean principles and practices as-needed or as-requested
- Defining and implementing workflow for organizational tools
- Defining meeting processes and frequency, and facilitating meetings not required by the Holacracy Constitution
- Keeping up with overall progress of the project and providing insight into that progress upon request
- Keeping up with overall progress of the project and providing insight into that progress upon request
- 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
## Purpose
Steward and stabilize the Circle’s formal records and record-keeping process.
## Filled by
### Term
## 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.
## Domains
### All constitutionally-required records of the Circle
## Purpose
Protecting our systems from people with malicious intent.
## Filled by
Bryan Richter
William "Salt" Hale
## Accountabilities
- Creating guidelines on security issues
- Creating security documentation
- Idenfitying where we're most vulnerable and prioritizing security issues
......@@ -9,3 +20,6 @@
- Defining access control schemes
- Mitigating unauthorized account usage
- on Snowdrift.coop, taiga.io, and any other systems
## Domains
## Purpose
Making sure money is tracked, transparent, and spent wisely.
## Filled by
Aaron Wolf
## 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)
- Maintaining https://wiki.snowdrift.coop/operations/accounting
## Domains
### Expenditures
#### **Policy: Spending**
Any partner may spend money if they: (1) check in with Tresurer to ensure that enough money exists, (2) In a tactical meeting, following the governance process, pass a proposal for spending, and (3) have it approved by the board (the rep link will bring the proposal to the board after step 2).
## Purpose
A core architecture for Snowdrift that enables rapid development and integrity of the codebase.
## Filled by
Bryan Richter
## 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.
## Domains
### Snowdrift technology stack
#### Mechanism Ownership**
pharpend can define snowdrift technology stack in the mechanism library (in accordance with top level standards).
## Purpose
Making sure we have high quality code.
## Filled by
Bryan Richter
Stephen Weber (singpolyma)?
## Accountabilities
- Testing code
- Reviewing code
- Processing merge requests
## Domains
### Coding style
## Purpose
Snowdrift software consisistent with design.
## Filled by
Bryan Richter
Peter Harpending
Jazzy?
Fr33?
iko?
## Accountabilities
- Implementing frontend and backend features
- Maintaining lists of newbie-friendly development tasks
## Purpose
Circle governance and operational practices aligned with the Constitution.
## Filled by
### Term
## 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
## Purpose
Website is usable.
## Filled by
Robert Martinez
Michael Siepmann
## Accountabilities
- Defining page existence, function, and content.
- Curating user stories.
- Validating designs through user research.
## Domains
### Page list & functions
## Purpose
The Lead Link holds the Purpose of the overall Circle.
## Filled by
## Accountabilities
- Structuring the Governance of the Circle to enact its Purpose and Accountabilities
- 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 priorities and Strategies for the Circle
- Defining metrics for the circle
- Removing constraints within the Circle to the Super-Circle enacting its
- Purpose and Accountabilities