diff --git a/i18n/es/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md b/i18n/es/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md index e88e46bf6..45b633a8c 100644 --- a/i18n/es/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md +++ b/i18n/es/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md @@ -6,25 +6,24 @@ import NotTranslatedMessage from '../../_notTranslatedES.mdx' -Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by subDAOs & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) +Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by Working Groups & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) -# subDAOs -The Giveth DAO is divided into smaller subDAOs or Working Groups (WG), each subDAO is responsible for managing it's own budget, goals and contributors, each subDAO also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the subDAO but also that they serve the [Giveth Mission](/whatisgiveth#our-mission). subDAOs are financially beholden to the DAO in that they must present a budget every 3 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). +# Working Groups +The Giveth DAO is divided into smaller Working Groups (WG), each Working Group is responsible for managing it's own budget, goals and contributors, each Working Group also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the Working Group but also that they serve the [Giveth Mission](./#our-mission). Working Groups are financially beholden to the DAO in that they must present a budget every 3-4 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). -SubDAOs are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. +Working Groups are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. -Giveth currently has 5 subDAOs in operation, they are: +Giveth currently has 5 Working Groups in operation, they are: -- [Communitas](https://forum.giveth.io/t/communitas-working-group-proposal/1107) -- [Dapp](https://forum.giveth.io/t/dapp-working-group-proposal/1146) -- [GIVeconomy](https://forum.giveth.io/t/giveconomy-working-group-proposal/1121) -- [Rewards](https://forum.giveth.io/t/rewards-working-group-proposal/1116) -- [DAO Ops](https://forum.giveth.io/t/dao-ops-working-group-proposal/1115) -- [Quadratic Funding](https://forum.giveth.io/t/quadratic-funding-qf-working-group-proposal/1120) +- [Dapp](https://forum.giveth.io/c/dapp-wg/18) +- [GIVeconomy](https://forum.giveth.io/c/giveconomy-wg/19) +- [DAO Ops](https://forum.giveth.io/c/dao-ops-wg/20) +- [Quadratic Funding](https://forum.giveth.io/c/qf-wg/22) +- [Fundraising](https://forum.giveth.io/c/fundraising/25) You can learn more about each by clicking any of the links above leading to their Working Group Proposal on the Giveth Forum. -Anyone can propose a new subDAO to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. +Anyone can propose a new Working Group to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. # Chapters @@ -42,7 +41,3 @@ These are the current Chapters in Giveth: To learn more about Chapters, join the [Giveth Discord](https://discord.giveth.io) and introduce yourself! -# Other DAO Stuff - -Giveth also uses other tools like Gnosis Safes and Aragon DAOs that are managed by either certain working groups or specific trusted contributors, as well as the [GIVgarden](../giveconomy/givgarden) for funding community initiatives. - diff --git a/i18n/pt/docusaurus-plugin-content-docs-dapps/current/givethioinstallation.md b/i18n/pt/docusaurus-plugin-content-docs-dapps/current/givethioinstallation.md deleted file mode 100644 index 94a23bab2..000000000 --- a/i18n/pt/docusaurus-plugin-content-docs-dapps/current/givethioinstallation.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -id: givethioinstallation -title: Installing Giveth.io for Local Development -slug: dapps/givethioinstallation ---- - -import useBaseUrl from '@docusaurus/useBaseUrl' -import styles from '../../../../src/css/custom.css' - -This guide will document the steps to set up and run Giveth.io locally for the purposes of development. The setup process was documented using Ubuntu 20.04 LTS. - -#### **You'll need a couple prerequisites to get started.** - - - [Redis](https://redis.io/topics/quickstart) - - [Postgres](https://www.postgresql.org/download) - - Node 14+ - - yarn - - npm - - Your favourite Code Editor (VScode for linting presets) - -#### **Giveth IO leverages notable packages, applications and architectures including:** - - Ethereum - - React - - NextJS - - Apollo GraphQL - - Tor.us - - theme-ui - -### Install the back-end (impact-graph) from GitHub -In order to develop locally you need to clone the back-end server. We are using https://github.com/Giveth/impact-graph for this. - -*via SSH on the CLI:* -```bash - git clone git@github.com:Giveth/impact-graph.git - cd impact-graph - npm i - cp .env.example .env -``` - - -### Create a Database and User in Postgres using psql -Follow this tutorial on PSQL to setup your username and create the database. -https://medium.com/coding-blocks/creating-user-database-and-adding-access-on-postgresql-8bfcd2f4a91e) - -**TL;DR** -```bash -sudo -u postgres psql -postgres=# create database ; -postgres=# create user with encrypted password ''; -postgres=# grant all privileges on database to ; -``` -### Clone and Install the Frontend - Head on over to https://github.com/Giveth/giveth-next, and clone the repo. - - *via SSH on the CLI:* - ```bash - git clone git@github.com:Giveth/giveth-next.git - cd giveth-next - yarn install - ``` - -### Get the Environment Variables - In order to run the local build for Giveth.io you'll need to ask for the environment variables. Head on over to our [Contributors Discord](https://discord.giveth.io), say Hi and get in touch with our product manager, @MoeNick or one of the developers. - - -### Launch the Development Server and Environment - Start up the `impact-graph` backend server and redis. - - Run redis by using the command `redis-server`. - - From the impact-graph repo start with `npm start`. - - :::info - ### Using the Staging Database for Development - If you don't need to setup a local database for your development purposes you can use the staging database instead. Set `NEXT_PUBLIC_APOLLO_SERVER` to `https://serve.giveth.io/graphql` (this uses the same database you see on https://next.giveth.io). - ::: - - -### Run the Migrations to Setup the Database -In a separate terminal `cd` into the `impact-graph` -run this command in the terminal: -```bash -npm run typeorm:cli -- migration:run -``` - -### Deploy the Front-end - To take advantage of linting presets, please use **VSCODE**: - * Select *File -> Open Workspace*. - * Navigate into the giveth-next directory. - * Open the workspace file `giveth2-full-stack.code-workspace`. - * Install recommended extensions (Prettier and StandardJS plugins). - * Then fire up the front-end locally. - - ```bash - yarn run dev - ``` - -### Start Editing! - -Open up the giveth-next repo on your code editor. - -Giveth.io is now running locally at `http://localhost:8000`! - -Giveth Running Locally - -You can also expiremnt with querying your data via GraphQL. You'll find it at this link here: `http://localhost:8000/___graphql` -Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.org/tutorial/part-five/#introducing-graphiql). - - Save your changes, and the browser will update in real time! - -**Current Build Statuses** - -[master](https://giveth.io) - -[![Netlify Status](https://api.netlify.com/api/v1/badges/f914ac7e-ce27-4909-bd3e-14d749731a52/deploy-status)](https://app.netlify.com/sites/giveth2/deploys) - -[staging](https://next.giveth.io) - -[![Netlify Status](https://api.netlify.com/api/v1/badges/2f325b5b-e159-443e-bac7-c5e15f3578c0/deploy-status)](https://app.netlify.com/sites/giveth-website-staging/deploys) -
diff --git a/i18n/pt/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md b/i18n/pt/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md index 54f66d034..dfb77bc24 100644 --- a/i18n/pt/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md +++ b/i18n/pt/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md @@ -6,25 +6,24 @@ import NotTranslatedMessage from '../../_notTranslatedPT.mdx' -Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by subDAOs & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) +Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by Working Groups & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) -# subDAOs -The Giveth DAO is divided into smaller subDAOs or Working Groups (WG), each subDAO is responsible for managing it's own budget, goals and contributors, each subDAO also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the subDAO but also that they serve the [Giveth Mission](/whatisgiveth#our-mission). subDAOs are financially beholden to the DAO in that they must present a budget every 3 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). +# Working Groups +The Giveth DAO is divided into smaller Working Groups (WG), each Working Group is responsible for managing it's own budget, goals and contributors, each Working Group also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the Working Group but also that they serve the [Giveth Mission](./#our-mission). Working Groups are financially beholden to the DAO in that they must present a budget every 3-4 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). -SubDAOs are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. +Working Groups are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. -Giveth currently has 5 subDAOs in operation, they are: +Giveth currently has 5 Working Groups in operation, they are: -- [Communitas](https://forum.giveth.io/t/communitas-working-group-proposal/1107) -- [Dapp](https://forum.giveth.io/t/dapp-working-group-proposal/1146) -- [GIVeconomy](https://forum.giveth.io/t/giveconomy-working-group-proposal/1121) -- [Rewards](https://forum.giveth.io/t/rewards-working-group-proposal/1116) -- [DAO Ops](https://forum.giveth.io/t/dao-ops-working-group-proposal/1115) -- [Quadratic Funding](https://forum.giveth.io/t/quadratic-funding-qf-working-group-proposal/1120) +- [Dapp](https://forum.giveth.io/c/dapp-wg/18) +- [GIVeconomy](https://forum.giveth.io/c/giveconomy-wg/19) +- [DAO Ops](https://forum.giveth.io/c/dao-ops-wg/20) +- [Quadratic Funding](https://forum.giveth.io/c/qf-wg/22) +- [Fundraising](https://forum.giveth.io/c/fundraising/25) You can learn more about each by clicking any of the links above leading to their Working Group Proposal on the Giveth Forum. -Anyone can propose a new subDAO to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. +Anyone can propose a new Working Group to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. # Chapters @@ -42,7 +41,3 @@ These are the current Chapters in Giveth: To learn more about Chapters, join the [Giveth Discord](https://discord.giveth.io) and introduce yourself! -# Other DAO Stuff - -Giveth also uses other tools like Gnosis Safes and Aragon DAOs that are managed by either certain working groups or specific trusted contributors, as well as the [GIVgarden](../giveconomy/givgarden) for funding community initiatives. - diff --git a/i18n/tr/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md b/i18n/tr/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md index b7f3c82d3..707e12e26 100644 --- a/i18n/tr/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md +++ b/i18n/tr/docusaurus-plugin-content-docs-whatisgiveth/current/daoStructure.md @@ -6,25 +6,24 @@ import NotTranslatedMessage from '../../_notTranslatedTR.mdx' -Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by subDAOs & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) +Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by Working Groups & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) -# subDAOs -The Giveth DAO is divided into smaller subDAOs or Working Groups (WG), each subDAO is responsible for managing it's own budget, goals and contributors, each subDAO also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the subDAO but also that they serve the [Giveth Mission](/whatisgiveth#our-mission). subDAOs are financially beholden to the DAO in that they must present a budget every 3 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). +# Working Groups +The Giveth DAO is divided into smaller Working Groups (WG), each Working Group is responsible for managing it's own budget, goals and contributors, each Working Group also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the Working Group but also that they serve the [Giveth Mission](./#our-mission). Working Groups are financially beholden to the DAO in that they must present a budget every 3-4 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). -SubDAOs are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. +Working Groups are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. -Giveth currently has 5 subDAOs in operation, they are: +Giveth currently has 5 Working Groups in operation, they are: -- [Communitas](https://forum.giveth.io/t/communitas-working-group-proposal/1107) -- [Dapp](https://forum.giveth.io/t/dapp-working-group-proposal/1146) -- [GIVeconomy](https://forum.giveth.io/t/giveconomy-working-group-proposal/1121) -- [Rewards](https://forum.giveth.io/t/rewards-working-group-proposal/1116) -- [DAO Ops](https://forum.giveth.io/t/dao-ops-working-group-proposal/1115) -- [Quadratic Funding](https://forum.giveth.io/t/quadratic-funding-qf-working-group-proposal/1120) +- [Dapp](https://forum.giveth.io/c/dapp-wg/18) +- [GIVeconomy](https://forum.giveth.io/c/giveconomy-wg/19) +- [DAO Ops](https://forum.giveth.io/c/dao-ops-wg/20) +- [Quadratic Funding](https://forum.giveth.io/c/qf-wg/22) +- [Fundraising](https://forum.giveth.io/c/fundraising/25) You can learn more about each by clicking any of the links above leading to their Working Group Proposal on the Giveth Forum. -Anyone can propose a new subDAO to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. +Anyone can propose a new Working Group to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. # Chapters @@ -42,7 +41,3 @@ These are the current Chapters in Giveth: To learn more about Chapters, join the [Giveth Discord](https://discord.giveth.io) and introduce yourself! -# Other DAO Stuff - -Giveth also uses other tools like Gnosis Safes and Aragon DAOs that are managed by either certain working groups or specific trusted contributors, as well as the [GIVgarden](../giveconomy/givgarden) for funding community initiatives. - diff --git a/sidebarsDapps.js b/sidebarsDapps.js index 9b0825f34..98a5c048e 100644 --- a/sidebarsDapps.js +++ b/sidebarsDapps.js @@ -9,58 +9,78 @@ module.exports = { description: 'Learn more about how the Giveth Dapp works. We have a variety of articles tailored for Donors, Project Owners and how to use the GIV token.', slug: 'dapps/' }, - items: [ + items:[ 'givethIO', 'gettingStarted', - { - type: 'category', - label: 'For Donors', - collapsed: true, - link: { type: 'doc', id: 'projectdonating' }, - items: ['projectdonating', 'donatingmetamask', 'multisigs', 'importTorusMM' + { + type: 'category', + label: 'For Donors', + collapsed: true, + link: {type: 'doc', id: 'projectdonating'}, + items: ['projectdonating', 'donatingmetamask' ,'multisigs', 'importTorusMM' ], - }, - { - type: 'category', - label: 'For Project Owners', - collapsed: true, - link: { type: 'doc', id: 'createproject' }, - items: ['createproject', 'listedUnlisted', 'projectVerification', 'projectUpdates', + }, + { + type: 'category', + label: 'For Project Owners', + collapsed: true, + link: {type: 'doc', id: 'createproject'}, + items: ['createproject','listedUnlisted','projectVerification', 'projectUpdates', ], - }, - { - type: 'category', + }, + { type: 'category', label: 'GIVeconomy', - link: { type: 'doc', id: 'giveconomy' }, - items: ['givbacks', 'givstream', 'givpower', - { - type: 'category', - label: 'GIVgarden', - link: { type: 'doc', id: 'givgarden' }, - items: ['termsForProposals'] - }, - { - type: 'category', - label: 'GIVfarm', - link: { type: 'doc', id: 'givfarm' }, - items: ['regenFarms', 'angelVault'] - } - , 'givdrop' - ] - }, - 'recurringDonation', 'quadraticfunding', 'giverspfp', 'niceToken' + link: {type: 'doc', id: 'giveconomy'}, + items: [ 'givbacks', 'givstream', 'givpower', + { + type: 'category', + label: 'GIVgarden', + link: {type: 'doc', id: 'givgarden'}, + items:['termsForProposals'] + }, + { + type: 'category', + label: 'GIVfarm', + link: {type: 'doc', id: 'givfarm'}, + items:['regenFarms'] + } + , 'givdrop' +] + }, + 'recurringDonation','quadraticfunding','giverspfp' + + + , + 'disclosure', + 'troubleshooting', + // { + // type: 'category', + // label: "Developer Guides", + // items: [ 'contributors','givethioinstallation' , { + // type: 'category', + // label: "Giveth TRACE (Deprecated)", + // items: ['TRACEinstallation','bridgeSecurity', 'developmentProcess'] + // }, + // 'regenFarmContracts' + // ] + // }, + { + type: 'category', + label: 'Archives', + items: [ + { + type: 'category', + label: 'Giveth TRACE (Deprecated)', + link: {type: 'doc', id:'introTrace'}, + items: [ 'entitiesAndRoles','makeTraceableProject','leavingTraces', 'technicalWhitePaper', 'exchangeRates', 'traceContracts' ] + },'niceToken', 'angelVault', + ] + }, + + + ], - , - 'disclosure', - 'troubleshooting', - { - type: 'category', - label: 'Giveth TRACE (Deprecated)', - link: { type: 'doc', id: 'introTrace' }, - items: ['entitiesAndRoles', 'makeTraceableProject', 'leavingTraces', 'technicalWhitePaper', 'exchangeRates', 'traceContracts'] - }, - ], - }, - ] -} + }, +] + } \ No newline at end of file diff --git a/sidebarsWhatisgiveth.js b/sidebarsWhatisgiveth.js index e3568920a..36f5aa4b0 100644 --- a/sidebarsWhatisgiveth.js +++ b/sidebarsWhatisgiveth.js @@ -1,11 +1,11 @@ module.exports = { whatisgiveth: [ - 'whatisgiveth','zero-fees', 'covenant','codeofconduct','daoStructure','governanceProcess','communityCommsGuide', 'conflictResolution','externalContributors', + 'whatisgiveth','zero-fees', 'covenant','codeofconduct','daoStructure','governanceProcess','communityCommsGuide', { type: 'category', label:'Guides', - items:['fundraisingGuide','meetingsGuide','adviceProcess', 'introDiscord','brandBook'] + items:['fundraisingGuide','adviceProcess','brandBook'] }, - , 'toolsDecentralizedCommunities','history' + ,'history' ], } diff --git a/whatisgiveth/conflictResolution.md b/whatisgiveth/conflictResolution.md deleted file mode 100644 index 1eb992bb7..000000000 --- a/whatisgiveth/conflictResolution.md +++ /dev/null @@ -1,86 +0,0 @@ ---- -id: conflictResolution -title: Conflict Resolution Working Group ---- - -# Conflict Resolution Working Group - -A working group of Gravitons who implement Gravity and provide education and support around conscious communication, empathic listening, and issue revelation and alleviation. - -We aim to bring people together and promote resilience in the Giveth DAO by training our members in non-violent communication, understanding and analyzing conflict and techniques to manage it (internally, individually and collectively). The mission is to help build a culture of wellbeing and high vibes, while also pointing out clear steps to strategically manage disputes whenever they arise. - - -### What is Gravity? - -Gravity aims to establish a culture of voluntary compliance around Giveth’s [Community Covenant](https://docs.giveth.io/whatisgiveth/covenant), [Code of Conduct](https://docs.giveth.io/whatisgiveth/codeofconduct), and [Community Communications Guide](https://docs.giveth.io/whatisgiveth/communityCommsGuide). It proposes the recognition and application of conflict management mechanisms to shape harmonious interactions between the members of its community. - - -### What is a Giveth Graviton? - -* Someone enthusiastic about conscious communication, conflict resolution, authentic relating and connection -* Has completed Gravity’s Graviton training -* Contributes to the Giveth Conflict Resolution working group -* A point of contact for reporting conflicts in Giveth -* Gathers information to develop cases and activities -* Delegates conflict mediation cases to other Gravitons -* Provides inter-Graviton support -* Promotes conscious communication strategies for Gravity & Giveth -* Fosters Gravity from their active participation in other working groups within Giveth - - -### Who are the Giveth Gravitons? - -@Forest Soleil is leading the Conflict Resolution working group at Giveth with support from @Juan Carlos Bell Llinás and @bends#3537 at Gravity. - -_Trained & Actively contributing—_ - -Forest (Active Graviton; Conflict Mediator) - -Ben (Gravity Support) - -Juanka (Active Graviton; Conflict Mediator; Gravity Support) - -_Givethers who also completed the Graviton training—_ - -Mateo - -Griff - -Ashley - -Lauren - -Suga - -👉🏼 DM @Juan Carlos Bell Llinás if you are interested in joining. - -The training is offered twice or more per year with the intention of forming Gravitons: a team of individuals equipped with knowledge and social tooling to address and mediate emerging conflicts or any uncomfortable situations in the best way possible. - - -### Main Actions - -* Everyone in the community can fill the Gravity [typeform](https://the-commons-stack.typeform.com/to/rCVsK5RK) _(currently utilizing the Gravity form, but plan to create a unique one for Giveth)_ or approach any of the Gravitons to request support for conflicts and any sort of uncomfortable or undesired situations. -* In case of conflict, Gravitons can approach the parties involved to collect information on the issues. -* Gravitons can take actions to [regulate unwanted behavior according to the graduated sanctions](https://forum.tecommons.org/t/scale-of-conflicts-graduated-sanction-guideline/234) _(Giveth Conflict Resolution Working Group is currently utilizing TEC Gravity’s graduated sanctions while concurrently meeting to adapt our own)._ -* All community members can propose new methodologies to approach **graduated sanctions** and **mutual monitoring** as well as upgrade current ones through [Advice Process](https://token-engineering-commons.gitbook.io/tec-handbook/tec-agreements-1/collective-agreements/advice-process) and [Forum Voting](https://forum.giveth.io/). -* Gravitons can submit conflicts or issues to the Gravity Registry, that is a database of the cases managed by Gravity. -* Conflict resolution calls and chats are closed to Gravitons and parties involved to respect privacy and vulnerability. -* The Giveth Conflict Resolution working group can facilitate safe spaces, skills up leveling workshops, and collaborate with TEC’s Gravity working group to host training and capacitate individuals to become Gravitons. - * The Gravity training is free and open for all. -* Gravity can remove proposals from all the voting categories if they receive **flags** and/or are seen as harmful for the community based on our rules, boundaries, T&C’s, [Community Covenant](https://docs.giveth.io/whatisgiveth/covenant),[ Code of Conduct](https://docs.giveth.io/whatisgiveth/codeofconduct), and [Community Communications Guide](https://docs.giveth.io/whatisgiveth/communityCommsGuide). - -**What actions or outcomes are required or encouraged?** - -* All members should be aware of the [guidelines for scale of conflict and graduated sanctions](https://forum.tecommons.org/t/scale-of-conflicts-graduated-sanction-guideline/234). -* All members should commit to respect the protocol for [Giveth Meetings](https://docs.giveth.io/whatisgiveth/meetingsGuide). -* Gravitons should comply to Giveth’s [Community Covenant](https://docs.giveth.io/whatisgiveth/covenant), [Code of Conduct](https://docs.giveth.io/whatisgiveth/codeofconduct), and [Community Communications Guide](https://docs.giveth.io/whatisgiveth/communityCommsGuide) and the additional [Graviton Code of Conduct](https://forum.tecommons.org/t/gravity-role-design/174). -* Gravitons should accept cases based on their competence and communicate to the Conflict Resolution working group if they don’t feel capable of handling an issue. -* Gravitons should promote trust and good relationships between the community. -* It is required to complete the Graviton Training successfully to become a Graviton. -* Gravitons should update the Gravity Registry with the information of possible agreements or the final resolutions. -* All members should respect the arrangements made about the situations issued. - -**What actions or outcomes are discouraged?** - -* Violating the agreements stated in this working group’s documentation on this page. -* Violating the requirements for the Graviton Role (Any member can monitor Gravitons actions and report to other Gravitons, fill in the typeform, or contact community stewards.) diff --git a/whatisgiveth/daoStructure.md b/whatisgiveth/daoStructure.md index 1568537a3..30aa00283 100644 --- a/whatisgiveth/daoStructure.md +++ b/whatisgiveth/daoStructure.md @@ -2,24 +2,24 @@ id: daoStructure title: DAO Structure --- -Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by subDAOs & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) +Giveth actively experiments with different organizational structures and governance models. We currently divide our contributors and work done by Working Groups & Chapters. To learn more about specific governance processes, [read here](./governanceProcess) -# subDAOs -The Giveth DAO is divided into smaller subDAOs or Working Groups (WG), each subDAO is responsible for managing it's own budget, goals and contributors, each subDAO also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the subDAO but also that they serve the [Giveth Mission](./#our-mission). subDAOs are financially beholden to the DAO in that they must present a budget every 3 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). +# Working Groups +The Giveth DAO is divided into smaller Working Groups (WG), each Working Group is responsible for managing it's own budget, goals and contributors, each Working Group also has a leader that carries the flag and ensure all of their contributors work towards not only the goals of the Working Group but also that they serve the [Giveth Mission](./#our-mission). Working Groups are financially beholden to the DAO in that they must present a budget every 3-4 months (Seasons) along with the goals they are hoping to achieve by the end of each Season. Budget proposals follow standard giveth [Advice Process](./adviceProcess) and subsequent voting on [Snapshot](./governanceProcess#snapshot-voting). -SubDAOs are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. +Working Groups are based around different products and programs and can have a wide range of contributors from developers, designers, community managers, marketers, etc. -Giveth currently has 5 subDAOs in operation, they are: +Giveth currently has 5 Working Groups in operation, they are: -- [Dapp](https://forum.giveth.io/t/dapp-working-group-proposal/1146) -- [GIVeconomy](https://forum.giveth.io/t/giveconomy-working-group-proposal/1121) -- [DAO Ops](https://forum.giveth.io/t/dao-ops-working-group-proposal/1115) -- [Quadratic Funding](https://forum.giveth.io/t/quadratic-funding-qf-working-group-proposal/1120) -- Fundraising - TBA +- [Dapp](https://forum.giveth.io/c/dapp-wg/18) +- [GIVeconomy](https://forum.giveth.io/c/giveconomy-wg/19) +- [DAO Ops](https://forum.giveth.io/c/dao-ops-wg/20) +- [Quadratic Funding](https://forum.giveth.io/c/qf-wg/22) +- [Fundraising](https://forum.giveth.io/c/fundraising/25) You can learn more about each by clicking any of the links above leading to their Working Group Proposal on the Giveth Forum. -Anyone can propose a new subDAO to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. +Anyone can propose a new Working Group to Giveth but they must create a proposal following roughly the format of the above proposals and submit it to the [Giveth Forum](https://forum.giveth.io/c/wgp/17) where other community members will comment and eventually vote on the proposal. # Chapters diff --git a/whatisgiveth/externalContributors.md b/whatisgiveth/externalContributors.md deleted file mode 100644 index c109935ba..000000000 --- a/whatisgiveth/externalContributors.md +++ /dev/null @@ -1,50 +0,0 @@ ---- -id: externalContributors -title: Working with Giveth as an External Collaborator ---- - -**Hey buidler!** - -We are stoked that you are interested in helping us buidl the Future of Giving. This short doc will give you the tips and tricks to work effectively with Giveth. - -If you don’t here are a few ways to get inspired: - - -* Check out the [ideas Channel on Discord](https://discord.com/channels/679428761438912522/689535474532221030). -* Have a look at our [Dework board](https://app.dework.xyz/test-120/giveth-dapps-v2/view/board-5901) (alpha version) and [community suggestions](https://app.dework.xyz/test-120/giveth-dapps-v2/community). -* Find issues suggested in [Tokenlog.](https://tokenlog.xyz/giveth/roadmap) -* Go to [meetings](https://calendar.google.com/calendar/u/1?cid=Z2l2ZXRoZG90aW9AZ21haWwuY29t) & ask around on Discord. - -Once you have an idea, contributing to Giveth is as easy as 1-2-3! Here’s what to do: - - - -### 1. Create a proposal - -Anyone is welcome to create a proposal on [Giveth’s Forum](https://forum.giveth.io/). Proposals can be very detailed or intentionally broad to get some feedback and polish the details in the advice process. Here is a [proposal template](https://forum.giveth.io/t/proposal-template/303) to help you rock this step. If you are not that comfortable writing a proposal in the forum yet, you can go to the [collab chat channe](https://discord.com/channels/679428761438912522/990973636603179079)l on Discord to get advice or join the AMA community orientation call (Wednesdays at 10 am CST). - - - -### 2. Get signaling and feedback - -Your proposal must be active in the forum for 5 days for the “[advice process](./adviceProcess.md#the-advice-process-flow)”. Signaling for support or specific details on the proposal can be achieved by inserting polls into the proposals. It’s strongly recommended to seek community engagement. To that end, you might consider using the following: - - - -* Giveth Discord channels -* GIVernance meeting - where our governance working group discusses active proposals in the forum (Mondays at 9 am CST). - -### 3. Final decision - -After the 5-day advice process, the proposal can be updated using the collected feedback & moved to the voting phase. When the proposal doesn’t require a budget, it should be posted and voted on [Giveth Snapshot](http://snapshot.org/#/giv.eth/). - -Don’t forget to post a link to the Snapshot vote on the original Forum post. To learn more about these voting apps & their requirements, check out our [documentation](./governanceProcess.md). - - -:::tip -* Ask for help. Giveth Discord is full of people who want to help! -* If the proposal requires funding, be clear about how you will use the funds. -* If you are unfamiliar with Giveth processes or the Giveth Dapp, try to find a champion who can help you understand how to create more value for Giveth (@Cotabe#4096 supports external collaborators). -::: - -Good! Now you know what’s the best way to work with Giveth as an external collaborator, it would be awesome to join us in the journey of Building the Future of Giving. \ No newline at end of file diff --git a/whatisgiveth/introCommunity.md b/whatisgiveth/introCommunity.md deleted file mode 100644 index b5def578e..000000000 --- a/whatisgiveth/introCommunity.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -id: introCommunity -title: Community ---- - -**COMMUNITY…** has always been the foundation of Giveth, the sum of all parts. - -**COMMUNICATION…** is the glue that holds these parts together. - -**COMMONS…** is the publicly accessible resources that are shared, cultivated and managed together. - -## Welcome to the Giveth Community Circle! - -This circle is held down by the Communications team yet comprised of representatives from the other two Circles, as well as various working groups that may form. Here is where new contributors, project owners, campaign managers, collaborators, conspirateurs, catalysts and really all the cool cats come to play, learn, give and grow. - -## Mission - -Our mission is to be the living and breathing core of Giveth, an ecosystem of collective support, abundance and communication where we cultivate relationships and assist innovative projects with a focus on blockchain4good. We connect Givers and Makers with the Giveth Community through transparent, intentionally crafted and clearly communicated stories and resources. - -## Goals - -* **Build Community around For-Good Projects** by nourishing relations between Givers, Makers and the greater community through meaningful engagement, outreach, trust facilitation and conflict resolution - creating a safe space for community members to communicate their passion projects, then recruit help or guidance from peers. -* **Offer a Clear & Supportive Onboarding Process** as Giveth develops the Dapps, economy, DAO and ongoing new features. The community circle provides a well-defined, transparent and helpful onboarding process that supports the needs of Contributors, Communities, Campaigns, Projects and Donors as well as functions as a bridge for newcomers into the crypto space. -* **Coordinate External and Internal Communications** when broadcasting or sharing activity and development progress externally through the Giveth channels and social media - ensuring that the voice of Giveth as an organization is aligned with our overarching Values, Vision, Mission and Goals and that all Giveth Circles are represented. -* **Create a Network of Partners** by way of collaboration, relationship building and support of common goals with various strategic partner organizations as well as community members focused on blockchain4good and improving the ethereum commons - providing resources, education and sharing of best practices. -*Partners currently include communities like [Commons Stack](https://commonsstack.org/), [TEC](https://forum.tecommons.org/), [DAppNode](https://dappnode.io/), [BrightID](https://www.brightid.org/), [1Hive](https://about.1hive.org/), [Panvala](https://panvala.com/), [GitCoin](https://gitcoin.co/) and [MetaGame](https://wiki.metagame.wtf/).* - -## How to Engage - -* Community Calls are held every Thurday in the appropriate voice channel in the [Discord server](https://discord.gg/DAFkKdkykr) and can be found scheduled on the [Giveth calendar](https://calendar.google.com/calendar/u/0/embed?src=givethdotio@gmail.com&ctz=America/Costa_Rica). Feel free to join us! -* If you want to get a feel of what we discuss during the Community Call, most of the recordings can be found on our [Giveth Transparency YouTube channel](https://www.youtube.com/channel/UCdqmP4axeI1hNmX20aZsOwg). -* You can read more on all of our initiatives on our [Medium blog](https://medium.com/giveth/) as well as engage with releveant topics and proposals on the [Giveth Forum](https://forum.giveth.io/). -* If you have any questions or are interested in contributing, feel free to reach out in the Discord server or [Telegram chat](https://t.me/Givethio). diff --git a/whatisgiveth/introDiscord.md b/whatisgiveth/introDiscord.md deleted file mode 100644 index 13908af5f..000000000 --- a/whatisgiveth/introDiscord.md +++ /dev/null @@ -1,234 +0,0 @@ ---- -id: introDiscord -title: Discord Introduction and Tutorial ---- - -If you haven’t used Discord before, fear not! Use this guide to help you get started - enjoy the journey and discover welcoming spaces and channels that spark your interest. So, if you’re ready to dive in, here’s a brief introduction to get you started. - - -## Links -Onboarding site - https://giveth.io/join - -Direct link to join Discord community - https://discord.giveth.io/ - -## How to join the Giveth Discord server - -Log in to Discord or make a new user. - https://discord.com/ or download the app ([iOS](https://apps.apple.com/us/app/discord-talk-chat-hang-out/id985746746), [Android](https://play.google.com/store/apps/details?id=com.discord&hl=en_CA&gl=US)) - -[How to Use Discord](https://support.discord.com/hc/en-us/articles/360045138571-Beginner-s-Guide-to-Discord) : Video ([Beginner to Advanced](https://www.youtube.com/watch?v=tNUq5Aqv60s)) - -[Getting Started with Discord](https://support.discord.com/hc/en-us/articles/360033931551-Getting-Started) - -Join the Giveth community server https://discord.giveth.io/ -Inside each server, you can have a unique nickname so feel free to change yours to whatever you would like to be known as. - -Once you have joined the server, a bot will send you a message with a Captcha to solve - you're not a robot are you? It should look something like this: - -![](https://i.imgur.com/XCaAhgo.png) - - -## Channel Descriptions - -### Welcome (start here) -**`#🤝welcome`** is our landing channel and contains tips to get you started, including links and basic faqs. -**`#👋say-hi`** to the community and tell us what you're working on, what brought you here or what you need help with. -**`#✋assign-roles`** allows you to assign yourself to roles, which automatically opens the relevant channels and gets you tagged in working-group related posts. - - -### Notice Board -**`#📢announcements`** is where you will find announcements from the Giveth community. -**`#📅event-calendar`** weekly and regular meetings and events are listed here in your local time. You can click to add events to your Google calendar. -**`#📌team availability`** accessible to team members only - the place where you can find who is on vacation or not available. Let us know when you are on vacation or not available, so we don’t bug you when you’re AFK. -**`#📋help wanted`** if you’re interested in joining Giveth and our greater contributor Galaxy - connect here to learn about open job positions. -**`#📚partner-updates`** is where you will find announcements from our Galaxy partners. - - -### Support -**`#💬support`** if you run into any problems, or need to ask a general question, post it here; please tag @admin or @support. Don’t forget to search the channel to see if there is already info on that topic. - -Hop over to any of these channels if your question relates to any of the following: - -- project-onboarding -- project-verification -- givbacks -- faq (in MAKER and GIVER channels) -- using-crypto channels if your question relates to any of these topics. - -**`#🤝project-onboarding`** is where prospective project owners can go for suggestions or advice about the project creation flow and how to create engaging and impressive projects on the DApp. -**`#⭐project-verification`** channel is where the Project Verification Team collaborates to review new applications and nominations for future verification invites. - - -### Community -**`#😄 communitas-headquarters`** a place of new ideas, initiatives and co-creation to make Giveth Community a better place for every member. -**`#🙂 daily happiness`** share what makes you happy. -**`#❤ praise`** rain praise upon your teammates! Let them know that you recognize the value they add to the various Giveth projects and community by typing "/praise '@username' for 'awesome thing that they did'" and ensure they get rewarded with GIV tokens for their contribution to the community. Follow Praise Bot’s instructions to activate your Praise account (you will need to connect your ETH wallet) and start collecting your rewards when someone /praises you. -**`# general`** for when your post doesn’t seem to fit nicely into one of our channels? Jump into the General channel and let us know what’s on your mind. We can chat there or guide you to a channel that fits. -**`#💡 ideas`** is a place for you to share inspirating and creative suggestions. -**`#✨ shtsnggls`** is for pure fun. -**`#🐦 tweeeeeter`** is where you will find all things related to the Giveth Twitter. It can be used for suggesting or drafting tweets, feedback regarding Twitter and sharing or promoting tweets to get more engagement. Please ask to become part of our Tweeeeter team to amplify Giveth message on Twitter using our Tweet bot. -**`#🐸 memes`** are powerful! We host weekly meme parties where we listen to music and pump out spicy memes. The schedule can be found in the [calendar](https://calendar.google.com/calendar/u/0/embed?src=givethdotio@gmail.com&ctz=America/Costa_Rica). -**`#💸 shill-your-project`** share info about your project, join discussions and expand fundraising frontiers in support of fulfilling Giveth's mission. -**`#➿ feedback`** through Typeform collected on the platform (giveth.io) is displayed in this channel. - - -### Global -**`#🌎 latam`** -**`# PT português`** -**`# ES español-spanish`** - - -### Collaborator Space -**`#🥇 bounties`** view tasks and apply for bounties in this channel. Click on each task to discover what’s required, what skills are needed, rewards offered, how to apply and the status. -**`#🤝 partner-threads`** -**`#💬 collab-chat`** want to collaborate with Giveth? Have a proposal? Head to the collab-chat channel and we’ll let you know the next steps. - - -### Giver Space -**`#❔faq`** -**`#👣 project-activity`** -**`#🎁 givbacks`** go here if you want to keep up-to-date with GIVback rounds, distributions and support? -**`#💬 giver-chat`** is a great space for givers to talk about projects they support and causes they are interested in. - - -### Maker Space -**`#❓ faq`** -**`#🧮 fundraising-101`** share tips and learn about fundraising in crypto. -**`#💱 using-crypto`** this channel is for sharing info and support on all the different ways to access and use your crypto donations. -**`#💬 maker-chat`** this channel is a great space for makers to network with other makers. - - -### Communications -**`#📣 communications`** hub of the Communications Team. You can find us here creating content, performing outreach and all things that are included in the Communications Circle. If you need the attention of the team, you can tag @Comms Stars in your message. -**`#🗒 docs`** let's talk about Giveth docs! -**`#🖋 docs-translations`** - - -### GIVernance -**`#🌐 dao`** provides links to DAO proposals and informs the community when it's time to vote. You can discuss anything proposal-related in this channel. -**`#👍 governance`** is where we experiment with decentralized governance and document anything that could be useful for future communities like ours. -**`#🔑 multisigs`** channel is for the operators and signatories on the Giveth multisigs. -**`# giveth-trace-payments`** is used to communicate information about payment transactions happening on the Giveth TRACE bridge. You can find more information about how the bridge works [here](https://docs.giveth.io/dapps/bridgeSecurity). -**`#🏆 rewards`** is where the rewards team hang-out. - - -### Devs -**`#👌 all-dev`** is the channel for general development discussions that include the Giveth Development Team as a whole. -**`#☝ givethtrace-dev`** is the hub of communications for the Giveth TRACE DApp Development Team. -**`#🐇 test-reports`** is for test reports and testing communication for both Giveth DApps. - - -### Design -**`#🌈 design`** is for design idea sharing and creative activity on the look, feel and language of any UI or UX updates in the pipeline for Giveth products. - - -### GIVeconomy -**`#💹 giv-economy`** is the place to share information about about Giveth tokenomics and its continuous evolution. -**`#🧲 giveth-fundraising`** is where the fundraising team hang-out. -**`#🔬 givbacks-distribution`** is where the GIVbacks review team hang-out and post GIVback distribution voting links are posted. - - -### Operations -**`#🚨 raise-incident`** A message sent in this channel will trigger automated incident management - be careful, you might wake somebody :) -**`#❔ incident-status`** -**`# ops`** - - -### Bridges -**`#🐝 1hive`** serves as bridge channel to our busy bee neighbors at [1Hive](https://about.1hive.org/). -**`#🌐 te-commons`** links the Giveth server to the vast community of token engineers over at the [TEC](https://tecommons.org). -**`#🐙 metagame`** bridges to a channel in the [Metagame](https://about.1hive.org/) discord server. -**`#✨ general-magic`** allows our server to be connected to our friends at [Panvala](https://panvala.com/). - - -### Monitoring -**`# devops-monitoring`** -**`# github-log`** is to cross notify pull requests and new Issues in Github in order to increase transparency, and engagement on Github. -**`# giveth-io-event-log`** is used as a log for Segment events that are tracked on Giveth.io. -**`# segment-dev`** relays events from dev environments. - - -### Server Stats -**`# daily-stats`** - - -### Voice Channels -These channels are used for voice and / or video chats with community members. - -**`#chip-playlist`** is a text channel used for typing Chip Bot commands. (More about bot commands **below**) -**`Community`** is used as a meeting place for the Community Circle working groups as well as weekly Community Calls. -**`🦄-only`** is used as a meeting place for Giveth core-team members. -**`Communications`** is where the Communications Team gathers for weekly syncs and hack sessions. -**`DAO only`** -**`Developers`** is a meeting place for the Platform Circle working groups. -**`Governance`** is the voice channel for our weekly Governance and DAO working group discussions. -**`GIVeconomy`** is where GIVeconomy working groups gather for weekly syncs and hack sessions. - -**All meeting times can be found on the [Giveth Calendar](https://calendar.google.com/calendar/u/0/embed?src=givethdotio@gmail.com&ctz=America/Costa_Rica).* - -### Tagging -You can tag certain roles by using "@" followed by the role. You also can tag an individual with "@" followed by the person's handle or nickname. - -#### Roles - -### Roles that can be self-assigned in the "assign-roles" channel -**@Giver** People who love funding for-good projects. You can assign yourself this role in the `#🤝welcome` channel by reacting to the bot message with the 💝 emoji. -**@Maker** People who are working hard to make the world a better place. This role can also be self assigned in the `#🤝welcome` channel by reacting to the bot message with a 🦄 emoji. -**@Collborator** People who want to collaborate or complete bounties. -**@Community Circle** People who want to get involved with our community. -**@Givernance Circle** People who are interested in discovering more about Giveth governance. -**@Platform Circle** People who are interested in the development of the Giveth platform. - -**@Unicorn** - People who regularly attend calls and are very actively contributing to Giveth. -**@DAO** - rGIV token holders. You can obtain rGIV tokens by consistently contributing to the community. -**@Comms Stars** - Communications Team members. -**@Community Support** - Members of the Community Support working group. -**@Governance** - Members of the Governance wroking group. -**@Design** - Members of the Design working group. - -### Bot Commands - -#### PraiseBot -At Giveth, we love to acknowledge the value that each member brings to the community and provide recognition for the awesomeness that they contribute. The praise given is tracked by PraiseBot and used to calculate rewards for active contributors. - -You can praise a fellow community member in any channel by typing **`/praise`** followed by "@" and their username. Don't forget to mention why you're praising them. - -**For example:** `/praise @WhyldWanderer for creating such an amazing Discord Guide` :stuck_out_tongue: - -Once you have typed your praise, you will know that the bot has tracked it because a ✅ emoji will appear as a reaction to your message. - -When you receive praise, you will be notified by the bot in your direct messages with a link to the message where you were praised. - - -#### Simple Poll Bot -This bot can be used to create a straw poll such as this one: - -![](https://i.imgur.com/ExLeqzW.png) - - -To create the poll shown above, you would simply type the command as follows: -`/poll "What is the best poll bot?" "Simple Poll" "R2D2"` - -By following this template, you can create as many answers to the question you would like and community members can answer by reacting with the corresponding emoji. -`/poll` `"Question"` `"Answer #1"` `"Answer#2"` `"Answer #3"` ..etc. - -#### Chip Bot - -[Chip bot](https://chipbot.gg/home) can be invited to any of the voice channels on the server. Once you have invited the bot into the channel, anyone can type commands in the **`#chip-playlist`** text channel to start playing or queuing songs. Here is a list of the available commands: - -**`ch!p`** *'`link or search query`'* - Loads your input and adds it to the queue; If there is no playing track, then it will start playing -**`ch!queue`** - Displays the current song queue -**`ch!skip`** - Skips to the next song -**`ch!clear`** - Removes all tracks from the queue -**`ch!skipto`** *'`track position or title`'* - Skips to the specified track -**`ch!lyrics`** - Displays lyrics for the currently playing track -**`ch!pause`** - Pauses playback -**`ch!resume`** - Resumes playback -**`ch!remove`** *'`track position or title`'* - Removes the specified track from the queue -**`ch!stop`** - Disconnects the bot from your voice channel and clears the queue -**`ch!shuffle`** - Randomizes the current order of tracks in the queue -**`ch!nowplaying`** - Displays information about the current playing track. - -Chip bot can play music from a multitude of sources including Spotify, YouTube, Soundcloud, etc. In order to have Chip bot play from Spotify just click on Share > Copy Playlist Link > copy this into your chat with the `ch!p` tag and you’re all set. - -### Support -If you run into any problems, or need to ask a question, please tag `@admin` or ask in the `#💬support` channel. diff --git a/whatisgiveth/meetingsGuide.md b/whatisgiveth/meetingsGuide.md deleted file mode 100644 index eb88499c4..000000000 --- a/whatisgiveth/meetingsGuide.md +++ /dev/null @@ -1,150 +0,0 @@ ---- -id: meetingsGuide -title: Meetings Guide ---- - -## Meeting Planning -* Please announce the meeting a few days in advance. You might want to use the advice process and [Doodle](https://doodle.com/dashboard) to find a date if the meeting is not regular. -* Be sure that there is at least one person taking notes in the meeting. -* Be sure that there will be somebody present who is capable of streaming the meeting. -* We use [Interspace](http://breakout.interspace.chat/) or [Discord](https://discord.gg/cCsYnNDkq2) for our meetings. -* Please don't forget to announce the meeting in the #scheduling channel of Discord before you begin. -* There should always be an introductory round and a closing round. -* After the meeting, please make sure the notes are saved in [Notion](https://www.notion.so/giveth/Giveth-2c97e0eca91e43238565c8f79dfe5e8d), a link to the notes is posted in the #meetingnotes channel of Discord, and the video is published to our [Transparency YouTube channel](https://www.youtube.com/channel/UCdqmP4axeI1hNmX20aZsOwg). - -## Note Taking -* There should be a designated note taker for each meeting. -* We use [Notion](https://www.notion.so/giveth/Giveth-2-0-2c97e0eca91e43238565c8f79dfe5e8d) for record keeping of our meeting notes. - -## Streaming and Video Recording - -We record and/or livestream our online video conferences for record keeping, to support our team and to uphold our values of transparency and accountability. You can find recordings of our meetings on the [Giveth Trasnparency YouTube Channel](https://www.youtube.com/channel/UCdqmP4axeI1hNmX20aZsOwg). - - -#### How to record meetings for Giveth Transparency: - - -* We use OBS to livestream and record our video calls. You can download it [here](https://obsproject.com/). -* During installation select "Optimize for streaming, recording is secondary". -* Select YouTube as the streaming service and input the Giveth Transparency YouTube Stream Key. If you need access to the Stream Key, please ask one of our team members. -* In general, the recommended settings in the setup wizard are already optimized for your device, but feel free to adjust them. -* Setup your video and audio sources; we recommend using Window Capture for streaming calls. -* When you are ready to stream the meeting, select the appropriate window to capture and select "Start Streaming". Your video will be automatically livestreamed on YouTube. -* For a more thorough setup guide, check out [this video](https://www.youtube.com/watch?v=qiRu-NRgso0) from our friends at the Token Engineering Commons (TEC). - -# Governance of Meetings - -*If you are looking for more notes on past Giveth DAC/Community Meetings, you can find this [here](https://wiki.giveth.io/dac/meeting-notes).* - -## Meeting Types & Intentions -Giveth aims to operate meetings that are efficient, connective, fair, transparent and heart-centered. We do this by honoring time and agreements that the collective has agreed to. Some meetings like our weekly Sunday Community Call are intended to deliver updates and highlights so that all circles can understand the latest and greatest of one another, and be in alignment. In our Community Call, the time is not to brainstorm ideas or make decisions but rather to share updates. - -Other meetings, like our weekly Monday Governance Call aka GIVernance, are intended to present proposals and field objections or feed-forward from the group. Besides these larger, recurring group meetings, Contributors can schedule 1 on 1 or small group work sessions to bring a specific task through to completion. These meetings gather necessary participants to focus on a goal and drive it home. - -## Meeting Roles -*There are specific roles to be filled. In general, we use roles to avoid things getting personal. For instance, it is not that Griff is interrupting Dani, but rather that the Facilitator is making sure the Smart Contract Reporter respects the meeting's process.* - -### The Facilitator -The Facilitator needs to stay curious and calm. They make sure the meeting process is RESPECTED at all costs, like a referee. The Facilitator is encouraged to interrupt when people are getting off topic and is discouraged from making extra commentary or from coaching. It is very important that the Facilitator stay neutral. - -The Facilitator holds the space so that people can process their tension on their own and react as they need to express themselves freely in a safe, controlled environment. - - -### The Note Taker -Note taking is important because it allows us to capture meeting highlights in a clear, organized way and store them in Notion, our shared transparent tool. The Facilitator can also be the Note Taker for smaller meetings, but in general it is best if they are 2 different people. - -The most important task is to record the agenda items. Everything else recorded is bonus :-D. The Note Taker has the responsibility the go to the person when there is a conflict interpreting the results of the meeting. - -After the meeting, the Note Taker will share a link to the meeting notes in the #meetingnotes Discord channel. - -### The Livestream Recorder -The Livestream Recorder is in charge of recording and publishing the audio/video recording of the meeting in the Giveth Transparency YouTube channel. In order to properly fulfill this responsibility, it is important that the Livestream Recorder be on time and present for the duration for all meetings that they are responsible for recording to ensure everything is being captured and shared transparently. - -### The Proposer -The Proposer is the person who put a tension on the agenda for the group to discuss. A 'tension' is languaging commonly used in sociocracy and holacracy. When someone has an objection, it's an issue, or tension, that needs to be processed - usually by way of creating or adapting the proposal until the tension is alleviated and the proposal/solution can be passed. - -It is the Proposer's responsibility to propose a solution to the tension and it is their responsibility to make sure that their solution will alleviate the tension. It is NOT their responsibility to solve other people's problems. One tension at a time. - -Don't feel pressured to solve other people's problems with your solution. Everyone is an adult and we need everyone to take care of themselves. That starts with you taking care of your responsibilities. You do not have to take any of the feedback you received. - -### The Reactors -The Reactors are everyone who is not the Proposer during the decision making process. They are encouraged to freely react however they want during the reaction round. - -### The Objector -The Objector needs to stay curious and calm. They are anyone who believes the proposed solution to the Proposer's tension would cause harm or move Giveth backwards. If they have a simple concern about the proposal or think something should be added to the proposal but don't believe the proposal would concretely cause harm or move Giveth backwards, then it is not a valid objection and it should be ruled as an invalid objection by the Facilitator. - -## Sample Meeting Flow - -*A Facilitator and a Note Taker for the meeting should have been chosen ahead of time and once everyone is at the meeting, the meeting can begin.* - -For our GIVernance Call specifically, we follow many of the sociocratic principles. This meeting is structured following the example of governance meetings in sociocracy. - -The purpose of a governance meeting is to: -- Create, remove or modify the Roles of the Circle -- Create, remove or modify the Policies of the Circle -- Elect people to the core roles of the Circle - -Now we will walk through a sample meeting flow and governance process: - -#### 1. *Optional Centering* -The Facilitator may choose to begin the meeting by leading the group through a centering practice to ground everyone's energy and tune into the same frequency. This may look like breathwork, a short meditation or visualization, sharing an inspirational quote or a combo platter. - -#### 2. Check in -Everyone voices what is most alive for them, reveals any momentary personal distractions and states a 30 second or less intention for the meeting. One person speaks at a time. This is not a time for responses or discussion. - -#### 3. Facilitator States Meeting Logistics -A simple space to triage any administrative and logistical issues to take into account for the meeting. E.g., We have 2 hours for the meeting; Jen needs to leave early; this meeting is being live streamed and has 25 viewers so far; we'll be bringing lunch at 1pm; etc. - -#### 4. Building the Agenda -The Faciliator introduces the pre-prepared meeting agenda and then opens the space for additional agenda requests before diving in. Agenda items may be submit ahead of time via Discord, previous meeting discussion and/or curated by the Meeting Facilitator. - -The goal is to build an agenda of tensions, or topics, to process. There is no specific order and anyone can add items to the agenda. The Note Taker captures the agenda items for everyone. The Facilitator will determine the order these agenda items are processed. - -#### 5. Process each agenda item with the Integrative Decision Making process -The Facilitator encourages everyone to take notes and determines the order these agenda items are processed on the fly. - -##### Present Proposal -Either the Meeting Facilitator shares the update/highlight with the group *-or-* the Proposer describes the tension and in one sentence makes a proposal to resolve it. The proposal should in general be a creation of a circle, role or policy. Only the proposer speaks during this time. - -##### Clarifying Questions -All the meeting participants may ask clarifying questions about the tension or proposal to ensure they have a good understanding. The Proposer then has a chance to respond to questions. This is not a space for back and forth discussion. - -It's NOT allowed to use clarifying questions to give an opinion about the proposal. Opinions, suggestions, reactions... all should be left for the Reaction Round coming next. The Facilitator will cut off any question that's conveying an opinion or isn't intended to better understand the proposal. There is no hard line between clarifying question and reaction, and it's at the Facilitator's discretion to discern between the two. - -##### Reactions -One at a time, each person reacts to the proposal as they see fit. No response or interruption is allowed during someone's reaction. Any type of reaction is welcome, from intellectual critiques to emotional outbursts. The only caveat is that reactions should not be engaging someone in particular. Everyone reacts except the Proposer. - -Reactions are the only step of the governance meeting when people can speak freely. It's a perfect phase for providing different perspectives and suggesting improvements to the proposal, so that the Proposer can integrate those changes if he or she likes them. - -This is the dangerous part of this meeting if people want to keep talking and talking… that is ok, and HAS to be allowed. This could make these meetings long. - -##### Amend & Clarify -After all reactions are complete, the Proposer can optionally clarify the intent of the proposal, or amend it based on the reactions. Only the proposer speaks; no discussion allowed. - -Although the proposer can modify the proposal however they want, the goal is for the Proposer to amend their proposal if they found a better way to address their tension. It's not his or her job to address all the concerns and reactions heard during the reaction round, or even to make improvements that were suggested by other participants. - -Watch out for proposal creep. - -##### Objection Round -One at a time, the Facilitator asks each participant if they see "any reason why adopting this proposal would cause harm or move Giveth backwards." The proposer also gets the opportunity to raise an objection. Objections are stated, tested and captured without discussion. One person may have several objections, and everyone's objections must be captured before we move to the next step. - -If there is no objection, the proposal is adopted and we move to the next agenda item. - -The Facilitator will need to test the objection occasionally to determine if the objection is valid or to help the Objector clarify the objection. To test, there are 3 questions to ask: - -* How do you believe adopting this proposal would cause harm or move Giveth backwards? -* Does this objection still exist if this proposal wasn't implemented? -* Is the proposal good enough for now and safe enough to try, knowing we can readdress this later if problems arise? - -##### Integration -If one or several Objections were raised, the Facilitator moves to the Integration step. The goal is to amend the proposal so that it would not cause the Objection, and would still address the proposer's original tension. Objections are integrated one at a time. For each objection, the Facilitator facilitates a discussion to help integrate the objection. Mostly the Objector and the Proposer speak, but others can help as well. The discussion stops as soon as the Objector and the Proposer have both agreed that an amended proposal would not cause an objection while still addressing the Proposer's tension. This is not a place to debate the value of the proposal or the objection! We need to focus on finding an acceptable amendment to the proposal that both the Objector and Proposer agree on. MOVE FORWARD ASAP! - -Once all objections are integrated, go back to an Objection Round to ensure there is no new objection. - -#### 6. Check out -Each person has an opportunity to share a closing reflection on this meeting. No discussion. - -#### 7. Transparency Publishing -The Note Taker posts the meeting notes in the #meetingnotes channel on the Giveth Discord. - -The Livestream Recorder publishes the audio/video recording of the meeting in the Giveth Transparency YouTube channel. diff --git a/whatisgiveth/toolsDecentralizedCommunities.md b/whatisgiveth/toolsDecentralizedCommunities.md deleted file mode 100644 index 28c7bbe08..000000000 --- a/whatisgiveth/toolsDecentralizedCommunities.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -id: toolsDecentralizedCommunities -title: Tools for Decentralized Communities ---- -### Distributed teams need distributed tools! - -Although we try to meet in person too, the most important aspect of running interconnected teams whose members are scattered around the globe comes down to the tools at our disposal. We always try to find the most open and expandable software tools to improve our organizational capability. - -When we are looking at available software for organization, open-source comes first, usability second. Sometimes we have to make our own tool or most likely expand on the work previously done by others. Explore our world-readable logs on Youtube, our Docs and the Chat - It should give you a good impression of who we are and what we are working on. - -### Chat -The Giveth community mainly communicates through these platforms: -[Discord](https://discord.gg/DAFkKdkykr) is currently the recommended option for joining the community. We also have a telegram chat that is bridged to our server. -[Telegram](https://t.me/Givethio) is also used and the chat group is bridged to the general channel in Discord. - -### Documents and Files -The Giveth DAC uses cloud-storage services for transparent document management. Most of our working documents are hosted and shared within [Notion](https://www.notion.so/giveth/Giveth-2c97e0eca91e43238565c8f79dfe5e8d). - -### Organization -Currently we are evaluating [AragonDAO](https://aragon.1hive.org/#/giveth/) which is an excellent decentralized solution for decision-making. - -### Accounting -Transparent tracking of spending on our own [Donation Application](https://trace.giveth.io/community/giveth-dac). - -### Medium -You can find news and updates on our [Medium](https://medium.com/giveth) page. - -### Youtube -[Giveth Main Content](https://www.youtube.com/givethio) -[Giveth Transparency Channel](https://www.youtube.com/channel/UCdqmP4axeI1hNmX20aZsOwg)