From d6486bf1e0689c0819605bc46abc47003901a1fe Mon Sep 17 00:00:00 2001 From: gardenenigma Date: Sun, 21 Apr 2024 13:55:03 -0700 Subject: [PATCH 1/2] Update to docs --- docs/Contributing citations.md | 11 + docs/Contributing content and edits.md | 11 + docs/Contributing figures.md | 8 +- ...buting getting started as a contributor.md | 33 +++ docs/Contributing in other ways.md | 11 + docs/Contributing to the docs.md | 11 + ...ations.md => Contributing translations.md} | 18 +- docs/Getting started as a contributor.md | 6 - docs/Gov4Git and PMP.md | 4 + docs/Governance Gov4Git.md | 16 ++ docs/Governance PMP.md | 23 +++ docs/Governance introduction.md | 22 ++ docs/Governance plural credits.md | 24 +++ docs/Home citing the book.md | 31 +++ docs/Home copyright.md | 14 ++ docs/Home editing and pull requests.md | 17 ++ docs/Home financial goals.md | 22 ++ ...rnance and progressive decentralization.md | 15 ++ docs/Style Guide.md | 188 ------------------ docs/Style guide book structure.md | 55 +++++ docs/Style guide citations and referencing.md | 61 ++++++ docs/Style guide figures.md | 60 ++++++ docs/Style guide introduction.md | 16 ++ docs/Style guide punctuation and grammar.md | 21 ++ docs/assets/favicon.png | Bin 0 -> 1096 bytes docs/assets/plurality logo.png | Bin 0 -> 805 bytes docs/index.md | 20 +- 27 files changed, 513 insertions(+), 205 deletions(-) create mode 100644 docs/Contributing citations.md create mode 100644 docs/Contributing content and edits.md create mode 100644 docs/Contributing getting started as a contributor.md create mode 100644 docs/Contributing in other ways.md create mode 100644 docs/Contributing to the docs.md rename docs/{Contribute translations.md => Contributing translations.md} (89%) delete mode 100644 docs/Getting started as a contributor.md create mode 100644 docs/Governance Gov4Git.md create mode 100644 docs/Governance PMP.md create mode 100644 docs/Governance introduction.md create mode 100644 docs/Governance plural credits.md create mode 100644 docs/Home citing the book.md create mode 100644 docs/Home copyright.md create mode 100644 docs/Home editing and pull requests.md create mode 100644 docs/Home financial goals.md create mode 100644 docs/Home governance and progressive decentralization.md delete mode 100644 docs/Style Guide.md create mode 100644 docs/Style guide book structure.md create mode 100644 docs/Style guide citations and referencing.md create mode 100644 docs/Style guide figures.md create mode 100644 docs/Style guide introduction.md create mode 100644 docs/Style guide punctuation and grammar.md create mode 100644 docs/assets/favicon.png create mode 100644 docs/assets/plurality logo.png diff --git a/docs/Contributing citations.md b/docs/Contributing citations.md new file mode 100644 index 00000000..816bc25e --- /dev/null +++ b/docs/Contributing citations.md @@ -0,0 +1,11 @@ +--- +title: Contributing citations +author: +date: +tags: + - +--- + +# Contributing citations and references + +> Brief info about contributing citations and references \ No newline at end of file diff --git a/docs/Contributing content and edits.md b/docs/Contributing content and edits.md new file mode 100644 index 00000000..7c5b11f2 --- /dev/null +++ b/docs/Contributing content and edits.md @@ -0,0 +1,11 @@ +--- +title: Contributing content and edits +author: +date: +tags: + - +--- + +# Contributing content and edits + +> Brief info about contributing edits \ No newline at end of file diff --git a/docs/Contributing figures.md b/docs/Contributing figures.md index ed0d1a90..bb76b082 100644 --- a/docs/Contributing figures.md +++ b/docs/Contributing figures.md @@ -1,5 +1,11 @@ --- Title: Contributing figures +author: +date: +tags: + - --- -# Contributing figures \ No newline at end of file +# Contributing figures + +> Brief overview of contriuting figures \ No newline at end of file diff --git a/docs/Contributing getting started as a contributor.md b/docs/Contributing getting started as a contributor.md new file mode 100644 index 00000000..e6be7317 --- /dev/null +++ b/docs/Contributing getting started as a contributor.md @@ -0,0 +1,33 @@ +--- +Title: Getting started as a contributor +author: +date: +tags: + - +--- + +# Getting started as a contributor + +> While this project will begin as a traditional open-source community, we eventually hope to provide more formal governance, participation, control rights and recognition of contributions than has been customary in such projects. + +We believe such features are important for open-source projects like this one to sustainably scale while staying true to their values. As such, a primary goal of our management of this project will be to clearly and (for the most part) publicly recognize contributions with both qualitative (viz. what kind of contribution was made) and quantitative (viz. how important was the contribution) tokens. + +However, these tokens cannot be traded/transferred directly across users; they are relevant only to governance of and participation in this community and are not intended to have any external financial value, except through the value of the community as a whole. We may raise some funds to support the community and the community will govern these funds. However, credit is a marker of contribution and entitlement to governance, not to direct external financial gain. +Contributions will be of many kinds. + +## Potential ways to contribute + +While we cannot hope to anticipate them all types of contributions, here is a short sampling that provides a sense for the range we expect: + +* Translations of the book to other languages and subcultures. +* Research assistance for and editing of the root text. +* Thoughtful and accurate prioritization of issues and pull requests. +* Contributing to or helping maintain the website interface for the book. +* Graphical design of elements of the book, including visual contributions and figures. +* Managing data engines and data visualization. +* Project management of interaction of these elements +* Contributing to the tools and platforms that support the collaborative process. + +Quality of contributions and thus quantity of recognition will largely (with some exceptions discussed below) begin as a discretionary choice of the maintainers. However, we eventually hope to transition an increasing range of the mechanisms through which we give out such recognition to formal community governance, as part of the governance and progressive decentralization below. + +All identity roles and credit will initially be public (possibly pseudonymous, but with no internal privacy controls). We hope to introduce some innovative privacy features consistent with the ideas in the book (such as designated verifier signatures) in the future. diff --git a/docs/Contributing in other ways.md b/docs/Contributing in other ways.md new file mode 100644 index 00000000..ad4d2b6a --- /dev/null +++ b/docs/Contributing in other ways.md @@ -0,0 +1,11 @@ +--- +title: Contributing citations +author: +date: +tags: + - +--- + +# Contributing in other ways + +> Brief info about contributing in other ways \ No newline at end of file diff --git a/docs/Contributing to the docs.md b/docs/Contributing to the docs.md new file mode 100644 index 00000000..14b3b8b2 --- /dev/null +++ b/docs/Contributing to the docs.md @@ -0,0 +1,11 @@ +--- +title: Contributing citations +author: +date: +tags: + - +--- + +# Contributing to the docs + +> Brief info about contributing to the docs \ No newline at end of file diff --git a/docs/Contribute translations.md b/docs/Contributing translations.md similarity index 89% rename from docs/Contribute translations.md rename to docs/Contributing translations.md index 3fdcf4ce..fa386e29 100644 --- a/docs/Contribute translations.md +++ b/docs/Contributing translations.md @@ -1,8 +1,12 @@ --- title: Contributing translations +author: +date: +tags: + - --- -# Plurality Translation Contributor Onboarding +# Contributing translations >👋 Welcome! This document aims to help onboard new contributors from different regional communities to help translate the Plurality book. @@ -20,14 +24,14 @@ Is there a point of contact or thread already for your language / region? * if yes, please find them in [#translations](https://discord.gg/9x3nBJeuPY), reach out to them in your community’s thread * if no, tag Jacky in #general under Contributors to get onboarded -![discord screenshot of translations tab](../assets/translation-screenshot-01.png) +![discord screenshot of translations tab](assets/translation-screenshot-01.png) ## Translation Process > *Reach out to Jacky if there are any questions here* * English and Traditional Mandarin are considered the root language that will be directly uploaded to the root repository. Translations of other languages will need to be done in forks from the root to decentralize and streamline each community’s independent workflow. -![translation git repos](../assets/translation-screenshot-02.png) +![translation git repos](assets/translation-screenshot-02.png) * The point of contact for each community can fork the main branch of [plurality root repository](https://github.com/pluralitybook/plurality) on GitHub and start adding their translated content in the forked repository. * please name the fork with book name + language name for easier recognizability (e.g plurality-japanese) @@ -38,17 +42,17 @@ Is there a point of contact or thread already for your language / region? > *Reach out to Aki or Jacky if there are any questions here. Many steps are still quite manual, the process should become easier as more people go through them.* * Start with translating the announcement if its not already translated, and submit it to be added under the different versions of the [announcement in GitHub](https://github.com/alexrandaccio/plurality.net/tree/main/src/site/versions). -![alt text](../assets/translation-screenshot-03.png) +![alt text](assets/translation-screenshot-03.png) * Add translated chapters in your forked repository with English file names * Create a pull request on https://github.com/alexrandaccio/plurality.net using same structure as https://github.com/alexrandaccio/plurality.net/pull/14/files to add new chapters [here](https://github.com/alexrandaccio/plurality.net/tree/main/src/site/chapterversions) -![alt text](../assets/translation-screenshot-04.png) -![alt text](../assets/translation-screenshot-05.png) +![alt text](assets/translation-screenshot-04.png) +![alt text](assets/translation-screenshot-05.png) * Aki will approve incoming pull requests in order for the content to be shown on the website -### References +## References > Feel free to ask any questions in Discord under **Contributors** category diff --git a/docs/Getting started as a contributor.md b/docs/Getting started as a contributor.md deleted file mode 100644 index bc964f5a..00000000 --- a/docs/Getting started as a contributor.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -Title: Getting started as a contributor ---- - -# Getting started as a contributor - diff --git a/docs/Gov4Git and PMP.md b/docs/Gov4Git and PMP.md index e4d959b1..b6a77efa 100644 --- a/docs/Gov4Git and PMP.md +++ b/docs/Gov4Git and PMP.md @@ -1,5 +1,9 @@ --- title: Gov4Git and PMP +author: +date: +tags: + - --- # ⿻ Plural Management of ⿻ 數位 Plurality diff --git a/docs/Governance Gov4Git.md b/docs/Governance Gov4Git.md new file mode 100644 index 00000000..e01feeea --- /dev/null +++ b/docs/Governance Gov4Git.md @@ -0,0 +1,16 @@ +--- +Title: Gov4Git +author: +date: +tags: + - +--- +# Gov4Git and PMP + +## Gov4Git + +> [Gov4Git](https://gov4git.org/) (G4G) is an open-source protocol that uses a blockchain-like structure where a ledger of credits is mirrored by the Git repositories of all its members. + +In contrast to standard blockchains G4G does not include financial incentives for maintenance of the ledger and instead relies on community members to mirror the underlying database for the same reason that they mirror the code of git projects (to participate in the community). + +When there is a conflict in the ledger, the governance procedures described below work to resolve these conflicts. The social capitalization table used for allocating PCs will live on a ledger that is maintained by the community through the Gov4Git protocol. diff --git a/docs/Governance PMP.md b/docs/Governance PMP.md new file mode 100644 index 00000000..db5032cf --- /dev/null +++ b/docs/Governance PMP.md @@ -0,0 +1,23 @@ +--- +Title: Governance PMP +author: +date: +tags: + - +--- + +# Plural Management Protocol + +> While the Gov4Git protocol offers a foundational layer for an essentially-arbitrary range of governance mechanics, the governance mechanism that we plan to implement is the Plural Management Protocol (PMP). + +The PMP harnesses and combines a range of the mechanisms described in the book to allow us to achieve our goals. Full details of the PMP can be found in the [Plural Management paper](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4688040). + +With the PMP, contributors can earn credits by making contributions to the book (approval of the contributors GitHub pull requests), and by helping others triage pull requests (predicting the outcome of a pull request approval vote). Contributors can then use their credits to prioritize GitHub issues, and to approve or reject GitHub pull requests. + +## Processes of the PMP + +1. **Prioritization**: Issues are prioritized by a version of the Capital-Constrained [Quadratic Funding](https://arxiv.org/abs/1809.06421) (QF) mechanism. Contributors dynamically contribute to proposals’ priorities and are matched according to the “democratic” QF formula (e.g. small contributions are matched more than large ones, and contributions to popular issues are matched more) and the current matching funds made available by sponsors. +2. **Subsidies**: The matching funds are provided by sponsors, mostly likely the largest PC holders such as E. Glen Weyl and Audrey Tang. +3. **Bounties and contributions**: The current priorities of issues are publicly displayed and ranked, so as to encourage contributors to prioritize addressing these. A contributor who submits a PR to address an issue and has this PR accepted will receive a bounty in PCs Plural Management user doc.docx proportional to this current priority (with a small “tax” to support the process of evaluating the PR). +4. **Approval votes**: Contributors can vote for a PR to be accepted or rejected. PRs with net positive votes at the end of the review period (currently a week) will be accepted. The cost in credits of $v$ votes is $kv^2$ where $k$ is a PR-specific constant. This instantiates the system of [Quadratic Voting](https://en.wikipedia.org/wiki/Quadratic_voting#:~:text=With%20quadratic%20voting%2C%20not%20only,be%20%244%2C%20and%20so%20on.) (QV) described in the book. +5. **Approval predictions**: In addition to voting, contributors are also implicitly predicting what decision the community will make; in addition to the cost of $kv^2$ they will also pay a cost of $|v|$ and receive a payment of $2|v|$ if the community decides in favor of the direction of their vote. For someone who is purely maximizing their return, it is optimal to vote in the amount $\frac{|p-1/2|}{2k}$ in the direction that they believe it is more likely for the vote to go, where $p$ is the probability they believe the vote will be approved. This provides low PC-holding community members to gain PCs by helping those who may have more PCs but less time to review submissions to sort the wheat from the chaff. \ No newline at end of file diff --git a/docs/Governance introduction.md b/docs/Governance introduction.md new file mode 100644 index 00000000..a1d156be --- /dev/null +++ b/docs/Governance introduction.md @@ -0,0 +1,22 @@ +--- +title: Governance introduction +author: +date: +tags: + - +--- + +# Governance introduction + +> The ideas described in Plurality aim to tell the world how collaborative technology can remake how we work and govern together. The Plurality community also aims show how these ideas can work in practice. + +To do this, the Plurality book will be built using the principles that are described in the book. This is a challenge because it is a book about innovation and thus the platforms for the things we want to show do not exist: we are building them as we go in the process of writing the book! + +## Governance goals + +We have several interlocking goals in the design of our management system: + +1. **We want to recognize project contributions formally, quantitatively, and democratically.** This can be contrasted to the informal and often confusing methods that are typical to open-source projects. +2. **We want to avoid speculation and financialization** of the devices that will be used to recognize contributions to the project. +3. **We want to demonstrate the ideas of Plurality.** To do this, we will aim to ensure that the direction of the project is determined democratically. Eventually, we want to turn over the maintenance of the project to the community completely. +4. **We want the project to scale smoothly while also ensuring that the systems we use are secured against malicious attacks.** We want to ensure that democratization and decentralization happens gradually and does not occur at the expensive of the integrity of the project’s contents or the community’s values. diff --git a/docs/Governance plural credits.md b/docs/Governance plural credits.md new file mode 100644 index 00000000..c4e2b163 --- /dev/null +++ b/docs/Governance plural credits.md @@ -0,0 +1,24 @@ +--- +Title: Governance plural credits +author: +date: +tags: + - +--- + +# Plural Credits + +> A key device that will be used by the community to accomplish our [governance goals](Governance introduction.md) is a system of unique credits we call Plural Credits. + +Plural credits (PCs) are used to formally recognize when someone contributes to the project. PCs will initially be interchangeable, quantitative, and divisible indicators of contribution. Individuals will not be able to transfer or sell credits to one another. While of no (direct) financial value, PCs will entitle holders to several social benefits. + +## Benefits of Plural Credits + +1. **Recognition**: Our ledger of PC holdings will be the definitive source of information on the contributions to the book. We plan to display the ledger in in several ways. One of these ways could be to create collective image that acts as a “credit scroll” of contributors. The more significant one’s contribution is to the project, the more prominently they will be displayed in this image. Whenever we refer to the “⿻ community”, we will implicitly be referencing this ledger. +2. **Governance rights**: PCs will be the tool that is used to govern the project. They govern by determining the priority of work, and the changes or contributions that should be accepted. When PCs are used for governance, they also determine who will receive PCs in the future and thus who will be able to make further governance decisions. More on governance is discussed below. +3. **Resources**: PCs will gate access to various resources. This includes ‘@plurality.net’ email addresses, GitHub Pro coupons, and other benefits (including possibly financial compensation from funds raised by book sales, all of which will be donated to the community’s collective governance). Resources will be voted on by the community and will remain consistent with our status as being fiscally sponsored by the charitable organisation (US 501c3) Open Collective Foundation. Any compensation is to be reasonable, transparent, and consistent with this status. +After introduction of quantitative PCs we plan to introduce qualitative tokens. Qualitative tokens will be able to indicate the type of contribution that an individual makes (e.g. a written, design, or technical contribution). + +## Social capitalization table + +We will shortly release a “social capitalization table” that will make the allocation of PCs now and in the short term more clear. Future evolution of the social capitalization table will be determined collectively by the community. The social capitalization table will initially be released as a simple spreadsheet, however it will eventually live in a distributed ledger maintained by the community through the open source Gov4Git (G4G) protocol. diff --git a/docs/Home citing the book.md b/docs/Home citing the book.md new file mode 100644 index 00000000..fa161af1 --- /dev/null +++ b/docs/Home citing the book.md @@ -0,0 +1,31 @@ +--- +title: Citing the book +author: +date: +tags: + - +--- + +# Citing the book + +> Citing the book promotes its recognition, increasing chances for collaboration and thus the inclusivity and sustainability of the project. + +Feel free to copy the citation samples below if you would like to cite the book. + +## Chicago citation sample + +``` +Weyl, E. Glen, Audrey Tang, and the Plurality Community. "Plurality: The Future of Collaborative Technology and Democracy." 2023. GitHub. Accessed [Date accessed]. https://github.com/pluralitybook/plurality/blob/main/contents/english. +``` + +## BibTeX sample + +``` +@online{plurality2023, + title={Plurality: The Future of Collaborative Technology and Democracy}, + author={Weyl, E. Glen and Tang, Audrey and {the Plurality Community}}, + year={2023}, + url={https://github.com/pluralitybook/plurality/blob/main/contents/english}, + publisher={GitHub}, +} +``` diff --git a/docs/Home copyright.md b/docs/Home copyright.md new file mode 100644 index 00000000..45b5049e --- /dev/null +++ b/docs/Home copyright.md @@ -0,0 +1,14 @@ +--- +title: +author: +date: +tags: + - +--- +# Copyright + +> All materials in this repo and in all other parts of this project (unless explicitly stated otherwise) are in the public domain +> +> A CC0 license can be found in the [project's repository](https://github.com/pluralitybook/plurality/blob/08ed3dff4071905bf2f741ec55b09127d340db87/LICENSE), and most of the related software has a [GNU General Public License](https://en.wikipedia.org/wiki/GNU_General_Public_License). + +We strongly encourage translations, both to other languages and to other cultural genres, whether in terms of formatting (fiction, journalism, etc.) or to different communities (religious, ethnic, disciplinary, etc.). While these "forks" can do whatever they wish with this public domain material, we plan to link to and "recognize" only a smaller group of projects that align to the root in terms of content, values, management style and copyrights. We hope this link and roots will remain relevant and respected because of the legitimacy this community will achieve through its principles and writing. \ No newline at end of file diff --git a/docs/Home editing and pull requests.md b/docs/Home editing and pull requests.md new file mode 100644 index 00000000..bc845223 --- /dev/null +++ b/docs/Home editing and pull requests.md @@ -0,0 +1,17 @@ +--- +title: +author: +date: +tags: + - +--- + +# Editing and pull requests + +> While there will be many types of contributions, arguably the focal and most common one will be editing of the root book. + +This will happen through the standard git issue-fork-pull request-merge process which we will not discuss further here, as it is well documented in many places online. As such, several central sources of credit and contribution will be related to this process and they are worth discussing in a bit greater detail here. + +In writing this book, we aim to create a new vision for the future of technology that can help inspire a community to pursue and help create it. We do not aim primarily at a statement of fact or consensus, though we hope to help surface facts and promote cooperation across difference. As such, we will strive to mostly maintain a coherent argument and authorial voice, rather than combining together separate contributions from distinct authors. However, we believe such a goal is consistent with a wide range of participation and input and that, ultimately, our ideas will only succeed if they eventually become a reflection of common sense of a community that pursues them. As such we hope that the community helping us build this book will contribute a range of edits from the small (e.g. copyedits) to the large (e.g. building blocks of text that help us flesh out an application or restate a principle). The more significant these contributions, the greater they will be recognized. We also seek to embrace technological advancements in all our work and thus welcome the use of a range of digital assistive tools, such as generative foundation models, in creating contributions. + +At the same time, we expect there to be far more engagement than any small group of maintainers can realistically manage in any project on these terms, especially one as ours that has natural adversaries. Thus the editorial and maintenance role will be at least as important for us to share with the community as the contribution role. We plan to do this by asking the community to help prioritize issues and PRs and to reward accurate prioritization, ones that end up being accepted/acted upon. The precise mechanisms we will use for this will evolve over time and we will shortly link to live explanatory documents. However, we will always endeavor to use creative approaches grounded in the principles described in the book, for example using a mixture of prediction markets and various forms of plural voting. diff --git a/docs/Home financial goals.md b/docs/Home financial goals.md new file mode 100644 index 00000000..20e54214 --- /dev/null +++ b/docs/Home financial goals.md @@ -0,0 +1,22 @@ +--- +title: Financial goals +author: +date: +tags: + - +--- + +# Financial goals + +> We have no aspiration to earn any financial return on any aspect of the project, and in fact are spending some personal resources to make it possible. + +However, there are elements of the project that may require financial support (e.g. promotion and distribution of the physical book) and many of the volunteers in the community may decide it is appropriate they be compensated for some part of the time they devote to the work. + +We are committed to putting all base materials into the public domain and it is core to this project to avoid it becoming financialized or speculative. At the same time, we believe that there are ways that are not only consistent with our values but illustrative of them to help raise funds to the extent they become relevant. We welcome ideas from the community on this; some preliminary thoughts of ours include: + +1. Non-fungible tokens (NFTs) that are issued along with physical copies of the book and allow the book to sell at a premium despite the lack of copyright. +2. Raising funds through a Quadratic Funding grant on platforms such as GitCoin. +3. Using partial common ownership/Harberger tokens to gate access to scarce associated resources (like Glen's consulting and speaking time). +4. Issuing credentials and SoulBound Tokens to both direct financial contributors and those who fund the project through GitCoin. + +We plan to pursue these approaches and to put any funds raised into the collective control of the community, after any necessary expenditures to ensure physical printing and distribution of the book are completed. We understand this will require appropriate legal steps to ensure compliance with organizational forms and standard in relevant jurisdictions and we plan to undertake these in the coming months, possibly with the assistance of the Open Collective Foundation. diff --git a/docs/Home governance and progressive decentralization.md b/docs/Home governance and progressive decentralization.md new file mode 100644 index 00000000..08615bd3 --- /dev/null +++ b/docs/Home governance and progressive decentralization.md @@ -0,0 +1,15 @@ +--- +Title: Governance and progressice decentralization +author: +date: +tags: + - +--- + +# Governance and progressive decentralization + +> All governance functions will harness both the qualitative and quantitative tokens discussed above. Governance will harness a range of approaches, from formal voting to informal discussions. We will aim to harness as many of the tools we describe in the book as possible, to show as well as tell the book's message. + +Governance will address the full range of issues in the project's development: the evolution of all repositories, decisions about the physical publication process, etc. Initially, community input will be advisory and this will remain the case in final decisions until the book is physically printed. + +However, we aim to harness Gov4Git to turn the process over to full and direct community control after the printing of the first edition of the physical books. While this milestone marks a point at which we aim to make the formal transition, we hope for this process to be gradual: we hope that overtime we rely more and more on the community to guide every decision and that our oversight becomes more of a formalism. We plan to incorporate additional governance elements to aid this transition over time, such as signals from the community of the value of various contributions which we can then approve. To get a sense of the kinds of governance structures we hope to employ, please visit the RadicalxChange website (http://www.radicalxchange.org). We will include more details linked here as we have a clearer sense of precisely how we will use these elements. diff --git a/docs/Style Guide.md b/docs/Style Guide.md deleted file mode 100644 index 912f377f..00000000 --- a/docs/Style Guide.md +++ /dev/null @@ -1,188 +0,0 @@ ---- -title: Style guide for ⿻數位 Plurality ---- - -# Style guide for ⿻數位 Plurality - -This article provides stylistic guidance for contributors who are in the process of adding content to *⿻數位 Plurality*. - -If you are new to the project and would like to learn how to contribute, you can start learning [here](Getting started as a contributor). - -## Book structure - -*⿻數位 Plurality* is broken up into different components which are referred to as *Parts*, *Chapters*, *Sections*, and occasional *Subsections*. - -These components are indicated in the markdown file name, within the markdown file itself, or both. - -### Parts - -Parts divide the content of ⿻數位 Plurality into sections of broadly connected concepts and ideas. The aim of Parts is to guide readers into the content that aligns most with their particular interests. There are currently 7 Parts. - -In the Markdown file name, the first number indicates the Part, starting at 0. - -*Example*: - -> **6**-2-health - -Parts are not indicated within the contents of the markdown file. - -### Chapters - -Chapters are found within Parts. Chapters are used to break down Parts into a specific set of related ideas or concepts. - -For example, *Part 6* might be interesting for a reader who would like to learn more about how Plurality impacts the real-world in specific social sectors. *Part 6, Chapter 2* will then focus in on the health sector. - -The second number in the markdown file name indicates the Chapter number, starting at 0. The text following the number indicates the chapter name. Each single markdown file is one Chapter. - -*Example*: - -> 6-**2**-**health** - -The Chapter title can also be found within the markdown file content, usually at the very top of the file, and is set off by a single "#". - -### Sections - -Sections are found within Chapters. They are used to provide structure to a chapter, and to focus the readers attention to a specific idea. - -For example: In *6-2-health*, there is a section on "Reimagining Health Insurance" - -The Section title can be found within a markdown file, somewhere below a Chapter, and is set off by a triple "###". - -### Subsections - -Subsections provide greater structure to a Chapter when required. The use of subsections should generally be avoided except when absolutely necessary. - -The subsection title can be found within a makrdown file, somewhere below a Section, and is set off by a quadrupule "####". - -### Divisions - -Chapters in Parts 2-7 all begin with some sort of introductory material before the main substances of the chapter. - -The introductory material is homogeneous in a Part and varies across Parts (e.g. Part 4 chapters all begin with an illustration of a currently deployed technology illustrating the idea of the chapter). - -Introductory material should be separated from the rest of the text with `---`. - -## Punctuation and grammar - -### Capitalization - -Chapter titles are fully capitalized; only the first letter of Sections are titled. - -### Commas - -We use Oxford commas. - -### Justification - -Paragraphs are not indented. - -## Figures - -This article provides information on figure style recommendations. For information on how to add a figure to ⿻數位 Plurality, see [Contributing figures](Contributing figures.md). - -If you have any questions about a figure that you would like to add, visit the discord and ask your question in the [#data](https://discord.com/channels/1133444567031627846/1212804858457890927) channel. - -### Figure syntax - -Figures are added as [HTML syntax](https://www.w3schools.com/html/html_images.asp) to markdown files. Figures should include the following: - -* A ```
``` tag -* An `````` tag -* The image source -* The image width which should be set to 100% -* An `````` tag that describes the image -* A ```
``` tag that indicates which chapter the figure is in, and assigns a letter to indicate the order in which the figure appears in a chapter (e.g. the first image in 2-0 would have the caption Fig 2-0-A) - -If a figure is referred to within a chapter, the reference should only use the letter of the figures caption (e.g. "Figure A shows...") - -Below is an example of the HTML syntax required for figure: - -``` -
- A plot showing the growth of private investment in AI over time. -
Figure 2-0-A The rise in private sector AI investment over time. Source: NetBase Quid/Stanford Center on Human-Centered AI .
-
-``` - -### Figure style - -Figures should have: -* A white background -* Black text/gridlines/etc. - -The preferred font is [Jost](https://fonts.google.com/specimen/Jost). - -Colours should be converted to grayscale. The recommended grayscale colours are: - -```python -BLACK = '#222222' -GRAY1 = '#5C5C5C' -GRAY2 = '#ADADAD' -GRAY3 = '#DEDEDE' -WHITE = '#FFFFFF' -``` -The resolution, number of pixels, and print size of figures are related mathematically. -Pixels = Resolution (DPI) × Print size (in inches). - -Figures should have at least 300 [DPI](https://en.wikipedia.org/wiki/Dots_per_inch) and should try to meet the following sizing guidelines: - -| Size | Image Width | @ 300 DPI | @ 500 DPI | -| :--- | :---------- | :-------- | :-------- | -| Small | 90 mm, 3.54 in | 1063 px | 1772 px | -| Medium | 140 mm, 5.51 in | 1654 px | 2756 px | -| Large | 190 mm, 7.48 in | 2244 px | 3740 px | - -## Citations and referencing - -This article provides information on citation style recommendations. For information on how to add a citations to ⿻數位 Plurality, see [Contributing citations](docs/Contributing citations.md). - -The book currently uses the Chicago Manual of Style for citations. For more information and examples citating using on the Chicago Manual of style, see [The Chicago Manual of Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). - -### Citing a book - -FirstName LastName, *Book Title* (City, State of publication: Publisher, Publication year), page number(s) if a direct quote. - -*Example*: - -> Zadie Smith, *Swing Time* (New York: Penguin Press, 2016), 315–16. - -### Citing a journal article - -FirstName LastName, “Article Title,” *Journal Title* volume number, issue number (Publication Year): page numbers, link or DOI if available. - -*Example*: - -> Shao-Hsun Keng, Chun-Hung Lin, and Peter F. Orazem, “Expanding College Access in Taiwan, 1978–2014: Effects on Graduate Quality and Income Inequality,” *Journal of Human Capital* 11, no. 1 (Spring 2017): 9–10, [https://doi.org/10.1086/690235](https://doi.org/10.1086/690235). - -### Citing a news or magazine article - -FirstName LastName, “Article Title,” *Publication Title*, Month Day, Year. Include URL if available. - -*Example*: - -> Rebecca Mead, “The Prophet of Dystopia,” New Yorker, April 17, 2017. - -### Citing a blog post - -FirstName LastName, “Blog Post Title,” *Blog Title*, Month Day, Year, link. - -*Example*: - -> Deb Amlen, “One Who Gives a Hoot,” *Wordplay*, January 26, 2015, [http://wordplay.blogs.nytimes.com/2015/01/26/one-who-gives-a-hoot/](http://wordplay.blogs.nytimes.com/2015/01/26/one-who-gives-a-hoot/). - -### Citing website content - -“Page Title,” Company, last modified Month Day, Year, link. - -*Example*: - -> "Privacy Policy", Privacy & Term", Google, last modified April 17, 2017, [https://www.google.com/policies/privacy/](https://www.google.com/policies/privacy/). - -### Internal referencing - -When referencing Parts, Chapters, or Sections, use their titles in quotes. - -*Example*: - -> * In the Part of the book on 'Freedom' -> * In our Chapter 'The Lost Dao' diff --git a/docs/Style guide book structure.md b/docs/Style guide book structure.md new file mode 100644 index 00000000..ed5281be --- /dev/null +++ b/docs/Style guide book structure.md @@ -0,0 +1,55 @@ +--- +title: Style guide structure +author: +date: +tags: + - +--- +# Structure +> *⿻數位 Plurality* is broken up into different components which are referred to as *Parts*, *Chapters*, *Sections*, and occasional *Subsections*. +> +> These components are indicated in the markdown file name and/or within the markdown file itself. + +## Parts + +Parts divide the content of ⿻數位 Plurality into sections of broadly connected concepts and ideas. The aim of Parts is to guide readers into the content that aligns most with their particular interests. There are currently 7 Parts. + +In the Markdown file name, the first number indicates the Part, starting at 0. + +*Example*: **6**-2-health + +Parts are not indicated within the contents of the markdown file. + +## Chapters + +Chapters are found within Parts. Chapters are used to break down Parts into a specific set of related ideas or concepts. + +For example, *Part 6* might be interesting for a reader who would like to learn more about how Plurality impacts the real-world in specific social sectors. *Part 6, Chapter 2* will then focus in on the health sector. + +The second number in the markdown file name indicates the Chapter number, starting at 0. The text following the number indicates the chapter name. Each single markdown file is one Chapter. + +*Example*: 6-**2**-**health** + +The Chapter title can also be found within the markdown file content, usually at the very top of the file, and is set off by a single "#". + +## Sections + +Sections are found within Chapters. They are used to provide structure to a chapter, and to focus the readers attention to a specific idea. + +*Example*: In *6-2-health*, there is a section on "Reimagining Health Insurance" + +The Section title can be found within a markdown file, somewhere below a Chapter, and is set off by a triple "###". + +## Subsections + +Subsections provide greater structure to a Chapter when required. The use of subsections should generally be avoided except when absolutely necessary. + +The subsection title can be found within a markdown file, somewhere below a Section, and is set off by a quadruple "####". + +## Divisions + +Chapters in Parts 2-7 all begin with some sort of introductory material before the main substances of the chapter. + +The introductory material is homogeneous in a Part and varies across Parts (e.g. Part 4 chapters all begin with an illustration of a currently deployed technology illustrating the idea of the chapter). + +Introductory material should be separated from the rest of the text with `---`. \ No newline at end of file diff --git a/docs/Style guide citations and referencing.md b/docs/Style guide citations and referencing.md new file mode 100644 index 00000000..f44ef8c1 --- /dev/null +++ b/docs/Style guide citations and referencing.md @@ -0,0 +1,61 @@ +--- +title: Style guide citations and references +author: +date: +tags: + - +--- +# Citations and references +> This article provides information on citation style recommendations. For information on how to add a citations to ⿻數位 Plurality, see [Contributing citations](Contributing citations.md). +> +> The book currently uses the Chicago Manual of Style for citations. For more information and examples citating using on the Chicago Manual of style, see [The Chicago Manual of Style](https://www.chicagomanualofstyle.org/tools_citationguide/citation-guide-1.html). + +### Citing a book + +FirstName LastName, *Book Title* (City, State of publication: Publisher, Publication year), page number(s) if a direct quote. + +*Example*: + +> Zadie Smith, *Swing Time* (New York: Penguin Press, 2016), 315–16. + +### Citing a journal article + +FirstName LastName, “Article Title,” *Journal Title* volume number, issue number (Publication Year): page numbers, link or DOI if available. + +*Example*: + +> Shao-Hsun Keng, Chun-Hung Lin, and Peter F. Orazem, “Expanding College Access in Taiwan, 1978–2014: Effects on Graduate Quality and Income Inequality,” *Journal of Human Capital* 11, no. 1 (Spring 2017): 9–10, [https://doi.org/10.1086/690235](https://doi.org/10.1086/690235). + +### Citing a news or magazine article + +FirstName LastName, “Article Title,” *Publication Title*, Month Day, Year. Include URL if available. + +*Example*: + +> Rebecca Mead, “The Prophet of Dystopia,” New Yorker, April 17, 2017. + +### Citing a blog post + +FirstName LastName, “Blog Post Title,” *Blog Title*, Month Day, Year, link. + +*Example*: + +> Deb Amlen, “One Who Gives a Hoot,” *Wordplay*, January 26, 2015, [http://wordplay.blogs.nytimes.com/2015/01/26/one-who-gives-a-hoot/](http://wordplay.blogs.nytimes.com/2015/01/26/one-who-gives-a-hoot/). + +### Citing website content + +“Page Title,” Company, last modified Month Day, Year, link. + +*Example*: + +> "Privacy Policy", Privacy & Term", Google, last modified April 17, 2017, [https://www.google.com/policies/privacy/](https://www.google.com/policies/privacy/). + +### Internal referencing + +When referencing Parts, Chapters, or Sections, use their titles in quotes. + +*Example*: + +> * In the Part of the book on 'Freedom' +> * In our Chapter 'The Lost Dao' + diff --git a/docs/Style guide figures.md b/docs/Style guide figures.md new file mode 100644 index 00000000..4415e11c --- /dev/null +++ b/docs/Style guide figures.md @@ -0,0 +1,60 @@ +--- +title: Style guide figures +author: +date: +tags: + - +--- +# Figures + +> This article provides information on figure style recommendations. For information on how to add a figure to ⿻數位 Plurality, see [Contributing figures](Contributing figures.md). +> +> If you have any questions about a figure that you would like to add, visit the discord and ask your question in the [#data](https://discord.com/channels/1133444567031627846/1212804858457890927) channel. + +## Figure syntax + +Figures are added as [HTML syntax](https://www.w3schools.com/html/html_images.asp) to markdown files. Figures should include the following: + +* A ```
``` tag +* An `````` tag +* The image source +* The image width which should be set to 100% +* An `````` tag that describes the image +* A ```
``` tag that indicates which chapter the figure is in, and assigns a letter to indicate the order in which the figure appears in a chapter (e.g. the first image in 2-0 would have the caption Fig 2-0-A) + +If a figure is referred to within a chapter, the reference should only use the letter of the figures caption (e.g. "Figure A shows...") + +Below is an example of the HTML syntax required for figure: + +``` +
+ A plot showing the growth of private investment in AI over time. +
Figure 2-0-A The rise in private sector AI investment over time. Source: NetBase Quid/Stanford Center on Human-Centered AI .
+
+``` + +## Figure style + +Figures should be styled in the following way: + +* A white background +* Black text/gridlines/etc. +* The preferred font is [Jost](https://fonts.google.com/specimen/Jost). +* Colours should be converted to grayscale. The recommended grayscale colours are: +```python + BLACK = '#222222' + GRAY1 = '#5C5C5C' + GRAY2 = '#ADADAD' + GRAY3 = '#DEDEDE' + WHITE = '#FFFFFF' +``` +* The resolution, number of pixels, and print size of figures are related mathematically: +``` +Pixels = Resolution (DPI) × Print size (in inches). +``` +* Figures should have at least 300 [DPI](https://en.wikipedia.org/wiki/Dots_per_inch) and should try to meet the following sizing guidelines: +| Size | Image Width | @ 300 DPI | @ 500 DPI | +| :----- | :-------------- | :-------- | :-------- | +| Small | 90 mm, 3.54 in | 1063 px | 1772 px | +| Medium | 140 mm, 5.51 in | 1654 px | 2756 px | +| Large | 190 mm, 7.48 in | 2244 px | 3740 px | \ No newline at end of file diff --git a/docs/Style guide introduction.md b/docs/Style guide introduction.md new file mode 100644 index 00000000..0d4be844 --- /dev/null +++ b/docs/Style guide introduction.md @@ -0,0 +1,16 @@ +--- +title: Style guide introduction +author: +date: +tags: + - +--- + +# Style guide for ⿻數位 Plurality + +> This sections below provide stylistic guidance for contributors who are in the process of adding content to *⿻數位 Plurality*. +> +> If you are new to the project and would like to learn how to contribute, you can start learning [here](Contributing getting started as a contributor.md). + + + diff --git a/docs/Style guide punctuation and grammar.md b/docs/Style guide punctuation and grammar.md new file mode 100644 index 00000000..6e212152 --- /dev/null +++ b/docs/Style guide punctuation and grammar.md @@ -0,0 +1,21 @@ +--- +title: Style guide punctuation and grammar +author: +date: +tags: + - +--- + +# Punctuation and grammar +> Information about the punctuation and grammar +## Capitalization + +Chapter titles are fully capitalized; only the first letter of Sections are titled. + +## Commas + +We use Oxford commas. + +## Justification + +Paragraphs are not indented. \ No newline at end of file diff --git a/docs/assets/favicon.png b/docs/assets/favicon.png new file mode 100644 index 0000000000000000000000000000000000000000..d0353aeef6252040284b15161f3122356a0d9a4c GIT binary patch literal 1096 zcmeAS@N?(olHy`uVBq!ia0vp^CqS5k4M?tyST~P>fra1G#WAGf*4w-LvnJPy9Qasl za-*p^FHfmNljG5aN6!@E8n-`qq-xPQo9pPs>JMTuF;@>dmhUbXVApgtIIil%;ps71 zy?);FpEV9|Zg0t)^<;K&UG2fNP*#JxqUDSnEG$e+jExNr4hjka0vsGHAWTRIq7p?F zl8}Qn@2!$#k(o9|NmHu;zIRp z=WzEuJX70f(VP%k$~JSOpMroeOCv{$p&AF%K^DOd;|>Rwq@zL|4gwtxJ_0O{rk)21 zaw-YTaTMs_Y;s^x0*n3C5D<1zU~*JoGIRtA@#_F-plT%nnM;Bm=g%vs0Zn0=eQj#J zMP9P7igCWnk*_=M=&#d%2jpTOJ>KpAKA=T zU;p0hgXufhBjwuDj5*FJ{EgZuz;W8wkR_=}L16toH4f#vGq>0D3l`pM`u*BKi7zeY zo2Ak@x9=~1%zrrL``POMfi8DMJB&~4SRT6d^ZsNT<9OF2pC!fjuUN&;ThlvPkL3~1 zBOMq1b0Ej-Mr;H+S$mp8Se+u!lTAPmH*y@gVdl6dLJi0@24c=fWf2?aII=W3tcl<_ z(v=Df8K63#fRca@P$x(UP*+tEo8d{DFs6-3iURE=K&Ju?zI4_4E(<7BfWbRMAxx*e zM3^OAKwFF{^WZB5fyRj3XA)IjmdzCpds_o&g=`0tQ=33(He%zo1-bS|s{{nY-OKCx zYy~VoE_fo8um5XfzVf4wQ*M7#-}Nzgjr^^=Ooh`jD?^{#Cp62&Y{_*KQ-?ir7e)jrTWN1ArQV7l+=;uum9 z_jb;~!aD{6EaDq2c%LTO%S@9G((^jJ@xoHA+q;T8T?^91qCQ9Ezbm-NJ3-;SpYo4v z*Mu#v+R~U5&#Eyx30&%N*jyH&$dT!`Akun`K#Pg;g*CEa98R+YGp_MzvnZbBFv&i? z$!S~e?ODCrSIAveUHi1PNJJ!3N;N=hN$WMx#B#?CQ1^3Qf6Xpwke04b0 zx2mf{|G!#X?1|G7k7tW6*37xR?Rm$KE&<^HQ#M5{$6{NjGY(fRT2`=}{mNm;9Qs&b zk&wxCHz0Mt87h?Jai~~&h6xms}=l+%x%wKOD_P6%OD;1@3{SD9NJSAF91y6^MKQQNEjBD|*V`)=W`Z1!Cu|r?w^^jU zso8ELA-Botg!Q6RvwzK;?;2ivy)578gnf6|dan5&Wr}tf?UF6{8XIPQul=vW6M>7j zm<2XX`~L8zKv74=TgK^vi;|-Ez773dyE=dG=^*wFfzQPpPXB~ne5~Yf5?FMOap%11 zj-CtB4FdZ9mb{8aPWcQ@du*PXw4C7B%gFKZ)0E3{K^;E1wFkD!^IZQt<$MP`@T8nl zTJANR=7{_&|8$Sky~|a9+;^_JXq&X|X?0{j$GWUD94nP(pK *Plurality* is an open, git-based collaborative book project that aims to offer a vision for the future of technology focused around empowering and bridging social difference. +> +> Before you get started with the docs, you might want to check out the *Plurality* book which can be found at [plurality.net](https://www.plurality.net/), or say 'Hi' to the community by sending a message introducing yourself on our [community discord](https://discord.gg/YWSDRqdW5n"). + +On this site you will find information about the *Plurality* book project and its governance, instructions on how to contribute to the project, reccomendations on creating you own copy of the project, and more. + +The initial maintainers of the *Plurality* book project are Audrey Tang, [Taiwan's digital minister](https://moda.gov.tw/en/), and [E. Glen Weyl](https://www.glenweyl.com). However, we plan to progressively decentralize control of the project using a new git-native formal governance protocol using blockchain-like affordances called [Gov4Git](https://github.com/gov4git/gov4git). After physical copies of the book have been printed we plan to transition the project to full community control. To get started with you own contributions, start [here](Contributing getting started as a contributor.md). + +All material in the *Plurality* book project is [CC0](https://en.wikipedia.org/wiki/Creative_Commons_license). If we made a mistake, take it as an invitation. If you feel we are wrong, set us straight. If we are not speaking in the language of your community, create a version that does. If you don't want to deal with the community, the material has no copyright so take anything you want and leave the rest. + +Ask not, "Why is nobody doing this?" You are the nobody. From e55106038982906b6b16fcdf6ef322dfda9ce125 Mon Sep 17 00:00:00 2001 From: pluralitybook Date: Sun, 21 Apr 2024 21:14:46 -0400 Subject: [PATCH 2/2] Adding Jordan endorsement --- contents/english/0-0-endorsements.md | 57 ++++++++++++++++------------ 1 file changed, 33 insertions(+), 24 deletions(-) diff --git a/contents/english/0-0-endorsements.md b/contents/english/0-0-endorsements.md index f71f95f7..0dd83558 100644 --- a/contents/english/0-0-endorsements.md +++ b/contents/english/0-0-endorsements.md @@ -35,11 +35,13 @@

-> Here in lucid and non-technical prose is a sweeping vision for how to integrate so much of what we've learned about technology and society in the past decades to remake the future of democracy, from someone who is actually doing it on the ground.

-— [Alex "Sandy" Pentland](https://en.wikipedia.org/wiki/Alex_Pentland), Inaugural Academic Head of the MIT Media Lab and founding father of Computational Social Science and Data Science +> Glen and Audrey lead a team offering a master class in how to harness advanced computation to augment rather than replace human social and economic systems, simultaneously showing and telling us how digital technology can make the world dramatically more cooperative and productive.

+— [Michael I. Jordan](https://en.wikipedia.org/wiki/Michael_I._Jordan), Pehong Chen Distinguished Professor of Computer Science and Statistics at the University of California, Berkeley, inaugural winner of the [World Laureates Association Prize](https://www.thewlaprize.org/) in Computer Science or Mathematics, and [named by *Science*](https://www.science.org/content/article/who-s-michael-jordan-computer-science-new-tool-ranks-researchers-influence) as the most influential computer scientist in the world in 2016.

+ + > *Plurality* unveils the powerful blueprint of Taiwan's resilient digital transformation...provides valuable insight for concerned citizens everywhere and...can help preserve democracy amidst...a precarious moment in history for liberty and open societies around the world.

— [Frank McCourt](https://en.wikipedia.org/wiki/Frank_McCourt_(executive)), Founder of [McCourt Global](https://www.mccourt.com/) and [Project Liberty](https://www.projectliberty.io/) and co-author of [*Our Biggest Fight*](https://ourbiggestfight.com/) @@ -70,11 +72,6 @@

-> Rejoice! Here is a burst of creativity that gives us a peek at the humanistic high tech future we suspected was possible.

-— [Jaron Lanier](https://en.wikipedia.org/wiki/Jaron_Lanier), inventor of Virtual Reality, author of [*Who Owns the Future?*](https://en.wikipedia.org/wiki/Who_Owns_the_Future%3F) and [*The Dawn of the New Everything*](https://us.macmillan.com/books/9781250097408/dawnoftheneweverything) and Microsoft's Office of the Chief Technology Officer Prime Unifying Scientist (OCTOPUS) - -

- > Audrey Tang and Glen Weyl's project will be effective and meaningful in helping Taiwan (and other countries) move in the direction of a new social democracy.

— [Karatani Kōjin](https://en.wikipedia.org/wiki/Kojin_Karatani), Author of [*The Structure of World History*](https://www.dukeupress.edu/the-structure-of-world-history) and winner of the Berggruen Prize for Culture and Philosophy @@ -85,26 +82,24 @@

-> (They) have written a brilliant book of breathtaking possibility, offering...hope in a dark time...drawing on disciplines from mathematics to literature...readers are likely to find plenty of things to ponder and challenge...(and) are invited to join the conversation! -

-— [Anne-Marie Slaughter](https://en.wikipedia.org/wiki/Anne-Marie_Slaughter), CEO of the [New America Foundation](https://www.newamerica.org/), former Director of Policy Planning at the US Department of State and author of [*Unfinished Business*](https://www.penguinrandomhouse.com/books/225053/unfinished-business-by-anne-marie-slaughter/) and [*The Chess Board and the Web*](https://yalebooks.yale.edu/book/9780300234664/the-chessboard-and-the-web/) +> \(A\) remarkable book which provides accessible, deep and novel insights into the way in which technology has, is, will and should shape our lives. It draws on a wealth of evidence to provide a powerful case in favour of promoting plurality...It holds important lessons for all of us.

+— [Colin Mayer](https://en.wikipedia.org/wiki/Colin_Mayer), Peter Moores Professor of Management Studies at the Oxford [Saïd School of Management](https://en.wikipedia.org/wiki/Sa%C3%AFd_Business_School) and author of [*Prosperity: Better Business Makes the Greater Good*](https://global.oup.com/academic/product/prosperity-9780198866824?lang=en&cc=sk)

-> At last, we have a book that centers plurality – both in theory and in practice. This is a much-needed guide for developing new strategies to navigate the relationship between technology and democracy, and for thinking beyond the usual Western frame.

-— [Kate Crawford](https://katecrawford.net/), Senior Researcher at Microsoft Research, research professor at the University of Southern California, artist, musician and author of [*Atlas of AI*](https://en.wikipedia.org/wiki/Atlas_of_AI) - +> (They) have written a brilliant book of breathtaking possibility, offering...hope in a dark time...drawing on disciplines from mathematics to literature...readers are likely to find plenty of things to ponder and challenge...(and) are invited to join the conversation!

- -> In an era of anxiety and division, Glen Weyl and Audrey Tang provide a rare, grounded vision for how technology and democracy can harmonize, and propel us to a better future.

-— [Tristan Harris](https://en.wikipedia.org/wiki/Tristan_Harris), Co-Founder of the [Center for Humane Technology](https://en.wikipedia.org/wiki/Center_for_Humane_Technology) and star of [*The Social Dilemma*](https://www.thesocialdilemma.com/) +— [Anne-Marie Slaughter](https://en.wikipedia.org/wiki/Anne-Marie_Slaughter), CEO of the [New America Foundation](https://www.newamerica.org/), former Director of Policy Planning at the US Department of State and author of [*Unfinished Business*](https://www.penguinrandomhouse.com/books/225053/unfinished-business-by-anne-marie-slaughter/) and [*The Chess Board and the Web*](https://yalebooks.yale.edu/book/9780300234664/the-chessboard-and-the-web/)

+> Rejoice! Here is a burst of creativity that gives us a peek at the humanistic high tech future we suspected was possible.

+— [Jaron Lanier](https://en.wikipedia.org/wiki/Jaron_Lanier), inventor of Virtual Reality, author of [*Who Owns the Future?*](https://en.wikipedia.org/wiki/Who_Owns_the_Future%3F) and [*The Dawn of the New Everything*](https://us.macmillan.com/books/9781250097408/dawnoftheneweverything) and Microsoft's Office of the Chief Technology Officer Prime Unifying Scientist (OCTOPUS) +

-> At once optimistic and pragmatic, *Plurality* offers a roadmap to reforge democracy for the AI era...we need not limit ourselves to the libertarian or authoritarian visions...a third way...leans into openness, plurality and the human spirit. So worth reading!

-— [Mark Surman](https://en.wikipedia.org/wiki/Mark_Surman), President and Executive Director of the [Mozilla Foundation](https://en.wikipedia.org/wiki/Mozilla_Foundation) +> At last, we have a book that centers plurality – both in theory and in practice. This is a much-needed guide for developing new strategies to navigate the relationship between technology and democracy, and for thinking beyond the usual Western frame.

+— [Kate Crawford](https://katecrawford.net/), Senior Researcher at Microsoft Research, research professor at the University of Southern California, artist, musician and author of [*Atlas of AI*](https://en.wikipedia.org/wiki/Atlas_of_AI)

@@ -113,8 +108,8 @@

-> \(A\) remarkable book which provides accessible, deep and novel insights into the way in which technology has, is, will and should shape our lives. It draws on a wealth of evidence to provide a powerful case in favour of promoting plurality...It holds important lessons for all of us.

-— [Colin Mayer](https://en.wikipedia.org/wiki/Colin_Mayer), Peter Moores Professor of Management Studies at the Oxford [Saïd School of Management](https://en.wikipedia.org/wiki/Sa%C3%AFd_Business_School) and author of [*Prosperity: Better Business Makes the Greater Good*](https://global.oup.com/academic/product/prosperity-9780198866824?lang=en&cc=sk) +> Here in lucid and non-technical prose is a sweeping vision for how to integrate so much of what we've learned about technology and society in the past decades to remake the future of democracy, from someone who is actually doing it on the ground.

+— [Alex "Sandy" Pentland](https://en.wikipedia.org/wiki/Alex_Pentland), Inaugural Academic Head of the MIT Media Lab and founding father of Computational Social Science and Data Science

@@ -123,6 +118,11 @@

+> In an era of anxiety and division, Glen Weyl and Audrey Tang provide a rare, grounded vision for how technology and democracy can harmonize, and propel us to a better future.

+— [Tristan Harris](https://en.wikipedia.org/wiki/Tristan_Harris), Co-Founder of the [Center for Humane Technology](https://en.wikipedia.org/wiki/Center_for_Humane_Technology) and star of [*The Social Dilemma*](https://www.thesocialdilemma.com/) + +

+ > *Plurality* is an important book on one of today’s central challenges—building collaboration and shared purpose across diversity. The authors approach this challenge not simply in ... politics...but also offer valuable insights on...technology, economics, and beyond.

— [Julius Krein](https://en.wikipedia.org/wiki/Julius_Krein), Founder and Editor-in-Chief, [*American Affairs*](https://americanaffairsjournal.org/) @@ -135,12 +135,25 @@

+ +> At once optimistic and pragmatic, *Plurality* offers a roadmap to reforge democracy for the AI era...we need not limit ourselves to the libertarian or authoritarian visions...a third way...leans into openness, plurality and the human spirit. So worth reading!

+— [Mark Surman](https://en.wikipedia.org/wiki/Mark_Surman), President and Executive Director of the [Mozilla Foundation](https://en.wikipedia.org/wiki/Mozilla_Foundation) + +

+ + + > An exciting, creative and provocative set of ideas on how to make progress on some of the most fundamental problems in the world. You will never think the same way again after reading this book.

— [Jason Furman](https://en.wikipedia.org/wiki/Jason_Furman), Former Chair of the Council of Economic Advisors and Aetna Professor of the Practice of Economic Policy, Harvard University

+> It is a delight to finally see a vision for the future of human progress so clearly grounded in its past. With Plurality, we have a framework for building the engines that harness the abundant energy latent in human diversity to power the next hundred years of economic growth.

+— [Oded Galor](https://www.odedgalor.com/), Author of *The [Journey of Humanity](https://www.odedgalor.com/copy-of-unified-growth-theory)* and Herbert Goldberger Professor of Economics at Brown University + + +

> Can the public sector move as fast to harness emerging technologies as the rest of society? Audrey Tang has shown on the ground that it can, and here she teaches you how to do the same.

— [Shlomit Wagman](https://cyber.harvard.edu/people/shlomit-wagman), former Director General of the [Israel Money Laundering and Terror Financing Prohibition Authority](https://www.gov.il/en/departments/impa/govil-landing-page) and [Privacy Protection Authority](https://www.gov.il/en/departments/the_privacy_protection_authority/govil-landing-page) @@ -155,10 +168,6 @@ > "Regulation” remains elusive as a path to taming our technofeudal masters. It will not succeed in dispersing power. *Plurality* charts a different path for us to take - open and democratic - to bypass and dis-intermediate these powers.

— [Cristina Caffarra](https://cristinacaffarra.com/), Honorary Professor at [University College London](https://profiles.ucl.ac.uk/77797-cristina-caffarra) and Co-Founder of the [CEPR Competition Research Policy Network](https://cepr.org/about/people/cristina-caffarra) -

- -> It is a delight to finally see a vision for the future of human progress so clearly grounded in its past. With Plurality, we have a framework for building the engines that harness the abundant energy latent in human diversity to power the next hundred years of economic growth.

-— [Oded Galor](https://www.odedgalor.com/), Author of *The [Journey of Humanity](https://www.odedgalor.com/copy-of-unified-growth-theory)* and Herbert Goldberger Professor of Economics at Brown University