Analytics Guild Governance

Authors:@paulapivat, @mamer

Status: DRAFT [Draft->Voting->Closed]

Voting Link: [link to the seshbot poll once created]

Closing Summary: TBD [blurb describing final decision, next steps, at time of close]

 

This current iteration of the guild governance document is meant to put into place most of the basic framework for guild operation. It utilizes many of the existing policies and procedures found in other guilds within the Bankless DAO. It is meant to be a living document and adapt to the dynamic nature of this organization.

Table of Contents

1. Guild Governance Framework

2. Guild Organization/Operation

3. Membership

4. Contributions

5. Proposals

6. Consensus

7. Treasury Management

8. Role Governance

Guild Governance Framework

 

 

1. Ideation
Share an idea in #📊analytics to get some quick feedback
Do a quick @seshbot poll to get a sense of what people think

2. Proposal Draft
Use this Google Docs template Proposal template when drafting a new proposal
Signal in #📊analytics that you’re working on it so that co-authors can signal interest in collaborating (i.e. work in the open)

3. Discussion/Revision
Receive comments in #📊analytics, Google Docs
Coordinate feedback/advice calls where needed
Redraft the Google Doc and communicate in #📊analytics when changes happen
Option: Use a @seshbot poll to see if it’s ready for voting if unsure

4. Voting (Consensus Check)
Make a forum poll on Discourse.
Proposal updated to status ‘Voting’ with link to the poll
Vote poll should be open for minimum 3 days to maximize participation
Be sure to clearly label it as a ‘consensus vote’ and use the @Analytics Guild tag when posting so guild is notified for maximum participation
All binary (yes/no) type votes require a 60% consensus to pass, all non-binary votes or variations required must be defined in the proposal and clearly state thresholds/mechanics for a successful consensus.

5. Closing and Treasury Distributions
Proposal is updated to status ‘Closed’ and decision summary is recorded
Guild coordinator role notified (if not aware) to rally the multi-sig signers
Signers sign transaction(s)

Guild Organization/Operation

1. Meetings
Meetings will be held as necessary, though weekly syncs are recommended.
All meetings should be documented in written form. Documentation should include at least attendance, updates, action items and any decisions made and listed under the Guild’s Notion page.
Any member can join the Analytics Guild by using the emoji reaction functionality in the #⚔️guild-select channel, or otherwise requesting the Analytics Guild role.
The Analytics Guild reserves the right to take action against the inactivity of those with a guild tag at the end of each season. The seasonal poll is to be conducted at the conclusion of each season.
Inactive members may have the Analytics Guild tag removed from their profile based on inactivity by the Guild.
A revoked tag may get reinstated per Sesh Poll during a Guild meeting

Membership

1. Any member can join the Analytics Guild by using the emoji reaction functionality in the #⚔️guild-select channel, or otherwise requesting the Analytics Guild role.

2. The Analytics Guild reserves the right to take action against the inactivity of those with a guild tag at the end of each season. A seasonal poll is to be conducted at the conclusion of each season.

3. Inactive members may have the Analytics Guild tag removed from their profile based on inactivity by the Guild.
A revoked tag may get reinstated per Sesh Poll during a Guild meeting

Contributions

1. Members of the Analytics Guild are encouraged to “actively contribute” to the success of the Guild which includes, but is not limited to:
Attending and participating in meetings
Voting on polls, roles, and any decisions affecting the Analytics Guild
Creating and/or editing content to be used internally or externally
Brainstorming and contributing to the creative process
Taking on ad-hoc tasks or bounties
Managing administrative functions
Participating in guild projects (i.e., DAO Dash)

Proposals

1. Proposals within the guild will come in two forms, informal, and formal and require appropriate methods of consensus (details provided in Consensus section below):
Informal
Guild level decisions that are non-binding, have no impact on guild funds, active roles, projects, or governance (e.g. coordination, informal polling, etc.)
Formal
All other guild level decisions that do have an impact on guild funds, active roles, projects or governance (e.g. changes to governance, election or removal of member to/from role, actions that are not explicitly covered by governance)

Consensus

1. Informal proposals
Emoji reactions on Discord

2. Formal proposals
Weekly Sync “show of hands” (documented in meeting notes)
Sesh Polls
Discourse Forum Posts

Treasury Management

1. Treasury transactions must be approved by ≥ 60% of the voting guild members and a quorum of at least 8 members via formal consensus mechanism, as outlined above.

2. The Guild’s treasury transactions will be executed by five (3/5) multisig holders who are responsible for executing transactions that are decided upon by The Guild membership at large. The Guild Treasury Committee will hold custody of The Guild’s funds in a Gnosis Safe, whereby transactions may be approved by a majority of three (3) signers.

3. The Gnosis Safe address: 0x28861eeec6ab073A36Cc299ef8186978893e21FF

4. Guild members may call for a change to the multisig prior to the beginning of each Season. Nominations and votes will be handled according to the Guild Governance Framework.

5. Transactions - Approval & Execution
All transactions must be approved by the Analytics Guild prior to execution. This is including but not limited to:
Reimbursements, rewards, and remunerations
Trades and swaps
Liquidity provisions to AMM pools
Investments and divestments
A formal proposal must be submitted to the Analytics Guild for review and discussion
Once soft consensus is reached, the proposal will be ratified through majority vote
Gas for all Analytics Guild and associated projects (i.e., DAO Dash) will be covered by the Treasury Guild

Role Governance

1. Primary Roles
These roles are positions that are envisioned to support on-going Guild functions not tied to a particular season.
These roles are subject to the general role governance regarding creating and deprecating roles.
These roles and associated responsibilities are created, dropped, updated along with each Guild Seasonal Specification and submitted to the Grants Committee for Guild funding.

2. Seasonal Elections
Salaries are defined and roles elected each season as part of season kick-off proposal
Roles will be re-evaluated and updated at the end of each season
Roles and positions will be drafted for the upcoming season and posted in a Discourse for members to apply to.
After applications are closed elections will be held to select parties for the roles.
Voting will be done in the #📊analytics channel via Sesh poll(s)

3. Revising Role Definition
Proposal to modify the responsibilities or salaries of the roles may be proposed during the drafting of the Guild Seasonal Specificaion via the guild governance framework.

4. Incepting New Roles
New roles may be proposed and elected at any time using this guild governance framework

5. Deprecating Roles
Roles that are no longer needed may be proposed as concluded at the end of a season using this guild governance framework.

6. Standards
Members working in official roles will be held accountable by The Guild’s membership at large. Should a member working a position consistently not fulfill the expectations and duties required of them in this role, The Guild’s membership may vote to remove the member from this office, and vote to approve a replacement.