├── .github └── workflows │ └── pages.yml ├── .gitignore ├── .nojekyll ├── CNAME ├── LICENSE ├── README.md ├── _config.yml ├── brand ├── JPG │ ├── Governance Icon-1.jpg │ ├── Governance Icon-2.jpg │ ├── Governance Icon.jpg │ ├── Stacks Governance - Blue Theme-1.jpg │ ├── Stacks Governance - Blue Theme.jpg │ ├── Stacks Governance - Dark Theme-1.jpg │ ├── Stacks Governance - Dark Theme.jpg │ ├── Stacks Governance - Light Theme-1.jpg │ └── Stacks Governance - Light Theme.jpg ├── PNG │ ├── Governance Icon-1.png │ ├── Governance Icon.png │ ├── Governance_Icon_150x150.png │ ├── Governance_Icon_500x500_whitebg.png │ ├── Governance_Logo_1280x640.png │ ├── Stacks Governance - Dark Theme-1.png │ ├── Stacks Governance - Dark Theme.png │ ├── Stacks Governance - Light Theme-1.png │ └── Stacks Governance - Light Theme.png ├── Stacks Governance - Minimum Size-1.jpg ├── Stacks Governance - Minimum Size.jpg ├── Stacks Governance - Safe Area-2.jpg └── Stacks Governance - Safe Area.jpg ├── calls ├── 20200213_community_call_001.pdf ├── README.md └── notes │ ├── 2020-02-13-Meeting-0001.md │ ├── 2020-03-02-Meeting-0002.md │ ├── 2020-03-11-Meeting-0003.md │ ├── 2020-03-18-Meeting-0004.md │ ├── 2020-03-25-Meeting-0005.md │ ├── 2020-04-01-Meeting-0006.md │ ├── 2020-04-08-Meeting-0007.md │ ├── 2020-04-15-Meeting-0008.md │ ├── 2020-04-22-Meeting-0009.md │ ├── 2020-04-29-Meeting-0010.md │ ├── 2020-05-06-Meeting-0011.md │ ├── 2020-05-13-Meeting-0012.md │ ├── 2020-05-20-Meeting-0013.md │ ├── 2020-05-27-Meeting-0014.md │ ├── 2020-06-03-Meeting-0015.md │ ├── 2020-06-10-Meeting-0016.md │ ├── 2020-06-17-Meeting-0017.md │ ├── 2020-06-24-Meeting-0018.md │ ├── 2020-07-01-Meeting-0019.md │ ├── 2020-07-20-Meeting-0020.md │ ├── 2020-08-06-Meeting-0021.md │ ├── 2020-08-20-Meeting-0022.md │ ├── 2020-09-10-Meeting-0023.md │ ├── 2020-09-24-Meeting-0024.md │ ├── 2020-10-08-Meeting-0025.md │ ├── 2020-10-22-Meeting-0026.md │ ├── 2020-11-05-Meeting-0027.md │ ├── 2020-11-19-Meeting-0028.md │ ├── 2020-12-03-Meeting-0029.md │ ├── 2020-12-17-Meeting-0030.md │ ├── 2021-01-07-Meeting-0031.md │ ├── 2021-01-21-Meeting-0032.md │ └── README.md ├── index.html ├── interviews ├── README.md ├── TEMPLATE.md ├── interview-001.md ├── interview-002.md ├── interview-003.md ├── interview-004.md ├── interview-005.md ├── interview-006.md └── interview-007.md ├── research ├── README.md └── emissions-research │ ├── halving_proposals.adoc │ └── pdf-theme.yml └── survey ├── README.md ├── analysis.pdf ├── dropoff-analysis.pdf ├── report.pdf ├── results-anonymized-randomized.csv └── results-anonymized-randomized.xlsx /.github/workflows/pages.yml: -------------------------------------------------------------------------------- 1 | name: Build and deploy to Github pages 2 | 3 | on: 4 | # Runs on pushes targeting the default branch 5 | push: 6 | branches: ["master"] 7 | 8 | # Allows you to run this workflow manually from the Actions tab 9 | workflow_dispatch: 10 | 11 | # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages 12 | permissions: 13 | contents: read 14 | pages: write 15 | id-token: write 16 | 17 | # Allow one concurrent deployment 18 | concurrency: 19 | group: "pages" 20 | cancel-in-progress: true 21 | 22 | jobs: 23 | deploy: 24 | runs-on: ubuntu-latest 25 | environment: 26 | name: github-pages 27 | url: ${{ steps.deployment.outputs.page_url }} 28 | steps: 29 | - name: Checkout 30 | uses: actions/checkout@v4 31 | - name: Setup ruby 32 | uses: ruby/setup-ruby@v1 33 | with: 34 | ruby-version: "3.2" 35 | - name: Install asciidoctor 36 | run: gem install asciidoctor asciidoctor-pdf 37 | - name: Build html and pdf 38 | run: | 39 | asciidoctor -D research/emissions-research research/emissions-research/*.adoc 40 | asciidoctor-pdf -D research/emissions-research --theme research/emissions-research/pdf-theme.yml -a toc research/emissions-research/*.adoc 41 | - name: Setup Pages 42 | uses: actions/configure-pages@v3 43 | - name: Upload artifact 44 | uses: actions/upload-pages-artifact@v2 45 | with: 46 | path: "./" 47 | - name: Deploy to GitHub Pages 48 | id: deployment 49 | uses: actions/deploy-pages@v2 50 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | _site 2 | .jekyll-cache 3 | dist 4 | -------------------------------------------------------------------------------- /.nojekyll: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/.nojekyll -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | resources.stacksgov.com -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Resources 2 | 3 | This repository contains several resources related to governance of the Stacks blockchain, including documentation of past community calls, a vast list of research, community survey results, initial stakeholder interviews, and more. 4 | 5 | ## Table of Contents 6 | 7 | 8 | 9 | - [Stacks Governance - Resources](#stacks-governance---resources) 10 | - [Table of Contents](#table-of-contents) 11 | - [Additional Outlets](#additional-outlets) 12 | - [Resource List](#resource-list) 13 | - [Get Involved](#get-involved) 14 | - [Governance Calls](#governance-calls) 15 | - [Governance Research](#governance-research) 16 | - [Governance Survey](#governance-survey) 17 | - [Stakeholder Interviews](#stakeholder-interviews) 18 | - [GitHub Repositories](#github-repositories) 19 | - [Stacks Community Forum](#stacks-community-forum) 20 | - [Licensing](#licensing) 21 | 22 | 23 | 24 | ## Additional Outlets 25 | 26 | More information about the Stacks Foundation and its mission can be found at the links below: 27 | 28 | - Website: https://stacks.org 29 | - Twitter: [@StacksOrg](https://twitter.com/StacksOrg) 30 | - Project Management: https://stacksgov.github.io/pm 31 | - Meeting Agendas: [on GitHub](https://github.com/stacksgov/pm/labels/mtg-agenda) 32 | 33 | # Resource List 34 | 35 | ## Get Involved 36 | 37 | From [Stacks Governance Update #1 - 4 March, 2020](https://github.com/stacksgov/updates/blob/master/updates/20200304-update-001.md): 38 | 39 | > Stacks governance is a community-run initiative! As such, it cannot work without your help, and without the input of as many community members as possible. You do not need anyone’s permission to get involved and contribute to the initiative. The #governance working group channel on [Stacks Discord](https://discordapp.com/invite/ny6wGkx) is a great place to begin getting involved, as many community members regularly share ideas, updates, and resources there. You can also find a number of topics under the [governance category](https://forum.stacks.org/c/Working-Groups/governance/) on the Stacks Community Forum which need your input. 40 | 41 | ## Governance Calls 42 | 43 | See [Governance Calls](https://stacksgov.github.io/resources/#/calls/) for more information about past governance community and engineering calls, including: 44 | 45 | - agendas 46 | - video recordings 47 | - notes 48 | - additional resource links 49 | 50 | ## Governance Research 51 | 52 | See [Governance Research](https://stacksgov.github.io/resources/#/research/) for websites, articles, videos, and other items used as a reference while working on this initiative. 53 | 54 | ## Governance Survey 55 | 56 | In Q2 2020 the community conducted a governance survey, inspired by a [similar survey](https://medium.com/coinmonks/ethereum-governance-survey-results-c67c11695f2a) conducted in the Ethereum community in 2019. 57 | 58 | See [Governance Survey](https://stacksgov.github.io/resources/#/survey/) for the archived survey results and analyses. 59 | 60 | ## Stakeholder Interviews 61 | 62 | In Q1 2020 Lane Rettig conducted one-on-one interviews with stakeholders about governance as part of a "listening campaign". 63 | 64 | See [Interview Notes](https://stacksgov.github.io/resources/#/interviews/) for the interview template and notes from each of the one-on-one interviews. 65 | 66 | ## GitHub Repositories 67 | 68 | The [stacksgov organization](https://github.com/stacksgov) on GitHub contains repositories for: 69 | 70 | - [resources](https://stacksgov.github.io/resources): the content found here 71 | - [pm](https://stacksgov.github.io/pm): project boards, open issues, work streams, and meeting agendas 72 | - [community](https://github.com/stacksgov/community): community resources, ecosystem calls, systems, and related processes 73 | - [updates](https://github.com/stacksgov/updates): regularly published updates to share the latest progress of the governance project with the community 74 | - [proposals](https://github.com/stacksgov/proposals): stores miscellaneous governance proposals [as issues](https://github.com/stacksgov/proposals/issues) for consideration and potential adoption 75 | 76 | ## Stacks Community Forum 77 | 78 | See the [Stacks Forum - Governance Working Group category](https://forum.stacks.org/c/Working-Groups/governance/) for posts related to the initiative. 79 | 80 | # Licensing 81 | 82 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/resources/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 83 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-minimal -------------------------------------------------------------------------------- /brand/JPG/Governance Icon-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Governance Icon-1.jpg -------------------------------------------------------------------------------- /brand/JPG/Governance Icon-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Governance Icon-2.jpg -------------------------------------------------------------------------------- /brand/JPG/Governance Icon.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Governance Icon.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Blue Theme-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Blue Theme-1.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Blue Theme.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Blue Theme.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Dark Theme-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Dark Theme-1.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Dark Theme.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Dark Theme.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Light Theme-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Light Theme-1.jpg -------------------------------------------------------------------------------- /brand/JPG/Stacks Governance - Light Theme.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/JPG/Stacks Governance - Light Theme.jpg -------------------------------------------------------------------------------- /brand/PNG/Governance Icon-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Governance Icon-1.png -------------------------------------------------------------------------------- /brand/PNG/Governance Icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Governance Icon.png -------------------------------------------------------------------------------- /brand/PNG/Governance_Icon_150x150.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Governance_Icon_150x150.png -------------------------------------------------------------------------------- /brand/PNG/Governance_Icon_500x500_whitebg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Governance_Icon_500x500_whitebg.png -------------------------------------------------------------------------------- /brand/PNG/Governance_Logo_1280x640.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Governance_Logo_1280x640.png -------------------------------------------------------------------------------- /brand/PNG/Stacks Governance - Dark Theme-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Stacks Governance - Dark Theme-1.png -------------------------------------------------------------------------------- /brand/PNG/Stacks Governance - Dark Theme.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Stacks Governance - Dark Theme.png -------------------------------------------------------------------------------- /brand/PNG/Stacks Governance - Light Theme-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Stacks Governance - Light Theme-1.png -------------------------------------------------------------------------------- /brand/PNG/Stacks Governance - Light Theme.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/PNG/Stacks Governance - Light Theme.png -------------------------------------------------------------------------------- /brand/Stacks Governance - Minimum Size-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/Stacks Governance - Minimum Size-1.jpg -------------------------------------------------------------------------------- /brand/Stacks Governance - Minimum Size.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/Stacks Governance - Minimum Size.jpg -------------------------------------------------------------------------------- /brand/Stacks Governance - Safe Area-2.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/Stacks Governance - Safe Area-2.jpg -------------------------------------------------------------------------------- /brand/Stacks Governance - Safe Area.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/brand/Stacks Governance - Safe Area.jpg -------------------------------------------------------------------------------- /calls/20200213_community_call_001.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/calls/20200213_community_call_001.pdf -------------------------------------------------------------------------------- /calls/README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Calls 2 | 3 | ## Purpose 4 | 5 | The governance working group hosts regular community calls to update the community about the progress of the project, and to give everyone a chance to have their voice heard. The first call was held on February 13, 2020, and future calls will be held based on the [agendas on GitHub](https://github.com/stacksgov/pm/labels/mtg-agenda). 6 | 7 | Please [reach out on Discord](https://discordapp.com/invite/ny6wGkx) if you would like to be added to the recurring email invitation. 8 | 9 | ## Who can Attend 10 | 11 | Stacks governance is a community-run initiative! As such, it cannot work without your help, and without the input of as many community members as possible. *You do not need anyone’s permission to get involved and contribute to the initiative.* The #governance working group channel on [Stacks Discord](https://discordapp.com/invite/ny6wGkx) is a great place to begin getting involved, as many community members regularly share ideas, updates, and resources there. You can also find a number of topics under the [governance category](https://forum.stacks.org/c/Working-Groups/governance/) on the Stacks Community Forum which need your input. 12 | 13 | ## Agenda Items 14 | 15 | You can find a link to the proposed agenda for the next call in the table below. The agenda for each meeting is saved as [an issue on Github](https://github.com/stacksgov/pm/labels/mtg-agenda) under the stacksgov [project management repository](https://github.com/stacksgov/pm). 16 | 17 | Please feel free to propose topics, additions, or amendments! 18 | 19 | # Previous Meetings 20 | 21 | Below is a list of all prior completed calls and related resources. 22 | 23 | ## Governance Working Group 24 | 25 | | No | Date | Time | Agenda | Video | Notes | Resources | 26 | | ---- | ---------- | ---- | ------- | ----- | ----- | ---- | 27 | | 0080 | 2022-12-08 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/196) | [Video](https://youtu.be/LpH1qBoz7iw) | Notes TBD | n/a | 28 | | 0079 | 2022-11-10 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/195) | canceled | Notes TBD | n/a | 29 | | 0078 | 2022-10-27 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/194) | [Video](https://youtu.be/ZN7RY3OYQlE) | Notes TBD | n/a | 30 | | 0077 | 2022-10-13 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/193) | [Video](https://youtu.be/obZHsTCJlIw) | Notes TBD | n/a | 31 | | 0076 | 2022-09-29 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/192) | [Video](https://youtu.be/n3aKtv3Uubk) | Notes TBD | n/a | 32 | | 0075 | 2022-09-15 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/191) | [Video](https://youtu.be/MbFf2LRugSw) | Notes TBD | n/a | 33 | | 0074 | 2022-09-01 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/190) | [Video](https://youtu.be/JXAjJMl16dU) | Notes TBD | n/a | 34 | | 0073 | 2022-08-18 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/189) | [Video](https://youtu.be/3QP1q3UfaLI) | Notes TBD | n/a | 35 | | 0072 | 2022-08-04 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/187) | [Video](https://youtu.be/CV6zX79-QQ0) | Notes TBD | n/a | 36 | | 0071 | 2022-07-21 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/186) | [Video](https://youtu.be/U956koqAoOI) | Notes TBD | n/a | 37 | | 0070 | 2022-07-07 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/185) | [Video](https://youtu.be/ngJW1_cs2Tg) | Notes TBD | n/a | 38 | | 0069 | 2022-06-23 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/184) | [Video](https://youtu.be/sUpXGV1CrXI) | Notes TBD | n/a | 39 | | 0068 | 2022-06-09 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/183) | [Video](https://youtu.be/l6rwGOtjGXc) | Notes TBD | n/a | 40 | | 0067 | 2022-05-26 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/182) | [Video](https://youtu.be/EFqJsX6YEbQ) | Notes TBD | n/a | 41 | | 0066 | 2022-05-12 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/180) | [Video](https://youtu.be/NLT1OJwCa0k) | Notes TBD | n/a | 42 | | 0065 | 2022-04-28 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/179) | [Video](https://youtu.be/NWvfaB1WGPc) | Notes TBD | n/a | 43 | | 0064 | 2022-04-14 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/176) | [Video](https://youtu.be/GmOuUXGEIeM) | Notes TBD | n/a | 44 | | 0063 | 2022-03-31 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/175) | [Video](https://youtu.be/089JKvOLt2A) | Notes TBD | n/a | 45 | | 0062 | 2022-03-17 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/174) | [Video](https://youtu.be/L_3ZxlBGakY) | Notes TBD | n/a | 46 | | 0061 | 2022-03-03 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/172) | Video TBD | Notes TBD | n/a | 47 | | 0060 | 2022-02-17 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/169) | [Video](https://youtu.be/6pEC85bZhcU) | Notes TBD | n/a | 48 | | 0059 | 2022-02-03 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/168) | [Video](https://youtu.be/I1eltRGmUXs) | Notes TBD | n/a | 49 | | 0058 | 2022-01-20 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/167) | [Video](https://youtu.be/SQFHGQ5yDhs) | Notes TBD | n/a | 50 | | 0057 | 2022-01-06 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/166) | [Video](https://youtu.be/V-YNggkIpdg) | Notes TBD | n/a | 51 | | 0056 | 2021-12-23 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/165) | Video TBD | Notes TBD | n/a | 52 | | 0055 | 2021-12-09 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/162) | [Video](https://youtu.be/AMDPxhKh3dk) | Notes TBD | n/a | 53 | | 0054 | 2021-11-25 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/160) | Video TBD | Notes TBD | n/a | 54 | | 0053 | 2021-11-11 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/159) | [Video](https://youtu.be/bgw3nyJ0dec) | Notes TBD | n/a | 55 | | 0052 | 2021-10-28 | 1500 UTC | [Agenda](https://github.com/stacksgov/pm/issues/158) | [Video](https://youtu.be/ha6WkXEeksc) | Notes TBD | n/a | 56 | | 0036 | 2021-03-18 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/135) | Video TBD | Notes TBD | n/a | 57 | | 0035 | 2021-03-04 | 1800 UTC | [Agenda](https://github.com/stacksgov/pm/issues/134) | Video TBD | Notes TBD | n/a | 58 | | 0034 | 2021-02-18 | 1800 UTC | [Agenda](https://github.com/stacksgov/pm/issues/133) | Video TBD | Notes TBD | n/a | 59 | | 0033 | 2021-02-04 | 2000 UTC | [Agenda](https://github.com/stacksgov/pm/issues/128) | Video TBD | Notes TBD | n/a | 60 | | 0032 | 2021-01-21 | 1900 UTC | [Agenda](https://github.com/stacksgov/pm/issues/127) | [Video](https://youtu.be/IQLft2jWhWQ) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2021-01-21-Meeting-0032) | n/a | 61 | | 0031 | 2021-01-07 | 1700 UTC | [Agenda](https://github.com/stacksgov/pm/issues/121) | [Video](https://youtu.be/URfvTEDnznM) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2021-01-07-Meeting-0031) | n/a | 62 | | 0030 | 2020-12-17 | 1700 UTC | [Agenda](https://github.com/stacksgov/pm/issues/120) | [Video](https://youtu.be/VLTYGtW-KEU) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-12-17-Meeting-0030) | n/a | 63 | | 0029 | 2020-12-03 | 1700 UTC | [Agenda](https://github.com/stacksgov/pm/issues/118) | [Video](https://youtu.be/Mc20-oIx_5s) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-12-03-Meeting-0029) | n/a | 64 | | 0028 | 2020-11-19 | 1700 UTC | [Agenda](https://github.com/stacksgov/pm/issues/113) | [Video](https://youtu.be/vp8XKCgFN3k) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-11-19-Meeting-0028) | n/a | 65 | | 0027 | 2020-11-05 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/105) | [Video](https://youtu.be/gUnzeUP5m6E) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-11-05-Meeting-0027) | [healthy ecosystem building from Ryan](https://youtu.be/2Oy9LyVThlg) | 66 | | 0026 | 2020-10-22 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/99) | [Video](https://youtu.be/WSuFP8eCv9c) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-10-22-Meeting-0026) | n/a | 67 | | 0025 | 2020-10-08 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/98) | [Video](https://youtu.be/KKR8taylEuM) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-10-08-Meeting-0025) | [grant proposal](https://paper.dropbox.com/doc/Stacksgov-Grant-Proposal--A9FticUOo4gxWoWRzabNARnkAg-ke9qLunt5n7WwWwZTV56I) | 68 | | 0024 | 2020-09-24 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/96) | [Video](https://youtu.be/fB7RNKH3908) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-09-24-Meeting-0024) | n/a | 69 | | 0023 | 2020-09-10 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/95) | [Video](https://youtu.be/1isfhOW09bw) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-09-10-Meeting-0023) | n/a | 70 | | 0022 | 2020-08-20 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/94) | [Video](https://youtu.be/Jqkg1ncFHzM) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-08-20-Meeting-0022) | n/a | 71 | | 0021 | 2020-08-06 | 1600 UTC | [Agenda](https://github.com/stacksgov/pm/issues/84) | [Video](https://youtu.be/2RWjd7rvCEA) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-08-06-Meeting-0021) | [Grant Proposal working doc](https://paper.dropbox.com/doc/Gov-Group-Grant-Proposal--A402pAn8MQVQPIikglkCKxXXAQ-RN1efxJdptsRGVrJIbwou) | 72 | | 0020 | 2020-07-20 | 1730 UTC | [Agenda](https://github.com/stacksgov/pm/issues/82) | [Video](https://youtu.be/TKhnqyPVLLE) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-07-20-Meeting-0020) | n/a | 73 | | 0019 | 2020-07-01 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/71) | [Video](https://youtu.be/h7iShriQ3q0) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-07-01-Meeting-0019) | @jcnelson [SIP-000 Slide Deck](https://docs.google.com/presentation/d/1k0VB5k5kVrSfib33yaq5n-ZGkrl1ueunqWj7eSKuVm8/edit#slide=id.g8b7270c087_0_48) | 74 | | 0018 | 2020-06-24 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/64) | [Video](https://youtu.be/o69zoNsP33w) | Notes [(TBD)](https://stacksgov.github.io/resources/#/calls/notes/2020-06-24-Meeting-0018) | n/a | 75 | | 0017 | 2020-06-17 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/61) | [Video](https://youtu.be/om6o81aB4t8) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-06-17-Meeting-0017) | n/a | 76 | | 0016 | 2020-06-10 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/58) | [Video](https://youtu.be/7j_0Xb3t0ck) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-06-10-Meeting-0016) | n/a | 77 | | 0015 | 2020-06-03 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/50) | [Video](https://youtu.be/5dISVmdBe3g) | Notes [(TBD)](https://github.com/stacksgov/pm/issues/57) | n/a | 78 | | 0014 | 2020-05-27 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/46) | [Video](https://youtu.be/SUASurbAyzI) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-05-27-Meeting-0014) | n/a | 79 | | 0013 | 2020-05-20 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/41) | [Video](https://youtu.be/ULdXgtrjb-8) | Notes [(TBD)](https://github.com/stacksgov/pm/issues/47) | n/a | 80 | | 0012 | 2020-05-13 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/39) | [Video](https://youtu.be/daxesAKFa6I) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-05-13-Meeting-0012) | n/a | 81 | | 0011 | 2020-05-06 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/37) | [Video](https://youtu.be/jCiJiifOYok) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-05-06-Meeting-0011) | [SIP Proposal](https://docs.google.com/document/d/1huF3u6BlrEapbjw77wGp_lq3d3kC17ZugCalvpN8M3U/edit?usp=sharing) / [FabAcademy Meeting](https://paper.dropbox.com/doc/Meeting-wTomas-DiezPrimavera-Connection--AzeCC~olgxmajJhWv49zT9~NAg-vgftHgoR26II8R3CGpi4h) | 82 | | 0010 | 2020-04-29 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/35) | [Video](https://youtu.be/f7nUMpUzu5E) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-04-29-Meeting-0010) | n/a | 83 | | 0009 | 2020-04-22 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/31) | [Video](https://youtu.be/TwkrWMA7Eo0) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-04-22-Meeting-0009) | n/a | 84 | | 0008 | 2020-04-15 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/25) | [Video](https://youtu.be/Pubkhn-reDk) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-04-15-Meeting-0008) | n/a | 85 | | 0007 | 2020-04-08 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/24) | [Video](https://youtu.be/-5BrfFvPvD4) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-04-08-Meeting-0007) | n/a | 86 | | 0006 | 2020-04-01 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/19) / [Google Doc](https://docs.google.com/document/d/1Lr9zOLWO5Xtg31M-dKaVXREYcyQn_zCepwPlErD3pvg/edit) | [Video](https://youtu.be/ALeaUzwxTe8) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-04-01-Meeting-0006) | n/a | 87 | | 0005 | 2020-03-25 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/16) | [Video](https://youtu.be/gpw6byKPeIw) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-03-25-Meeting-0005) | n/a | 88 | | 0004 | 2020-03-18 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/9) | [Video](https://youtu.be/u8lZsVFCFtc) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-03-18-Meeting-0004) | @dantrevino [Presentation Slides](https://slides.com/dantrevino/blockstack-governance) / @blocks8 [Foundation Notes](https://docs.google.com/document/d/125MQTwpP9oooAUSES4U_HTcVJ02lVOR7A1IWEC3jh3g/edit?usp=sharing) | 89 | | 0003 | 2020-03-11 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/5) | [Video](https://youtu.be/d7cGndifjR0) | [Notes](https://stacksgov.github.io/resources/#/calls/notes/2020-03-11-Meeting-0003) | [Community Foundation Questions](https://github.com/stacksgov/pm/issues/11) | 90 | | 0002 | 2020-03-02 | 1400 UTC | [Agenda](https://github.com/stacksgov/pm/issues/3) | [Video](https://youtu.be/jAEHyq4TKeI) | Notes [(TBD)](https://stacksgov.github.io/resources/#/calls/notes/2020-03-02-Meeting-0002) | n/a | 91 | | 0001 | 2020-02-13 | 1500 UTC | n/a | [Video](https://youtu.be/GilQ9qU4Sa0) | Notes [(TBD)](https://stacksgov.github.io/resources/#/calls/notes/2020-02-13-Meeting-0001) | [Presentation Slides](https://stacksgov.github.io/resources/calls/20200213_community_call_001.pdf) | 92 | 93 | ## Engineering Team Meetings 94 | 95 | The engineering team holds regular public meetings to discuss the [Stacks 2.0 blockchain implementation](https://github.com/blockstack/stacks-blockchain). 96 | 97 | 98 | | No | Date | Time | Video | 99 | | ---- | ---------- | ---- | ----- | 100 | | 0036 | 2021-03-08 | 1500 UTC | [Video](https://youtu.be/Vx0YoqinJwo) | 101 | | 0035 | 2021-03-01 | 1500 UTC | [Video](https://youtu.be/DDAIiKnskog) | 102 | | 0034 | 2021-02-22 | 1500 UTC | [Video](https://youtu.be/U8Zew3P9AhA) | 103 | | 0033 | 2021-02-15 | 1500 UTC | [Video](https://youtu.be/bBTkontMv3E) | 104 | | 0032 | 2021-02-09 | 1500 UTC | [Video](https://youtu.be/qMsInJuLQXQ) | 105 | | 0031 | 2021-02-02 | 1500 UTC | [Video](https://youtu.be/G0mE0CVZgCU) | 106 | | 0030 | 2021-01-25 | 1500 UTC | [Video](https://youtu.be/evXIKW87O6U) | 107 | | 0029 | 2021-01-19 | 1500 UTC | [Video](https://youtu.be/2sbbdsdn_UE) | 108 | | 0028 | 2021-01-11 | 1500 UTC | [Video](https://youtu.be/3Av2E2AxQuM) | 109 | | 0027 | 2021-01-04 | 1500 UTC | [Video](https://youtu.be/OKr_WjJJZuU) | 110 | | 0026 | 2020-12-28 | 1500 UTC | [Video](https://youtu.be/L0ysOO5qLrE) | 111 | | 0025 | 2020-12-14 | 1500 UTC | [Video](https://youtu.be/7It0NWB7io0) | 112 | | 0024 | 2020-12-07 | 1500 UTC | [Video](https://youtu.be/3e0JjAD9ZFw) | 113 | | 0023 | 2020-11-30 | 1500 UTC | [Video](https://youtu.be/PYGACq-8FMQ) | 114 | | 0022 | 2020-11-23 | 1500 UTC | [Video](https://youtu.be/PIX4UOnX2lU) | 115 | | 0021 | 2020-11-16 | 1500 UTC | [Video](https://youtu.be/E4u7hS4vwRI) | 116 | | 0020 | 2020-11-09 | 1500 UTC | [Video](https://youtu.be/GcLpFYv_4GA) | 117 | | 0019 | 2020-11-02 | 1500 UTC | [Video](https://youtu.be/vgSzw2uWNkc) | 118 | | 0018 | 2020-10-26 | 1500 UTC | [Video](https://youtu.be/Pq0hH6XkHws) | 119 | | 0017 | 2020-10-19 | 1500 UTC | [Video](https://youtu.be/QZ36xI0q2-g) | 120 | | 0016 | 2020-10-05 | 1500 UTC | [Video](https://youtu.be/1JpROdyuhek) | 121 | | 0015 | 2020-09-15 | 1500 UTC | [Video](https://youtu.be/8y3tA0Ozemo) | 122 | | 0014 | 2020-08-31 | 1500 UTC | [Video](https://youtu.be/_t_J0fK7edM) | 123 | | 0013 | 2020-08-17 | 1500 UTC | [Video](https://youtu.be/2Y7pN068wBs) | 124 | | 0012 | 2020-08-10 | 1500 UTC | [Video](https://youtu.be/wTugvYIegNU) | 125 | | 0011 | 2020-08-03 | 1500 UTC | [Video](https://youtu.be/7DgB7vgInzo) | 126 | | 0010 | 2020-07-27 | 1500 UTC | [Video](https://youtu.be/3zWOG49Q0Cg) | 127 | | 0009 | 2020-07-20 | 1500 UTC | [Video](https://youtu.be/706jYJxCh70) | 128 | | 0008 | 2020-07-13 | 1500 UTC | [Video](https://youtu.be/9czYpwgt7CQ) | 129 | | 0007 | 2020-07-06 | 1500 UTC | [Video](https://youtu.be/M24ytGdb330) | 130 | | 0006 | 2020-06-29 | 1500 UTC | [Video](https://youtu.be/w5EEL-4EkHw) | 131 | | 0005 | 2020-06-22 | 1500 UTC | [Video](https://youtu.be/nR1ZhMBw_pg) | 132 | | 0004 | 2020-06-15 | 1500 UTC | [Video](https://youtu.be/6HWR4wPKtV0) | 133 | | 0003 | 2020-06-08 | 1500 UTC | [Video](https://youtu.be/byktpBjVYU0) | 134 | | 0002 | 2020-06-01 | 1500 UTC | [Video](https://youtu.be/ImUaan5kaU0) | 135 | | 0001 | 2020-05-26 | 1400 UTC | [Video](https://youtu.be/60JqCcCNEPg) | 136 | 137 | # General Resources 138 | 139 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 140 | 141 | # Licensing 142 | 143 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/resources/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 144 | -------------------------------------------------------------------------------- /calls/notes/2020-02-13-Meeting-0001.md: -------------------------------------------------------------------------------- 1 | # 20200213 Governance Working Group Call 1 2 | 3 | (placeholder) - [see pm/issue#74](https://github.com/stacksgov/pm/issues/74) 4 | 5 | # General Resources 6 | 7 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /calls/notes/2020-03-02-Meeting-0002.md: -------------------------------------------------------------------------------- 1 | # 20200302 Governance Working Group Call 2 2 | 3 | (placeholder) - [see pm/issue#75](https://github.com/stacksgov/pm/issues/75) 4 | 5 | # General Resources 6 | 7 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /calls/notes/2020-03-11-Meeting-0003.md: -------------------------------------------------------------------------------- 1 | # 20200311 Governance Working Group Call 3 2 | 3 | Lane (@lrettig) is moderating today. 4 | 5 | ## Agenda 6 | 7 | https://github.com/stacksgov/pm/issues/5 8 | 9 | ## Intros 10 | 11 | We heard a quick introduction from the following participants: 12 | 13 | - Lane Rettig 14 | - Jason Schrader 15 | - Juliet Oberding 16 | - Phillip Roe 17 | 18 | ## Updates over the past week 19 | 20 | Lane provided us with some updates over the past week. 21 | 22 | ### Resources (YouTube/GitHub/Discord/Discourse/others) 23 | 24 | - last week's video recording on Youtube 25 | - github has been pretty active, resources are expanding 26 | - great place to contribute and get started 27 | - will serve as a shared knowledge base 28 | - ongoing conversation in Discord 29 | - chat.blockstack.org --> Discord invite 30 | - The contribute blockstack repo (@blockstackers) that has working group info, link to specific channels in repo 31 | 32 | ### Regular updates 33 | 34 | - another repository on github (stacksgov/updates repo) 35 | - publish updates weekly after the calls, factor in any updates that people share 36 | - open issue that people can add to, becomes a PR, merged in once final 37 | 38 | ### One on one "stakeholder interviews" 39 | 40 | - started with PBC folks, now beginning to speak to broader ecosystem as well 41 | - 4 done, 5th scheduled, beginning to lose track (a good thing) 42 | - taken extensive notes, but will clean up and share with each interviewee 43 | - if you want to nominate there is a form to do that, or message Lane directly 44 | 45 | ## Standups 46 | 47 | ### Jason Schrader 48 | 49 | Jason: Working on community health files for GH repos - looking at examples from other projects, consolidating resources, we are on the right track 50 | 51 | ### Phillip Roe 52 | 53 | Phillip: Trying to understand experience of blockchain networks, their experience on other networks, a lot of issues with capitalism in the blockchain, many people mention these issues, something we have to think about, how to deal with that. 54 | 55 | Phillip: As we launch blockstack apps, we are going forward in trying to get some revenues from the user of the DApp, see that (capitalist) attitude come into the ecosystem. Wanting to understand governance issues from other blockchain projects. 56 | 57 | Phillip: Goal to protect the people, ways we can govern, how do we address the "ambition problem", “Brutality of capitalism” is seen in the blockchain arena, many people mention this in different places. He is very technical, but this content is much more technical, curious how we determine governance when this is such a complex subject. 58 | 59 | Phillip: governance always under laws of one country, at international level (united nations), enforcement is not being applied sometimes. the law at the end is one that has to be applied, this government has to be under the law, and how this is going to show "proof" or other elements in order to be protected. 60 | 61 | Phillip: been working with Blockstack since 2017, riding the horse and it's going faster and faster, (Lane agrees). Would love to review and unpack some of those questions. Let's continue the conversation on the forum, discord, or github? 62 | 63 | ## Community Survey 64 | 65 | Lane: using Typeform, built from Google Doc, few folks have seen it, comments helpful for content and flow, factoring in other feedback now, expect to have minimum viable survey finished by tomorrow (Thu 2020/03/12). 66 | 67 | Lane: Jenny/Brittany, any input on how to launch? let's not make it perfect in the beginning. next step is have the working group take the survey themselves, then discuss how it works then discuss again. If possible - would like to share it in a somewhat scientific fashion, from a few people, look at scientific survey methodology to get true results. have some ideas: 68 | - sampling random stacks token addresses 69 | - other methods that will be shared 70 | 71 | Lane: Another line of questioning: what is the purpose? what are the action points? 72 | - smart questions, especially before, thoughts shared in the forum (as well as in Google Doc). 73 | - been adding/removing stuff while factoring this thought in 74 | - making it clear that every question has an action item associated with it. 75 | - example: asking location/continents, change to countries, useful because helps like scheduling calls, time zones, blockstack summit locations. 76 | - possible result: turns out a large portion of the community in an area we weren't aware of 77 | 78 | Lane: Anyone have anything to add or share? 79 | 80 | Phillip: a question about the behaviors or challenges that you have seen in blockchain communities? a way to grasp the spirit of what's going on and how. 81 | 82 | Lane: posted link to the draft survey, not ready to be shared, but can get a sense of it. Doesn't include most recent updates (but will, soon). In the governance section, at least one question toward this topic, open-ended questions: what challenges do you see with the existing governance platform? 83 | 84 | Jason: if we have this on agenda, why do it in the survey? 85 | 86 | Lane: surveys get the pulse of the community. most people like quick select-answers, not open-ended questions. One option is to turn it into multiple choice: which issues concern you the most (examples from others, with an other). 87 | 88 | Lane: Survey aspect of what other projects are doing, doesn't belong here, can crowdsource that on github or in the forum or both. Already happening as a part of the cryptogov working table / group. stakeholder survey created for projects in general. Wharton crypto gov initiative - we can lean on this as well - has collected responses from a dozen the projects or more: https://cryptogov.net/ 89 | 90 | Juliet: read out question regarding governance, concerned that after looking at governance conversations in the community, not sure if they really know what it is, or what it means 91 | - ideas of rules of law vs on chain vs off chain governance 92 | - concern of question being very general 93 | - if I'm going to answer: "Blockstack's done a great job", without considering what was in place 94 | - maybe something we can do some work around, what is the governance model right now, and what does that mean? 95 | 96 | Lane: There are two pieces to it: 97 | - what is governance in general 98 | - what is your understanding of how Governance works now (or has worked) in the Blockstack ecosystem 99 | 100 | Lane: the survey is a great place to ask questions, aiming for the latter. What is in your opinion, the "mission of the project"? Also degree of alignment, and around values, could be phrased differently, what do people think? 101 | 102 | Joris Hermans: governance is very broad term, integrated many different ways, when you are really familiar with the blockchain world it's much easier. know that a lot of poeple / devs joining from outside that world thinks open source projects, how they govern their ecosystems (Lane strongly agrees). 103 | 104 | Lane: thought to add on, a lot of what we are doing feels very new/novel, but a lot of this is not new, been done for decades, there are great examples and much to learn from open source. 105 | 106 | Joris: lots of foundations, stakeholders in foundations, really like: Gatsby, how they organize themselves, all developers are empowered to take ownership of pieces of the whole stack, how they comunicate in github appeals to him, also wants to bring up on community dev calls, also nice to look at javascript foundation. 107 | 108 | Dan: my confusion is that we still haven't defined (to Juliet/Joris point) what the governance affects, the only visible indicator up until now has been around app mining (standing from the outside). we have a very heavy handed (corporate controlled) approach to development (but PBC is working on it, they accept PRs, not a complaint), structure of dev team much different for app mining 109 | 110 | Dan: what is the purpose of governance? what does it cover? what is the mission statement for stacksgov? will we come out of this without doing a stacks foundation? Friedger asking if app mining should be included, secondary to the mission or "the whole point", PBC doesn't want to govern the network, separate foundation makes sense, have we talked about what the structure of the foundation, the questions we are asking don't seem very directed. 111 | 112 | Lane: the goal of the survey is not to ask people how they want to be governed going forward, gauged more to level of understanding and involvement. I’ve been asking these questions on the one on ones, agree they’re important, probably not helpful to ask such open ended questions on the survey, but - how do we make sure we hear everyone’s voice here? 113 | 114 | Juliet: contributing to the call on the foundation, setup in singapore, based on the type available there, one director required to be a native, director and secretaries, and the kinds of directors and who are selected and what their role yet has not been discussed with us yet. Brittany is working on and haven't heard updates yet. 115 | 116 | Dan: totally remember that, confusion comes from it seems like "we" picked an idea for a "foundation". created, established, structure semi-defined. still feels like we are asking the community "what do you think" when the direction was already defined. would like to see not just the notes, but also the "here's where we are" with a timeline, tentative structure, opportunity to voice thoughts on what that structure looks like. 117 | 118 | Dan: What are the open questions around the Foundation? I don’t think anybody is questioning that. What can we the community actually contribute to vs. what has already been decided? What are the things they think the Foundation is gonna manage? App mining? Where’s that list of questions? E.g. how will it be funded? There’s a cart-and-horse thing there. It feels like we’ve picked a general structure but it’s not being communicated; what is governance? 119 | 120 | Joris: basics not right, collections, contacts, don't see any further work on that, working group for data, where we can define data structures, what are we going to do to open up between every application. to bring unity. These things are very important, they need to be defined, structure to let them grow. feeling now: a lot of poeple are experimenting on their own islands. 121 | 122 | Dan: what he is saying is hugely valuable, but his question, does that have anything to do with the stacksgov foundation? He likes open source software, working in Github, on the development side is a different side and structure than what we are talking about with funding, governance, and others. Ad hoc the community has been working on collections, but does the foundation have a role in organizing dev teams? or organizing development? 123 | 124 | Joris: not just development, structure, documentation, the fact with PBC is they are developing docs, very basic thing that needs to be setup. important to take next step forward. saw a lot of things about PoX, read a lot about it, but things are very complex. 125 | 126 | Dan: hugely valuable, if you can send us all a link to the community you just mentioned, documentation working groups. like to see how other groups are doing these type of things. big example on how stewardship is setup. If we leave it up to PBC it's going to be all VCs. They can set up leadership, but community wants to have input too, maybe someone more into development. What does the foundation actually cover? 127 | 128 | Phillip: questions in the survey? his view: difficult for all the people that are participating, hard to understand full view, as you said there are always some people that work one way for years, leave because they have info, likes openness of these groups that let us understand what's going on. Surprise to learn about Singapore for foundation, didn't see this last time, heard of Estonia has a corporation, start wondering what's going on with that, something that we have to put in place. 129 | 130 | Phillip: appreciate your interest and participation, only have so much time. this is the opportunity to express and thank you to Lane for being selected and working through tasks. other thing is that the law is something already defined. structures defined. the way you have to implement the foundation in different parts of the world. have to jam through those and use that part and adjust our knowledge on top of that. the new knowledge is about concept of blockchain governing itself. Don't believe it but want to embrace new concept. 131 | 132 | Lane: In the future, we can move from 60-90 min call, running short on time (top of the hour). Summarizing the questions briefly: 133 | - I think there are very important/valid questions about some of the basics: right structure? why was Singapore chosen, better option? how should it be governed? what should it's scope be? what is the mission/charter? all questions already on his mind 134 | - first: actual formation of the legal entity is not within his personal scope of work. PBC is leading this effort, and Brittany is the main source (not on call), he will collect questions to bring up with her. 135 | - my understanding: Juliet mentioned, it will be a foundation, Singapore entity, "minimum-viable" to start, fill in the positions and what happens from there is up to us (as a community) 136 | - "It's on us". This is a permissionless peer-led commons project. We have to come together to answer these questions. As long as we are reasonable in expectations and cost then PBC should step up. 137 | - Closing thought: let's think through these items and start throwing out proposals. Excited to work with everyone. 138 | 139 | Jenny: on that, hear what Dan is saying, all this activity super valuable to understand how it works, what it could look like, surface all work streams we are all involved in: Elijah and data collections, as an exercise with the community we can organize those work streams under those questions, hearing Dan's questions, maybe a disconnect between the directive of wanting to work together versus what the practical example of what it is. 140 | 141 | Juliet: Dan nailed it, each question needs to be outlined, follow and answer those questions, thanks for raising that. really really important those questions are answered, and at this point, we don't have any input. where are we making input? how we are contributing input? how are we being heard? 142 | 143 | Joris: add transparency and clear communication, makes more sense to recommunicate clear, get everyone on same page. thinks it will be a big challenge. 144 | 145 | Lane: volunteering to type up a list of these questions as Dan put them forward, will raise other questions as part of the process, happy to put them on the forum as a starting point. do invite and ask everyone else to contribute. can mean more questions, answers, making sure people have a voice. 146 | 147 | List of questions from the call: 148 | https://github.com/stacksgov/pm/issues/11 149 | 150 | Lane: finishing up this agenda item, clear actions: 151 | - draw up list of questions 152 | - start drawing answers from everyone 153 | 154 | Jenny: happy to help sort questions into categories (macro categories) of governance, each question can help illustrate what aspects we are working on 155 | 156 | Juliet: happy to advocate for getting those questions answered and pushing forward 157 | 158 | ## How to get involved/contribute 159 | 160 | - add the How to Git Involved blog post to the resources 161 | - when the survey is up, please respond and let us know thoughts 162 | - resources repository on stacksgov, open issues, add info 163 | - contribute to regular updates (out by tomorrow) 164 | 165 | ## Next/recurring call schedule 166 | 167 | This time slot on Wednesdays, weekly, any strong objections? sticking with for now (based on those on the call), if its an issue, please jump in on Discord, or comment on Github. 168 | 169 | ## Open call - any other updates? 170 | 171 | (none) 172 | 173 | # General Resources 174 | 175 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 176 | 177 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 178 | -------------------------------------------------------------------------------- /calls/notes/2020-03-25-Meeting-0005.md: -------------------------------------------------------------------------------- 1 | # 20200325 Governance Working Group Call 5 2 | 3 | ## Quick round of intros 4 | 5 | skip today, drop from agenda, separate more social call or other ways for intros if needed. more time to focus on the agenda. 6 | 7 | ## What happened over the past week? 8 | 9 | Lane: last week factored in feedback from the forums, gotten a lot of feedback, thank you everyone for taking the survey. Now ready to share it - tweet went out this morning! "The baby's out in the world". 10 | 11 | Twitter Post: https://twitter.com/blockstack/status/1242784590378553345 12 | 13 | Lane: How can we amplify? 14 | 15 | Jenny: share post with any of your own audience, twitter, other social media, will check progress in a few days to see if distribution is very effective. going for a solid number, the more help the better. if we are not seeing enough responses, we can pivot and take a new approach. Easiest way to distribute. 16 | 17 | Lane: target of 100 responses, other ideas like picking random set of investors, open to other ideas - feel free to share! 18 | 19 | Lane: Finished 8th interview last week, cleaned up notes from 5/8, given interviewees chance to review and cleared for public sharing, planning to finish last 3 this week. Pausing at 8, good high-level sense of what people are feeling, but could be value doing more in the future. Pausing to focus on governance proposal. 20 | 21 | Outstanding question - sharing the notes from the interviews, some concerns about privacy, open to thoughts on splitting up per question. 22 | 23 | Lane: Governance proposal almost in a place comfortable sharing it with the working group, Brittany highlighted a few points to weigh in on first (to clarify PBC's perspective) 24 | 25 | Brittany: questions around structural questions, setting up the new entity requires tax advice, working with outside counsel, and the inside counsel advising on requirements, still in research phase. 26 | - number of board members, where meetings are held, tax regulations 27 | - number of open questions she is getting answered this week 28 | - could impact governance proposal depending on restrictions/rules 29 | - goal is to get clarity on the requirements and how it will impact governance proposal 30 | - having a conversation with the tax counsel on Friday 31 | - until those are finalized, will not be able to move forward 32 | 33 | Lane: some context, Lane's deliverable to PBC in contract with PBC, taken shape as a monolithic proposal, includes broader challenges in blockchain ecosystems, high-level governance of the ecosystem, and talks more about the foundation governance and structure. May make sense to break this up into a set of proposals, with one piece focusing on the foundation. There are pieces of it that should be shared now, including the general piece. Feel free to share thoughts. 34 | 35 | ## Standup! (Lane) 36 | 37 | Lane: planning to continue on the proposal, continue cleaning up notes from 1 on 1 interviews, only blocker is working through legal requirements with Brittany, 38 | 39 | ## Standup! (Jenny) 40 | 41 | Jenny: how the working groups work, aligning on goals and mission. at the moment focuses are distinct. proposal about the survey going on, foundation formation on the horizon. Did want to drop the question of "what will our role be moving forward?" 42 | 43 | The PoX group, there is an expiration date, when Stacks 2 launches that group may disband. Governance is an ongoing effort, so what would our role be moving forward? 44 | 45 | Is the way that Blockstack governance in the ecosystem fair and beneficial to its stakeholders? Ask week over week and develop a metric to see if we are moving the needle on that. A simple mental model for others to consume. Not something to solve today, but wanted to put it out there, and the role of this group is big on the success of governance in the blockstack ecosystem. 46 | 47 | If you have any ideas toward making these groups more profitable / productive, please share. Had a great chat with Juliet and working to apply any best practices to what we are doing. 48 | 49 | Brittany: Thanks Jenny, that's a great thing to consider, and could be redirected to the forum instead of the calls. 50 | 51 | Lane: Resources, templates, best practices, done a pretty good job with some of that so far. Some meta thought on how to make these "templates", like the github repos, there are ideas there that could be shared across working groups and good information to work with together. A knowledge base or set of resources for working group needs would be a cool thing to have. 52 | 53 | Jenny: happy to have others drive the discussion, love the idea of community leads, we do it informally with the working groups, but can look at a process to have leaders, or nominate leaders, like nominating Juliet for being observer on PBC calls. Can see others taking leads. Have a great small core group now, but as it grows, it can get unwieldly. It will likely be outlined in the proposal but looking forward to that as well. 54 | 55 | Lane: There is an inherent tension as we move forward, on one hand, core focus group and we've gotten to know each other, and his inclination is that "we don't need to formalize things, it's a small group, we know each other", the lesson from other communities, if you don't do that then it doesn't scale. As it moves to 60, 600 people, there's tension there, it can be weird to say "there should be a leader" but it is a good idea at this point. 56 | 57 | ## Standup! (Juliet) 58 | 59 | Working on a forum post, what we've been working on our working group, will pass around to everyone here today when finished. Still going through academic literature, and it's been an interesting process. Also wanted to jump in on the points Lane made about the process, it's a fantastic idea to put a structure together, this group is definitely going to grow in the future and it won't be our cozy group of 5 or 7 that's been here in the past. 60 | 61 | No blockers moving forward. 62 | 63 | Lane: any preliminary findings you'd like to share? 64 | 65 | Juliet: not on the academic side, but have been reading Primavera's work and there are some items that dovetail with what Harold is saying. We can bring it up in conversation when the post is ready to go. 66 | 67 | Lane: Thank you, your ask would be to review and provide feedback, so we will be sure to do that. 68 | 69 | ## Stacksgov Icon 70 | 71 | Lane: tiny thing, pasting the link in, it's not insignificant in the sense that branding is important, but if you'd like to share more. 72 | 73 | Jason provided some info and background around proposed icon design. 74 | 75 | Github Issue: https://github.com/stacksgov/pm/issues/10 76 | 77 | Proposed Icon: 78 | ![Proposed Stacksgov Icon](https://user-images.githubusercontent.com/9038904/76906806-fc2ac800-6861-11ea-9169-71c82fb74f06.png) 79 | 80 | Sounds like consensus! Will start to put across all outlets. 81 | 82 | ## One-on-one interviews and notes 83 | 84 | Juliet: will you be able to wrap up discussion with individuals so the rest of us can see the notes? 85 | 86 | Lane: It's not up to me on when they respond and how they feel, do we just move forward and share the other ones? Do we chop it up and collate around particular questions and share around those? Do not have a strong feeling, but want to get it into everyone's hands. 87 | 88 | Juliet: we should be able to see the other ones, thought that person was still thinking about it, didn't realize they didn't want to share at all. 89 | 90 | Lane: no reason not to move forward, that person is still considering, may redact part of that, don't see a major blocker here, everyone has expressed they are ok with it, think we can do it this week 91 | 92 | Juliet: great, looking forward to it 93 | 94 | Lane: will drop into github as raw text / markdown files, if the format should be different, let him know 95 | 96 | Dan: didn't see the results of our discussion 97 | 98 | Lane: yours is one of the three, it's coming soon, nothing will be shared publicly until the interviewee has a chance to scrub out anything they don't want shared publicly 99 | 100 | ## Stacks Foundation update (from PBC) 101 | 102 | Brittany: mentioned earlier, some of the work is around the structure of the new entity, as we talked about last week, the best way to proceed is to be truly independent of PBC as to not have any bias, getting that entity setup is important. Have done some research on the legal side, the Singapore foundation is highlighted and may fit our needs, doing more analysis on the tax side, may be a tax restriction that if board members are not present in person, then they are not able to vote. If the in person meeting takes place in a certain jurisdiction, such as US, then there may be US tax implications. 103 | 104 | Trying to figure out the best way to work with board members, trying to avoid additional complexity, may be forced to revisit another type of entity, or if we need to create another legal structure around it. This is somewhat vague, but came from talking to other nonprofits and foundations in this space, problems they had after incorporation. Doing their best to learn from their issues so they can deliver this independent entity. People on the board can actually vote/participate, community can be involved in a seamless way, will have an update on the legal entity side soon. 105 | 106 | Lane was discussing on the proposal, been collaborating with him, trying to construct a structure where they can get feedback. Have been looking at other foundations, ZCash really transparent, would love everyone to take a look at how it works. They have an advisory council, any member of the community can be on the council, cannot violate TOS. You can be denied access or removed, but otherwise open, and can be 100 members strong, surface issues, voting on issues, highlight things for implementation. Like this model because everyone can be involved. Do not require people have their real names, but do have checks in the background to make sure people aren't tryiing to use multiple votes. The power of what the entity can do largely resides with the advisory council. The board can veto as necessary for the mission, but so far, it's worked seamlessly. Having a really open structure as part of the foundation executes ideas, and having another small group of people help enact any final decisions, works very well. Wanted to surface that since we can view how they work with the community and include all members. 107 | 108 | Would love poeple to look at the ZCash advisory board and see what they think of it, to drive a new discussion on what we like, don't like, and what we would like to see. 109 | 110 | Zcash Foundation: https://www.zfnd.org/ 111 | Zcash Foundation Governance: https://www.zfnd.org/governance/ 112 | 113 | Lane: 2nd that ZCash is an excellent resource, open sourced everything they are doing, everything in the public domain 114 | 115 | Brittany: having learned more about them, and with what we want to do, maybe secondary goal is we can create a model that others would look to and value as working well. We have a lot of people we can learn from and have an advantage they don't have when less info was available. 116 | 117 | Juliet: think the process sounds good with respect to the foundation, need to take a deep look at the tax implications and other implications of the structure selected, so it's great ot hear that is really deeply looked at. If there are any other issues that come up with the structure and how it would impact governance moving forward it would be great to hear about that, when you know more of what the structure is going to be outside of just the foundation concept. 118 | 119 | Brittany: call with tax people on Friday, will hopefully have more info to share after the call, and will share it as soon as we have it. Not sharing more to date - if it is true there is a lot of complexity there, we may have to go back to the drawing board. Trying to give more things to dig into then be distracted by things that may not happen. 120 | 121 | ## Any other updates? 122 | 123 | (silence) 124 | 125 | Lane: items from last time still on agenda 126 | 127 | ### extend call to 90min 128 | 129 | Lane: extend call to 90 min? agreed last call, official call at 60 minutes, can have optional extended time topics to stay later. Did add one to this call: Harold proposed in working group channel, but unfortunately he's not on the call. 130 | 131 | Lane: does anyone have any other input on the call length, or options? 132 | 133 | Jason: it was nice to have the extra time 134 | 135 | Juliet: it was nice to have that extra time 136 | 137 | Lane: will end the call now and offer to switch host at the end 138 | 139 | ## Closing 140 | 141 | Lane: reiterating that no individual person should be thought of a single point of failure, a bottleneck, in any of these procedures. moderating github, maintianing repos, merging pull requests, hosting this call, and everything else. It's an open call or participation: if anyone wants to host the call (agenda, reminder, host/moderate), help on github, just send a DM on Discord and he will be happy to add. 142 | 143 | A few reasons for that: anti-frigility, governance should continue even if he isn't available, and an accountability issue to have others. 144 | 145 | Juliet: happy to request stepping up for being a moderator on occasion, being able to assist on the agenda and all of that on github. 146 | 147 | Lane: send me your handle then we can move forward, trading off can help, much less of a burden per person 148 | 149 | Jenny: happy to help moderate as well 150 | 151 | Lane: anything else to discuss, or anyone want to stick around? 152 | 153 | (silence) 154 | 155 | Lane: bye everyone! 156 | 157 | # General Resources 158 | 159 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 160 | 161 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 162 | -------------------------------------------------------------------------------- /calls/notes/2020-04-08-Meeting-0007.md: -------------------------------------------------------------------------------- 1 | # 20200408 Governance Working Group Call 7 2 | 3 | Jason (@whoabuddy) is hosting the meeting today. 4 | 5 | ## Standups! What are you working on? 6 | 7 | ### Jenny 8 | 9 | Trying to up number of participants in survey, included in Blockstack's newsletter yesterday, and tweeted out last night too. 10 | 11 | No blockers, good to discuss on this call: writing the blog, or an update on the work we've been doing, great to showcase all the research to the broader community. 12 | 13 | ### Phillip 14 | 15 | Blocker: time. a lot ot learn but advancing. 16 | 17 | ### Jason 18 | 19 | More github management: need to publish an update for last week, going to remove survey repo and integrate into resources (plus all related linking/documentation). 20 | 21 | ### Lane 22 | 23 | I also posted a [written update](https://github.com/stacksgov/pm/issues/24#issuecomment-610588742). 24 | 25 | We're at 39 survey responses (+31 since release), really exciting to see, thank you Jenny for mentioning in the newsletter. Would still love to see us get to 100, but almost halfway there! 26 | 27 | All one on one interview notes [have been published](https://github.com/stacksgov/resources/tree/master/interviews) 28 | 29 | No major update on the governance proposal, last week we copied over parts of it to the [new proposals repository](https://github.com/stacksgov/proposals/issues), some comments and questions have come through, this is where it stands as of last week and the outstanding part is the foundation governance and will get an update from Brittany on PBC side. 30 | 31 | I wrote a "standard operating procedures" doc [for stacksgov project management](https://github.com/stacksgov/pm/pull/23) and could use everyone's feedback and suggestions! Idea originally proposed by Brittany, as the initiative grows, would be best to record best practices. how to run these calls including setting up ahead of time, running the call, what happens when it's over. Also regular updates and how to manage the github organization, what the repos are for, and a bit about the Discord chat and the Discourse forum. Did his best to do a brain dump, but please submit proposals, notes, etc and we will merge the pull request in after. 32 | 33 | I'm working [on a SIPs proposal](https://github.com/stacksgov/pm/issues/22) - based on Ethereum EIPs, Zcash ZIPs, Bitcoin BIPs and others. Not ready to share yet but will do so soon. Main deliverable right now around SIP process, doing some reading/homework on other "X improvement proposal" projects. How they happen, how those procedures apply or don't apply, and how we might want to improve that process or change it. Should be ready in the next few days, any ideas or comments please share now. 34 | 35 | ## Community survey 36 | 37 | Lane: Mentioned it a few times - question we should ask ourselves, what do we want to do with the results? at what point do we want to begin peeking at them? waiting for the number to kick up right now. Do we want to begin sharing? Wait for some point? How to share the results? These are things everyone should begin thinking about, and share your thoughts if you have them! 38 | 39 | Phillip: timing for results? need that to process and generate conclusions, the more time the better 40 | 41 | Lane: good question, "our" initial plan (discussion with Brittany), based on the paid typeform account. Survey would run until the end of this month so three more weeks to gather responses. If people feel this is not sufficient then let us know what you think. 42 | 43 | Phillip: so we have to give effort to make more people respond? maybe the best way is to do a personalized incentive? talk to each one - did you fill out the survey? 44 | 45 | Jenny: think we have pretty good distribution from the April newsletter (pretty large email list), that will be going out this week, would probably wait on personal incentives and see what the results are from the newsletter. could be a good route to go toward the end of the 3 week period. 46 | 47 | ## Blog Post Idea / Outline 48 | 49 | Jenny: no other major thoughts - but want to ask if everyone feels ready, or if we want to wait for a milestone. The work we've been doing is really interesting, if we want participation from other community members could be a good way to go about it, how to structure / how to report back to the group, any initial thoughts we have then we can discuss. 50 | 51 | The process of getting the blog post up would be fairly simple, if we can draft it and send to Mitchell it will be easy enough. Any thoughts everyone? 52 | 53 | Lane: think it's a great idea, been discussing from way back, spreading the word and letting a broader set of people see what is going on. question I'm asking myself - what is the core message? what is the call to action? because we are doing a lot of things. 54 | 55 | Jenny: think the initial motivation is that this would help with distribution for the survey, could be a good opportunity to showcase all the different sets of expertise within the group, everyone coming from a different background with their own personal interests, impressed with the initial discussion and last week we had Harold's presentation on the research he's done, the perspective of so many community members, might help people pull the trigger on participating. can get involved regardless of what your background is, and __everyone interested in the success of the ecosystem has a stake in the work we're doing.__ 56 | 57 | Jason: This question came up recently with CoronaTracker, what is Blockstack doing for governance? A blog post like that would be a great resource to share. 58 | 59 | Jenny: absolutely, since Github is standard operating procedure let's make that work, maybe open an issue, could go faster if we crowdsource material from this group. wanted to get a temp check today. 60 | 61 | Lane: ask about timing, connection to survey, should this happen in the next week? 62 | 63 | Jenny: if yes to helping with survey, maybe sooner, but don't want to add onto workload beyond what we have already. if we can make it easy as in submitting thoughts on github to turn that into a workable draft, I encourage us to do it. Depends on whether we feel comfortable and we have the capacity. 64 | 65 | Phillip: the summary of what we are doing is a list of questions we want to answer, way to explain that's why we have a survey, here is how to particpate, and to try and answer these questions. there is no definite answer yet. that ask for help and participation is a nice call for action. we still have the time to do that. 66 | 67 | Juliet: also put together a list of questions raised in the group initially, many have been answered, been meaning to get this to a forum post but happy to throw those things into an issue on github. 68 | 69 | Brittany: love the idea of crowdsourcing, what's important to the community, help answer questions for others. 70 | 71 | Jenny: next step she can take, can post some questions and topic ideas to github, make it easier to drop in their comments. she can start on that very soon, thanks everyone! 72 | 73 | ## Stacks Foundation Update (from PBC) 74 | 75 | Brittany: we've talked to our tax team, helps determine structure and what works best, where we are at now: most operations in the US, so exploring a US foundation. there are a few different types: 501(c)(3) charitable org (Zcash), other foundations that can exist: c6, c7, and c4, more like industry organizations such as the american bar association (industry nonprofit), main distinction between types is how they receive funding and activities they can do. 76 | 77 | When talking with people on the tax side, if we are exploring this route: will donations come in from community members? will we use other fundings? key question. 78 | 79 | Another key question around what types of activities the org can do: are we giving out grants? hosting fellowships? program like app mining? how will that impact our status and operate in that way. 80 | 81 | Since it's relatively new, we want to make sure to get an expert opinion and abide by all the requirements, with the knowledge some of our consensus mechanisms in blockstack are pretty novel, the foundation will take over the stacks treasury, would be eligible for stacking, maybe BTC rewards could fund it without any other sources. Does that count as income? Would we lose charitable status? questions are being explored. 82 | 83 | Eliminating the Singapore and other international foundations was a key learning for them, learned through talking to peers (can see in notes around Algorand), benefits of doing US is there aren't as many restrictions around off-shore board meetings and members. Seemed very limiting in how we could think of a board especially if it requires international travel. How do we be as inclusive as possible, and how do we think globally, as we grow and evolve how are we not limited in what we an achieve in the ecosystem. 84 | 85 | Next steps: have a convo with Deloitte later today, will help provide some outlines of a c3 vs c4 vs c6, and guidance as to which will make sense to allow them to do the activities she outlined. 86 | 87 | We will be drafting an application for that type of organization, would love to share with the community, we've been working with outside sources but sharing everything created thus far with this group, the proposal, survey feedback, all shared as part of this process. Feedback from this group will be realy helpful. 88 | 89 | Any questions to talk through? keep us in the loop as we progress through stages of understanding. 90 | 91 | Harold: thank you kindly for that, exciting to see a way for the foundation to be self-sufficient, leveraging what we have with the novel consensus algorithm. The public utility path that Blockstack has paved - is this is a viable means? Maybe attaching a governance-specific blockchain for self-sufficiency? 92 | 93 | Brittany: It would be the normal Stacks blockchain, PBC cannot earn BTC rewards as a for-profit entity (assumption, may change), but for the foundation it would potentially qualify to do stacking. Can have a more firm answer on that later. 94 | 95 | Harold: curious if down the line, with app chains, a chain specific to governance. 96 | 97 | Brittany: thanks for sharing, know that app chains have come up on the business models, thanks for mentioning that. 98 | 99 | Lane: had a thought - two sides of a coin. think the self sustainability is very exciting, PoX gives a potential route to that, just sorting out the kind of possibilities. There is a risk to highlight super briefly, his perspective that other foundations have done very poorly is lack of accountability. if you've read what i've written, it's a big thing he cares/thinks about, in the pre-crypto world foundations in an abstract sense that they do things brittany described: grants, funding, etc, but have to go through donors to raise funds. 100 | 101 | What we've seen in the cyrpto foundations that since they can mint their own money, it leads to sub-optimal behavior on behalf of the organizations. in the absence of relying on donors, what sort of *other* accountability mechanisms could we put in place? I'd like everyone to begin thinking about this. 102 | 103 | Brittany: a great point to bring up to be mindful and aware of. industry associations require paying members to exist, if a 501(c)(3) donations have to be a certain portion of operating budget, has to be through a large number of individual donors or company donors. loops could be built in. foundations have a 3 year grace period. like the idea of being accountable. 104 | 105 | Dan: another question/consideration, related to the Justin Sun takeover of STEEM, given the stacks foundation would control treasury, if we end up doing some kind of on-chain voting, how do these organizational structures prevent - how do we maintain the accountability? might be repeating the same concern as Lane? how do we avoid the justin sun thing on steem? not the same because he bought a company that controlled steem tokens, but something to keep in the back of the mind. 106 | 107 | Lane: add on to what you're saying, might not technically be the right term, but how to avoid "capture". there are more explicit and also more insidious forms of capture and accountability and transparency are two defense mechanisms. 108 | 109 | Brittany: would love to get feedback from this group with others who have done more research / exploration into these subjects. ways to create resistance against those. examples of most recent ones and what's gone wrong. 110 | 111 | Lane: great topics to include in the blog post, super timely and relevant. 112 | 113 | Harold: this reminds him of what he learned in joining the meeting with Jenny over game theory, slightly different topic but could apply to accountability, the game theories reference how important integrity is important in the blockchains. how things have been built by PBC, things coming in the future, lots of other possibilities that add integrity to this blockchain that others don't have. Dissuade from the only incentive to game the network. Accountability question brings to mind possibilities building this type of integrity into the governance system to broaden the donors. the breadth of interested donors to lane's point. in the way of important things: ecological sustainbility going into the future, business models the community is privy to, what kind of models those are, as it relates to ecological sustainability and paradigm shifts in data collection and consumption. added layers to governance. 114 | 115 | Jason: I think that's amazing, looking at the opportunity we have here as we think through, just like Jude did the [blog post on the common smart contract issues](https://blog.blockstack.org/bringing-clarity-to-8-dangerous-smart-contract-vulnerabilities/), we can look at what other governance issues are out there, and how the steem community has migrated to the hive community and some successes and failures with that. One of the things that has come up in the past for me is having no main one entity able to make decisions, in a way like "having two keys to turn the nuke", the phrase I think of, to add a check and balance procedure that will make more sense in the long run. 116 | 117 | Lane: that's a great example, mentioned before, a lot we can learn form Zcash, one thing unique is "multisig" on the brand: between the electric coin company and the foundation. there are some interesting ideas there. it has not been all smooth sailing, there was a dispute resolved last year, but multisig great example of accountability. 118 | 119 | Brittany: agree, great way to frame it. 120 | 121 | ## Any other updates? 122 | 123 | Phillip: comment, got stuck with microphone, many institutions in crisis now, governments in crisis, people don't believe in them. in the internet arena - all this icon/NICs that manage DNS getting a lot of pressure from the people, how they are dealing with the management of the domains. here in Chile and other countries suffering because of that. a lot of resources, managing that, accountability issue is getting stronger and stronger in how we do that. definitely an important aspect to consider, how we deal with that, how the foundation will get resources, etc. Very important aspect. Before there was no issue about that, nowadays everything very complicated. 124 | 125 | Jason: I think that's an interesting point, if we look at the bigger companies that handle the large portions of Internet traffic around the world, you're layer 3's of the world, start as a simple concept that expands and grows. As that happens you gain new abilities, ideally if you are doing it right, you will be entrusted with more and more and try to hold up that integrity. Definitely a good point and ties into what we are talking about. 126 | 127 | Any other updates, or anything to add? If not then thank you everyone for being on the call today, always a pleasure to go through this together! 128 | 129 | ## Next/recurring call schedule 130 | 131 | April 15th, 10am Eastern, 7am Pacific. 132 | 133 | # General Resources 134 | 135 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 136 | 137 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 138 | -------------------------------------------------------------------------------- /calls/notes/2020-05-20-Meeting-0013.md: -------------------------------------------------------------------------------- 1 | # 20200520 Governance Working Group Call 13 2 | 3 | (placeholder) - [see pm/issue#47](https://github.com/stacksgov/pm/issues/47) 4 | 5 | # General Resources 6 | 7 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /calls/notes/2020-06-03-Meeting-0015.md: -------------------------------------------------------------------------------- 1 | # 20200603 Governance Working Group Call 15 2 | 3 | (placeholder) - [see pm/issue#57](https://github.com/stacksgov/pm/issues/57) 4 | 5 | # General Resources 6 | 7 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /calls/notes/2020-06-24-Meeting-0018.md: -------------------------------------------------------------------------------- 1 | # 20200624 Governance Working Group Call 18 2 | 3 | (placeholder) 4 | 5 | # General Resources 6 | 7 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /calls/notes/2020-09-24-Meeting-0024.md: -------------------------------------------------------------------------------- 1 | # 20200924 Governance Working Group Call 24 2 | 3 | Note: *The content below is a raw, unedited transcript from Zoom.* 4 | 5 | ----- 6 | 7 | 1 8 | 00:00:00.570 --> 00:00:19.440 9 | Jenny Mith: Hey everybody, and welcome to the stocks governance working group meeting. Today is Thursday, September 24 and it is just after noon PST 9am PST and 5pm for those of us in London, which is just me. 10 | 11 | 2 12 | 00:00:20.850 --> 00:00:29.280 13 | Jenny Mith: And we've got a bit of a smaller group today. So we kind of agreed that we wouldn't be able to, we wouldn't have any forum for 14 | 15 | 3 16 | 00:00:29.910 --> 00:00:37.860 17 | Jenny Mith: Decision making, or anything, but we thought it would be worth going over some short updates and and also put an idea out there. 18 | 19 | 4 20 | 00:00:38.370 --> 00:00:46.020 21 | Jenny Mith: to incentivize more folks to get on the next call so that we can start making some of those decisions. And so I will start at 22 | 23 | 5 24 | 00:00:46.500 --> 00:00:58.380 25 | Jenny Mith: Because I know this has been on on everyone's minds on the grant proposal actually haven't done that much work in terms of revising or updating the material I think based on the last 26 | 27 | 6 28 | 00:00:58.800 --> 00:01:12.330 29 | Jenny Mith: meeting that we had. There aren't a ton of changes. We wanted to make what I think does need work is the bit on the guy hub in boxes proposal and like I mentioned in discord. I had a productive call with Jude. 30 | 31 | 7 32 | 00:01:13.170 --> 00:01:28.140 33 | Jenny Mith: On how to structure the project management of that particular project. Namely, we want to get an engineer from the PVC team involved to at least check in with certain teams and on their progress so that 34 | 35 | 8 36 | 00:01:28.680 --> 00:01:34.920 37 | Jenny Mith: Whatever is produced from that particular project is something that BBC could realistically adopt. 38 | 39 | 9 40 | 00:01:36.480 --> 00:01:47.160 41 | Jenny Mith: And yeah, so rather than applying this sort of bounty or like Hackathon type of framework. It's a little more of a dude I forget what you were calling it but it's like when 42 | 43 | 10 44 | 00:01:48.240 --> 00:01:52.830 45 | Jenny Mith: Governments bid for projects. What was the term your you. What was the phrase, you're using 46 | 47 | 11 48 | 00:01:53.340 --> 00:01:55.080 49 | Jenny Mith: Procurement. Yes. Yeah. 50 | 51 | 12 52 | 00:01:55.890 --> 00:02:10.560 53 | Jenny Mith: Or like a procurement process, which I think makes a lot of sense. And so I can actually, I can update that in writing. What is blocking me at the moment is I sort of put my asks from the engineering team on hold, given that this is a really busy week 54 | 55 | 13 56 | 00:02:10.920 --> 00:02:14.640 57 | Jenny Mith: For test it. I have it on my calendar to drop that in. 58 | 59 | 14 60 | 00:02:14.790 --> 00:02:20.730 61 | Jenny Mith: Some asks, but I basically need approval from the engineering team that this is something that we can take on and 62 | 63 | 15 64 | 00:02:21.540 --> 00:02:38.430 65 | Jenny Mith: Approval that someone from the engineering team can actually supervise this work, which I I'm pretty confident we can get. But yeah, that asked has just been put on hold for a week or so, but it is the last thing that sort of holding up the governance. 66 | 67 | 16 68 | 00:02:39.750 --> 00:02:44.490 69 | Jenny Mith: Or the grant proposal. So once I get decisions and answers on that and 70 | 71 | 17 72 | 00:02:45.180 --> 00:02:56.490 73 | Jenny Mith: Once you have some time to put the design doc together or another engineer has some time to put the design doc together. I think we would be ready to submit my goal is really to submit it by next week, so 74 | 75 | 18 76 | 00:02:56.910 --> 00:03:06.300 77 | Jenny Mith: Everyone can keep an eye out for that progress in the discord chats and obviously you're all welcome to plug in with feedback yourself in the doc. 78 | 79 | 19 80 | 00:03:08.370 --> 00:03:09.360 81 | Jenny Mith: That's my update 82 | 83 | 20 84 | 00:03:11.160 --> 00:03:17.040 85 | Jenny Mith: Jason, did you have anything you want to say on the the work you've been doing with the agenda and other things. 86 | 87 | 21 88 | 00:03:18.150 --> 00:03:19.440 89 | Jason Schrader: Sure. So last 90 | 91 | 22 92 | 00:03:19.440 --> 00:03:31.170 93 | Jason Schrader: Week. You know, I kind of threw a comment into the last agenda that talked about making the agenda, much more general and kind of taking each of the discussion items and 94 | 95 | 23 96 | 00:03:31.500 --> 00:03:40.380 97 | Jason Schrader: The items that we use to list out in the agendas back to the issues and that way we can get a little more involved with them and start getting them closed out and addressed. 98 | 99 | 24 100 | 00:03:40.920 --> 00:03:47.910 101 | Jason Schrader: So with that, right after this call. I am planning to submit a pull request that will have an issue template. 102 | 103 | 25 104 | 00:03:48.390 --> 00:03:58.380 105 | Jason Schrader: That's very generic and the main goal is that instead of listing out all of the action items within the agenda will instead just go straight to that label for the issues. 106 | 107 | 26 108 | 00:03:58.740 --> 00:04:13.620 109 | Jason Schrader: And we can continue to use labels and other ways is a better way to manage the topics but it's, it should reduce some of the redundant work and make it much easier to create agendas in the future as far as that goes, I don't have any blockers at this time. So I think that's it for me. 110 | 111 | 27 112 | 00:04:17.460 --> 00:04:19.020 113 | Jason Schrader: Well, you 114 | 115 | 28 116 | 00:04:19.080 --> 00:04:27.930 117 | Jenny Mith: And I know I know Ryan You're here to moderate a very small meeting, but if you have any updates, please feel free to share and Jude. Same goes for you. 118 | 119 | 29 120 | 00:04:30.180 --> 00:04:40.620 121 | Ryan Arndt: Yeah, can give an update, just a bike when doing calls for different for the grants program is to call us with different app and stuff like that move things forward. So it's keeping on keeping on looking forward to seeing the world from the gardens. 122 | 123 | 30 124 | 00:04:45.270 --> 00:04:56.790 125 | Jude Nelson: That much for me the Krypton release is imminent. So, and working primarily on that but sub 000 is now under master with the changes recommended by the governance group and by the 126 | 127 | 31 128 | 00:04:58.140 --> 00:05:04.410 129 | Jude Nelson: End by PVC surrendering and see on the technical steering committee so all the documentation is not linked to that. 130 | 131 | 32 132 | 00:05:05.820 --> 00:05:06.030 133 | Jude Nelson: And 134 | 135 | 33 136 | 00:05:06.810 --> 00:05:07.590 137 | Jenny Mith: That's a great update 138 | 139 | 34 140 | 00:05:09.570 --> 00:05:09.990 141 | Jenny Mith: Okay. 142 | 143 | 35 144 | 00:05:11.010 --> 00:05:16.890 145 | Jenny Mith: See that's leading of this call, we established that this would be a fairly short one, since we don't have a ton of people on 146 | 147 | 36 148 | 00:05:17.490 --> 00:05:24.660 149 | Jenny Mith: The idea that we wanted to throw out is that for our next meeting. Perhaps we could have something a little more social. 150 | 151 | 37 152 | 00:05:25.320 --> 00:05:38.820 153 | Jenny Mith: By everyone's some coffee cards and have everyone show with their coffee and pastries to just simulate the feeling of having an actual working group meeting and and I think that we all have been craving, the more social aspect of 154 | 155 | 38 156 | 00:05:40.080 --> 00:05:50.220 157 | Jenny Mith: Working together. So our next meeting should be scheduled for two weeks from now, but I'm you know I'm flexible in terms of like having it next week just 158 | 159 | 39 160 | 00:05:50.700 --> 00:05:56.190 161 | Jenny Mith: Because we didn't have a huge one this week, or we can keep it two weeks from now I 162 | 163 | 40 164 | 00:05:56.700 --> 00:06:04.860 165 | Jenny Mith: Totally am sorry for making mistake of not duplicating the meaning from a couple of weeks ago and only putting it on my calendar promise I won't do that this time around. 166 | 167 | 41 168 | 00:06:05.370 --> 00:06:13.890 169 | Jenny Mith: And but yeah for the next meeting. Whenever we decide to do it either next week or the week after. And let's make it a fun and social one 170 | 171 | 42 172 | 00:06:14.250 --> 00:06:20.490 173 | Jenny Mith: Will pay for some coffee and pastries and everyone should have a sufficient amount of time to 174 | 175 | 43 176 | 00:06:20.880 --> 00:06:30.210 177 | Jenny Mith: get updated on the content, we've been discussing and come prepared with their ideas because I know I saw a comment from Riga about something he wanted to raise with the governance group as well about 178 | 179 | 44 180 | 00:06:30.660 --> 00:06:40.050 181 | Jenny Mith: Making a specific decision on off chain names or something. And he's not here today. So I'd like to give folks like Rieger a chance to tune in as well. 182 | 183 | 45 184 | 00:06:42.570 --> 00:06:46.170 185 | Ryan Arndt: I've made the mistake before to Jay that duplicating on my own calendar thing. So I feel like 186 | 187 | 46 188 | 00:06:47.790 --> 00:06:51.870 189 | Jenny Mith: Everything is. All right. Any final updates everyone 190 | 191 | 47 192 | 00:06:54.720 --> 00:07:06.090 193 | Jason Schrader: Know that's that's it on my side and just thanks everyone for being here. Good to see you and Jude. Thanks for all the hard work. I've been watching and following along, and wow we're, we're almost to that next phase. I'm excited. 194 | 195 | 48 196 | 00:07:07.620 --> 00:07:08.160 197 | Jenny Mith: Thanks you. 198 | 199 | 49 200 | 00:07:09.420 --> 00:07:10.680 201 | Ryan Arndt: Know, thanks to 202 | 203 | 50 204 | 00:07:12.090 --> 00:07:12.510 205 | Ryan Arndt: Everyone 206 | 207 | 51 208 | 00:07:13.380 --> 00:07:14.820 209 | Jenny Mith: Alright see everyone later. 210 | 211 | 52 212 | 00:07:15.540 --> 00:07:15.780 213 | Ryan Arndt: All right. 214 | 215 | 53 216 | 00:07:16.440 --> 00:07:16.890 217 | Everyone 218 | 219 | # General Resources 220 | 221 | See [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) for the table of past calls. 222 | 223 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 224 | -------------------------------------------------------------------------------- /calls/notes/README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Working Group Call Notes 2 | 3 | Meeting notes from the [Stacks Governance Working Group Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group). 4 | 5 | The [full table of previous meetings](https://stacksgov.github.io/resources/#/calls/?id=previous-meetings) is available here. 6 | 7 | # General Resources 8 | 9 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 10 | -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /interviews/README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Stakeholder Interviews 2 | 3 | This directory contains notes from one-on-one interviews conducted by @lrettig as part of the "listening campaign" during February and March, 2020. 4 | 5 | - [Interview 1](https://stacksgov.github.io/resources/#/interviews/interview-001) 6 | - [Interview 2](https://stacksgov.github.io/resources/#/interviews/interview-002) 7 | - [Interview 3](https://stacksgov.github.io/resources/#/interviews/interview-003) 8 | - [Interview 4](https://stacksgov.github.io/resources/#/interviews/interview-004) 9 | - [Interview 5](https://stacksgov.github.io/resources/#/interviews/interview-005) 10 | - [Interview 6](https://stacksgov.github.io/resources/#/interviews/interview-006) 11 | - [Interview 7](https://stacksgov.github.io/resources/#/interviews/interview-007) 12 | 13 | It also includes an [interview template](https://stacksgov.github.io/resources/#/interviews/TEMPLATE). 14 | 15 | # General Resources 16 | 17 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 18 | 19 | # Licensing 20 | 21 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/resources/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 22 | -------------------------------------------------------------------------------- /interviews/TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview Template 2 | 3 | This is the template that was used for the interviews. Note that not every interview included every question. 4 | 5 | - What’s your role in the project/community/ecosystem? 6 | - How did you first get involved? 7 | - What are the mission/vision/values of this community/project? 8 | - What does governance mean to you? 9 | - What does _good_ governance mean to you? 10 | - How do you achieve legitimacy/confidence/trust in governance? 11 | - Is decentralization of governance the right goal? Why or why not? 12 | - Is this the right goal (i.e., decentralizing governance)? 13 | - How has governance worked in the past? 14 | - What’s gone well/not so well? 15 | - How would you like things to work in the future? 16 | - Where do we draw the line around stakeholders? 17 | - Who should have a role in protocol governance? 18 | - What are your thoughts on App Mining? 19 | - How do we govern the Foundation? E.g. directors, to whom should it be accountable? 20 | - What else should I have asked you? 21 | 22 | # General Resources 23 | 24 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 25 | 26 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 27 | -------------------------------------------------------------------------------- /interviews/interview-001.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 1 2 | 3 | * What is your role? 4 | * People don’t usually pay attention to what I do as long as it works 5 | * I give an occasional meetup talk often only 1/3 of audience understands 6 | * This is usually what I do, the extent of my interaction with the community 7 | * Community is very important for cryptocurrencies, even more than for e.g. Linux. A large community is a strong security measure against attacks on the blockchain, since they’re all vigilant and they care. 8 | * There’s real money at stake, skin in the game for community members 9 | * Reasons for them to care a lot about future of the project 10 | * Unlike conventional open source, forking a codebase is not sufficient to resolve problems - e.g., dozens of forks of BTC but their collective market caps are tiny 11 | * The notion of wealth/that your tokens have worth is “shared state” across the community - your tokens are only valuable if others believe they’re valuable 12 | * So we need to be able to resolve conflicts “in band” i.e. without forking 13 | * So the need for a cohesive community and conflict resolution mechanisms is far more important in cryptocurrencies 14 | * That said I don’t think governance is anything like it is in meatspace 15 | * Unlike governments of the world, you are not bound to one particular “nation” ie. blockchain 16 | * What that means is that the people that are most in need of conflict resolution protocols (automated or human-driven) are those who have skin in the game economically as well as emotionally - “I use this thing because I really do believe in the mission" 17 | * In academia, software forks happen all the time, it’s celebrated: we forked the Linux kernel and made these changes to test this hypotheses 18 | * The word “fork” is overloaded: you can easily fork the code, but forking the community is much harder. 19 | * How do you make people believe in your legitimacy? 20 | * People believe in blockchains for reasons that are monetary but it’s more than that 21 | * There’s a mission statement, ethos, set of values that resonate 22 | * Demonstrating that you can “walk the walk” of that vision 23 | * This is true outside of crypto - any sort of social movement is like this! The ones leading that movement are the ones seen as leading it the strongest 24 | * A lot of political revolutions e.g. LGBTQ, civil rights happen because they can appeal to consistency with e.g. freedoms in the Constitution/what the founding fathers said/believed. (Example: “black people and white people should be equal before the law” because “All men are created equal”) 25 | * This is generally true outside of “real governments" 26 | * And in blockchain - for people who care about that 27 | * There’s a lot of value in faking that signal long enough for bag holders to dump - there’s a lot of that faking going on, muddying the waters for economic advantage 28 | * You manage to walk the walk even when times are hard - e.g. when your token isn’t doing well 29 | * You do it with no skin in the game, or only token skin in the game - e.g. I want this to exist even if I don’t personally hold these tokens 30 | * This is true for Bitcoin as well - if Satoshi never spends those tokens - the ethos behind this “banking system independent of government” - whether you believe this mission statement or not is irrelevant, some people do 31 | * Ethereum: “We want to be the world computer” where you can execute programs without permission of government - this appeals to a similar segment of people 32 | * Blockstack: We want to create the user-owned internet; data, compute, you reap the value that your online activity generates. The notion of ownership is extended into your digital life, you’re a more fully-realized digital citizen whose inalienable rights are met through the deployment/instantiation of this particular protocol. 33 | * What do we do for lack of a constitution? 34 | * Eos was onto something but executed it badly 35 | * Constitution is legally binding but you can’t legally bind blockchain validators - there’s no body politic to do this 36 | * It was considered an encroachment on their rights 37 | * The idea was directionally right - should’ve called them operating principles - “here are the guidelines that make for a good validator” - rather than binding legal guidelines 38 | * We have [principles of dapps](https://docs.blockstack.org/develop/dapp_principles.html) - one of our most widely visited docs - based on an hourlong braindump I wrote on a train ride 39 | * This happens outside blockchain: e.g., [UNIX philosophy](https://en.wikipedia.org/wiki/Unix_philosophy) 40 | * A similar high level ontology could be created for Stacks that also enshrines operating principles 41 | * If you succeed in doing this, a trailing success signal of the quality of your principles would be many protocol-level incompatible implementations of those principles that all adhere to those principles 42 | * E.g. there are many binary incompatible but philosophically aligned UNIX implementations 43 | * I no longer believe in most of Barlow’s [Declaration of Independence of Cyberspace](https://www.eff.org/cyberspace-independence) 44 | * It’s a “fundamentally undemocratic manifesto”, i.e., “I should be able to do whatever I want, FU for getting in my way” 45 | * Does that include money laundering, child porn, financing terrorism? 46 | * Some people in Bitcoin reject the idea that these things could be bad since they reject the idea of government telling them what they can do with their money 47 | * I reject this idea for Stacks - it’s reprehensible 48 | * UNIX philosophy is not a manifesto - they were organically observed 49 | * a manifesto is different - goes stale faster than set of design principles - a manifesto is a creation of the political times in which they were written 50 | * Not really falsifiable - “it’s my opinion that…” e.g., “I should be able to do whatever the hell I want in cyberspace” 51 | * If you put it to the test and let people do this it’ll lead to outcomes that are at odds with western liberal democracies 52 | * This is not true for e.g. UNIX philosophies 53 | * Lane: design philosophies not designed to address social/economic/political things, so they’re less contentious 54 | * Design philosophy doesn’t say anything about social stuff 55 | * I disagree with the “apolitical” mentality: you cannot avoid politics 56 | * The tyranny of structurelessness happens implicitly 57 | * Aaron has a more Hobbesian take on humanity - he’s more cynical than I am 58 | * What are the values? 59 | * People play different roles, wear different hats 60 | * You can be a community member, a miner, an operator of a full node - or in multiple roles 61 | * I spend the most time thinking about how miners should behave, that’s the closest to what I have to work with 62 | * My thoughts are about how to keep the system running “without us” - if we core devs were to step away tomorrow - our job isn’t done until this is a resounding “yes!” 63 | * I don’t like the word decentralized b/c it’s not well-defined, it means “whatever feels good" 64 | * Our blockchain’s principles of operation cannot be separated from a notion of governance 65 | * Those who produce the blocks ultimately decide the evolution of the chain state as a whole 66 | * What appeals to me is less decentralization, and more, “how resilient is the system to bad governance?” E.g. if miners were to mine empty blocks? Or invalid blocks? If peer network were attacked and chain were to split? Can system recover by itself from these things? 67 | * Someday the governments of the world will pass laws limiting what exchanges can do - can the blockchain be designed in such a way that’s compatible with those laws? Without breaking the system/causing a hard fork? 68 | * Hard fork is mechanism of last resort - something more severe than amending the constitution - like an insurgency (not quite a civil war) or a secession 69 | * A lot of designs in Stacks chain are such that as miners do their thing, the system can stay in sync with what’s going on, _in situ,_ i.e., _without needing hard forks_ 70 | * To make sure the system can “keep up with the times”, can adapt to changes in regulation, what users need, etc. - we’ve done the following: 71 | * Clarity is a decidable programming language so it’s possible to soft-fork by constraining the set of valid transactions 72 | * This means you can tell whether a tx will do “the bad thing” before running it, and soft-fork by agreeing to not mine it 73 | * If the DAO were built on blockstack + clarity, you would not need to hard fork - you could tell it will withdraw funds from the DAO - I won’t mine it - soft fork it out of existence, without a chain split 74 | * Also, our system can fork, there can be multiple forks of the Stacks chain, that’s vital to surviving periods of miner issues - it’s possible for a longer fork to later invalidate decisions of some miners 75 | * The act of mining a block is the act of burning/transferring BTC via PoX 76 | * Another level in hands of users - “user support burns” - it’s not just me who is mining a block in the chain, others users can commit BTC to a block - if I’m an honest miner, my supporters can help me produce the chain, or take support away if I stop being good - users can send a transaction directly, their BTC + my BTC is summed together to form my mining power 77 | * This is not delegation - those to whom votes are delegated to can keep votes by force by refusing to mine those tx - as a miner, I cannot stop you from un-delegating 78 | * Users receive a portion of the coinbase, a fraction relative to their overall size, for each mined block - users aren’t just doing this out of goodness of their hearts 79 | * Are you afraid of vote buying? 80 | * Economists don’t expect rational actors to ever use user supports because “it’s more profitable to be a miner" and “it’s more profitable to consolidate user-support burns to avoid transaction fees” 81 | * Money is not the only thing that motivates people 82 | * E.g. segwit getting activated is evidence that people care about BTC’s longevity 83 | * A way for users to signal support for miners that are doing the things they want - there is a notion of consent of the governed here - and miners can’t stop you from doing this 84 | * What other ways exist to have consent of the governed? 85 | * Discord, forum, people talk to each other - we need to have a public forum for the community - in touch with each other, miners, developers, etc. 86 | * I try to do my interactions in public (no DMs) 87 | * Less technical, more of an operating principle: be as transparent as you can 88 | * Do. Not. Lie. 89 | * Do. Not. Mislead. 90 | * Do. Not. Bullshit. 91 | * I’ve seen the shitstorm that Twitter can be 92 | * Thought about this a lot, not in terms of governance, but how do I build social media apps that I’d enjoy using? 93 | * My idealized comms channel with the community would have two properties: 94 | * I can shadow ban people, full stop, if you’re a dick I don’t need to hear from you ever again, I’d rather let you “scream into the void” 95 | * You should be able to subscribe to my shadow ban list. This is a great way to deal with trolls, if you also don’t want to hear from the same trolls 96 | * Has the effect of creating a fishbowl that’s soundproof - you and I as core devs can talk on Twitter, there’s value in our relationship - the people from the outside (w shadow ban turned off) can see miasma of shitpoisting on Twitter - but our conversation is still public, don’t need to deal with psychological burden of shitposting - good for our mental health and also for the community 97 | * Don’t want people to burn out because others are horrible to them 98 | * My attention isn’t free, so it won’t be wasted on people who waste my time 99 | * A lot of people I follow on Twitter are on the receiving end of this - they get doxxed, harassed, even physically harassed, often women and people of color - in e.g. open source communities 100 | * Yes people are shitty and I blame people for that but I also blame the platform for encouraging shittiness - I need a way to avoid shittiness, and the platform needs a way to discourage it. 101 | * So my idealized channels: need to be able to shadow ban people, subscribe to your shadow ban list, and this info needs to be kept private so the trolls are forced to waste their time - there are studies that show this works and in fact that it’s the only thing that works - the effectiveness of shadow banning - is demoralizing rather than enraging 102 | * Free speech stops at my computer - once it’s at my computer I can do what I want with your data - this is not censorship 103 | * I as a user should have the right to implement to my own client that does this - you have the ability to build your own client with or without the platform’s blessing - this is an under appreciated feature - ability to curate your experience of the platform to you 104 | * The ability for users to own their own chain - I briefly described app chains to you - I’m completely ignoring eth2.0 and algorand and dfinity and other shard-based systems because I don’t think they’ll work 105 | * The problem I’m interested in solving isn’t building a bigger mainframe 106 | * Users can seize the means of production by owning the computing that happens on just their data (didn’t mean this to sound so Marxist!) 107 | * The history of computing is largely the history of sharing time on the mainframe - batch jobs went away in favor of the computer multiplexing itself into processes, login shells, virtual computers - giving you the illusion that you have access to the entire computer - with the assumption that none of us will even come close to using the system’s full resources 108 | * Preemptive multitasking system - this principle lives on today! 109 | * Also true for web servers and the cloud - we call it “login sessions” not “time sharing” 110 | * You’re using a tiny sliver of Facebook’s processing might - all those things require computing, state transitions - e.g. updating your feed, image tagging, etc. 111 | * Stacks gives users the same kind of power - not by forcing them to all compete over a tiny trickle of bandwidth like blockchains today - but by letting users run their own blockchains, i.e., app chains, that only process requests on the user’s data 112 | * The act of mining an app chain is the act of sending transactions to a parent chain that anchors blocks in place and encodes parent-child relationships 113 | * Stacking many chains on top of each other - there can be infinitely-many such chains, all just as reorg.-resistant as main BTC chain 114 | * There’s a fundamental difference with sharding - each chain has its own token, and there’s no two-way transfer 115 | * That these are blockchains is an implementation detail - in reality they are just decentralized personal servers - I have a raspberry pi at home acting as my server - take that away but keep the concept - other people authorize transactions by mining them - the server logic itself is replicated across all your devices and your Gaia hub - Gaia can serve chain data to anybody and thus service read-only requests while you’re offline 116 | * It’s offline until you sign into app, then you process incoming transactions, state transitions - because the system can fork, your decentralized personal server is resilient to failure - can restart it at any time to undo things that happened in the past (or pick up where you left off if your device breaks or gets stolen) 117 | * There’s no maintenance because the programming model of Clarity is much smaller than sharing e.g. a VM across devices - much more tailored towards realizing this decentralized personal server that carries out state transitions on your data 118 | * The fact that we have a token is serendipitous. The token is really just a way to implement time sharing in a resource-accountable manner. There are underexplored business models that would allow me to sell tokens to others to allow them to post data to me: 119 | * For me realizing a benefit from the app 120 | * Having an easier time mining blocks that requires a tx on a separate chain that I need a token for 121 | * Etc. 122 | * On “App Chain” concept 123 | * That stuff is about business models, but the overall mission of app chains is fundamentally about users owning the internet 124 | * App chains also have an impact on governance: there’s no need to change the main chain all the time for every new feature. If you want to try out and use a new blockchain feature in production that’s incompatible with the mainnet, you can spin up your own app chain with that feature. For example, if you want Clarity routines for verifying zero-knowledge proofs, you can fork the Stacks codebase, add that in, and spin up an app chain with those new functions available. You don’t have to modify the Stacks chain itself. 125 | * In this model there are three roles: 126 | * Stacks chain proper, root chain that stores mining and routing for discovery of chain above it 127 | * Intermediate chains - all app-chains, their function is to be hosts for other chains, e.g., “cloud servers” - to increase total no. of chains at periphery that can be supported 128 | * User-mined app chains that will only ever have one miner - the user itself within the context of that one app. I as a user can have such a chain for every account I have in every app - just legitimizing writes others make to my state. 129 | * Re: governance: GNU herd, obscure kernel that Linux ended up taking over 130 | * Stallman tried to put in design principle: OS behaviors - process management, dealing with device drivers, resource allocation policies, etc. - can be set on a per-user basis 131 | * Different than normal timesharing systems like UNIX where you’re at the mercy of the sysadmin 132 | * Between traditional timeserving and e./g. your own VM on AWS 133 | * Difference is lack of coordination - frees users from stepping on each others’ toes 134 | * If you put each human in their own “hermetically sealed matrix” - everyone you talk to is a robot - you’re the only real person in your own universe 135 | * No need for governance because you’re not interacting w people in the first place 136 | * Makes innovation easier to come by - your app chain can be tailored to do anything 137 | * “The only way you can interact with my app chain is through my tx which I mine” - wholly acceptable for me not to mine your tx 138 | * What about Urbit, or SSB? 139 | * Urbit is toxic and I don’t seek to emulate it in any way - it’s “digital naziism" 140 | * you are given a name that you don’t own, you’re at whims of galactic senate - it’s neo-feudalism 141 | * SSB is very link-local: my state is not externalized anywhere. 142 | * the only way you and I can sync is if we are on same LAN or have third party relay server that relays STF 143 | * in our model, we make provision, you don’t need to publish blocks, just hashes, but you do have to publish blocks to legitimize the decisions you made 144 | * How do changes happen now? 145 | * Very much by decree. We say a hard fork has happened and it happens. 146 | * It’s all been uncontentious so far 147 | * I don’t like it, I don’t think it’s sustainable 148 | * We’re getting rid of it too. 149 | * Stacks 2.0 has mechanisms to do _in situ_ soft forks, and rolling out incompatible features as app chains, it should remove need to do hard forks altogether 150 | * If a hard fork is ever needed, we’d have a committee set up for deciding this - Muneeb is best person to talk to about this - a five person committee: one person from PBC, one from Stacks Foundation, one community seat, and two others 151 | * They’d have power to say emergency is happening, we have to hardfork 152 | * A lot of things won’t need this 153 | * Similar to BTC we’d have support for on-chain signalling 154 | * App chains for launching new features that are backwards incompatible but still valuable 155 | * Technical governance is more like a do-ocracy 156 | * Unlike BTC and ETH we’d encourage people to make their own chains 157 | * The token is not meant to be money or replacement for money 158 | * Do these things because they’re interesting or solve a problem not for money 159 | * Token IS an AWS compute credit 160 | 161 | # General Resources 162 | 163 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 164 | 165 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 166 | -------------------------------------------------------------------------------- /interviews/interview-002.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 2 2 | 3 | * What’s your role? 4 | * Getting to know community well enough that I can develop effective strategies for growing the community and engaging/activating the community 5 | * Blockstack has a really broad community of interested stakeholders, but for a while it operated like a brand community - a platform people were excited about, they came to us about features 6 | * but didn’t really come to us as much about getting involved, even if they’re talented/intellectually curious/have overlap in interests 7 | * It’s interesting and challenging, getting to know people, find out how they want to step up and take charge 8 | * This year, been building on momentum from PoX, concerns or response to pausing of app mining 9 | * People can tell there’s a shift in focus and what we’re building, there’s still a lot confidence and trust 10 | * We’ve made it clear to community members that they’re playing a huge role in that - my job is to facilitate that genuine collaboration 11 | * Nebulous role but focused on community 12 | * Why is there confidence and trust? 13 | * Despite the fact that the team hasn’t flexed that open source muscle as much - having a system of working alongside community - we are in touch w the community regularly 14 | * Make a lot of time for personalized communication 15 | * Not just pushing out a blog, newsletter, etc. - those things are valuable and we need to do them 16 | * Muneeb spends a lot of time in telegram personally answering questions 17 | * We started having town halls - fairly new 18 | * Hasn’t been systematized but when they hear from us it is personal and our messaging puts them first 19 | * Bonds they make with each other are strong - you see the friendships at the blockstack summit - these community members talk to each other a lot 20 | * Where else in the world will they find someone who has been through the challenges of app mining? Only here 21 | * Element of trust must come from being very principled as a company 22 | * Can’t Be Evil campaign resonates w people, pursuing transparency in SEC work - we spent a lot of time and money on this process - want to make us and what were doing more accessible 23 | * I’ve heard from community member, and I agree, this is an inclusive community, relative to other crypto communities 24 | * We didn’t have regular community managers until last summer - so people were monitoring themselves - that’s pretty special 25 | * Even I’m trying to work on having a formalized code of conduct, finding a way for community members to enforce that - we have some incidences of people being unpleasant - but people being outright unpleasant are new, trolling is new 26 | * Real community members don’t troll. They’ve taken the time to go through our docs and are focused on other things, i.e., building on Blockstack. 27 | * How has governance run up to now? 28 | * App mining - but this example carries across the project 29 | * An idea that was heavily researched and developed by PBC team 30 | * Evolution of app mining was interactive: very vocal community members were involved in suggesting improvements, but they were looking to PBC to make the decision 31 | * If enough people were vocal about something, we could take that into account - or about something they did like 32 | * It seemed more one-sided than where we’re trying to go 33 | * There were some technical things with judging - people could easily spam Twitter or other social media with app name - that could count for Awario - so we got better about that scoring. 34 | * When people figured out that people were gaming the app mining program, they raised it and it would be immediately addressed - crowdsourcing to detect gaming - community would self-police. People very vocal about perceived injustices, vocal about banning people or changing judging criteria. 35 | * But we really value community input, and are happy to change decisions based on what community members are saying, what they want 36 | * Where we want to go is community members suggesting things, not immediately coming to PBC team members, they have processes and procedures and resources for those ideas without needing to come to me or to the team at all 37 | * Going forward 38 | * I’d want governance to empower community members to build things on their own 39 | * There’s been so much good engagement on app mining. We asked for proposals, got a lot of great feedback, but also got a lot of thoughts and opinions about how it should be done or what’s fair/not fair. Good to have that kind of discussion, but I was hoping to see more community members saying, clearly this is easily gameable, I wonder what I have to learn to understand why it’s easily gameable - game theory involved - I organized a game theory call for community members to understand basics 40 | * Would want to see people doing research, sharing it: “this key element of app mining program is faulty, I propose we swap it out for this idea instead, here’s why and here’s the research that backs it up, here’s next steps, here’s how we facilitate it” - more thorough! 41 | * Right now this falls on PBC, it’s time/resource intensive, we’re happy to do it, but would be great if community could do more 42 | * Gov. model that caters to this would be one that lays out clear processes for building support, resources for ideas that have clear support 43 | * Self-policing a community: processes you can put in place that don’t involve law enforcement! Self-sovereignty, this is what our community cares a lot about. 44 | * What else? 45 | * How automated can we make governance? This is interesting. 46 | * I can see where these people are coming from 47 | * I think you need a social element, and you need people to enforce an effective governance model. 48 | * What has worked for other projects in terms of rotating contributors? Even for something small as a GitHub repo — how do you make sure the community members who take it over don’t monopolize it? 49 | * In first draft of governance proposal I’d like to see a very good idea for how to give everyone a say, implement time/term limits - make sure they’re actually doing their part, that you can rely on them 50 | * People talk about voting a lot, there are lots of ideas out there 51 | * As a small community only a few people offer ideas, easy to vote 52 | * If you have 100 people volunteering to maintain a repo, how do community members vote on their representatives? 53 | * I don’t have super strong opinions about how this should work, it’s about what the community thinks 54 | * I’m always tempted to jump in to these convos - will it make the rich richer? Should you need STX? What if you don’t have any? I have lots of opinions about these 55 | * Balancing act - leading from behind - while being open to the will of the community - this is “good stewardship" 56 | * What else? 57 | * How community management would work under this future governance model 58 | * People feel like decentralization is really far away, and having an operational governance model is also far away, so we need a dedicated community person to make sure things are on track 59 | * But if we are decentralized, people are engaged/empowered to do their work? Is there a liaison? 60 | * I would want that to be laid out 61 | * How will this role evolve? Vis-a-vis new entities, processes, etc. 62 | * New entities that can exist - we talk about possibility of lots of new entities to spin up out of community - I imagine this process could be quite complicated - entities have resources, adhere to certain principles 63 | * What’s the constitution - guiding/overarching principles? for all these entities 64 | * How do you define a stakeholder? Where do we draw the line? 65 | * I understand POV that stakeholder literally has to hold STX tokens, but I think a lot of community members don’t for financial or other reasons, but have contributed to growth of ecosystem/community, and I think I’d count them as stakeholders too because they do work/put in effort to advance ecosystem 66 | * In future, whether we count non-STX holders, a stakeholder needs to be someone willing to share not only in benefits but also in risks and failures 67 | * Stakeholder theory - Mariana Mazzucato - what’s happened in US economy recently - increasing privatization of benefits, socialization of risks, e.g., big bank bailouts 68 | * If you’re a stakeholder you have to be willing to take the downside too 69 | * App mining was super valuable, it’s paused at the moment, it’s not what we wanted it to be, but learnings were so invaluable 70 | * I hope we can work with the community to come up with a better version of App Mining soon - we learned what we needed to learn to run a better version in future 71 | * Some people got payouts, some may feel like they lost out, but that’s to be expected from something experimental 72 | * I hope our community is one that understands that dynamic, that to be a stakeholder it’s not just upside, there are risks we take to move the ecosystem forward, and if they don’t work, we just move forward 73 | * Kinda like how the state runs (or used to run) 74 | * I tried to remind the community that Tesla got its start from a $550M loan from the government 75 | * A stakeholder is someone who understands the risks of participation - want ppl to take that seriously 76 | * Is there anyone you’d exclude? 77 | * Don’t quote me on this as my final answer but I’ve been thinking about this. In the future I’d exclude passive app users who don’t hold STX. 78 | * I count people actively contributing to community, STX holders, developers, app users using STX for apps - there’s a direct contribution to the community 79 | * If you’re a passive user, just DL an app, not really providing feedback - although those people have potential to grow into genuine stakeholders - but I wouldn’t lose sleep over that 80 | * Should we make progress on our mission, user-owned internet, it would/could affect everyone 81 | * My thought: we draw lines today but can make room for an arbitrarily large set of people 82 | * App mining - not what we wanted it to be 83 | * From what I know, when we set out to implement this program, the idea was to have an algorithmic program that could easily evaluate app quality and scale to hundreds of thousands of apps - through many iterations it was clear that’s a huge challenge 84 | * In other community proposals, they’re suggesting we get real people involved - maybe not possible to automate it - people always have to be involved in that process 85 | * Personally I don’t think it has to be automated - that would be nice but there’s always nuance when it comes to projects that people put time and effort into - to have something spit out a score for an app that took years, has the potential to become really good - this could be unfair, you can’t please everyone, just because they put work into it 86 | * Community member brought this up, it’s a good point - there’s a distinction between incentivizing good app development, and rewarding devs just for building apps, vs. grants or bounties - there’s a certain amount for a project that achieves this, who can build this? 87 | * Right incentives, not just rewards program 88 | * What is good governance? 89 | * Has processes in place to always take into account those who are the worst off 90 | * Could be programs, subsidies, social mobility programs in general. Those would be laid out, accessible to those who are worst off. 91 | * This invokes images of people in poverty but in our case it could be those without STX - is there a way for them to get STX? To become stakeholders quickly. 92 | * Good governance would take that into account. 93 | * Good governance by default can build diverse communities 94 | * In crypto there’s a lot of discussion about diversity issues 95 | * Community advisory boards - criteria for people getting elected takes into account diversity - has to ensure that the people on the board have varying amounts of STX holdings, come from very different backgrounds 96 | * Can’t think of a PC way to describe it but it would be built into the criteria for representative positions 97 | * As an example - in traditional way people talk about diversity, identity, don’t have to talk about this - look at passive app users who don’t have STX - maybe we should reserve a position for that kind of person, a voice from someone on the fence about joining. Maybe this is a bad example but it’s a thought experiment that would be good for everyone to do. 98 | * If this “passive app user” represents a group that could convert to full-time users. 99 | * What are our mission/values/etc.? 100 | * I’m a big proponent of building a user-owned/controlled Internet 101 | * For me what that means is shifting the power dynamic s.t. users are the ones in control of their identities, data, and digital assets 102 | * Ownership is a complicated thing, I don’t love idea of “grow internet ownership” b/c it doesn’t mean anything to a lot of people - until you start talking about things like home ownership - who in our society has full ownership over their property? 103 | * Three-pronged: digital assets, hope you have full control over these; data, would be better if you have full control; identity, e.g., Balaji talks about pseudonymity (not sure how I feel about this) but you want it to be the case that your ID is yours and no one can ever commit fraud in your name or whatever 104 | * these things need to be in place to have true ownership and self-sovereignty 105 | * The mission of the project - which has grown to encompass many things - is to build a user-owned internet 106 | * What that looks like in future? Thriving economy, users have a say as opposed to just big tech 107 | * What about shared values? 108 | * Can’t be evil engineering principles 109 | * #1 Ownership > Access 110 | * #2 Safety > Convenience 111 | * #3 Permissionless > Trust 112 | * #4 Incentives > Enforcement 113 | * #5 Cautious > Agile 114 | * Privacy or at the very least transparency 115 | * People always talk about privacy, a big value is transparency, want to know what I’m getting into/where my data is going 116 | * Ownership of data and private keys 117 | * Safety and security over accessibility - dealing with inconvenience of web3 products now, tradeoff being that you know what’s happening to your data 118 | * Esp. with PoX - there might be newer values people talk about - but values that have resonated most are under this can’t be evil umbrella 119 | * What else should I have asked you? 120 | * What role does PBC team play in decentralization? 121 | * Sometimes we say, “Not much will change” (in the near future) 122 | * But don’t know if that’s the case 123 | * I think we’d continue to focus on product offering - developer tools 124 | * Being active contributors to the product - but "just another open source contributor” 125 | * I’m very curious about that. 126 | * Stakeholder theory - there’s some uptake on that idea in the community - but what expectations do community members have for decentralization? E.g., roles to grow into 127 | * I often talk about decentralization as PBC members working more collaboratively with community members as if we’re on one big team - in a company you talk about sharing in profit, revenue, salary, etc. - and I think, what are the community members’ expectations? 128 | 129 | # General Resources 130 | 131 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 132 | 133 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 134 | -------------------------------------------------------------------------------- /interviews/interview-003.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 3 2 | 3 | * What’s your role? 4 | * I’m one of the core devs. I’ve been involved in design of blockchain, both consensus protocols and smart contract language 5 | * I’m most involved in the Clarity language, esp. the implementation of the VM and static analysis patches 6 | * Also worked on dev tooling, things like that 7 | * Interactions with/relationship to the community 8 | * I interact a bit less than other engineers 9 | * I reply to GitHub issues, occasionally give talks on the tech 10 | * Otherwise not super involved in social consensus/what community wants or needs from the platform 11 | * Why? Personal preference. I tend to be less of a large group people person. 12 | * I haven’t experienced much negativity online, but I also don’t have much a preference on e.g. Twitter 13 | * When we’ve posted articles that were, e.g., critical of various projects I’ve gotten feedback emails from people, but nothing particularly negative 14 | * I just have a difficult time interacting with open feedback channels 15 | * I tend to try to treat each piece of feedback as “its own micro-emergency” which not conducive to getting a lot of work 16 | * Who should have a role in protocol governance? 17 | * There’s a time-dependency to this answer 18 | * The Stacks 2.0 that is launching is something that is very much “a bet and the brainchild of Blockstack PBC" 19 | * Once that has hit the network, once people are using it, it “sort of leaves our control" 20 | * At that point the stakeholders invested in this chain - not just funds - people that have invested time, energy, etc. - they should all have a say 21 | * Does this include anything other than protocol? 22 | * No - not treasury management, nor management of funds - that’s up to the possessor of those funds 23 | * Deployment of funds managed by Stacks Foundation should be governed by agreement/charter/mandate of the Foundation 24 | * Who is a stakeholder? 25 | * Those who definitely are: those who hold STX tokens, developers of apps that use the Stacks blockchain, users of those apps 26 | * Those are primary stakeholders 27 | * I take an expansive view of who a stakeholder should be 28 | * Ultimate goals of project is to bring a better class of apps to users in general 29 | * Viewed through that lens, everyone who is alive today or will ever live is a potential stakeholder 30 | * And there is no “blacklist” (of those who are not stakeholders) 31 | * What are the values of this community/project? 32 | * Respecting users’ digital interactions, “digital rights” (we played around with this idea for a while) 33 | * That’s the goal of the project - apps that preserve both users’ data privacy, and treats their data, public interactions with a kind of respect 34 | * Compare to e.g. Google, which had the “Do no evil” ethos at one point 35 | * At Blockstack we want an Internet where that’s fundamental to the protocol - apps can’t be evil with respect to use of user data 36 | * That’s the largest shared value 37 | * What does governance mean to you? 38 | * How you resolve conflicts of direction and also how you decide you’ve reached consensus about direction for anything 39 | * Primary use case: We want to introduce new functionality to our blockchain - how do you decide whether it should be introduced? How it should be introduced? Who has “veto control” over approving the implementation or whatever? 40 | * Other use cases? 41 | * There are areas where governance is less critical but could be helpful 42 | * Tooling built on top of the protocol - there’s tooling that will have various levels of being blessed by the community 43 | * That “blessing” process involves governance 44 | * The first question someone will inevitably ask when building an app on blockstack is - what do I need/which library should I use? 45 | * This could be community-driven - needs a way to “bless” things 46 | * Look at Truffle in Ethereum - it wouldn’t cause a chain split if people used another tool - but if you don’t have a system in place to choose the best tool, it has a negative impact on the DevEx which affects the community 47 | * What does _good_ governance mean to you? 48 | * "A system where stakeholders don’t feel that they need to leave the ecosystem in order to have their voices heard or their issues addressed" 49 | * Or if left unaddressed, then they’re small enough issues that they wouldn’t leave the ecosystem 50 | * It’s very much related to the impetus to leave. Analogy to real-world government: it’s good if it’s responsive enough that people don’t seek “extra-democratic means for resolving conflicts." 51 | * Anything else? 52 | * Transparency of decisions - that’s a fundamental tenet of good governance 53 | * When a decision is made, even if it’s one you disagree with, you can see how/why it was made, how it was achieved, and the motivation for that decision 54 | * When people think about doing governance in “automated fashion” like on-chain voting it’s somewhat wrongheaded because the important thing is that, when decisions are made, you understand how they’re being made 55 | * The trap that people fall into with on-chain voting is that you get an audit trail but it can obscure what’s actually going on in a way that public board votes, etc. don’t obscure 56 | * How do you get legitimacy/confidence/trust? 57 | * Trust and legitimacy are a bit different 58 | * Trust is earned through actions: a community trusts you if the things you as a governance platform have been producing, the decisions you’ve been making, "actually reflect the community’s desires" 59 | * Legitimacy is kind of like verification that the actual mechanisms of governance are operating correctly - if we have a governance system where we say we have these independent components - Foundation, PBC, representatives of the community - verifying that those mechanisms are actually behaving independently, actually reflecting the stakeholders that they claim to reflect 60 | * Confidence is a measure of how confident you are in something else like legitimacy or trust 61 | * Can be increased through, e.g., more transparency 62 | * I’m placing trust in something, in some process, and I have some degree of confidence that decisions are being made as they say they are 63 | * Is decentralization of governance the right goal? Why or why not? Is this the right way to do it? 64 | * I think it is the right goal because centralization is kind of like a “ticking time bomb” unless maybe there’s other ways of formulating a centralized body 65 | * "If a platform is centralized, you’re just waiting until the day that the controller of that centralized body decides that it’s more profitable, that there’s more power to be gained or whatever by exploiting the platform" 66 | * "Decentralization can solve that problem by putting more power into the hands of the stakeholders of the platform so that they can ensure that never happens" 67 | * There are centralized bodies that don’t suffer from this, e.g., structure of companies that are co-ops: they can avoid this ticking time bomb, but in a sense they are decentralized in their governance too 68 | * Does this all apply to Blockstack as well? 69 | * Sure 70 | * The way this becomes important for, e.g., the protocol: centralized apparatuses that support protocol like Blockstack PBC might have finite lifetimes 71 | * But if we correctly decentralize the platform, users would be able to continue to support the platform 72 | * "The protocol itself by design can hopefully prevent a lot of rent-seeking behavior but that’s not exactly the same as the sort of decentralization concepts that people think about when they think about governance" 73 | * Is this (i.e., setting up a Foundation) the right way to do it? 74 | * (after a long pause) I’m not sure 75 | * Determining the “voice of the community” when it comes to the future of the protocol is tricky and I’m not sure I have a ton of insight there 76 | * If I’m looking at models outside of the blockchain space, co-ops are perhaps the best model 77 | * Usually you have to pay some sort of membership fee, there’s a “verification that you’re a real person,” but there’s a benefit you get from the co-op beyond just a vote. You get, e.g., a membership discount in addition to being able to vote. REI is such a successful co-op. Also, Vanguard. But your vote is “earned by keeping your money with Vanguard." 78 | * I think there might be some kernel of an idea there - the “user voice” towards the protocol could through some sort of org. structure that looks like a co-op. 79 | * How have things worked in the past? 80 | * It’s been dictatorial (benevolently) 81 | * PBC has functioned as the arbiter regarding the direction of the platform, makes proposals, accepts feedback from the community, takes suggestions though the forum, Discord, etc. 82 | * Acts on that feedback, "like the relationship of a king to his subjects" 83 | * There have been a couple of cases in which feedback has been integrated 84 | * Biggest area of contention so far has been App Mining 85 | * There’s been a lot of community engagement and enforcement of the “correct operation of App Mining" 86 | * Has a lot to do with transparency of the process 87 | * Transparent components, e.g., how scores translated into rankings were continuously checked by the community: there was an incentive to do so because people checking were getting App Mining rewards - there were actually cases of errors being found 88 | * In some cases, designs have changed based on community feedback on, e.g., blockstack.JS and the Blockstack browser - they haven’t “radically changed the directions” of proposals but tweaks were made 89 | * What’s gone well/not so well? 90 | * The changes we’ve made over time have been towards our protocol gradually moving away from reliance on Bitcoin in a lot of ways 91 | * We’ve “gradually devolved from Bitcoin" 92 | * Each step of that process has been a proposal we submitted to the community, and then we got some feedback on it 93 | * These successive steps have gotten less contentious at each step 94 | * But in the beginning when we started moving away from BTC, e.g., paying for names using STX instead of BTC, that was fairly contentious 95 | * The nature of our community changed a lot - a lot of "big bitcoiners" stopped engaging, and new people came in - this may be why it became less contentious 96 | * It worked well in the sense that we are where we are today because of those steps, but at the same time, someone might call it an instance of “governance failure” because we made this decision in spite of some opposition on the part of some of the community 97 | * And it was a decision about evolving the platform to something potentially radically different - from various perspectives you could say that’s “not even a matter of governance,” we decided we wanted the platform to be something very different than it was 98 | * How would you like things to work in the future? 99 | * The direction I want to see the platform go is I’d like to see the Stacks 2.0 launch, and run continuously for the indefinite future 100 | * The ecosystem, platform, community should mostly be focused on the apps that the community is using 101 | * These apps should be as preserving of users’ rights as they claim to be 102 | * I’d like to see consensus around what is a good app, and how a good app should run or function, so there’s a “badge of approval” that, e.g., this app is a “digital-rights-preserving app" 103 | * I’d like to see that aspect being community-governed 104 | * Lane: this is almost like an evolution of App Mining 105 | * What about App Mining? 106 | * I think of App Mining as a funding engine for these apps that we want to exist. I’m less concerned about the mechanisms of that funding than maybe other people. 107 | * But I’d like to see these apps get funding maybe in a similar way to how funding works for apps in the “real world” - if it looked like the VC ecosystem, I wouldn’t see that as a failure, even though a lot of people probably would 108 | * "They see the blockchain world as a way to 'escape the financial systems we’ve built’ but there’s been 100 years of experience in our financial system for funding" 109 | * What is our role here, then? 110 | * Someone - the Foundation? - holds the tokens that need to be deployed, to kickstart the process 111 | * We have capital set aside specifically for doing this 112 | * There’s a role for the Foundation but it could be as limited as saying “these 35 orgs, each gets 1M STX, each one signs some charter or something that they’re going to use these funds for the purpose of kickstarting an app ecosystem" 113 | * How do we govern the Foundation? E.g. directors, to whom should it be accountable? 114 | * Depends partially on its powers 115 | * You should have a board member that represents community in some way 116 | * And a board member that represents the developers in some way 117 | * If you look at how European company boards tend to work, they tend to have a board member that’s a union representative 118 | * In the USA we tend to think of unions as a “counterbalance to boards” - it’s different in Europe 119 | 120 | # General Resources 121 | 122 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 123 | 124 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 125 | -------------------------------------------------------------------------------- /interviews/interview-004.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 4 2 | 3 | * What’s your role in the project/community/ecosystem? 4 | * I stumbled upon the community and been struggling with trying to find my goal 5 | * I see a vision I agree with, that aligns with my values 6 | * Been trying to find out where I fit in the ecosystem: governance, biz models, mining 7 | * Governance, biz models both big subjects. The way everything fits together is what I’m thinking about. There’s some overlap between these groups. I want to help consolidate this info, make sure we’re working under one Code of Conduct. 8 | * For this month, I had some extra time, and it’s perfect timing, but on a month by month basis I’m still trying to decide how much time I can allocate. For now this is a passion project/hobbyist project for me. But I’m trying to figure out how to integrate my business ideas into this ecosystem. 9 | * I want to do this in a way that truly gives back. Spent years working with only open source applications. Now it’s time to teach others how to do that, and to “be in touch with your software.” Blockstack is all about user-owned internet. 10 | * What are the values of this community/project? 11 | * Digital rights, privacy, “user-owned” concept: taking things out of the hands of large companies, people that censor. This is a noble cause. But a large part of the community is focused on those items. 12 | * A lot of those values are based on core values as a person, e.g., love and compassion - how do people manifest that through software or in this community? 13 | * What personal values come out of it? Collaboration. We’re seeing that too: wanting to see each other’s successes. “We should always raise others to our level so that we can break through to the next.” Working together we really want to honor each other - finding ways to establish consensus, share what’s worked and what hasn’t. Answers a lot of questions people have personally about - how do you feel when you create an app? Do you feel stifled on the market? Answers a lot about how people feel about larger corporate take over of the Internet. 14 | * Any normal user I’ve talked to - I had 70 clients for five years, all quite different - "we all make choices because we don’t think we have another option. A lot of us are here to develop the other option, we just don’t quite know how." 15 | * That’s fine! We have some amazing resources. In dev side, academic knowledge - very impressive, almost intimidating! But I know I can play a part - just trying to figure out what it is. 16 | * You and PBC are taking a hands off approach, trying to establish those boundaries, we’re in a transition phase, it will take some time to figure out. 17 | * “If you gave me six hours to chop down a tree I’d spend the first four sharpening my axe.” We’re in this phase now. 18 | * In the next step we’re going to build the ability to answer these questions. Up to now PBC has handled things. That makes sense looking at the background but it’s hard to see people making decisions when you’re not part of it but you’re supposed to be. 19 | * It’s about vulnerability - gives us the ability to connect - but the first step is hard, like jumping off the high dive. 20 | * What does governance mean to you? 21 | * "Structure in which we make decisions" 22 | * Foundation, ecosystem, questions asked - what are we responsible for? A, B, C, D - if we want to add “E” - how do we as a group come to consensus on that? 23 | * Decision-making with regard to resources - funding, App Mining, etc. 24 | * [Governance] is our outlet for allowing [the community] to be a part of it 25 | * What does (good) governance mean to you? 26 | * "Fair and equal rights." 27 | * Everyone’s biggest concern in any type of decentralized governance system seems to be one large party being able to affect the votes/take over the system. 28 | * We’re all trying to find ways to make sure votes are fair, e.g., quadratic voting - that’s a cool idea, sounds like it could help! 29 | * Finding that balance so it’s never completely controlled by one actor, even if behind multiple parties. 30 | * Transparency. Being able to take part in, contribute to, see progress of the project out in the open. 31 | * How do you get legitimacy/confidence/trust? 32 | * Trust. Legitimacy and trust play into each other. 33 | * Big theme coming from the crypto community and digital privacy rights is how to build things [without trust] - that’s the big question - how to build it in such a way so that we don’t have to have that level of trust? 34 | * Trust comes from relationships - build relationships w/each other, a community - we are vulnerable - these relationships of trust are very important. 35 | * But also caution on trust being required in the first place, because that’s where it becomes a grey area. Building up trust, community values, when I contribute it gets included, when I vote my vote counts. 36 | * How do you make something acceptable, without requirement? 37 | * It should be voluntary 38 | * We’re reaching an interesting “age” in our democracy - a lot of places [historically] didn’t make it much further. 39 | * People have lost touch with the government process. Could we enable a lot of term limits? Cycle through people faster. Anyone I talk to in my generation, and the ones above and below, they don’t think they can have an impact anymore. Once you lose this "want to do something” you’re not even contributing anymore - it’s really sad. 40 | * How many people are involved today vs. how many will be here in six months, or 5-10 yrs? How have BTC/ETH/other projects done this/what are the trends? Do people stay involved for the long term? 41 | * Is decentralization of governance the right goal? Why or why not? Is this the right way to do it? 42 | * Balaji made a case for some centralization making sense. 43 | * I don’t have a strong opinion either way - I’m learning from past examples 44 | * At the end of the day someone has to be responsible 45 | * In a centralized system we make it the way it operates 46 | * It’s a hard question 47 | * Like doing recursive programming, you have to wrap your head around it - it’s an interesting goal, how do we make it work the way we want? 48 | * Don’t have a strong feeling as long as it held the values and structure I think makes sense 49 | * Some of the team values quick action, some value long-term thinking, you need both 50 | * "Two keys to launch the nuke” - multisig wallets are an interesting topic. Even with Quadratic Voting, how could there be multiple requirements to make something pass? 51 | * I think hybrid makes sense - determining which pieces make sense for each part of the structure 52 | * [Zcash “multisig” on brand](https://electriccoin.co/blog/electric-coin-co-donates-zcash-trademark-to-zcash-foundation/) - does everything need to go through this system? What happens in the case of stalemate? 53 | * Ideally it works well. If there’s a major issue then that has some underlying cause as well. 54 | * I’d like to extract the “why” from each link that’s been shared in the chat/on the resources - still trying to figure out how to do this. 55 | * We have a great community but it’s becoming quite time consuming - I feel the stress - no one has said anything yet, e.g., I have calls Mon-Wed-Fri every week through May. I’m okay with that but don’t know how others can adjust. 56 | * As a community member, if I can take on a small clear project, like with keeping resources updated, I’d be okay with that, just want to clearly define it so I know I can achieve it. 57 | * My thought: can we set up a delegative/representative system to address this? 58 | * The Foundation of course has to follow the legal charter in the jurisdiction in which it’s formed, but what rights will be given to it? 59 | * How have things worked in the past? 60 | * Biggest complaint is what was brought to light on the governance working group call today: governance very centralized in the hands of PBC. 61 | * Stacks 2.0 not done yet, when it’s launched the intention is to hand it off and get things going from there. 62 | * Doing fine but it’s about to change - this is on the horizon and coming on fast. 63 | * Things are centralized now but it has to start somewhere. 64 | * Thinking about how to move forward is why I want to be a part of this. If I want to bring my business operations under the Blockstack umbrella I need to make sure my core values are upheld in community and the Foundation. 65 | * What’s gone well/not so well? 66 | * Biggest challenges: communication, education. Both are already being worked on, progressing towards better solutions. 67 | * Communication - a lot of places to look for a lot of things - I want to keep driving things back towards GitHub, use it as the core, e.g., forum discussion. Action items should become GitHub issues. 68 | * Not everyone has received that message yet. 69 | * It’s messy, the way GTD tools like Trello that get tasks out of our head are the best tools. 70 | * When you look at the [PM repository](https://github.com/stacksgov/pm) you don’t immediately see the Projects tab - or that it’s related to issues. That’s where some people are, unless they’ve been using GitHub for a long time. 71 | * Want to share the blog post I wrote - get people to think through how that process works. We can make more simple instructions. 72 | * Is this the right way to do it? 73 | * The “multisig” idea is more appealing to me, and to a lot of people that want to be a part of the process or have a voice, whether through the Foundation or a different structure. 74 | * As long as the Foundation is in alignment with community, you can have it, and Foundation, and other pieces down the road. 75 | * Maybe there could be a third? 76 | * Wouldn’t necessarily change this 77 | * At a high level I agree with this structure. Based on my complete inexperience :) 78 | * How would you like things to work in the future? 79 | * PBC currently embraces this, and it’s something we want to consider part of governance: ability to allow for change. Everything is built on top of BTC but if we had to it could be changed to something else. 80 | * I’d suggest same for structure. Start with Foundation and PBC, see how it goes, but how do we make it so that it could be changed without a huge impact on the governance initiative itself? 81 | * How do you “refactor” governance / what “API” do you build around it? 82 | * This is the thing that’s missing from real world governance now - the ability to refactor. 83 | * That’s where you’d see soft and hard forks. 84 | * Embrace change/chaos. 85 | * How do you do this? 86 | * Offhand, not sure, but I can look into this more. 87 | * Biz models group: we discussed “thinking outside of the dapp.” You want to make one that does shared Google Docs? Why not make an engine for people to create something that allows for shared Google Docs, i.e., one layer higher of abstraction. 88 | * Where do we draw the line around Stakeholders? 89 | * There’s a list of roles in the survey. “I’m in the more inclusive camp. The more people included the better. But I don’t know what that does in terms of complexity." 90 | * Want to balance this: being able to make decisions vs. no one making one. 91 | * It would be easier for me to comment on each of the stakeholder positions, submit others if I think of them. 92 | * I tick many boxes: I work in dev, design, user, evangelist, miner, community member, business, investor in future. 93 | * I wonder how many people have multiple identifications vs. identify more deeply with one. 94 | * Anyone who should be excluded? 95 | * No - good to be inclusive 96 | * I plan to run a node and try mining, not for financial stake 97 | * I’d go into research on why Ethereum and other communities don’t like miners, make a decision from there 98 | * Who should have a role in protocol governance? 99 | * Difficulty here is education. Don’t mind everyone having a voice/stake but you want people to know what they’re talking about. 100 | * These challenges highlight where problems can be fixed. If we can’t ELI5 then maybe we can improve. 101 | * I want to lean towards inclusive but I see some challenges given the technical nature. 102 | * Some of this has come up in multiple meetings - it’s highly technical, and hard to get up to speed. 103 | * How do you create small bands of people together, e.g., a guild that upholds some set of values - do some KYC, this is who I am - and the guilds works together on an open source project - have their dapps, and contribute to Blockstack stuff. 104 | * How do we encourage this type of participation - you get access to a pool or a “PM” type role - build some model around that thought 105 | * I wonder if that kind of allegiance would play into making decisions or being able to vote 106 | * It’s a way to put group affiliations out in the open, which should help with undercover group associations trying to attack the network 107 | * Tying it into a pooling and stacking is a fun idea 108 | * What about App Mining? 109 | * I joined towards the end of it, although it was one of the first things that drew me in 110 | * The idea that I could make money developing something was attractive 111 | * It was a strong draw but it brought on a bunch of people with ideas that I think may not work long-term 112 | * I love the idea of hackathons, of generating new ideas, but if they’re just ideas that no one is maintaining, what value are they adding to the ecosystem? Other than just sharing codebase 113 | * I saw [Muneeb’s comment on the future](https://blog.blockstack.org/the-next-phase-of-app-mining/), and challenges, and I agree with him 114 | * Challenges on what the incentivization did 115 | * We had some early notification on what Larry was up to with New Internet Labs (NIL) - what if you made a guild requirement open source, or something that had to be verified and checked off? 116 | * I don’t want to duplicate any of the efforts done by NIL but I love the idea of analyzing something against a set of core values 117 | * If it was a system that made sense as part of the ecosystem, it could be something the Foundation could make canonical, you could spin up your own app chain but have to qualify to be on the canonical list 118 | * What we’re learning in decentralization in governance applies to apps and biz models and everything else - we’re hacking the way things work originally 119 | * How do we govern the Foundation? E.g. directors, to whom should it be accountable? 120 | * I’m looking forward to watching this conversation play out 121 | * Need to honor what the community wants 122 | * Hardest thing to accept is that it has to be a Singapore native, has to be some minimum number of people 123 | * Without that trust, people are starting to ask - where are we going? 124 | * What can a member do in the Foundation? Directors vs. community leaders - don’t know this yet, don’t know structure yet. 125 | * I’m the guy who sits in the back and takes notes and makes a decision later 126 | * What else should I have asked you? 127 | * I think we covered more than enough. 128 | * Feel like we’re working on the same page here. 129 | * I’m trying to do the same: hearing the community’s opinion rather than just sharing my own - I’m more interested in this collaborative nature. 130 | * Silence on these calls is normal at this stage - and it means consensus on some level - “I agree and I have nothing to add." 131 | * “Silence is one of the most beautiful tools we have." 132 | 133 | # General Resources 134 | 135 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 136 | 137 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 138 | -------------------------------------------------------------------------------- /interviews/interview-005.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 5 2 | 3 | * What’s your role? 4 | * Officially, maintainer of Android SDK, so my role is technical 5 | * (we have an iOS SDK but Apple is pushing back on it, so the future is unclear) 6 | * I’m an interested follower 7 | * Technical developer, evangelist, community manager 8 | * And exploring technologies, so I try to make prototypes more than real projects 9 | * Where’s the line between the two? 10 | * I don’t pursue the go to market, I don’t have a team, no one to run campaigns, no marketing or customer service 11 | * I have a freelance contract with PBC 12 | * Got involved when it was OneName.com, I had registered a name, when they made the change to Blockstack I rediscovered it, and the Android SDK, began contributing to it, invited them to sponsor an Android conference, from there on we had a conversation about the Android part 13 | * What interested me was the App Mining program 14 | * I was looking at the EOS worker proposal fund, found it interesting as an idea for helping develop apps but it didn’t really work out 15 | * What do you think about App Mining? 16 | * I don’t really have a solution 17 | * What went wrong? At the end, PBC didn’t take enough lead to tackle the problems 18 | * They said they received pushback from some developers on certain rules even though it was clear that the rules are not in support of the goals 19 | * They could’ve said, okay, these are the rules but we’ll break them because it’s going the wrong direction 20 | * It’s a centralized decision but you need some mechanism to protect your community, that didn’t really happen 21 | * Q: What could that mechanism look like? 22 | * Should be a third party that could oversee the progress 23 | * I don’t think there’s anything comparable out there 24 | * There’s government, big companies, citizens, but none of these could solve the problem 25 | * The solution would be to have some collective mechanism, but that’s probably complicated 26 | * I had a conversation about this recently, in the context of civic tech, about identity 27 | * At the moment I can’t say, e.g., “let the police solve it" 28 | * Users cannot solve it because they’re not knowledgeable, not educated enough, need education to solve the problem - probably only a subset of people could do the task 29 | * Q: Okay, so what could/should we be doing? 30 | * Limit the expectation of decentralization a bit, so that there has to be some entity that make decisions: rather than making decisions as a group, there’s an entity that follows rules that everyone in the group agrees on 31 | * Just in order to keep everything functioning, and a bit more efficient 32 | * Re: a Foundation, I think it’s a good approach 33 | * you say, everyone agrees on these fundamental ideas, that the Foundation describes 34 | * if you disagree you’re free to fork the project and do something else 35 | * Foundation could be the entity making decisions 36 | * I see the Foundation as bigger than App Mining 37 | * Q: What _did_ go well? 38 | * It’s important to find a solution to how developers can be paid for creating UIs for user data 39 | * I’d like to see a shift from the _developer_ as the owner of the app/project, it should be more open so everyone, user, designer, etc. can build the app in a collaborative way 40 | * For decentralized apps it’s important 41 | * next step: enabling customization so it’s easy to fork an app, to have user-specific app, so that even the users themselves can adapt the app 42 | * As a community, as all stakeholders that have an interest in the app - app “framework” for this use case - then everyone can push and pull a bit and have what they really want 43 | * I’m in discussion with mathematician/philosopher, who has an interesting approach to this - it’s about exchanging value, how you evaluate the contribution you’re doing, everyone can switch roles 44 | * I’m also following the Holochain app system, valueflo.ws, they describe this approach also in a similar way, Holo-REA project is the tech implementation, [valueflo.ws](https://valueflo.ws/) is the more theoretical approach 45 | * We didn’t really manage to collaborate on the data collections but that’s also something that Stacks 2.0 impacted and then it wasn’t high priority anymore - App Mining stopped when collections topic came up (data structures, standards) 46 | * Content provider on Android: brings this into web world, and cross-platform, this is very comparable 47 | * What I did for the calendar, I tried to show how this can work together (see [OI Calendar](http://www.openintents.org/calendar/)) 48 | * What’s the role of the Foundation? 49 | * In general, oversee the development of the project 50 | * Try to steer the community as well, see what they want, where everyone is going 51 | * By majority, follow this track 52 | * Is majority the right metric? 53 | * In general, yes. 54 | * On second thought, maybe not? 55 | * If you get lots of people onboarded to the community that have different goals, you shouldn’t follow them. 56 | * Anything else? 57 | * Protect the values of the community, “policing" 58 | * It should at least point out that certain activities are not aligned with the goals/principles 59 | * Then maybe suggest actions or enforce them if agreed this should happen 60 | * Do we want a Foundation in the first place? 61 | * I don’t see any other options 62 | * Do we need a legal entity in the first place? 63 | * For App Mining treasury, yes, I think we need a legal entity that can make contracts with the miners 64 | * Q: We can’t use smart contracts for this? 65 | * It’s just a tool, not a legal entity. You’re using them in order to execute a legal contract in a more efficient way. 66 | * I don’t see that the smart contract can be a legal entity? 67 | * In general I like the co-op concept, I don’t know how it differs from a foundation 68 | * With co-op you’d define community more strictly 69 | * You become part of co-op, same as joining the community. If you’re a “member” of the Foundation, is this the same? 70 | * Who is a stakeholder/citizen/who do we listen to? 71 | * It should be based on reputation 72 | * But I don’t really have a good understanding of all the possibilities or mechanisms 73 | * Even a user of an app, or holder of identity, is a stakeholder 74 | * (STX token holders, developers) 75 | * If you have STX tokens but “you don’t really care” then you’re not really part of the community 76 | * "Holding tokens per se does not make you a stakeholder” even though it’s a financial investment 77 | * Anyone else you would exclude? 78 | * Big tech companies 79 | * Nothing else comes to mind, haven’t thought about it much 80 | * What are the mission/vision/values of this community/project? 81 | * Very strong on user-owned identity, esp. in contrast to [Sovrin](https://sovrin.org/): user can have multiple identities and it’s lessa about KYC, can use different identities for different purposes 82 | * Stacks 2.0 is orthogonal, not directly related to identity, but it’s a tool to make identity possible 83 | * Could be used for anything, it’s very general, not specifically pushing on identity 84 | * Data ownership 85 | * Data security, less dependency on one service provider, decentralization of data 86 | * Muneeb says data is replicated but in reality it’s not 87 | * If you write to Gaia you can define/it is defined that the data is at several locations but at the moment it’s at just one location the user has defined 88 | * Privacy - is or should be important 89 | * Current solution not as private as it could be - we could emphasize this more 90 | * It’s important to clarify where Blockstack as a project stands on this: At the moment some people say it’s private, some say it’s not 91 | * What does governance mean to you? 92 | * A set of rules that describes how rules can be changed 93 | * So that it’s clear what you want to do, also includes how you can change the rules if you need - in a very abstract way 94 | * It’s easy to say but hard to realize 95 | * What does _good_ governance mean to you? 96 | * Everyone has the possibility to share their opinion 97 | * Also push back if it’s not in the interest of the majority, however we define that 98 | * Transparency is very important: if you’re pushing back, everyone knows the reasons, we agree on it 99 | * How do we do this in Blockstack? 100 | * App Mining: you could say, this app won’t receive rewards because of these rules, because we think it does not follow this interest so we cut off this app 101 | * Q: Who is the “we”? 102 | * The “we” that makes the decision. 103 | * It could be a good idea to split and localize the task, so that you have smaller responsibility and therefore less important if you make wrong decisions 104 | * Q: What could that look like in App Mining? 105 | * I proposed we split the rewards into different data structures, or more generally different use cases 106 | * Each use case has its own team or governance, working group that distributes the rewards for the apps that fall into this category 107 | * So maybe that can be more generalized as well: split task, money into smaller pieces, smaller pots of money, give more people responsibility 108 | * Does it work in the real world? 109 | * Big companies grow and eat everyone up 110 | * Cities, e.g. taking action on climate change, they can also achieve things 111 | * Does it scale? Maybe not. So we have to think about that as well. 112 | * Scalability for these rules is important. 113 | * How do you get legitimacy/confidence/trust? 114 | * Transparency is the most important 115 | * Diversity so that we have good representation of different opinions 116 | * Q: Defined how? If humans, then different gender, cultural background, education, opinions 117 | * The results matter too - if you have a history of good results, you have more trust. For this it’s important to have transparency so people can see what you have and haven’t achieved. 118 | * Is decentralization of governance the right goal? Why or why not? 119 | * I don’t have a view on how decentralization of governance would work 120 | * You have one single set of principles or rules that defines the goals, the foundation, there is only one of these, you cannot decentralize this 121 | * If you put this into a smart contract or a DAO then there could be decentralized governance 122 | * My understanding is that PBC is not the right entity to do the work for legal reasons 123 | * Because they are under US control 124 | * Singapore is more reasonable, even if maybe there are more democratic countries 125 | * You may want to choose one that’s more aligned with the goals of the Foundation 126 | * How have things worked in the past? 127 | * Not very transparent 128 | * Some people gave feedback on the Blockstack project, I didn’t receive any information 129 | * I heard several people gave feedback but it didn’t result in any action/feedback/statement, that’s very non-transparent. People left the project, gave reasons why, I heard about these people but there was no discussion/outcome. PBC has the sole decision-making, vision, no one else can influence them. 130 | * What’s gone well/not so well? 131 | * There has been good progress, good development (technology-wise) 132 | * Also, the credibility of the project is high in general (even though the price is down) 133 | * I hear lots of people who know about Blockstack and say it’s interesting 134 | * How would you like things to work in the future? 135 | * (esp: treasury, protocol) 136 | * App Mining is the most important part 137 | * No particular thoughts on the protocol - transparency, etc. 138 | * How do we govern the Foundation? E.g. directors, to whom should it be accountable? 139 | * Q: should it be accountable to someone? yes, probably 🙂 140 | * It (its governance) should be diverse, accountable to the community, whatever that means - e.g., who is in and out 141 | * Divide-and-conquer - I don’t know how this could work but it could be part of the solution 142 | * What else should I have asked you? 143 | * I don’t have a lot of experience 144 | * I like the Mozilla Foundation as a credible foundation, what they do, but I don’t know how its governance works 145 | 146 | # General Resources 147 | 148 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 149 | 150 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 151 | -------------------------------------------------------------------------------- /interviews/interview-006.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 6 2 | 3 | * What’s your role? 4 | * I think I ticked almost all of the boxes in the survey. I feel like I’m part of the community, evangelist, app developer, and I have an opinion on a lot of things. I’m all over the place. 5 | * I’m a full-time hobbyist. 6 | * How did you get involved? 7 | * I was looking at Ethereum and ran across Muneeb’s post - I’ve told this story in the community 1000 times - he had a post in 2016 about [three things Ethereum would have need to work on](https://medium.com/@muneeb/the-road-ahead-for-ethereum-b5b090bcd1a) - it resonated with me 8 | * Started hanging out in their Slack channel, chatting with Patrick, etc. so it went from there 9 | * Way back in 97-99 I was one of the guys outside of libraries handing out Linux CDs, I’ve always been active in the open source community 10 | * Also part of Google developer groups 11 | * I was a Ubuntu Florida local community lead for a while 12 | * I’ve always been organizing open source community groups, meetings, etc. 13 | * In 2009 I dropped out of Ubuntu, did the Google thing for a few years, then I wasn’t doing anything, found Blockstack, it resonated with me, the ethos, the fact that I didn’t see Muneeb screaming about how good it is, and instead I saw core engineers focused on making it good 14 | * I remember seeing other projects that would complete an ICO, then the project lead went on a world tour - I was like, you just raised money and you should be working! 15 | * What’s the same or different with the other open source projects you’ve contributed to? 16 | * Early Linux stuff - was literally people in IRC coordinating. There was no hackathons, no one handing out swag. That was very grassroots. 17 | * Ubuntu, Mark Shuttleworth brought $1B in, had big dev conferences in the community. They paid for a large number of sponsorships, brought us to Barcelona for big dev conferences. This was the first time I saw a lot of money in a community. It was good and bad. When they stopped that, the community bottomed out. People were there “for the free stuff” - as compared to the early days, when we handed out Slackware CDs because we cared about the project 18 | * Google open source stuff - not just Android, it was all the Google tech - had a lot of money, better organized. 19 | * Ubuntu had a community council that made decisions, did dispute resolution, etc. 20 | * This was good and bad 21 | * Ended up being a "buddy system”, in my opinion - it was the core people that had started, rotated among a small group of core people. As the community exploded the governance and leadership still remained with those core people, there was no influx. I was part of the core community, I just looked around and thought, why aren’t we talking to all these new people? 22 | * Google was much more organized - that’s something I’ve brought to the community here - “we’re introducing Dart in two months, here are tutorials, etc.” - we don’t get that with Blockstack, that’s a hard one to deal with 23 | * Bringing money to the table, trying to grow community by paying people, this rubs me the wrong way 24 | * Comparing to the Blockstack community, there are similarities and differences. There are some core people who are definitely here for the principles, which reminds me of early Linux days. One of my core questions is, are you here for the principles or for the money? This affects how much I trust you to do the right thing. 25 | * Q: How do you tell? 26 | * It’s not always obvious, don’t always do a good job, I try to give you the benefit of the doubt, but if your first question is about money then, to me, it’s obvious 27 | * If devs come into Discord and ask questions I try to help 28 | * I definitely form opinions about people - based on things I see them doing or not doing 29 | * I’m trying to better about not judging 30 | * What are the mission/vision/values of this community/project? 31 | * Blockstack’s mission is to create a new internet that enables users to be in control of their own data. Re-enabling privacy. 32 | * Privacy as core value? Yes, I’d say that. 33 | * This does motivate me to an extent - privacy is important 34 | * But also the data sovereignty. I’ve never been a fan of vendor lock-in, walled gardens, data silos. 35 | * My tagline in my email is: “Life, liberty, and the pursuit of Open Standards." 36 | * Data ownership & portability as well 37 | * Open source nature of it - if this were happening in the Hadera Hashgraph kind of way I don’t think I’d be as on board 38 | * Or even Google with Android - "they just throw the open source stuff over the wall every few months" 39 | * App Mining 40 | * I thought it was terrible but I wanted to give it time 41 | * My issue is basically that when we started it we did experiments, there were ten of us that had been around in the community from before App Mining. We came up with some apps, they definitely weren’t great, but the people were there for the principle. 42 | * Justin Hunter’s Graphite was the best app out there. We had Justin as the spokesperson for Blockstack apps, he’s well spoken, he thinks things through, had a decent app. 43 | * Prabhaav, wrote [Stealthy](https://www.stealthy.im/), it was limited, but he was there for the principle, decentralized messaging 44 | * We went from Graphite and Stealthy, to apps like EasyGif, being a representation of Blockstack’s “best”. 45 | * If you look at what happened, you had these great spokespeople, good developers, who if they had more money could’ve made their apps much better. This was totally derailed by apps that were super simple and created by developers who mostly didn’t really care for Blockstack’s principles. 46 | * App Mining turned out to be a good idea but it wasn’t responsive enough, when we saw issues they weren’t addressed immediately 47 | * I take the “mining” metaphor a little more literally in the sense that if you’re mining on a blockchain and you attack it you’re immediately penalized - by slashing or some other penalty - blockchain protocols do this. App Mining did not. 48 | * We saw calculator-type apps trying to win and people buying Twitter activity and Product Hunt upvotes, people cheating the system, with no penalty. 49 | * When Justin, Prabhaav began to drop in rankings compared to apps by people who didn’t really care, they moved on - to Ethereum 50 | * Started off with SimpleID, universal ID that makes it easier so you don’t have to go through horrible MetaMask UX, they pivoted to something else 51 | * For people who made simple apps and got $100k it’s great but where are they now? 52 | * And how should we do it going forward? 53 | * Should be radically different 54 | * Maybe it’s a selfish desire but the idea of funding apps is still a good idea 55 | * I like the way some on chain voting goes - people make a proposal, it gets voted on and gets funded or not 56 | * The downside is, if you look at a lot of these ecosystems they are still very buddy-buddy. Whoever knows the whales who can move the vote, etc. 57 | * On the other hand, it seems better from the outside than what we had, where if you spend four hours rewriting the UI and now you have two note apps - you can get 2x the funding 58 | * Our testing: we (NoteRiot, Webby, LandHo) opted out of App Mining at the end - because it was just noise 59 | * Haven’t made any major changes to our app in ~7 mos because we are rewriting it 60 | * NoteRiot - could use some updates 61 | * There were months where we’d get a TryMyUI score of 82, the next month 37 - how does this make any sense? The scoring was off, the testing was off, the gaming was rampant 62 | * Ideally there would be some funding mechanism to bring in apps that are high quality but there is no algorithm for this - it needs a person/people 63 | * I would say that there is a minimum layer of privacy that needs to be built into the app - if you’re sending data to third parties the app should not qualify for consideration, if you’re using Google Analytics you’re not qualified - basic rules based on principle should be a gating mechanism 64 | * Still a good idea if there’s some group making a decision, or at least some form of human reviewer(s). 65 | * What does governance mean to you? 66 | * I’d turn this around to the working group 67 | * Are we talking about community governance like Ubuntu community councils, development governance (e.g. Blockstack core), funding for App Mining, funding for the Foundation? 68 | * Lots off different pieces 69 | * Protocol changes, on-chain governance, etc. 70 | * It means possibly all of those things or maybe one or two of them? Need to define the scope 71 | * What does _good_ governance mean to you? 72 | * Fair 73 | * Let’s define what governance we’re talking about first 74 | * App funding: means there’s a rough consensus around which apps are getting funded 75 | * Core dev: dev is focusing on features that community and developers/miners need 76 | * Responsive 77 | * Kinda hard to nail down more than that 78 | * How do you get legitimacy/confidence/trust? 79 | * Transparency 80 | * Inclusiveness 81 | * Q: How do we do this? 82 | * Not all-encompassing 83 | * I am less worried about the people who don’t have a stake - I think you need to have a stake in what you’re voting for 84 | * Someone popped in to Xan’s AMA and said Blockstack is shit, STX is shit - let’s not allow that person to vote 85 | * Need to have some stake in the game to have a voice 86 | * a community should have a voice but not necessarily a vote 87 | * concept of binding vs. non-binding vote 88 | * Where do we draw the line around Stakeholders? 89 | * For those who don’t own STX, who aren’t miners, aren’t developers: non-binding voice 90 | * Pooling is important, so people who are minorities can join together to make their voice heard 91 | * some kind of delegation process, similar to what they just implemented in Clarity/STX 2.0, native delegation in protocol 92 | * Does anyone NOT get even a voice? 93 | * That’s a hard one, even harder 94 | * Ideally every random person gets a voice but this may not be the reality 95 | * I don’t think there’s an answer there 96 | * Someone sent a meeting invite to the wrong person, she popped in, said “I don’t know who you are, what is this meeting about?”, but she shared her thought and made a good point then left - there’s value out there but hard to separate it from the crap 97 | * Is decentralization of governance the right goal? Why or why not? 98 | * Decentralization in the actual mechanism - ideally in my perfect world we’d have a Linus Torvalds leading the thing - not decentralized but he generally aligns with my personal PoV so I like it - ideally have one person that I like 99 | * I don’t want a committee, committees are terrible, I’d rather have a Benevolent Dictator for Life. 100 | * But, who is that and how do you call yourself decentralized if you have one person dictating? 101 | * Muneeb could be that person - there are things I wish he’d done more - I wish he’d been more available - we need people out there talking about this stuff more. He’s begun to do more of this in the past six months. 102 | * Whoever that first director is, of the Foundation, I’d like Muneeb to be that person 103 | * How do you put someone in that place, an Executive Director of the Foundation, that hasn’t spent a lot of time in the community, doesn’t have the background - I’d hate to see some random person like Tezos did, some random person in Switzerland - but also you have to pay that person 104 | * Someone leading a company, with experience and expertise, if it’s a full time job you have to pay them 105 | * I’m afraid if we leave it to them [PBC] they’ll pick a VC 106 | * How do we govern the Foundation? E.g. directors, to whom should it be accountable? 107 | * Should have a strong leader, but should also be accountable to the community 108 | * How do we vote someone in, how do we vote them out? 109 | * Are there term limits? 110 | * Rather than appointing a director for two years, how do we kick them out if they’re no longer acting in line with the will of the community? 111 | * There should be an accountability piece - that’s fundamental 112 | * I want to see how it gets structured first. How do decisions get made? 113 | * How have things worked in the past? What’s gone well/not so well? 114 | * The reason you’re here is because PBC has been “the governance for everything" 115 | * It’s been PBC decisions, whoever made them at the time 116 | * No specific issues with PBC decisions - I’d just say that recently the complete focus on Stacks 2.0 and STX tokens coupled with a not-big-enough engineering team has meant that Blockstack has focused on parts of development that are speculative vs. stuff that we know the community wants like stable p2p radix, collections 117 | * Talking Pure governance: on the dev side there are things we want other than Stacks 2.0 118 | * I see Stacks 2.0 as hugely important but also less important than some of the foundational pieces that could’ve been there - I’m an investor but not in PBC and I’m not the one paying the developers so "I get it" 119 | * We (developers) have asked for these things, but never said “we don’t want you to work on Stacks 2.0 we want you to work on radix” - “it’s on the back burner, we want community help on it" 120 | * How would you like things to work in the future? 121 | * Nothing we haven’t talked about already 122 | * I wish I had a better perspective, wish I knew every project and what’s working and what isn't 123 | * Who should have a role in protocol governance? 124 | * One and the same with governance in general 125 | * Even for protocol change you want miners, developers, user consensus 126 | * Even if people are totally uninformed! 127 | * Ideally we’d have a BDFL but that’s probably not gonna help us long term. 128 | * It’s hard when you’re taking a public, VC-backed company and say “this is a public internet” - that’s a hugely difficult operation - it’s something I constantly go back and forth on. Do I really want a VC-owned internet? Hell no 129 | * But we can set basic standards and use that money to do good things and start changing the conversation - privacy as default expectation - versus the assumption that I have to give all my info away 130 | 131 | # General Resources 132 | 133 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 134 | 135 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 136 | -------------------------------------------------------------------------------- /interviews/interview-007.md: -------------------------------------------------------------------------------- 1 | # Stakeholder Interview 7 2 | 3 | * What’s your role in the project/community/ecosystem? 4 | * I work for PBC, evangelism + meetups 5 | * I still think of myself as a community member, I try to be super transparent about all of our initiatives - this is one piece of feedback we got last year, that things are closed and the community don’t know what’s going on 6 | * Being transparent is important to the community but it’s difficult to do because our timeframe is so aggressive 7 | * How did you first get involved? 8 | * Was familiar with the space since 2017, in 2018 I joined. Background in IT, was working on infrastructure, RedHat. Really boring, nothing revolutionary, nothing to brag about. 9 | * I saw a YouTube video of Muneeb and Ryan, then went down the rabbit hole 10 | * Joined community, offered to do what I can. 11 | * I sent a pitch deck to Patrick - said guys, I want to work for you, don’t know on what, just hire me 12 | * After a month he got back to me, but I was already super active. I have a generalist background, not a great dev but I can code, not a great designer but I can design, so I dove in, started to design e.g. posters 13 | * I will forever appreciate the opportunity to work on Blockstack 14 | * I was reading a lot of Antonoupolous’s stuff, met him face to face, hope he still remembers me 15 | * What are the mission/vision/values of this community/project? 16 | * Mission is to replace every function that PBC has. At the end of the day you don’t want a single entity to have control over the network 17 | * Mission of Blockstack is to provide open, free Internet 18 | * As a community we need to think of ways that each of us can help replace the functions of PBC 19 | * What about values? 20 | * I’ve been speaking to a lot of evangelists 21 | * They like the fact that we're pushing for privacy, security, digital freedom 22 | * They want to contribute to the project for these reasons, even without monetary compensation 23 | * What do you mean by evangelist? 24 | * We’re trying to revamp it in a way that makes sense 25 | * Kind of like brand ambassadors 26 | * We didn’t have specific threshold of responsibilities that they can feel accountable for 27 | * We have > 100 evangelists, probably around 25-30% that are active, people come and go 28 | * We have the OG ones, e.g. Juliet, DanT, now Jason 29 | * Blockstack Evangelist means you help move the needle in the ecosystem in some way, community development, joining different working groups, e.g. governance, business model, PoX 30 | * What does governance mean to you? 31 | * This is always a difficult question 32 | * "I hate politics, to be honest, I don’t really like the government" 33 | * It’s hard! 34 | * Right now I think being involved in the decision-making process could help me understand why we should have governance 35 | * Right now mostly the decisions are made by PBC, and the community has only a little stake in it 36 | * If you’re gonna go back to the first question, what’s Blockstack’s mission? I think governance plays a big role 37 | * How you decide on the “open internet” - it’s open, at the end of the day, people can do good or bad stuff, how do you “punish the bad actors”? 38 | * One of the best ways for governance is to write up some rules 39 | * Like App Mining 40 | * What do you think about App Mining? 41 | * It was a good mechanism, but fell short because there weren’t really any consequences for bad actors 42 | * Game theory says there should be! 43 | * It was so hard for PBC to make a decision on how to punish bad actors - worried about how the community will feel 44 | * May think it’s too centralized, e.g., if a decision is made to kick an actor out of the ecosystem 45 | * One way to solve that problem is governance 46 | * The community probably felt they’d been heard but none of the proposals were put into action; or, they were, but it was really really slow 47 | * Problem in PBC is that there’s not enough bandwidth 48 | * There’s no flow: if I propose something what’s the next step? At the end of the day PBC makes the decision to implement or not 49 | * For example PBC could have one vote, community one vote, other stakeholders’ entities could have one vote 50 | * So e.g. community could override PBC’s opinion 51 | * What does _good_ governance mean to you? 52 | * From a guy who doesn’t really like politics! Can make a decision that will be beneficial for all actors in the ecosystem - everything has pros and cons 53 | * Good governance means you offer the best decision that will benefit the most actors in a positive way (i.e., a utilitarian definition of good governance) 54 | * What should it not do? 55 | * Right now I know that PBC makes most of the decisions 56 | * I’ve been listening to the conversation in the governance working group 57 | * No concrete model yet for governance 58 | * We have ~300k token holders, some are probably whales 59 | * Good governance should eliminate the fact that - I don’t like it when whales have so much power over decision making 60 | * I don’t like that it’s one token one vote; I prefer "one entity one vote" 61 | * At the end of the day, we have self-sovereign identity, so it should be “one identity one vote” - that’s what we stand for 62 | * Lane: How do you do that, though? In a decentralized network 63 | * If you want to have this “governance utopia” - it’s quite difficult 64 | * You need some sort of mechanism 65 | * How do you get legitimacy/confidence/trust? 66 | * Transparency - e.g., if I pay my taxes, I want to know where it goes 67 | * E.g., “Why are we building so many roads?” 68 | * I want it to be super-transparent 69 | * Involve people in decision-making; “inclusivity" 70 | * E.g., ask me: “Do we want to build a road?” 71 | * Is decentralization of governance the right goal? Why or why not? 72 | * That’s a tricky question 73 | * It’s hard if you just put it all on the community at once 74 | * We need organization: community could vote on who should be the governing organization, could also vote it out 75 | * I mean any organization! Not just PBC, Foundation, etc. 76 | * There could be several, at the same time 77 | * There should be different kinds of governing orgs. 78 | * In different roles 79 | * Once it’s more settled, they could dissolve - e.g., set up mechanism that works for community, e.g. a DAO, if you do this successfully then the governing body has no more reason to exist 80 | * I.e., governance that’s as “thin” as possible - everything is automated - that’s utopia for me 81 | * At the end of the day you want these microeconomies - it doesn’t really work on the big scale 82 | * For me the whole point of this space is decentralization! including of governance 83 | * Is this the right way to do it (i.e., decentralize governance)? 84 | * Foundation could be a great step bc it could remove some of the power from PBC itself 85 | * We always talk about the path to decentralization. One of the best ways to do it is to put more association within the network itself before you give it to the community. 86 | * Could be a foundation, different entity that has different opinions about the ecosystem 87 | * Right now, in terms of timeline, creating a DAO in Q3 or Q4 when mainnet is rolled out - could be good 88 | * From community standpoint, educating people on why governance is actually important is also important 89 | * Lane talked about community touchpoint - ordinary people often don’t care! How do you get them to care? 90 | * We should tell them: “this governance is for you” - this is how things will work if e.g. PBC goes away 91 | * I could help you guys organize this - governance workshop sessions - that’s what we’re doing, more virtual workshops - happy to coordinate these throughout the community 92 | * Cryptoeconomic governance workshop - could be valuable to the community 93 | * That’s also one of the problems of PBC before - we have silos at the moment - trying to break these down bit by bit 94 | * How have things worked in the past? 95 | * I won’t speak as a PBC employee but from my standpoint the decision making process - a lot power in the hands of PBC for entire network - it’s only really in the past few months that we’ve really begun to operate as an open source project 96 | * For past four years we operated more as a closed source project 97 | * Q: What changed? 98 | * We, the team in general, realized that the way to go is to be more open on the things we actually do - to be more involved in the community 99 | * We’ve built a community we can lean on 100 | * We asked ourselves before - the Ethereum community is really intellectually knowledgeable about everything, have the first-mover advantage, got a lot of people who are willing to experiment 101 | * Before we didn’t have smart contracts, was mostly consumer-facing utility products - don’t get much in the community with that 102 | * Now, with a token, with smart contracts - a lot more going on in the ecosystem - the community now willing to be more involved 103 | * These things have been in the pipeline for a long time, but it just took a long time to roll it out 104 | * What’s gone well/not so well? 105 | * App Mining was a fail 106 | * If we had a governance model that let us move specific features forward - e.g., voting mechanisms for reviewers - it would have been so much better 107 | * Protocol: Blockstack takes a long time to launch things, tons of R&D involved. If you have a single body that’s doing all the R&D then it’s much more robust. This went well. This is an advantage of having a single body that makes the decision. It’s “less noisy." 108 | * Sometimes community gives feedback but there’s no action associated with it 109 | * When you want to work with a super fast timetable - you get a comment - not sure what to do with it? 110 | * Should we try App Mining again? 111 | * We were trying to launch the same initiative for community rewards - who will oversee it? Decide if it’s good or not? 112 | * Always hard because there will probably be a single decision-making entity to govern it to make it good 113 | * If e.g. App Mining was run by a single entity it would’ve been even better - would’ve had more quality apps, as opposed to quantity 114 | * With decentralization - you put different kinds of entities on it - if it works then it works perfectly, if not then it doesn’t really work 115 | * To be honest the optimum is somewhere in the middle - don’t put entire decision in hands of any one entity 116 | * How would you like things to work in the future? 117 | * If all entities were dissolved - could set up a really nice mechanism to set up “microeconomies” - every person has a stake within the ecosystem 118 | * We have certain funds we need to unlock, need e.g. 60% majority of community members to unlock it to proceed 119 | * Microeconomies within the Stacks community managing things, no Stacks foundation, no PBC - these entities set up the mechanism, then go away 120 | * Certain percentage you need - 300k token holders, maybe we need 51% simple majority, maybe 70% 121 | * That’s my vision 122 | * Where do we draw the line around stakeholders? 123 | * There are different stakeholders, e.g., some evangelists don’t own tokens 124 | * I’d segregate it within the community: STX holders and non-STX holders 125 | * Who goes into the latter? Those who have a Blockstack identity. If you’re super involved but don’t have tokens you probably still have an ID. 126 | * Q: What does it cost to generate a new ID? 127 | * It’s free but you can pay for a premium ID. 128 | * Q: What prevents Sybil attacks here? 129 | * That’s a good question. You can’t really do KYC. I don’t have an answer. 130 | * Q: Would you explicitly exclude anyone? 131 | * Core devs, maybe. Because they’re probably biased when it comes to decision-making. They’re heavily invested. Every core dev. has their own version of utopia but it’s often not the best way to go for the whole community 132 | * If they believe in the mission of open internet, they probably want what the people want. 133 | * They should share this vision. 134 | * Who should have a role in protocol governance? 135 | * Core devs should only have a say on the protocol because they know best 136 | * For ecosystem-wide decision making that doesn’t involve core protocol - core devs shouldn’t be involved in it 137 | * Two tiers of governance: core protocol, then everything else as a second tier 138 | * How do we govern the Foundation? E.g. directors, to whom should it be accountable? 139 | * I’m heavily involved in the community. 140 | * You have different kinds of working group - one from each working group should be on the board - then one person from community (not in working group), “average Joe." 141 | * Also, someone from PBC. 142 | * That’s a nice way to set it up. 143 | * Then you know what’s going on with different working groups - unites everything - also core protocol 144 | * Q: Does this capture everything necessary? All the necessary expertise? 145 | * I’d remove the “average Joe.” The community should have some sort of vote on how to move forward. Maybe the STX holders. 146 | * What are we funding? if I know what we’re funding then I could give a more concrete answer on who should run the foundation. 147 | * This is a tricky question too 148 | * I see Blockstack more as infrastructure 149 | * I don’t think apps should be funded 150 | * You should invest in good dev tools to create a really nice OSS infra., without dev tools you can’t make nice apps 151 | * The Foundation should not fund apps, it should fund tools to make apps 152 | * Fund the people who will build the tools around it, including the protocol itself 153 | * Any final thoughts? 154 | * I never talked about governance before, I really enjoyed this! 155 | * I’m excited about this and how it will move forward! 156 | 157 | # General Resources 158 | 159 | See [Stakeholder Interviews](https://stacksgov.github.io/resources/#/interviews/) for the list of one-of-one interviews. 160 | 161 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 162 | -------------------------------------------------------------------------------- /research/README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Research 2 | 3 | In the initial phases of developing the Governance Working Group, several articles, websites, and other items were collected as a reference. These were used as a starting point to developing the Stacks Foundation governance model, and continue to expand as time goes on. 4 | 5 | Updates are welcome via issues in [stacksgov/pm](https://github.com/stacksgov/pm/issues) or via pull request! 6 | 7 | ## Table of Contents 8 | 9 | 10 | 11 | - [Stacks Governance - Research](#stacks-governance---research) 12 | - [Table of Contents](#table-of-contents) 13 | - [General Blockchain Governance](#general-blockchain-governance) 14 | - [Articles / Websites](#articles--websites) 15 | - [Documents](#documents) 16 | - [Examples](#examples) 17 | - [Videos](#videos) 18 | - [Other Governance Resources](#other-governance-resources) 19 | - [Open Source Software Articles](#open-source-software-articles) 20 | - [Open Source Software Examples](#open-source-software-examples) 21 | - [Commons, Consensus, and Decision-making](#commons-consensus-and-decision-making) 22 | - [General Resources](#general-resources) 23 | - [Licensing](#licensing) 24 | 25 | 26 | 27 | # General Blockchain Governance 28 | 29 | ## Articles / Websites 30 | 31 | - [Crypto-Governance and the Dangers of Faction](https://medium.com/@BuckPerley/crypto-governance-f1318affbbe0) 32 | - [Blockchain Governance: Programming Our Future](https://medium.com/@FEhrsam/blockchain-governance-programming-our-future-c3bfe30f2d74) 33 | - [What Is Quadratic Voting?](https://towardsdatascience.com/what-is-quadratic-voting-4f81805d5a06) 34 | - [Etherean.org Series: The key ingredients to a better blockchain](https://www.etherean.org/) 35 | - [Part I: Tech and protocol](https://www.etherean.org/blockchain/2019/09/09/key-ingredients-better-blockchain-part-i-tech-and-protocol.html) 36 | - [Part II: Decentralization](https://www.etherean.org/blockchain/2019/09/15/key-ingredients-better-blockchain-part-ii-decentralization.html) 37 | - [Part III: Community](https://www.etherean.org/blockchain/community/2019/09/19/key-ingredients-better-blockchain-part-iii-community.html) 38 | - [Part IV: Constitution](https://www.etherean.org/blockchain/community/governance/2019/11/18/key-ingredients-better-blockchain-part-iv-constitution.html) 39 | - [Part V: Governance](https://www.etherean.org/blockchain/governance/2020/01/06/key-ingredients-better-blockchain-part-v-governance.html) 40 | - [Part VI: Privacy](https://www.etherean.org/blockchain/privacy/2020/03/26/key-ingredients-better-blockchain-part-vi-privacy.html) 41 | - [Wharton Crytpogovernance Workshop - View Responses by Question](https://cryptogov.net/view-responses-by-question/) 42 | - [What is Blockchain Governance: Ultimate Beginner's Guide](https://blockgeeks.com/guides/what-is-blockchain-governance-ultimate-beginners-guide/) 43 | - ["The invisible politics of Bitcoin: governance crisis of a decentralised infrastructure" by Primavera De Filippi, Benjamin Loveluck](https://policyreview.info/articles/analysis/invisible-politics-bitcoin-governance-crisis-decentralised-infrastructure) 44 | 45 | ## Documents 46 | 47 | - [Consensus through Blockchains: Exploring Governance across interorganizational Settings](https://www.zora.uzh.ch/id/eprint/160378/1/ICIS_Blockchain_Governance.pdf) from University of Zurich 48 | - [Basins of Attraction for Generative Justice](https://www.researchgate.net/publication/274832746_Basins_of_Attraction_for_Generative_Justice) 49 | 50 | ## Examples 51 | 52 | - [Zcash Foundation](https://www.zfnd.org/about/) 53 | - [Algorand Foundation](https://algorand.foundation/community) 54 | - [Ethereum Governance](https://docs.ethhub.io/ethereum-basics/governance/) 55 | - [Helium Governance](https://heliumchain.org/governance/) 56 | 57 | ## Videos 58 | 59 | - [Blockchain Governance Youtube playlist](https://www.youtube.com/playlist?list=PLpNeGhwVBcha8itBSQlUoeMy_6EtTeoVd) curated by @dantrevino 60 | - [Radical Markets: Fireside Chat: Glen Weyl and Jaron Lanier](https://youtu.be/R4XBAwKInig) 61 | - [Vitalik Buterin Discusses On-chain Governance](https://www.youtube.com/watch?v=w-CH_5il9aU) 62 | - [Balaji Srinivasan 15:13-20:48 Curation and collaboration in decentralized and centralized communities](https://youtu.be/A2K5OSMbV40?t=913) 63 | 64 | # Other Governance Resources 65 | 66 | ## Open Source Software Articles 67 | 68 | - [6 open governance questions every project needs to answer](https://opensource.com/article/20/2/open-source-projects-governance) 69 | 70 | > 1. Who makes the decisions? 71 | > 2. How are maintainers added? 72 | > 3. Who owns the rights to the domain? 73 | > 4. Who owns the rights to the trademarks? 74 | > 5. How are those things governed? 75 | > 6. Who owns how the build system works? 76 | 77 | - [Code Forking, Governance, and Sustainability in Open Source Software](https://timreview.ca/article/644) 78 | - [Open Stand: Global advocates for open standards & technology development](https://open-stand.org/about-us/principles/) 79 | 80 | ## Open Source Software Examples 81 | 82 | - [Apache Software Foundation: The Apache Way](https://www.apache.org/theapacheway/index.html) 83 | - [Cloud Native Computing Foundation Policy Repo](https://github.com/cncf/foundation) 84 | - [Electron repository for governance issues and documents](https://github.com/electron/governance) 85 | - [Ghost.org Governance](https://ghost.org/docs/concepts/governance/) 86 | - [Internet Engineering Task Force (IETF) About Page](https://www.ietf.org/about/) 87 | - [International Standards Organization (ISO) structure and governance](https://www.iso.org/structure.html) 88 | - [Linux Foundation Bylaws](https://www.linuxfoundation.org/bylaws/) 89 | - [Mozilla Foundation Governance](https://www.mozilla.org/en-US/about/governance/) 90 | - [Open Source Guides: Leadership and Governance](https://opensource.guide/leadership-and-governance/) 91 | - [OpenJS Foundation Governance](https://openjsf.org/about/governance/) 92 | - [OpenStack Technical Committee Decisions](https://opendev.org/openstack/governance/) 93 | - [Python Language Governance](https://www.python.org/dev/peps/pep-0013/) 94 | - [Wikimedia Foundation About Page](https://wikimediafoundation.org/about/) 95 | - [World Wide Web Consortium (W3C) Mission](https://www.w3.org/Consortium/mission) 96 | 97 | ## Commons, Consensus, and Decision-making 98 | 99 | - [An Introduction to Generative Justice](https://www.researchgate.net/publication/311811471_An_Introduction_to_Generative_Justice) 100 | - [Consensus Decision-making as a Research Method for Generative Justice: empirical practices from a money-less economy in Chiapas, Mexico](https://www.researchgate.net/publication/311853527_Consensus_Decision-making_as_a_Research_Method_for_Generative_Justice_empirical_practices_from_a_money-less_economy_in_Chiapas_Mexico) 101 | - [Moneyless economics and non-hierarchical exchange values in Chiapas, Mexico](https://www.researchgate.net/publication/325172729_Moneyless_economics_and_non-hierarchical_exchange_values_in_Chiapas_Mexico) 102 | - [Anti-Authoritarian Metrics: Recursivity as a strategy for post-capitalism](https://www.researchgate.net/publication/311853369_Anti-Authoritarian_Metrics_Recursivity_as_a_strategy_for_post-capitalism) 103 | - [Whitepaper (WIP) on Two Row Wampum Social Layer](https://github.com/HaroldDavis3/Two-Row-Wampum-Social-Layer-Platform) 104 | 105 | # General Resources 106 | 107 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 108 | 109 | # Licensing 110 | 111 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/resources/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 112 | -------------------------------------------------------------------------------- /research/emissions-research/pdf-theme.yml: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/research/emissions-research/pdf-theme.yml -------------------------------------------------------------------------------- /survey/README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Community Survey 2 | 3 | In Q2 2020 the community conducted a governance survey, inspired by a [similar survey](https://medium.com/coinmonks/ethereum-governance-survey-results-c67c11695f2a) conducted in the Ethereum community in 2019. 4 | 5 | Learn more about the survey, its goals, and community contributions in [this forum thread](https://forum.stacks.org/t/community-governance-survey/10387) or in [this Github issue](https://github.com/stacksgov/pm/issues/1). 6 | 7 | ## Survey Results 8 | 9 | - [full report of results](https://stacksgov.github.io/resources/survey/report.pdf) - note that this does not include responses to open-ended questions 10 | - [raw results, anonymized and randomized (CSV)](https://stacksgov.github.io/resources/survey/results-anonymized-randomized.csv) - full, raw results in CSV format (order randomized, and with identifying information removed) 11 | - [raw results, anonymized and randomized (XLSX)](https://stacksgov.github.io/resources/survey/results-anonymized-randomized.xlsx) - the same thing in Excel format 12 | 13 | ## Survey Analyses 14 | 15 | - [Lane's analysis of results](https://stacksgov.github.io/resources/survey/analysis.pdf) 16 | - [dropoff analysis](https://stacksgov.github.io/resources/survey/dropoff-analysis.pdf) (this is the percentage of respondents who stopped answering the survey after each question) 17 | 18 | # General Resources 19 | 20 | See [Stacks Governance Resources](https://stacksgov.github.io/resources/) for additional information related to governance of the Stacks blockchain. 21 | 22 | # Licensing 23 | 24 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/resources/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 25 | -------------------------------------------------------------------------------- /survey/analysis.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/survey/analysis.pdf -------------------------------------------------------------------------------- /survey/dropoff-analysis.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/survey/dropoff-analysis.pdf -------------------------------------------------------------------------------- /survey/report.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/survey/report.pdf -------------------------------------------------------------------------------- /survey/results-anonymized-randomized.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/resources/d28666c2e0dff8c83f6c51b7f2ea4ea4e8312b7a/survey/results-anonymized-randomized.xlsx --------------------------------------------------------------------------------