├── .archive ├── .gitbook.yaml ├── .gitbook │ └── assets │ │ ├── 91_discord_logo_logos-512.png │ │ ├── banyan.jpg │ │ ├── blog-discord-logo.jpg │ │ ├── cell (1).jpeg │ │ ├── cell.jpeg │ │ ├── dorg-press-kit.zip │ │ ├── dorgs2.gif │ │ ├── faye-cornish-ggv3i6oxpcg-unsplash.jpg │ │ ├── google-workspace-logo.png │ │ ├── growing-mushrooms-timelapse-3.gif │ │ ├── heartbeat.gif │ │ ├── icon.svg │ │ ├── icon_black.png │ │ ├── icon_white.png │ │ ├── image (1).png │ │ ├── image (10).png │ │ ├── image (11) (1).png │ │ ├── image (11).png │ │ ├── image (12).png │ │ ├── image (13).png │ │ ├── image (14).png │ │ ├── image (15).png │ │ ├── image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png │ │ ├── image (22).png │ │ ├── image (23).png │ │ ├── image (24).png │ │ ├── image (27) (1) (1) (1).png │ │ ├── image (27) (1) (1).png │ │ ├── image (28).png │ │ ├── image (29).png │ │ ├── image (3).png │ │ ├── image (30).png │ │ ├── image (31).png │ │ ├── image (32).png │ │ ├── image (33).png │ │ ├── image (34).png │ │ ├── image (35).png │ │ ├── image (5).png │ │ ├── image (6).png │ │ ├── image (9) (1).png │ │ ├── image (9).png │ │ ├── image.png │ │ ├── imagen (2).png │ │ ├── imagen (3).png │ │ ├── imagen (4).png │ │ ├── imagen (7).png │ │ ├── imagen (8).png │ │ ├── imagen.png │ │ ├── legal.dorg.1.png │ │ ├── logo (1).svg │ │ ├── logo.svg │ │ ├── logo_background_black (1).png │ │ ├── logo_background_black.png │ │ ├── logo_background_white.png │ │ ├── logo_black (1).png │ │ ├── logo_black.png │ │ ├── logo_white.png │ │ ├── maxresdefault.jpg │ │ ├── membrane.jpg │ │ ├── neurons.jpg │ │ ├── plant2.gif │ │ ├── pumpflow.gif │ │ ├── rainbow_banner.jpg │ │ ├── rainbow_logo.jpg │ │ ├── screen-shot-2021-08-23-at-14.27.00.png │ │ ├── screen-shot-2021-08-23-at-14.33.49.png │ │ ├── screen-shot-2021-08-25-at-10.05.12.png │ │ ├── screen-shot-2021-08-27-at-14.17.23.png │ │ ├── screen-shot-2021-09-01-at-13.30.43.png │ │ ├── screenshot-2021-08-25-at-14.56.58.png │ │ ├── undraw_quite_town_mg2q.png │ │ ├── undraw_vault_9cmw.png │ │ ├── unit-economics.png │ │ └── value-flow.png ├── Contractor_Term_Sheet_Updated_2019.pdf ├── DSPs │ ├── 000-Template.md │ ├── 001-Web3API.md │ ├── 002-Ops-Roles.md │ ├── 003-Clade.md │ ├── 004-Landing-Page.md │ ├── 005-Builder-Referrals.md │ ├── 006-Onboarding-&-Engagement.md │ ├── 007-Bookkeeping.md │ ├── 008-Token-Redemption.md │ ├── 010-SaaS-Q1-21.md │ ├── 011-Raid-Guild-dOrg-Referrals.md │ ├── 012-dOrg-app.md │ ├── 013-Code-of-Ethics.md │ ├── 014-Bookkeeping-Q2-21.md │ ├── 015-ContentComms.md │ ├── 016-Landing Page Maintenance Q2 2021.md │ ├── 017-SaaS-&-Tax-Q2-21.md │ ├── 018-Marcomms-2.md │ └── 19-QA-Upgrade.md ├── LICENSE.txt ├── Operating_Agreement_Updated_2019.pdf ├── Participation_Terms_And_Conditions_Updated_2019.pdf ├── activation.md └── handbook │ ├── .gitbook │ └── assets │ │ ├── 2022.02.04 dOrg Governance model (1).jpg │ │ ├── 2022.02.04 dOrg Governance model.jpg │ │ ├── 2203_W9 Form.jpg │ │ ├── 91_discord_logo_logos-512.png │ │ ├── Screen Shot 2021-08-23 at 14.27.00.png │ │ ├── Screen Shot 2021-08-23 at 14.33.49.png │ │ ├── Screen Shot 2021-08-27 at 14.17.23.png │ │ ├── Screen Shot 2021-09-01 at 13.30.43.png │ │ ├── Screen Shot 2022-02-22 at 10.40.24 AM.png │ │ ├── Screen_Shot_2022-02-14_at_1.52.50_PM.png │ │ ├── Screenshot 2021-08-25 at 14.56.58.png │ │ ├── Screenshot 2022-01-03 at 17.55.47.png │ │ ├── Screenshot 2022-01-03 at 18.01.07.png │ │ ├── Screenshot 2022-01-13 at 17.20.11.png │ │ ├── Screenshot 2022-03-07 at 16.12.16.png │ │ ├── Screenshot 2022-04-08 at 17.36.23.png │ │ ├── Screenshot 2022-08-08 at 21.18.33.png │ │ ├── Treasury Screenshot.png │ │ ├── Untitled-1 (1).jpg │ │ ├── Untitled-1.jpg │ │ ├── Value Flow.png │ │ ├── banyan.jpg │ │ ├── blog-discord-logo.jpg │ │ ├── cell (1).jpeg │ │ ├── cell.jpeg │ │ ├── dOrg Flywheel (1).png │ │ ├── dOrg Flywheel.png │ │ ├── dOrg Press Kit.zip │ │ ├── dOrg Structure.png │ │ ├── dOrg estimated payments.png │ │ ├── dOrg-black-svg.svg │ │ ├── dOrg-black-transparent.png │ │ ├── dOrg-color-banner.png │ │ ├── dOrg-colored-black-bg.png │ │ ├── dOrg-colored-svg.svg │ │ ├── dOrg-colored-white-bg.png │ │ ├── dOrg-white-svg.svg │ │ ├── dOrg-white-transparent.png │ │ ├── dorg-press-kit.zip │ │ ├── dorgs2.gif │ │ ├── faye-cornish-ggv3i6oxpcg-unsplash.jpg │ │ ├── flow of funds - feb 22 (1).png │ │ ├── flow of funds - feb 22 (2).png │ │ ├── flow of funds - feb 22.png │ │ ├── flywheel - Feb 22.png │ │ ├── google-workspace-logo.png │ │ ├── growing-mushrooms-timelapse-3.gif │ │ ├── heartbeat.gif │ │ ├── icon.svg │ │ ├── icon_black.png │ │ ├── icon_white.png │ │ ├── image (1).png │ │ ├── image (10).png │ │ ├── image (11) (1).png │ │ ├── image (11).png │ │ ├── image (12).png │ │ ├── image (13).png │ │ ├── image (14).png │ │ ├── image (15).png │ │ ├── image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png │ │ ├── image (2) (1) (1) (1) (1) (1) (1) (1) (1).png │ │ ├── image (22).png │ │ ├── image (23).png │ │ ├── image (24).png │ │ ├── image (27) (1) (1) (1).png │ │ ├── image (27) (1) (1).png │ │ ├── image (28).png │ │ ├── image (29).png │ │ ├── image (3).png │ │ ├── image (30).png │ │ ├── image (31).png │ │ ├── image (32).png │ │ ├── image (33).png │ │ ├── image (34).png │ │ ├── image (35).png │ │ ├── image (5).png │ │ ├── image (6).png │ │ ├── image (9) (1).png │ │ ├── image (9).png │ │ ├── image.png │ │ ├── imagen (2).png │ │ ├── imagen (3).png │ │ ├── imagen (4).png │ │ ├── imagen (7).png │ │ ├── imagen (8).png │ │ ├── imagen.png │ │ ├── legal.dorg.1.pdf │ │ ├── legal.dorg.1.png │ │ ├── logo (1).svg │ │ ├── logo.svg │ │ ├── logo_background_black (1).png │ │ ├── logo_background_black.png │ │ ├── logo_background_white.png │ │ ├── logo_black (1).png │ │ ├── logo_black.png │ │ ├── logo_white.png │ │ ├── maxresdefault.jpg │ │ ├── membrane.jpg │ │ ├── neurons.jpg │ │ ├── plant2.gif │ │ ├── pumpflow.gif │ │ ├── rainbow_banner.jpg │ │ ├── rainbow_logo.jpg │ │ ├── screen-shot-2021-08-23-at-14.27.00.png │ │ ├── screen-shot-2021-08-23-at-14.33.49.png │ │ ├── screen-shot-2021-08-25-at-10.05.12.png │ │ ├── screen-shot-2021-08-27-at-14.17.23.png │ │ ├── screen-shot-2021-09-01-at-13.30.43.png │ │ ├── screenshot-2021-08-25-at-14.56.58.png │ │ ├── undraw_quite_town_mg2q.png │ │ ├── undraw_vault_9cmw.png │ │ ├── unit economics.png │ │ ├── unit-economics.png │ │ ├── unnamed.jpg │ │ └── value-flow.png │ ├── README.md │ ├── SUMMARY.md │ ├── builder-resources │ ├── best-practice-overview.md │ ├── choosing-a-hosting-platform.md │ ├── creating-a-react-dapp.md │ ├── doing-a-code-review.md │ ├── git.md │ ├── upskilling.md │ └── web3-glossary.md │ ├── covenant.md │ ├── glossary │ ├── dorg.md │ └── web3.md │ ├── governance │ ├── covenant.md │ ├── global-variables.md │ └── voting-power.md │ ├── lifecycle │ ├── applying.md │ ├── member-status.md │ ├── onboarding.md │ └── removal.md │ ├── links.md │ ├── overview │ ├── form-and-function.md │ ├── our-values.md │ ├── principles.md │ └── purpose.md │ ├── resources │ ├── best-practice-overview │ │ ├── README.md │ │ ├── choosing-a-hosting-platform.md │ │ ├── doing-a-code-review.md │ │ ├── git.md │ │ ├── react-dapp.md │ │ └── tests.md │ ├── getting-stuff-done-in-a-dao.md │ ├── links.md │ ├── press-kit.md │ ├── quarterly-dorg-tax-payments.md │ ├── referral-program.md │ ├── social-media.md │ └── upskilling.md │ ├── structure.md │ └── workflows │ ├── billing.md │ ├── coordination-lead.md │ ├── doing-internal-work │ ├── README.md │ └── funded-initiatives.md │ ├── events.md │ ├── executing.md │ ├── expense-reimbursement-policy.md │ ├── joining.md │ ├── navigating.md │ ├── qa-lead.md │ └── sourcing.md ├── .gitignore └── legal ├── Client_Terms_And_Conditions.pdf ├── Contractor_Services_Agreement_Updated_2022.pdf ├── Contractor_and_Operational_Agreement_NDA_Master_Services_2024.pdf └── Operating_Agreement_Updated_2022.pdf /.archive/.gitbook.yaml: -------------------------------------------------------------------------------- 1 | root: ./handbook/ 2 | 3 | structure: 4 | readme: README.md 5 | summary: SUMMARY.md 6 | -------------------------------------------------------------------------------- /.archive/.gitbook/assets/91_discord_logo_logos-512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/91_discord_logo_logos-512.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/banyan.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/banyan.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/blog-discord-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/blog-discord-logo.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/cell (1).jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/cell (1).jpeg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/cell.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/cell.jpeg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/dorg-press-kit.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/dorg-press-kit.zip -------------------------------------------------------------------------------- /.archive/.gitbook/assets/dorgs2.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/dorgs2.gif -------------------------------------------------------------------------------- /.archive/.gitbook/assets/faye-cornish-ggv3i6oxpcg-unsplash.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/faye-cornish-ggv3i6oxpcg-unsplash.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/google-workspace-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/google-workspace-logo.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/growing-mushrooms-timelapse-3.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/growing-mushrooms-timelapse-3.gif -------------------------------------------------------------------------------- /.archive/.gitbook/assets/heartbeat.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/heartbeat.gif -------------------------------------------------------------------------------- /.archive/.gitbook/assets/icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | favicon 5 | Created with Sketch. 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /.archive/.gitbook/assets/icon_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/icon_black.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/icon_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/icon_white.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (10).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (10).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (11) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (11) (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (11).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (11).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (12).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (12).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (13).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (13).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (14).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (14).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (15).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (15).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (22).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (22).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (23).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (23).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (24).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (24).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (27) (1) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (27) (1) (1) (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (27) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (27) (1) (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (28).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (28).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (29).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (29).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (3).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (3).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (30).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (30).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (31).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (31).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (32).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (32).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (33).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (33).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (34).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (34).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (35).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (35).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (5).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (5).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (6).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (6).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (9) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (9) (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image (9).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image (9).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/image.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen (2).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen (2).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen (3).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen (3).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen (4).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen (4).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen (7).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen (7).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen (8).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen (8).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/imagen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/imagen.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/legal.dorg.1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/legal.dorg.1.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_background_black (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_background_black (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_background_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_background_black.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_background_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_background_white.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_black (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_black (1).png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_black.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/logo_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/logo_white.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/maxresdefault.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/maxresdefault.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/membrane.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/membrane.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/neurons.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/neurons.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/plant2.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/plant2.gif -------------------------------------------------------------------------------- /.archive/.gitbook/assets/pumpflow.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/pumpflow.gif -------------------------------------------------------------------------------- /.archive/.gitbook/assets/rainbow_banner.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/rainbow_banner.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/rainbow_logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/rainbow_logo.jpg -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screen-shot-2021-08-23-at-14.27.00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screen-shot-2021-08-23-at-14.27.00.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screen-shot-2021-08-23-at-14.33.49.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screen-shot-2021-08-23-at-14.33.49.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screen-shot-2021-08-25-at-10.05.12.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screen-shot-2021-08-25-at-10.05.12.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screen-shot-2021-08-27-at-14.17.23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screen-shot-2021-08-27-at-14.17.23.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screen-shot-2021-09-01-at-13.30.43.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screen-shot-2021-09-01-at-13.30.43.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/screenshot-2021-08-25-at-14.56.58.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/screenshot-2021-08-25-at-14.56.58.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/undraw_quite_town_mg2q.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/undraw_quite_town_mg2q.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/undraw_vault_9cmw.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/undraw_vault_9cmw.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/unit-economics.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/unit-economics.png -------------------------------------------------------------------------------- /.archive/.gitbook/assets/value-flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/.gitbook/assets/value-flow.png -------------------------------------------------------------------------------- /.archive/Contractor_Term_Sheet_Updated_2019.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/Contractor_Term_Sheet_Updated_2019.pdf -------------------------------------------------------------------------------- /.archive/DSPs/000-Template.md: -------------------------------------------------------------------------------- 1 | # Proposal Title 2 | 3 | | Budget | Term | Lead | 4 | |-|-|-| 5 | | [X DAI + Y DORG](link to budget spreadsheet) | # of Weeks (Date Range) | Name | 6 | 7 | ## Summary 8 | 9 | Quick summary of the proposal 10 | 11 | ## Why should we fund this? 12 | 13 | Breakdown why you think dOrg should spend resources on this proposal. Does it create revenue? Does it benefit us or the decentralization ecosystem in some other way? 14 | 15 | ## Anything else you'd like to add? 16 | 17 | Add additional details such as workbins, roadmap, and accountability structures. 18 | 19 | ## Cost Breakdown 20 | 21 | | Item | Description | $/Hr | Hrs | Cost | 22 | |-|-|-|-|-| 23 | | .. | .. | $.. | .. | $.. | 24 | | .. | .. | $.. | .. | $.. | 25 | | | | TOTAL | .. | $.. | 26 | -------------------------------------------------------------------------------- /.archive/DSPs/001-Web3API.md: -------------------------------------------------------------------------------- 1 | # Web3API Seed Funding 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [15,000 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1425922851) | 3 Months (Jun 1 - Sep 30 '20) | Jordan | Ori, Roberto, Cesar | 6 | 7 | This proposal will provide initial funding for the development of the Web3API and seeding of the Web3API DAO. 8 | 9 | ## Cost Breakdown 10 | 11 | - June - $5k 12 | - August - $5k 13 | - September - $5k 14 | -------------------------------------------------------------------------------- /.archive/DSPs/002-Ops-Roles.md: -------------------------------------------------------------------------------- 1 | # Ops Roles Q4 2020 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [8,100 DAI](https://docs.zoho.com/sheet/open/a4p9k334be0a1097242a3b83d72f227695a48/sheets/Internal%20Ops/ranges/A1) | 9 Weeks (Nov 2 - Jan 4, '21) | Ori | Magenta, Roberto | 6 | 7 | ## Summary 8 | 9 | Designate leads and fixed weekly budgets for admin, facilitation, and comms. 10 | 11 | ## Why should we fund this? 12 | 13 | Having well-defined areas with leads will help us avoid diffusion of responsibilities for crucial operational tasks, while creating higher transparency for the entire organization of who is handling what. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | While each role has a lead, anyone from dOrg is welcome to contribute and earn from the role budgets. 18 | 19 | | Role | Description | Lead | 20 | |-|-|-| 21 | | [Admin](https://docs.google.com/document/d/1CAuJaqNVZHKhL3dKWt7XWFSEE_gFWNdd1OJRGFuKE6o) | Maintain and improve systems for keeping dOrg’s finances and transactions healthy and transparent | Magenta | 22 | | [Facilitation](https://docs.google.com/document/d/1NoAHVQxOONc7hHXk9H_lr6W8AuEv57hYii6cT6W-IC4) | Focus on ways to continuously enhance the dOrg builder experience | Ori | 23 | | [Comms](https://docs.google.com/document/d/1k9yGypCxPLQxhSn7oZUU8cJ9gbqxze96MRKrK0FZQW8) | Keep dOrg’s external relationships and communication channels lively and growing | Roberto | 24 | 25 | ## Cost Breakdown 26 | 27 | $8100 28 | - 3 Roles (admin, facilitation, comms) 29 | - 9 Weeks (Nov 2, 2020 - Jan 4, 2021) 30 | - 0.15 FTEs (~6 hours / week) per Role 31 | - $2,000 per week per FTE 32 | 33 | Payment proposals will be broken down into three 3-week periods 34 | -------------------------------------------------------------------------------- /.archive/DSPs/003-Clade.md: -------------------------------------------------------------------------------- 1 | # Clade Prototype Video 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [4,100 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1668320325) | 6 Months (Nov - Apr '21) | Magenta | Ben, David, Ori | 6 | 7 | ## Summary 8 | 9 | Create a flagship video to test the Clade project hypothesis, for bridging the world of DAO’s with the broader world of cooperative organizations and future of work. 10 | 11 | * Produce 3-5 minute video: showing the history of work and how digital cooperatives are the future of work; with animation and narration. 12 | * Research topics from a civilian perspective: Identify 3-4 key words or phrases that people are searching that this content provides answers and resources to. Our audiences are: existing cooperatives, freelancers, activist communities. 13 | * Publish video to aligned communities for feedback. 14 | * Review effectiveness and assess next steps: evaluate if we have created quality content and if there is sufficient audience and partner interest to move forward. 15 | 16 | ## Why should we fund this? 17 | 18 | * To begin the Clade project as a place for dOrg builders to share about what we're creating here and the DAO space as a whole, why it's meaningful to us, and help more people experience liberation through these modes of organizing together 19 | * Show to partners who are interested in helping to fund future content, so we can continue creating content and value (revenue) streams - [see brainstorm document](https://docs.google.com/document/d/1POTlN4AsxBk-Gv8eYzRmyqh8muvFcOg2hanb6yUEEio/edit) 20 | * This is a video we can show to people about how dOrg works, whether client or builder 21 | 22 | ## Anything else you'd like to add? 23 | 24 | Clade as a spin-off project has been in discussion in dOrg since September 2020. 25 | 26 | Roles 27 | * Script lead: Ben with support from David 28 | * Production and Storyboard lead: David 29 | * Support on details/facts: Ori and Jordan 30 | * Research lead: Bernie 31 | * Execution lead: Magenta 32 | 33 | ## Cost Breakdown 34 | 35 | $4100 x Nov - Apr 36 | - $1100 Animation 37 | - $250 Brand Design 38 | With remainder of budget distribution as follows: 39 | - 30% Script Writing and Review 40 | - 35% Production 41 | - 15% Research 42 | - 10% Outreach/Circulation 43 | - 10% Project Coordination 44 | -------------------------------------------------------------------------------- /.archive/DSPs/004-Landing-Page.md: -------------------------------------------------------------------------------- 1 | # Landing Page Redesign 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [9,000 DAI + 1,000 DORG](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1401977836) | 6 Weeks (Nov 11 - Dec 23 '21) | Kris | Ben, Roberto | 6 | 7 | ## Summary 8 | 9 | Commission a website redesign through a [99designs](https://99designs.com) contest and implement internally. 10 | 11 | ## Why should we fund this? 12 | 13 | Our website needs to be up to date with our portfolio and how we work in order to keep attracting the best builders and clients. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | - [Wireframe](https://docs.google.com/presentation/d/1P7jeGETFRJBKlyXUjk9j9-QUUa8BctjFVSwMaIyev6M) 18 | - Building from the existing [landing page repository](https://github.com/dOrgTech/landing-page) 19 | 20 | ### Timeline 21 | 22 | - Design Contest: 2 weeks 23 | - Qualifying round (6 days) 24 | - Select finalists (1-2 days) 25 | - Final round (5 days) 26 | - Choose a winner (1-2 days) 27 | - Implementation: Est. 2-4 weeks (0.25 - 0.50 FTE) 28 | 29 | *Start Date*: Nov 11 30 | 31 | *ETA*: Dec 9 - 23 32 | 33 | ### Builders 34 | - Roberto: design contest lead 35 | - Ben: coordination lead 36 | - Kris: implementation 37 | - Open to help from all other builders on design contest and implementation 38 | 39 | ## Cost Breakdown 40 | 41 | Up to $9,000 42 | - $2,000 - Design ($1780 design contest + $220 internal work) 43 | - $7,000 + 1,000 DXRG - Implementation (internal) 44 | -------------------------------------------------------------------------------- /.archive/DSPs/005-Builder-Referrals.md: -------------------------------------------------------------------------------- 1 | BUILDER REFERRAL INCENTIVES HAVE BEEN TURNED OFF FOR ACTIVATION PROPOSALS MADE AFTER JULY 1, 2021 2 | 3 | # Builder Referral Incentives 4 | 5 | | Budget | Term | Lead (hr/wk ) | 6 | |-|-|-| 7 | | [Up to $5k per new builder](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1833782755) | Perpetual | Ron, Ori | 8 | 9 | ## Summary 10 | 11 | Builder referral model that ties incentive to revenue generated by the referred builder. 12 | 13 | ## Why should we fund this? 14 | 15 | For dOrg to continue to provide high quality service and take on exciting projects, the organization needs to be able to attract and maintain top engineering talent. 16 | 17 | ## Anything else you'd like to add? 18 | 19 | The incentive will be equivalent to 10% of the referred builder's first $50k earned from client work. dOrg currently makes 12.5 cents on every dollar earned by a builder on client work. In the case of a referred builder, dOrg would effectively earn 2.5 cents instead, with the remaining 10 cents going to the referrer. 20 | 21 | In order to simplify the tracking overhead, referral incentives will be payable to referrers at 4 milestones: 22 | 1. $5k (-> $500) 23 | 2. $15k (-> $1000) 24 | 3. $25k (-> $1000) 25 | 4. $50k (-> $2500) 26 | 27 | (Max Commission: $5,000 total) 28 | 29 | Advantages of the model: 30 | - The revenue generated by the referred builder pays for the referral incentive 31 | - Simple to understand, account for, and track 32 | - Pays out gradually, has caps so the costs are controlled 33 | - Doesn't take money out of the referred builder's pocket 34 | 35 | ## Cost Breakdown 36 | 37 | 80% of dOrg's 10% Margin on the first $50k of client work compensation earned by each newly referred builder (max $5K per new builder) 38 | -------------------------------------------------------------------------------- /.archive/DSPs/006-Onboarding-&-Engagement.md: -------------------------------------------------------------------------------- 1 | # Onboarding & Engagement Q1 2021 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [22,800 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=32799193) | 12 Weeks (Jan 4 - Mar 29, '21) | Steff (12) | Ori (5-6) Rob (3-6) Bernie (1-2) | 6 | 7 | ## Summary 8 | 9 | This proposal establishes a new workstream focused on improving the quality of builder engagement across the DAO. We’ll guide this work stream by 10 | - Facilitating effective & ongoing collaboration 11 | - Coordinating work bins to achieve measurable outcomes 12 | - Analyzing and reporting our progress to the DAO 13 | - Unifying work bins into learning milestones, so that we can evolve & iterate 14 | 15 | ## Why should we fund this? 16 | 17 | We need to continue to have dedicated people maintaining and improving our processes as we continue to take on on a higher volume of projects and builders. 18 | 19 | ## Anything else you'd like to add? 20 | 21 | This workstream covers the quality of engagement with and within the DAO at any of these stages: 22 | - Discovering the DAO 23 | - Onboarding 24 | - Project enrollment 25 | - Ongoing empowerment 26 | - Builder referrals & client sourcing 27 | 28 | Sample tasks will likely include these and more... 29 | - Map the [Member Journey](https://docs.google.com/document/d/1z47NnQ91T0OvlHFYXhwEY9SSEmz1Tj0MpNeT695XKJE/edit) 30 | - Gather feedback about builder experiences through focus group surveys 31 | - Iterate on the website redesign 32 | - Redesign client proposal template 33 | - Migrate CRM from Airtable to HubSpot 34 | 35 | This workstream will lead to new initiatives as well as build off of existing ones, such as: 36 | - [DSP 2: Q4 2020 Ops Roles](https://github.com/dOrgTech/Ops/blob/master/DSPs/002-Ops-Roles.md) 37 | - [DSP 4: Landing Page Redesign](https://github.com/dOrgTech/Ops/blob/master/DSPs/004-Landing-Page.md) 38 | - [DSP 5: Builder Referrals](https://github.com/dOrgTech/Ops/blob/master/DSPs/005-Builder-Referrals.md) 39 | - [Issue 70 Gamifying QA](https://github.com/dOrgTech/Ops/issues/72) 40 | - [Issue 72 Improve activation/onboarding funnel](https://github.com/dOrgTech/Ops/issues/70) 41 | 42 | ## Cost Breakdown 43 | 44 | | Item | Description | $/Hr | Hrs | Cost | 45 | |-|-|-|-|-| 46 | | *Systems Building* | Research, design, and build processes for engagement and onboarding | $75 | 20*12 | $18,000 | 47 | | *Engagement* | Ongoing meetings, emails, chats, and follow-ups | $60 | 8*12 | $4,800 | 48 | | | TOTAL | | 336 | $22,800 | -------------------------------------------------------------------------------- /.archive/DSPs/007-Bookkeeping.md: -------------------------------------------------------------------------------- 1 | # Bookkeeping Q1 2021 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [8,895 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=414785260) | 3 Months (Jan 1 - Mar 31, '21) | Magenta, Ori | 6 | 7 | ## Summary 8 | 9 | Maintain and improve systems for keeping dOrg’s finances and transactions healthy and transparent 10 | 11 | ## Why should we fund this? 12 | 13 | This will help dOrg become a financially secure & legally compliant organization (Goal #7). 14 | 15 | ## Anything else you'd like to add? 16 | 17 | This workstream consists of both a professional CPA and dOrg builders. 18 | 19 | The CPA will be responsible for the following ([see attachment here for full SoW](https://airtable.com/tblufTXr6zuUl1Aml/viwC2pIYVNGSJP54h/recEyDQBaufUFLMZH/flddH5SlUfoTGH9Nh/attr6h7Ljxd7uhXSX?blocks=hide)): 20 | - Taxation services - 1120C Corporate Tax Return 21 | - Advisory services - General advisory services (CFO, Tax, Health Check, Compliance) 22 | - Reporting services- Financial & Management reporting (Income Statement, Balance Sheet) 23 | - Discounted personal tax prep for US builders (not included in the cost here) 24 | 25 | The dOrg builders will: 26 | - Interface with the CPA on bookkeeping and tax prep 27 | - Prep 1099 tax forms 28 | - Synthesize builder agreements 29 | - Setup [automated bookkeeping](https://cointracking.info) and [invoicing](https://request.network) 30 | 31 | ## Cost x Timeframe 32 | 33 | | Item | Description | $/Hr | Hrs | Cost | 34 | |-|-|-|-|-| 35 | | *CPA* | Professional tax prep, advisory, and reporting services | $240.63 | 8*3 | $5,775 | 36 | | *dOrg* | Interfacing with CPA and handling other bookkeeping related tasks | $65 | 16*3 | $3,120 | 37 | | | Total | | 336 | $8,895 | 38 | 39 | The CPA will be paid upfront and dOrg builders will be paid in three 1-month periods. -------------------------------------------------------------------------------- /.archive/DSPs/008-Token-Redemption.md: -------------------------------------------------------------------------------- 1 | # DORG Token Redemption 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [2,000 DAI + 2,000 DORG]() | 1 month (Dec 15 - Jan 15 '21) | Nestor B (15) | 6 | 7 | ## Summary 8 | 9 | Build the UI Client for the dOrg token redemption/staking contracts. 10 | 11 | ## Why should we fund this? 12 | 13 | This project will give usability to the current dOrg token deployed contract. It will let the token holder redeem it for a choice of the preferred stablecoin, it will also enable the ability to stake the token to earn an APR based on the amount of dOrg token the holder commits to staking. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | **Scope:** 18 | 19 | **StableRedemption UI:** 20 | This feature let's the user connect to the StableRedemption contract that will be deployed on Mainnet, using the DORG token contract as the input token and setting a list of 4 stable coins as the redeem tokens (USDC, USDT, DAI, TUSD). 21 | 22 | The user is able to redeem their DORG tokens for any of the whitelisted stablecoins. Also it has the feature to add a new stablecoin to the list (this new stablecoin needs to be whitelisted and funded into the StableRedemption contract by the DAO). 23 | 24 | **StakingRewards UI:** 25 | This feature let's the user connect to the StakingReward contract that will be deployed on Mainnet, using the DORG token as the input token and by setting an APR to it https://github.com/dOrgTech/token-redemption/issues/10 26 | 27 | The user is able to stake/unstake/claim rewards/unstake and claim rewards/claim partial rewards based on the amount of DORG tokens on his wallet (to stake) or the amount of rewards he has gained by staking (staking rewards). 28 | 29 | ## Cost Breakdown 30 | 31 | Estimated delivery day: Waiting for https://github.com/dOrgTech/token-redemption/issues/10 to be resolved in order to deploy the contracts and ui client. 32 | 33 | Estimated hours spent: 65 hours. 34 | 35 | Estimated hours lef to spend: 2-3 hours (Deployment) 36 | 37 | This is my first project for dOrg and was completed between mid December and mid January. 38 | 39 | Delivery: https://github.com/dOrgTech/token-redemption 40 | 41 | 42 | -------------------------------------------------------------------------------- /.archive/DSPs/010-SaaS-Q1-21.md: -------------------------------------------------------------------------------- 1 | # SaaS Q1 2021 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-| 5 | | [1,539.67 DAI]() | 3 months (Jan 1 - Mar 31 '21) | Ori | 6 | 7 | ## Summary 8 | 9 | SaaS spending for Q1 2020 10 | 11 | ## Why should we fund this? 12 | 13 | These are the essential software tools for running a remote team. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | In this period we will be transitioning from Airtable to HubSpot. 18 | 19 | ## Cost Breakdown 20 | 21 | | Item | Description | $ breakdown | Total $ | 22 | |-|-|-|-| 23 | | *Netlify* | Hosting https://dorg.tech landing page and sometimes used to stage sites on client projects | $45+$57+$40 | $142 | 24 | | *Google Workspace* | | $191.99+$208.63+$229.92 | $630.54 | 25 | | *Airtable* | | | $15.13 | 26 | | *HubSpot* | Sales & marketing pro bundle at 90% startup discount | $139 x 3 (+$300 one-time) | $717 | 27 | | *Vermont* | Annual report fee | | $35 | 28 | | | | | $1,539.67 | 29 | 30 | A reimbursement proposal will be submitted at the end of the period. -------------------------------------------------------------------------------- /.archive/DSPs/011-Raid-Guild-dOrg-Referrals.md: -------------------------------------------------------------------------------- 1 | # Proposal Title 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | 5% of revenue from referred projects | Perpetual | Ben | 6 | 7 | ## Summary 8 | 9 | Establish a reciprocal qualified sales referral program for [dOrg](https://dorg.tech/) and [Raid Guild](https://raidguild.org/) commesurate to five percent (5%) of the total project budget. 10 | 11 | ## Why should we fund this? 12 | 13 | This arrangement could result in new revenue for both organizations by maximizing usage of our varying capacities and availabilities. 14 | It could also represent the beginnings of a decentralized autonomous organization (DAO) consortium to broadly promote digital cooperatives and the future of work. 15 | 16 | ## Anything else you'd like to add? 17 | 18 | For qualified sales referred to Raid Guild, the funds will be payable to the dOrg DAO @ `dorg.eth` (0x15344ecdc2c4edfcb092e284d93c20f0529fd8a6). 19 | For qualified sales referred to dOrg, the funds will be payable to the Raid Guild DAO [here](https://pokemol.com/dao/0xbeb3e32355a933501c247e2dbde6e6ca2489bf3d) (0xbeb3e32355a933501c247e2dbde6e6ca2489bf3d). 20 | 21 | ## Cost Breakdown 22 | 23 | Five percent (5%) of the total project budget of any referred sale 24 | Within dOrg, half of this amount will go to the source lead that provides sales qualfication before referral to Raid Guild. -------------------------------------------------------------------------------- /.archive/DSPs/012-dOrg-app.md: -------------------------------------------------------------------------------- 1 | # app.dOrg 2 | 3 | | Budget | Term | Lead | Builders | 4 | |-|-|-|-| 5 | | [$17,200 + 3,000 DXRG](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=46471418) | 14 Weeks (Mar 22 - Jun 28) | Colin | Leif, Carlos, Jason, Zachary | 6 | 7 | ## Summary 8 | 9 | It's no secret that there are inefficiencies within our internal processes. And while we are making a concerted effort to reveal and address these, our current smorgasboard of internal apps and software makes it difficult for us to resolve some of these inefficiencies. Furthermore, some of these apps have functional limitations and underlying UX inefficiencies that we are currently handcuffed to. 10 | 11 | To give a little more context, some of these issues include: 12 | - Inability to edit or redact an existing proposal 13 | - Inability to make batched payments 14 | - Making a new proposal is unintuitive 15 | - Cumbersome google sheets which make budgeting/operations difficult to manage 16 | - Proposal-specific communication is difficult 17 | - Lack of async notifications for DAO activity and project updates/requests 18 | 19 | 20 | ## Why should we fund this? 21 | 22 | The problems outlined above create enormous amounts of overhead in our day-to-day by making things unnecessarily difficult to understand, and they increase the risk of mistakes and fraudulent proposals. 23 | 24 | Creating a specialized dOrg app that we own, build, and iterate on gives us full control of customizing and optimizing our systems and procedures to fit dOrg's specific and fluid needs, while also increasing our security standards. 25 | 26 | On top of this, the end product is something that can be forked, and will also further establish our expertise in the DAO ecosystem. 27 | 28 | ## Anything else you'd like to add? 29 | 30 | ### Timeline 31 | 32 | - **Phase 1: Design Strategy:** Est. 4 weeks (~10 hr/wk) 33 | - Discovery (1 week) 34 | - Ideation and Refinement (1 week) 35 | - Info architecture map (0.5 week) 36 | - Basic style/figma components (0.5 week) 37 | - Mock-ups (1 week) 38 | - **Phase 2: Development Coordination:** Est. 4 weeks (~5 hr/wk) 39 | - Determine scope for development phase 40 | - Product Development 41 | - **Phase 3: Product Development:** Est. 8 weeks (~25 hr/wk) 42 | - Design refinement 43 | - Product Development 44 | 45 | - **Feedback & Advisory** Ongoing (12 hrs in Phase 1 and ~1 hr/wk for Phase 3) 46 | - Internal feedback and advice 47 | 48 | ### Accountability 49 | 50 | - Team: 51 | - Colin: Design/Frontend Development 52 | - Leif: Product Manager 53 | - Carlos: Fullstack Development 54 | - Jason: Backend Development 55 | - Zachary: Backend Development 56 | - Project: https://github.com/dOrgTech/app-dorg/projects 57 | - Project Brief: https://docs.google.com/document/d/1koJt7MxpLMKQCQKAn6a-zZhA2ey5GLckC5jvcpkVMEY 58 | - Updates: @ dOrg-wide biweekly syncs 59 | 60 | ## Cost Breakdown 61 | 62 | | Item | Description | $/Hr | Hrs | Cost | 63 | |-|-|-|-|-| 64 | | Product strategy | Research, design, and strategy for the MVP version of the app. | $65 | 40 | $2600 | 65 | | Development Coordination | Organize, coordinate with dev team and set general scope + mockup scope rollover from phase 1 (4.5 hrs) | $65 | 24.5 | ~$1,600 | 66 | | Product development | MVP fully functional site | 200 | $75 | $15,000 | 67 | | Feedback & advisory | User interviews, feedback, support (internal) | 20 | $50 | $1000 | 68 | | | | TOTAL | ~285 | ~$20,200 | 69 | 70 | Payment proposals will be broken down into 3 4-week periods (and 1 2-week coordination period) and will be distributed based on contribution. 71 | 72 | | Date | Amount | 73 | |-|-| 74 | | Apr 19 | $2,800 / 400 DXRG | 75 | | May 16 | ~$1,600 | 76 | | Jun 13 | $6,400 / 1300 DXRG | 77 | | Jul 11 | $6,400 / 1300 DXRG | 78 | -------------------------------------------------------------------------------- /.archive/DSPs/013-Code-of-Ethics.md: -------------------------------------------------------------------------------- 1 | # Proposal Title 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [2500 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1121144772) | 2 Weeks (Mar 24 - Apr 5 '21) | Ben | 6 | 7 | ## Summary 8 | 9 | A code of ethics is a long standing need for dOrg (see [#9](https://github.com/dOrgTech/Ops/issues/9)) that has become readily apparent due to recent operational challenges. 10 | 11 | ## Why should we fund this? 12 | 13 | A code of ethics for dOrg will explicitly define the expected/avoided behavior of dOrg's builders as well as enforcement mechanisms, matching the interests of dOrg as a whole. 14 | This will reduce business and legal risk to dOrg, ensuring that its builder lifecycle can continue to scale with its growing capacity. 15 | 16 | ## Cost Breakdown 17 | 18 | | Item | Description | $/Hr | Hrs | Cost | 19 | |-|-|-|-|-| 20 | | Assessment | Assess ethical challenges and research options | $50 | 20 | $1000 | 21 | | Draft/Revision | Draft code and revise to feedback | $50 | 15 | $750 | 22 | | Implementation | Implement code and agreed upon enforcement tactics | $50 | 15 | $750 | 23 | | | Total | 50 | $2500 | -------------------------------------------------------------------------------- /.archive/DSPs/014-Bookkeeping-Q2-21.md: -------------------------------------------------------------------------------- 1 | # Bookkeeping Q2 2021 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [8,895 DAI](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=414785260) | 3 Months (Apr 1 - June 30, 2021) | Magenta, Ori | 6 | 7 | ## Summary 8 | 9 | Maintain and improve systems for keeping dOrg’s finances and transactions healthy and transparent 10 | 11 | ## Why should we fund this? 12 | 13 | This will help dOrg become a financially secure & legally compliant organization (Goal #7). 14 | 15 | ## Anything else you'd like to add? 16 | 17 | This workstream consists of both a professional CPA and dOrg builders. 18 | 19 | The CPA will be responsible for the following ([see attachment here for full SoW](https://airtable.com/tblufTXr6zuUl1Aml/viwC2pIYVNGSJP54h/recEyDQBaufUFLMZH/flddH5SlUfoTGH9Nh/attr6h7Ljxd7uhXSX?blocks=hide)): 20 | - Taxation services - 1120C Corporate Tax Return 21 | - Advisory services - General advisory services (CFO, Tax, Health Check, Compliance) 22 | - Reporting services- Financial & Management reporting (Income Statement, Balance Sheet) 23 | - Discounted personal tax prep for US builders (not included in the cost here) 24 | 25 | The dOrg builders will: 26 | - Interface with the CPA on bookkeeping and tax prep 27 | - Prep 1099 tax forms 28 | - Synthesize builder agreements 29 | - Setup [automated bookkeeping](https://cointracking.info) 30 | 31 | ## Cost Breakdown 32 | 33 | 34 | | Item | Description | $/Hr | Hrs | Cost | 35 | |-|-|-|-|-| 36 | | *CPA* | Professional tax prep, advisory, and reporting services | $240.63 | 8*3 | $5,775 | 37 | | *dOrg* | Interfacing with CPA and handling other bookkeeping related tasks | $65 | 16*3 | $3,120 | 38 | | | Total | | 336 | $8,895 | 39 | 40 | The CPA will be paid upfront and dOrg builders will be paid in three 1-month periods. 41 | -------------------------------------------------------------------------------- /.archive/DSPs/015-ContentComms.md: -------------------------------------------------------------------------------- 1 | # MarkComms 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [1,540 DAI + 280 DORG](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=318900412) | 4 Weeks (April 5 - May 2) | Ernesto | 6 | 7 | ## Summary 8 | Develop an integrated content strategy that positions dORG as a leader in the blockchain development space, highlighting our experience, talent, and community. 9 | 10 | Purpose 11 | - Position dOrg as a thought leader in our space 12 | - Associate us with keywords (DAOs, NFTs, DeFi) 13 | - Build community 14 | 15 | ## Why should we fund this? 16 | 17 | I have put the information around this proposal here: 18 | https://docs.google.com/presentation/d/1tC33uGvALpQTMcOtrGl18o0fK8TV_wm1ne_MHUKRI_I/edit?usp=sharing 19 | 20 | ## Anything else you'd like to add? 21 | 22 | ### Content Roadmap 23 | - 1x Builder profiles (monthly) 24 | - 1x Project highlights (monthly) 25 | - 1x State of dOrg (quarterly) 26 | 27 | ### Strategy 28 | Create high-value content in multiple formats including text, video, images, and audio, then formatting it to be distributed across multiple digital channels including blog, messaging, and social. Content will associate dORG with relevant keywords such as DAOs, NFTs, DeFi, etc. 29 | 30 | ### Other Responsibilities 31 | - Create content from events 32 | - Manage socials (Content calendar) 33 | - Setting up a brand 320 34 | + 240 DORG- Ecosystem mapping 35 | - Media/Press (magazines, youtubers, podcasts, etc.) 36 | 37 | ### Accountability 38 | - Updates at Biweekly Syncs 39 | 40 | ## Cost Breakdown 41 | 42 | | Item | Description | $/Hr | Hrs | Cost | 43 | |-|-|-|-|-| 44 | | *Core Work* | Content production and editing, social media management, content optimization. | $65 | 6*4 | $1,560 | 45 | | *Incentive* | Compensate builders for their time getting interviewed, making themselves available for content production | $65 | 1*4 | $260 | 46 | | | | TOTAL | 28 | $1,820 | 47 | 48 | Payment proposals will be broken down into two 2-week periods. 49 | -------------------------------------------------------------------------------- /.archive/DSPs/016-Landing Page Maintenance Q2 2021.md: -------------------------------------------------------------------------------- 1 | # Landing Page Ongoing Maintenance Budget for Q2 2021 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [1,200 DAI + 300 DORG](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=1401977836) | 3 Months (Apr 1 - Jun 30 '21) | Kris (5) | Muath (5) | 6 | 7 | ## Summary 8 | 9 | This proposal adds a budget for ongoing maintanence of the dorg.tech landing page. The budget will fund improvements and bug fixes identified by dOrg members. 10 | 11 | ## Why should we fund this? 12 | 13 | An ongoing maintanence budget will provide funding to fix bugs and implement improvements to the landing page. The current backlog can be viewed here: https://github.com/dOrgTech/landing-page-v2/issues. Future improvements may include any changes dOrg members believe will add value to the landing page. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | The builder will also be responsible for reminder dOrg members once per month to provide feedback on the landing page by making issues or providing feedback in the landing page discord channel. 18 | 19 | ## Cost Breakdown 20 | 21 | | Item | Description | $/Hr | Hrs | Cost | 22 | |-|-|-|-|-| 23 | | Development | Tackle issues in the landing page repo | $50 | 10*3 | $1500 | -------------------------------------------------------------------------------- /.archive/DSPs/017-SaaS-&-Tax-Q2-21.md: -------------------------------------------------------------------------------- 1 | # Q2 SaaS & Tax Expenses 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [2,468 DAI]() | 3 months (Apr 1 - Jun 30) | Ori | 6 | 7 | ## Summary 8 | 9 | SaaS and Tax expenses spending for Q2 2020 10 | 11 | ## Why should we fund this? 12 | 13 | Essential software tools for running a remote team and tax payments for running a US company. 14 | 15 | ## Anything else you'd like to add? 16 | 17 | The breakdown below is a conservative estimate that will be updated as real expenses are incurred. 18 | 19 | ## Cost Breakdown 20 | 21 | | Item | Purpose | $ breakdown | Total $ | 22 | |-|-|-|-| 23 | | *Netlify* | Hosting https://dorg.tech landing page and sometimes used to stage sites on client projects | $45 x 3 | $135 | 24 | | *Google Workspace* | Gmail, Google Calendar, and Google Drive | $250 x 3 | $750 | 25 | | *HubSpot* | Sales & marketing pro bundle at 90% startup discount | $139 x 3 | $417 | 26 | | *2020 taxes* | Federal and State taxes for 2020 | $300 Vermont + $866 Federal | $1,166 | 27 | | *2021 Q1 estimated tax* | | | TBD | 28 | | | | | $2,468 | 29 | 30 | The 2020 tax reimbursement proposal will be made upon execution of this DSP. 31 | 32 | Remaining expenses will be reimbursed at the end of the quarter. 33 | -------------------------------------------------------------------------------- /.archive/DSPs/018-Marcomms-2.md: -------------------------------------------------------------------------------- 1 | # MarComms DSP: May, June, July 2 | 3 | | Budget | Term | Lead (hr/wk ) | 4 | |-|-|-| 5 | | [11,880 DAI + 2,160 DORG](https://docs.google.com/spreadsheets/d/1mwYhzTNXSytzVtACZLu1V_EVTfjPKhGfHu-KhnBFESk/edit#gid=318900412) | 12 Weeks (May 3 - July 30) | Ernesto, Diego | 6 | 7 | ## Summary 8 | This DSP funds all marketing & communications efforts including social media management, content creation, communication materials such as decks or slides, event management, search engine optimization, and talent recruitment. At the end of each MarComms DSP, we'll deliver a report with the relevant metrics and highlights from the month. 9 | 10 | Purpose 11 | - Position dOrg as a thought leader in our space 12 | - Associate dOrg with keywords (DAOs, NFTs, DeFi) 13 | - Build community 14 | - Build brand awareness 15 | - Increase website KPIs such as visits, leads 16 | - Increase number of talent applications by qualified builders (tech & non-tech) 17 | 18 | ## Why should we fund this? 19 | 20 | 1. Having a robust online presence will solidify dOrg’s brand, and will increase our likelihood to close client projects and attract and retain top-tier talent. 21 | 2. High-Value Content is an excellent vehicle for thought-leadership, decentralization is a relatively new space and as a first-mover this creates an ideal opportunity to remain a leader in the space through original content generation. 22 | 3. Content will make it easier for members to talk and communicate about dOrg to friends, family, coworkers, prospective clients, and the community at large. 23 | 4. Every content initiative will be measured and tracked so as to be able to get a sense of which initiative is driving the most value, and optimize against it. 24 | 5. Ultimately, we want dOrg to have a strong presence in the blockchain space, and solidify its leadership position as the go-to for all things Web3 - which can be achieved if we begin to generate long-lasting favorability starting today. 25 | 26 | ## KPIs 27 | * Net Follower Growth % 28 | * Engagement Rate % 29 | * Unique Visitors 30 | * Views 31 | * Impressions 32 | * Reach 33 | * Number of Leads (Clients) 34 | * Number of Leads (Talent) 35 | * Client Leads Growth % 36 | * Talent Leads Growth % 37 | 38 | ## Anything else you'd like to add? 39 | 40 | ### Content Features 41 | - Builder profiles (monthly) 42 | - Project highlights (monthly) 43 | - State of dOrg (quarterly) 44 | 45 | ### Social Media Management 46 | - Create and manage social calendar 47 | - Optimize content for social distribution 48 | - Actively engage / reply to users 49 | 50 | ### Content Creation 51 | Create high-value content in multiple formats including text, video, images, and audio, then formatting it to be distributed across multiple digital channels including blog, messaging, and social. Content will associate dORG with relevant keywords such as DAOs, NFTs, DeFi, etc. 52 | 53 | ### Communication Materials 54 | - Talent outreach deck 55 | - Onboarding deck 56 | 57 | ### Event Management 58 | - Support event activation 59 | - Creating visuals, decks, and other comms materials 60 | - Event promotion and outreach 61 | - On Demand content 62 | 63 | ### Search Engine Optimization 64 | - Keyword research 65 | - Blog creation 66 | - Google Analytics implementation 67 | 68 | ### Talent Recruitment 69 | - Creation and posting on Job Boards in Blockchain related websites 70 | - LinkedIn Optimization 71 | - LinkedIn Job Posts 72 | - Talent sourcing and engagement 73 | - Outreach through Discord communities 74 | 75 | ### Community and Onboarding 76 | - Engage with Discord members 77 | - Engage with other Discords 78 | - Onboarding process for new members 79 | - Efforts to improve overall onboarding experience 80 | 81 | ### Other Responsibilities 82 | - Setting up a brand tracker 83 | - Ecosystem mapping 84 | - Media/Press (magazines, youtubers, podcasts, etc.) 85 | 86 | ### Accountability 87 | - Updates at Biweekly Syncs 88 | - End of month recaps 89 | 90 | ## Cost Breakdown 91 | 92 | | Item | Description | $/Hr | Hrs | Cost | 93 | |-|-|-|-|-| 94 | | *Core Work* | Marketing and communication activities including social media management, content creation, communication materials, event management, search engine optimization, talent recruitment, onboarding of new members, community building, and any other MarComm related task. | $65 | 15*12 | $11,700 | 95 | | *Builder Incentive* | Compensate builders for their time getting interviewed, making themselves available for content production | $65 | 3*12 | $2,340 | 96 | | | | TOTAL | 216 | $14,040 | 97 | 98 | Payment proposal will be done at the end of each month 99 | - May 31, 2021 (Work performed May 3 - May 30) @ $1,170 x week = $4,680 (3960 DAI, 720 DORG) 100 | - June 30, 2021 (Work performed May 31 - June 29) @ $1,170 x week = $4,680 (3960 DAI, 720 DORG) 101 | - July 30, 2021 (Work performed June 30 - July 29) @ $1,170 x week = $4,680 (3960 DAI, 720 DORG) -------------------------------------------------------------------------------- /.archive/DSPs/19-QA-Upgrade.md: -------------------------------------------------------------------------------- 1 | # Quality Assurance Upgrade 2 | 3 | | Budget | Term | Lead (hr/wk ) | Builders (hr/wk) | 4 | |-|-|-|-| 5 | | [18,360 DAI + 2,880 DORG]() | 12 Weeks (May 18 - Aug 9, 2021) | Magenta (2-6) | Leif (3-5) Ori (4-6) Jessica (2-3) Jesse (1-2) | 6 | 7 | ## Summary 8 | 9 | Building on our success from the [Quality Engagement DSP](https://github.com/dOrgTech/Ops/blob/master/DSPs/006-Onboarding-%26-Engagement.md), which focused on improving the recruitment and onboarding experience, the next period will focus on designing a set of quality assurance practices to integrate into the lifecycle of every client project. 10 | 11 | ## Why should we fund this? 12 | 13 | Now that we have a growing community of quality builders, our biggest bottleneck to sustainable growth is the quality of our work. By optimizing the Quality Assurance process across all dOrg projects, we can greatly improve our retention, as well as client and builder happiness. 14 | 15 | These processes will allow our teams to consistently achieve a high quality of work and internalize new lessons, fueling reflexive, iterative & cohesive growth across the entire DAO. 16 | 17 | ## Anything else you'd like to add? 18 | 19 | Our primary focus will be to improve and standardize the... 20 | 21 | * Project initiation process 22 | - Screening clients & scoping technical requirements 23 | - Drafting an SoW 24 | - Forming a team 25 | - Approving the project 26 | * Project management practices 27 | - Setting expectations & resolving difficult situations 28 | - Ongoing QA processes 29 | - Client invoicing & builder outvoicing 30 | - Client & builder feedback flows 31 | 32 | At a high-level we intend for this workstream to cover the remaining elements in the quality engagement roadmap: 33 | - [x] Builder recruiting (outreach, activation, onboarding) 34 | - [ ] Client sourcing (screening, scoping, team formation, closing) 35 | - [ ] Client happinness (quality assurance, invoicing) 36 | - [ ] Builder happinness (upskilling, flex time, outvoicing) 37 | 38 | ## Cost Breakdown 39 | 40 | | Item | Description | $/Hr | Hrs | Cost | 41 | | --------------------- | ----------------------------------------------------------- | -------- | ---- | ------- | 42 | | *Process Improvement* | Research, design, and build processes for quality assurance | $75 | 22*12| $19,800 | 43 | | *Interviews* | Interview other builders | $60 | 2*12 | $1,440 | 44 | | | Total | TOTAL | 288 | $21,240 | -------------------------------------------------------------------------------- /.archive/LICENSE.txt: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2019 - dOrg, LLC 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. -------------------------------------------------------------------------------- /.archive/Operating_Agreement_Updated_2019.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/Operating_Agreement_Updated_2019.pdf -------------------------------------------------------------------------------- /.archive/Participation_Terms_And_Conditions_Updated_2019.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/Participation_Terms_And_Conditions_Updated_2019.pdf -------------------------------------------------------------------------------- /.archive/activation.md: -------------------------------------------------------------------------------- 1 | # dOrg Activation Challenge 2 | > Join dOrg by doing what you're best at! 3 | 4 | [More Information Here](https://docs.dorg.tech/lifecycle/activation) 5 | 6 | ## Examples 7 | 1. [Micro DAO](https://github.com/dOrgTech/mini-hack-example) by Jordan 8 | 2. [Agent Availability Bot](https://github.com/dOrgTech/AgentAvailability/) by Ben 9 | 3. [Proposal Listening Bot](https://github.com/linus-stark/dOrg_activation) by Linus 10 | 4. [Decentralized Product Management Spec](https://docs.google.com/document/d/1r3SYoIONQ3pWmyFLaUE68XIvpwC1tcOv9ABPxguHFzk/edit) by Jesse 11 | 5. [DAO Launcher Tutorial](https://twitter.com/Ingalandia/status/1237525857981218816) by Ingamar 12 | 6. [Wallet Balance Data Science Notebook](https://www.linkedin.com/pulse/exploring-ethereum-blockchain-bigquery-python-henriquez-perozo/?trackingId=voaeJu9BSjmJJuuSszPpGA%3D%3D) by Roberto 13 | 7. [Prototype for Decentralized Finance of On-the-Ground Communities](https://docs.google.com/document/d/1DX0P21g2kAkAR8KwqkDbNzMcwiiKfFLDfjazvHQwx2A/edit?usp=sharing) by Magenta 14 | 8. [OpenRaise “v2”: Improvement Proposals](https://docs.google.com/document/d/1JR23RbB4XujKOCmBZM969wwpykTbBXkD0HHXRgE1xKA/edit?usp=sharing) by Phil 15 | 9. [Web3API Home Page Redesign](https://drive.google.com/drive/folders/1cjWIU3T4kRsHDQC4Vcg-9iSW2fpWvQ7r) by Duvan 16 | 10. [Voter Participation Visualizer](https://github.com/c0rv0s/voter-participation) by Nate 17 | 11. [Rep Flow Visualization](https://github.com/krisbitney/RepFlowVisualization) by Kris 18 | 12. [BaseDAO](https://github.com/stan36/BaseDAO) by Chris 19 | 13. [Video Concepts](https://docs.google.com/document/d/1QufLe3HBsSTzYp4ZSqti8_e5QIQjVZmGMeELTReNEnc/edit?usp=sharing) by David 20 | 14. [Mobility Ads DAO](https://github.com/imthatcarlos/mobility-ads-dao) by Carlos 21 | 15. [Decentralized Autonomous Record Network](https://docs.google.com/document/d/1dieQq5R2uONbdGNZc99M5pHbfP4jVMJ6q8f2UHf-MU0/edit) by Bernardo 22 | 16. [Virtual Game Items](https://github.com/Remscar/dOrg-Activation) by Zachary 23 | 17. [DAO message board app](https://github.com/LPSCRYPT/dpost-alpha) by Louis 24 | 18. [DAO contract visualization & NFT marketplace](https://github.com/Calvinoea/activation-challenge) by Calvin 25 | 19. [Builder referral reward model](https://www.notion.so/dOrg-writeup-d8c190e23cc34f989e9023dfd2a31029) by Ron 26 | 20. [Web3 Payroll App](https://github.com/nestorbe/payrollTS) by Nestor B. 27 | 20. [Mobile design for Balancer Exchange dApp](https://www.figma.com/file/i6MokLTORQKexECogLMUCw/Balancer-Mobile) by Alana 28 | 21. [EtherealIce](https://github.com/MQDuck/EtherealIce-Contract) by Jeff 29 | 22. [Flash Loan Swap](https://github.com/reddyismav/flash-loan-swap/tree/master) by Vamsi 30 | 23. [Popcorn DAO](https://docs.google.com/document/d/1bNM4oYOqyJ9C28PcnUJBhdDDoHogaOwtSLoY-dBkPxg/edit) by Anthony 31 | 24. [DAO Browser](https://github.com/MountVase/DAObrowser) by Markus 32 | 25. [dOrg Rebrand](https://drive.google.com/file/d/1WkMceH9x7pGPj9E-AwIkvz0ItSgUWBcP/view) by Lauren 33 | 26. [Comms Campaign](https://docs.google.com/document/d/1BRpqB8oKOuHBPssn5U9JhqdkHm3bUnUvMa3311ZIkK8/edit) by Ernesto 34 | 27. [Simplifying DAO Creation](https://app.pitch.com/app/public/presentation/05805f01-a1ce-4c19-a98c-b417c47f42a3) by Colin 35 | 28. [Timekeeper dApp](https://youtu.be/X6DaodcpBoU) by Bhanu 36 | 29. [Proposal Creator](https://github.com/MatthiasBakken/proposal-creator) by Matthias 37 | 30. [Voting History on DAOStack Profile](https://docs.google.com/document/d/1LZCCElaFSaG69v8AJPlMvEv6CAmeUrsHa-qiszlBbbQ/edit?usp=sharing) by Robert 38 | 31. [NFT Lootbox](https://github.com/beyond7/nft-lootbox) by James 39 | 32. [NFT Avatars](https://github.com/Niraj-Kamdar/NFT-Avatars) by Niraj 40 | 41 | ## Additional Ideas 42 | - **Visualization** of dOrg proposal, token or Rep flows 43 | - Simple **front-end** for interacting with the dOrg DAO 44 | - Minimum viable DAO **smart contract** 45 | - Wireframe **design** for a new DAO dashboard 46 | - **Product** spec for a new web3 tool 47 | - Short **research** report on DAO frameworks 48 | - **Business** plan for DAO adoption in a particular sector/use-case 49 | - Article, video, artwork or any type of **content** that explains DAOs or dOrg to a general audience. 50 | -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/2022.02.04 dOrg Governance model (1).jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/2022.02.04 dOrg Governance model (1).jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/2022.02.04 dOrg Governance model.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/2022.02.04 dOrg Governance model.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/2203_W9 Form.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/2203_W9 Form.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/91_discord_logo_logos-512.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/91_discord_logo_logos-512.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen Shot 2021-08-23 at 14.27.00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen Shot 2021-08-23 at 14.27.00.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen Shot 2021-08-23 at 14.33.49.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen Shot 2021-08-23 at 14.33.49.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen Shot 2021-08-27 at 14.17.23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen Shot 2021-08-27 at 14.17.23.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen Shot 2021-09-01 at 13.30.43.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen Shot 2021-09-01 at 13.30.43.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen Shot 2022-02-22 at 10.40.24 AM.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen Shot 2022-02-22 at 10.40.24 AM.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screen_Shot_2022-02-14_at_1.52.50_PM.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screen_Shot_2022-02-14_at_1.52.50_PM.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2021-08-25 at 14.56.58.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2021-08-25 at 14.56.58.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-01-03 at 17.55.47.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-01-03 at 17.55.47.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-01-03 at 18.01.07.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-01-03 at 18.01.07.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-01-13 at 17.20.11.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-01-13 at 17.20.11.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-03-07 at 16.12.16.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-03-07 at 16.12.16.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-04-08 at 17.36.23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-04-08 at 17.36.23.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Screenshot 2022-08-08 at 21.18.33.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Screenshot 2022-08-08 at 21.18.33.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Treasury Screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Treasury Screenshot.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Untitled-1 (1).jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Untitled-1 (1).jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Untitled-1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Untitled-1.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/Value Flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/Value Flow.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/banyan.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/banyan.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/blog-discord-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/blog-discord-logo.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/cell (1).jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/cell (1).jpeg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/cell.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/cell.jpeg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg Flywheel (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg Flywheel (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg Flywheel.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg Flywheel.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg Press Kit.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg Press Kit.zip -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg Structure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg Structure.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg estimated payments.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg estimated payments.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg-black-transparent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg-black-transparent.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg-color-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg-color-banner.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg-colored-black-bg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg-colored-black-bg.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg-colored-white-bg.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg-colored-white-bg.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dOrg-white-transparent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dOrg-white-transparent.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dorg-press-kit.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dorg-press-kit.zip -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/dorgs2.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/dorgs2.gif -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/faye-cornish-ggv3i6oxpcg-unsplash.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/faye-cornish-ggv3i6oxpcg-unsplash.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/flow of funds - feb 22 (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/flow of funds - feb 22 (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/flow of funds - feb 22 (2).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/flow of funds - feb 22 (2).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/flow of funds - feb 22.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/flow of funds - feb 22.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/flywheel - Feb 22.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/flywheel - Feb 22.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/google-workspace-logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/google-workspace-logo.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/growing-mushrooms-timelapse-3.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/growing-mushrooms-timelapse-3.gif -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/heartbeat.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/heartbeat.gif -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/icon.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | favicon 5 | Created with Sketch. 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/icon_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/icon_black.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/icon_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/icon_white.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (10).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (10).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (11) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (11) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (11).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (11).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (12).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (12).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (13).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (13).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (14).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (14).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (15).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (15).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (2) (1) (1) (1) (1) (1) (1) (1) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (22).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (22).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (23).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (23).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (24).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (24).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (27) (1) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (27) (1) (1) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (27) (1) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (27) (1) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (28).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (28).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (29).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (29).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (3).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (3).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (30).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (30).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (31).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (31).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (32).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (32).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (33).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (33).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (34).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (34).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (35).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (35).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (5).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (5).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (6).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (6).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (9) (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (9) (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image (9).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image (9).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/image.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/image.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen (2).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen (2).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen (3).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen (3).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen (4).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen (4).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen (7).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen (7).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen (8).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen (8).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/imagen.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/imagen.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/legal.dorg.1.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/legal.dorg.1.pdf -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/legal.dorg.1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/legal.dorg.1.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_background_black (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_background_black (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_background_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_background_black.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_background_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_background_white.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_black (1).png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_black (1).png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_black.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_black.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/logo_white.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/logo_white.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/maxresdefault.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/maxresdefault.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/membrane.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/membrane.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/neurons.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/neurons.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/plant2.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/plant2.gif -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/pumpflow.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/pumpflow.gif -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/rainbow_banner.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/rainbow_banner.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/rainbow_logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/rainbow_logo.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screen-shot-2021-08-23-at-14.27.00.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screen-shot-2021-08-23-at-14.27.00.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screen-shot-2021-08-23-at-14.33.49.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screen-shot-2021-08-23-at-14.33.49.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screen-shot-2021-08-25-at-10.05.12.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screen-shot-2021-08-25-at-10.05.12.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screen-shot-2021-08-27-at-14.17.23.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screen-shot-2021-08-27-at-14.17.23.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screen-shot-2021-09-01-at-13.30.43.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screen-shot-2021-09-01-at-13.30.43.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/screenshot-2021-08-25-at-14.56.58.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/screenshot-2021-08-25-at-14.56.58.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/undraw_quite_town_mg2q.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/undraw_quite_town_mg2q.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/undraw_vault_9cmw.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/undraw_vault_9cmw.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/unit economics.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/unit economics.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/unit-economics.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/unit-economics.png -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/unnamed.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/unnamed.jpg -------------------------------------------------------------------------------- /.archive/handbook/.gitbook/assets/value-flow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/.archive/handbook/.gitbook/assets/value-flow.png -------------------------------------------------------------------------------- /.archive/handbook/README.md: -------------------------------------------------------------------------------- 1 | # Welcome to dOrg! 2 | 3 | ![](https://i.gifer.com/3t5T.gif) 4 | 5 | ### What is dOrg? 6 | 7 | dOrg is an autonomous collective of web3 engineers, creatives, and operators. We build tools that empower people to self-organize. 8 | 9 | We envision a future where power is radically decentralized – people can easily coordinate and transact without intermediaries; institutions are transparent and responsive to their constituents; self-governing collectives outcompete coercive monopolies; ownership is widely distributed; and machines handle the boring work while humans focus on meaningful pursuits. 10 | 11 | We believe that web3 will be a key part of this future and we’re here to build it. 12 | 13 | ### How? 14 | 15 | dOrg simultaneously serves as a... 16 | 17 | * **Community for talented builders** to earn, learn, and cultivate autonomy while working on bleeding edge tech; 18 | * **Service provider for high-potential projects** to accelerate development with minimal friction; and 19 | * **Open-source template** for aspiring collectives to fork and iterate upon. 20 | 21 | Several mutually-reinforcing feedback loops propel our progress: 22 | 23 | ![Feed any part to accelerate the whole](<.gitbook/assets/dOrg Flywheel (1).png>) 24 | 25 | ### Our Values 26 | 27 | * **Autonomous Action** - We encourage each other to pursue initiatives in good faith rather than waiting for others to act or seeking approval. 28 | * **Transparency** - We guarantee all members equal access to organizational information, including financial data, legal documents, and internal processes. 29 | * **Participatory Meritocracy** - We distribute governance rights and rewards based on value contributed, not titles or hierarchy. 30 | * **Inclusion & Respect** - We foster a diverse membership and support one another in maintaining a healthy digital workplace. 31 | 32 | ![](https://miro.medium.com/max/1000/1\*5WIVZ1eZQ8G2ITihkYI2SQ.gif) 33 | 34 | {% hint style="danger" %} 35 | dOrg is a living, breathing system that evolves faster than this handbook. Proceed with caution. 36 | {% endhint %} 37 | -------------------------------------------------------------------------------- /.archive/handbook/SUMMARY.md: -------------------------------------------------------------------------------- 1 | # Table of contents 2 | 3 | * [Welcome to dOrg!](README.md) 4 | * [Structure](structure.md) 5 | * [Member Covenant](covenant.md) 6 | 7 | ## Member Lifecycle 8 | 9 | * [Applying](lifecycle/applying.md) 10 | * [Onboarding](lifecycle/onboarding.md) 11 | * [Building & Chilling](lifecycle/member-status.md) 12 | * [Removal](lifecycle/removal.md) 13 | 14 | ## Workflows 15 | 16 | * [Navigating our Channels](workflows/navigating.md) 17 | * [Doing Internal Work](workflows/doing-internal-work/README.md) 18 | * [Funded initiatives](workflows/doing-internal-work/funded-initiatives.md) 19 | * [Joining a Client Project](workflows/joining.md) 20 | * [Sourcing a New Client Projects](workflows/sourcing.md) 21 | * [Being a Coordination Lead](workflows/coordination-lead.md) 22 | * [Being a QA Lead](workflows/qa-lead.md) 23 | * [Billing](workflows/billing.md) 24 | * [Reimbursing Expenses](workflows/expense-reimbursement-policy.md) 25 | * [Events](workflows/events.md) 26 | 27 | ## Resources 28 | 29 | * [Important Links](resources/links.md) 30 | * [Development Best Practices](resources/best-practice-overview/README.md) 31 | * [Git](resources/best-practice-overview/git.md) 32 | * [Code Reviews](resources/best-practice-overview/doing-a-code-review.md) 33 | * [Creating a React dApp](resources/best-practice-overview/react-dapp.md) 34 | * [Choosing a hosting platform](resources/best-practice-overview/choosing-a-hosting-platform.md) 35 | * [Tests](resources/best-practice-overview/tests.md) 36 | * [Getting Stuff Done in a DAO](resources/getting-stuff-done-in-a-dao.md) 37 | * [Upskilling](resources/upskilling.md) 38 | * [Press Kit](resources/press-kit.md) 39 | * [Social Media Guidelines](resources/social-media.md) 40 | * [Referral Program](resources/referral-program.md) 41 | * [Quarterly dOrg Tax Payments](resources/quarterly-dorg-tax-payments.md) 42 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/best-practice-overview.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: These are the developments standards of dOrg. 3 | --- 4 | 5 | # Best practice overview 6 | 7 | ### dApp 8 | 9 | * React should always be your tool to develop a dApp unless there's an explicit reason to not do it 10 | * Use typescript always, never use vanilla javascript 11 | * Use linter \(ESLint + Prettier is the default in TS\) 12 | * For styles in react, Styled Components or CSS-in-JS is a must, unless its an Angular or Vue project 13 | * Configure husky \(Attach linter to pre commit hooks so the code is the same for all the developers on the project\) 14 | * The suite of tests of the integrations is a must and should always aim to also test the UI components, but we can be flexible with it 15 | 16 | ### Smart contracts 17 | 18 | * Use hardhat to develop your contracts 19 | * [NatSpec](https://docs.soliditylang.org/en/v0.8.7/natspec-format.html) is a must, this way it's easier when it comes to audit and to people that want to understand the code 20 | * Tests must be implemented and cover at **least** 90% of the code. [Solidity Coverage](https://github.com/sc-forks/solidity-coverage) is an excellent tool that will help you to check exactly which lines are missing 21 | * Use linter \(Prettier and [Solhint](https://github.com/protofire/solhint)\) - Note that solhint gives you lint and security validations 22 | * Good documentation. Beside of natspec and the tests, good markdown files explaining what the Smart Contracts are trying to achieve is really important; this way, the developer can give an overview of how the contracts works, hence, making it easier for auditors/other developers to collaborate and/or review 23 | * Use libraries in order to implement standards whenever possible, especially Open Zeppelin 24 | * If you are using a solidity version lower than `0.8`, make sure you use `SafeMath` in order to avoid under/overflows 25 | * Attack vectors to be aware of: [https://github.com/crytic/building-secure-contracts](https://github.com/crytic/building-secure-contracts) 26 | * This should be every SC dev's bible: [https://consensys.github.io/smart-contract-best-practices/](https://consensys.github.io/smart-contract-best-practices/) 27 | 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/choosing-a-hosting-platform.md: -------------------------------------------------------------------------------- 1 | # Choosing a hosting platform 2 | 3 | There are numerous hosting and deployment services available online that can run your app from. Below is a comparative list of the most typically used at dOrg: 4 | 5 | ### Netlify 6 | 7 | {% embed url="https://www.netlify.com/" %} 8 | 9 | Best for: 10 | 11 | * Front end/React applications 12 | 13 | Pros: 14 | 15 | * Very fast/easy configuration for hosting and DNS 16 | * Free SSL 17 | * Automatic deployment of PRs on staging site without needing a CI/CD 18 | * Automated deployments without needing a CI/CD 19 | * Serverless functions 20 | 21 | Cons: 22 | 23 | * Doesn't have Docker support 24 | * Doesn't support Database management \(except for their own FaunaDB\) 25 | 26 | Beware: 27 | 28 | * For CRA Applications to work properly with React Router: [https://stackoverflow.com/a/55990523](https://stackoverflow.com/a/55990523) 29 | 30 | ### Heroku 31 | 32 | {% embed url="https://www.heroku.com/" %} 33 | 34 | Best for: 35 | 36 | * Dockerized applications 37 | * Database hosting 38 | 39 | Pros: 40 | 41 | * Very fast/easy configuration for hosting and DNS 42 | * Docker support 43 | * Automated deployments, even with Docker, without needing a CI/CD 44 | * Database management 45 | 46 | Cons: 47 | 48 | * Its free tier "sleeps" when idle. That means that your hosted application will have downtime, don't use this plan on production 49 | * No serverless functions 50 | * No automated PR deployment 51 | 52 | Beware: 53 | 54 | * Free tier's sleep 55 | * For CRA Applications to work properly: [https://stackoverflow.com/questions/50327645/deploy-production-of-create-react-app-to-heroku-without-buildpacks](https://stackoverflow.com/questions/50327645/deploy-production-of-create-react-app-to-heroku-without-buildpacks) 56 | 57 | ### Vercel 58 | 59 | [https://vercel.com/](https://vercel.com/) 60 | 61 | Best for: 62 | 63 | * NextJS applications 64 | 65 | Pros: 66 | 67 | * Very fast/easy configuration for hosting and DNS 68 | * Out of the box support for NextJS 69 | * Automatic deployment of PRs on staging site without needing a CI/CD 70 | * Automated deployments without needing a CI/CD 71 | * Serverless functions 72 | 73 | Cons: 74 | 75 | * No docker or database support 76 | 77 | ### AWS 78 | 79 | {% embed url="https://aws.amazon.com/" %} 80 | 81 | Best for: 82 | 83 | * Application with multiple docker files, or with docker-compose 84 | * A very custom infrastructure is needed \(multiple dbs, or apis\) 85 | 86 | Pros: 87 | 88 | * No limits, can set up any services you want 89 | 90 | Cons: 91 | 92 | * It is not really easy to use so you need to educate yourself in order to use it 93 | * Paid service 94 | * You need to manually configure CI with Github Actions or any other CI/CD pipeline 95 | 96 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/creating-a-react-dapp.md: -------------------------------------------------------------------------------- 1 | # Creating a React dApp 2 | 3 | ## Set up initial project structure 4 | 5 | There are lots of great initial scaffolding repositories, like [Scaffold-ETH](https://github.com/austintgriffith/scaffold-eth#-scaffold-eth). For a more lightweight CRA scaffolding version, with Typescript and linting configured, and dOrg's preffered libraries check out [React-Dapp-Boilerplate](https://github.com/dOrgTech/react-dapp-boilerplate). Feel free to use the initial structure or scaffolding that best suits your needs 6 | 7 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/doing-a-code-review.md: -------------------------------------------------------------------------------- 1 | # Doing a code review for another project's team 2 | 3 | ## How to review 4 | 5 | The review should be done with the premise in mind that pull requests reflect the way of thinking of someone captured in form of code. Each person is unique and in software there's no such thing as unique solution, therefore review should be performed not only **objectively** but also **kindly**. 6 | 7 | Most discussions in the PR happen in an async nature that might have delay between responses, therefore, avoiding ambiguity in messages is encouraged. Conciseness can save ton of time. 8 | 9 | Reviews should aim for acceptance rather than perfection, have a high bar quality wise but also have reasonable limits. 10 | 11 | There's an [article](https://curtiseinsmann.medium.com/ive-code-reviewed-over-750-pull-requests-at-amazon-here-s-my-exact-thought-process-cec7c942a3a4) from [Curtis Einsmann](https://twitter.com/curtiseinsmann), a former AWS team lead, that really resembles the kind of code review that we find valuable the most, it is a recommended read. 12 | 13 | ## When to review 14 | 15 | At any moment the developers working on a project can ask for help and/or reviews from other devs of the organization. This process must be less frequent than the daily/periodic code review done internally by the project team, as it requires significantly more time and effort. 16 | 17 | **While this process may be really useful in certain circumstances, it should not be used to replace the need for a strong technical lead or to compensate a lower expertise team level than the project requires** 18 | 19 | ## **Type of reviews** 20 | 21 | We can differentiate two types of external builder reviews: **general/architectural review** and **feature review**. 22 | 23 | ### General Review 24 | 25 | A general code review entails a revision of the full/significant part of the project's codebase. 26 | 27 | **As a requester:** 28 | 29 | When requesting this kind of review, it's worth noting that the external builder who will perform the review does not know the specifics, nor the implementation details of the project, so the recommended process is as follows: 30 | 31 | 1. Reach out to the builder/builders to request for review 32 | 2. Schedule a time to have a call or chat to walk the reviewer through the codebase and the areas that need revision the most 33 | 34 | **Important information to share during the call:** 35 | 36 | * Project's deadlines 37 | * General architecture overview 38 | * Libraries being used in implementation 39 | * High level functionality desired 40 | 41 | **As a reviewer:** 42 | 43 | After this, the reviewer should: 44 | 45 | 1. Clone the project's repository 46 | 2. Checkout branch to review 47 | 3. Perform review and provide feedback 48 | 49 | Things to look out for when reviewing: 50 | 51 | * Does the codebase contain tests for core functionality? Do they all pass? 52 | * Is Feature Review 53 | 54 | ### Feature Review 55 | 56 | A feature code review entails a revision of a single feature/functionality of the project being developed. This is particularly helpful for unique, complex or uncommon patterns needed to achieve a feature. 57 | 58 | #### As a requester: 59 | 60 | The recommended process is as follows: 61 | 62 | 1. Open a Pull Request on GitHub that contains: 63 | * Description of high level functionality 64 | * Description of current approach and implementation 65 | * Steps to reproduce changes or test functionality 66 | * Related issues 67 | 2. Request for review through GitHub and reach out to builder for review. 68 | 69 | #### As a reviewer: 70 | 71 | The reviewer does not need to necessarily clone the project, but can perform a regular code review through GitHub diffs. 72 | 73 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/git.md: -------------------------------------------------------------------------------- 1 | # Git 2 | 3 | Git is the tool that allows developers to contribute in an easy way to the same code base of a project. 4 | 5 | Knowing the good practices of how to use git can save a lot of time when new changes are added, allowing the team to commit and review these in a comfortable way. Some of these good practices are: 6 | 7 | * **Explicit commit message**: When you commit something, the message should be explicit enough so any person that reads the message can know what the change is about. It should have the following structure: `topic: short description of what you did` an example of this can be`feat: implement authentication logic` or `chore: dependencies updated` 8 | * **New change, new branch:** Every time there's a code change, you need to create a new branch with an explicit name. It should have the following structure: `topic/title-of-changes` an example of this can be `feat/auth-logic` or `fix/swap-functionality` 9 | * **Changes should not be too big**: When developing a new feature, it's normal that the pull request gets big, you should push the code in multiple commits so if anything is broken, developers can find easier where the break was introduced 10 | * **Descriptive PRs**: When opening a PR, developer must add information on what's trying to be achieved with the changes proposed 11 | 1. A detailed description of what has been done 12 | 2. Link to issue \(GH Issue or task in Trello, for example\) 13 | 3. Steps of how to reproduce/test the new changes 14 | * **Remove old branches**: When developing as a team, it's normal that the old branches stays there forever - They should be cleaned sporadically, so it's easier to locate the active branches 15 | 16 | 17 | 18 | 19 | 20 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/upskilling.md: -------------------------------------------------------------------------------- 1 | # Upskilling Resources 2 | 3 | ### Learn with Others 4 | 5 | * [Gitcoin](https://gitcoin.co/learn) - kernel fellowship, hackathons, bounties 6 | * [Chainshot](https://www.chainshot.com) - bootcamp 7 | * [Consensys Academy](https://consensys.net/academy) - bootcamp 8 | * [ETHGlobal](https://ethglobal.co) - hackathons 9 | * [Enter Ethereum](https://discord.gg/cr7YGADDH3) - discord community 10 | * [Token Engineering Academy](https://tokenengineeringcommunity.github.io/website/docs/academy-welcome) - seminars 11 | 12 | ### Teach Yourself 13 | 14 | * [CryptoZombies](https://cryptozombies.io) 15 | * [Ethernaut](https://ethernaut.openzeppelin.com/) 16 | * [ETH.Build](https://eth.build/) 17 | * [Ethereum Dev Speed Run](https://medium.com/@austin_48503/%EF%B8%8Fethereum-dev-speed-run-bd72bcba6a4c) 18 | * [The Complete Guide to Full Stack Ethereum Development](https://dev.to/dabit3/the-complete-guide-to-full-stack-ethereum-development-3j13) 19 | * [Learning Solidity](https://github.com/willitscale/learning-solidity) 20 | * [Ethereum and Solidity: The Complete Developer's Guide \(Udemy\)](https://www.udemy.com/course/ethereum-and-solidity-the-complete-developers-guide/) 21 | * [Discover Ethereum & Solidity \(Ludu\)](https://www.ludu.co/course/ethereum/what-is-ethereum) 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /.archive/handbook/builder-resources/web3-glossary.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | This resource is meant to ease the learning curve for anyone interested in 4 | Web3. 5 | --- 6 | 7 | # Web3 Glossary 8 | 9 | ![](../.gitbook/assets/image%20%2815%29.png) 10 | 11 | ## Open Source 12 | 13 | > Software for which the original source code is made **freely available** and **may be redistributed and modified.** 14 | > 15 | > Many great projects are developed under an open source model, where developers, community members, and users come together to build and improve a product. 16 | 17 | * [Wikipedia](https://en.wikipedia.org/wiki/Open-source_software) 18 | * Examples of open source projects: 19 | * Linux \(Operating system\) 20 | * Python \(High-level programming language\) 21 | * PostgreSQL \(Relational query and database language\) 22 | * Word Press \(Content management system for web\) 23 | * Drupal \(Content management system\) 24 | 25 | ## Web3 26 | 27 | ![](https://lh6.googleusercontent.com/WOaT5LWvKxh9eUP6RJ5Ts3js_wgvezRhoErRTouMz_8i9YS8yPiP88NbcvfWXPSy0Rgw0E30z3NhANRdZdFq0k2E2k27ThWaxP4tRfrsCI0cl0TZba2kqpPWtbLJdquuuCKgLU27) 28 | 29 | > **Web3** is the vision of the serverless internet, a decentralized web. An internet where users are in control of their own data, identity, and destiny. 30 | 31 | * [What is Web3?](https://www.youtube.com/watch?v=l44z35vabvA) \(30 Minutes \| Youtube\) 32 | * [From Web 1.0 to Web3: How the Internet Grew Over The Years](https://hackernoon.com/from-web-10-to-web3-how-the-internet-grew-over-the-years-zac032g1) \(Hackernoon\) 33 | 34 | ## Ethereum 35 | 36 | ![](../.gitbook/assets/image%20%2827%29%20%281%29%20%281%29%20%281%29.png) 37 | 38 | > **Ethereum** is a decentralized platform that runs **smart contracts**: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference. 39 | 40 | * [Wikipedia](https://en.wikipedia.org/wiki/Ethereum) 41 | * [Ethereum for dummies](https://hackernoon.com/ethereum-for-dummies-af5aeacb13d4) \(Hackernoon\) 42 | 43 | ## Smart Contract 44 | 45 | ```javascript 46 | pragma solidity ^0.4.0; 47 | 48 | contract SimpleStorage { 49 | uint storedData; 50 | 51 | function set(uint x) public { 52 | storedData = x; 53 | } 54 | 55 | function get() public view returns (uint) { 56 | return storedData; 57 | } 58 | } 59 | ``` 60 | 61 | > A **smart contract** is a self-executing agreement where the terms are directly written into a computer program that is deployed to a blockchain. 62 | 63 | * [Blockchain and smart contracts](https://www.youtube.com/watch?v=B3cSoWoAkI4) \(7 Minutes \| Youtube\) 64 | * [What are smart contracts?](https://cointelegraph.com/ethereum-for-beginners/what-are-smart-contracts-guide-for-beginners) \(Cointelegraph\) 65 | * [What is Solidity?](https://www.youtube.com/watch?v=3i203iTmcFc) \(2 Minutes \| Youtube\) 66 | 67 | ## Gas 68 | 69 | ![In the Ethereum blockchain, "Gas" is an abstraction of the resources needed to "write" data.](../.gitbook/assets/image%20%2831%29.png) 70 | 71 | > **Gas** is the pricing value required to **conduct a transaction** or **execute a contract** on the Ethereum blockchain platform. It can be seen as a **fee** that any user pays when **writing** information into the Ethereum network; this could be a transaction, a deployment of a smart contract, sending a proposal to an organization, just to mention a few. The price of Gas is set by the market \(supply and demand\), and varies over time. 72 | 73 | * [What is Ethereum Gas?](https://www.ethos.io/what-is-ethereum-gas/) \(Ethos\) 74 | 75 | ## Wallet 76 | 77 | ![Different wallets can hold different crypto assets, such as Ether or ERC20 Tokens](../.gitbook/assets/image%20%2813%29.png) 78 | 79 | > A **cryptocurrency wallet** is a device, physical medium, program or a service which stores **public and private keys** and can be used to track ownership, receive or spend **cryptocurrencies**. 80 | 81 | * [Intro to Ethereum Wallets](https://docs.ethhub.io/using-ethereum/wallets/intro-to-ethereum-wallets/) \(EthHub\) 82 | * [Metamask](https://metamask.io/index.html) 83 | 84 | {% hint style="info" %} 85 | There are many wallet providers other than Metamask. We encourage you to do your research to find the one that best suits your needs. 86 | {% endhint %} 87 | 88 | ## ERC20 Token 89 | 90 | ![Tokens are commonly used to represent value, like currency or assets.](../.gitbook/assets/image%20%283%29.png) 91 | 92 | > Ethereum **tokens** are digital assets built on top of the **Ethereum** blockchain. They can be **created by anyone** with access to the Ethereum network. The **ERC20** is the most popular standards for creating tokens on Ethereum. 93 | 94 | {% hint style="danger" %} 95 | Keep in mind that not all tokens hold value, nor are backed by any type of collateral. Be cautious when accepting payments in tokens, as anyone can create their own. As of June 2020 there are nearly 200,000 different tokens registered on the Ethereum Blockchain, the vast majority of which hold no "market value." 96 | {% endhint %} 97 | 98 | * [ERC20 Tokens, Simply Explained](https://www.youtube.com/watch?v=cqZhNzZoMh8) \(6 Minutes \| YouTube\) 99 | * [The ERC20 standard](https://eips.ethereum.org/EIPS/eip-20) \(Ethereum Improvement Proposal\) 100 | 101 | ## DAO 102 | 103 | ![DAOs are normally organized by members who work together to achieve a common goal.](../.gitbook/assets/image%20%285%29.png) 104 | 105 | > A **Decentralized Autonomous Organization** \(DAO\) supports itself on multiple **smart contracts** to perform its functions. This type of organization is represented by **rules** encoded as a computer program that is **transparent**, controlled by **stakeholders**, and **not influenced** by a central government. Anyone with an Ethereum Wallet can interact with a DAO. 106 | 107 | * [What is a DAO?](https://hackernoon.com/what-is-a-dao-c7e84aa1bd69) \(Hackernoon\) 108 | * [What is a DAO?](https://www.youtube.com/watch?v=JcPNO0o_Cng) \(5 Minutes \| Youtube\) 109 | * [Wikpedia](https://en.wikipedia.org/wiki/Decentralized_autonomous_organization) 110 | * [What We Talk About When We Talk About DAOs](https://www.youtube.com/watch?v=RkN7-UcpC4A) \(1 hr \| Youtube\) 111 | 112 | -------------------------------------------------------------------------------- /.archive/handbook/covenant.md: -------------------------------------------------------------------------------- 1 | # Member Covenant 2 | 3 | We as dOrg members pledge to make participation in our community a positive experience for everyone. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. 4 | 5 | ## Our Standards 6 | 7 | Examples of behavior that contributes to a positive environment for our community include: 8 | 9 | * Demonstrating empathy and kindness toward other people 10 | * Assuming good intentions 11 | * Being respectful of differing opinions, viewpoints, and experiences 12 | * Giving and gracefully accepting constructive feedback 13 | * Taking ownership of our commitments and communicating changes with multiple weeks notice 14 | * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 15 | * Encouraging transparency and collaboration while preserving privacy where reasonably expected 16 | * Focusing on what is best not just for us as individuals, but for the overall community 17 | 18 | Examples of unacceptable behavior include: 19 | 20 | * Trolling, insulting or derogatory comments, and personal or political attacks 21 | * False accusations or accusations without evidence 22 | * Public or private harassment (repeated unwanted contact) 23 | * Spam (unsolicited off-topic messages) 24 | * Sexually or violently explicit content 25 | * Silencing others (e.g. deleting innocuous comments) 26 | * Retaliatory work stoppage or public defamation 27 | * Persistently missing meetings without notice 28 | * Ghosting clients or teammates 29 | * Other conduct which could reasonably be considered inappropriate in a professional setting 30 | 31 | ## Scope 32 | 33 | This Member Covenant applies within all dOrg spaces, including our forum, Discord, Snapshot, Github, and all other spaces associated with dOrg. This covenant also applies when an individual is representing dOrg in public spaces, such as using an official email address, social media account, interacting with a client, or acting as a representative at an online or offline event. 34 | 35 | Anyone who infringes on this Member Covenant may be subject to our [member removal protocol](lifecycle/removal.md#proposing-removal). 36 | 37 | {% hint style="info" %} 38 | This Code of Conduct is adapted from the [Contributor Covenant v2.0](http://contributor-covenant.org/version/2/0/code\_of\_conduct). 39 | {% endhint %} 40 | -------------------------------------------------------------------------------- /.archive/handbook/glossary/dorg.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Core concepts defined 3 | --- 4 | 5 | # dOrg 6 | 7 | ![At dOrg we are creating "digital organisms"](../.gitbook/assets/dorgs2.gif) 8 | 9 | **dOrg** - a self-service web3 development agency; structured as a reputation-weighted DAO with legal personality 10 | 11 | **Reputation** - voting weight on proposals to the DAO; non-transferrable 12 | 13 | **DORG Token** - token issued by the DAO to track unpaid obligations 14 | 15 | **Proposal** - basic unit of decision-making for any DAO action \(payments, adding/removing Rep, issuing Tokens, ratifying agreements, modifying the DAO, and more\) 16 | 17 | {% hint style="info" %} 18 | Anyone can **submit** a proposal to the DAO. Anyone with reputation in the DAO can **vote** to approve or reject a proposal. All votes are be **publicly visible** in the [Ethereum](web3.md#ethereum) Blockchain. If the proposal **passes**, anyone can **execute** the action specified. 19 | 20 | Submitting, voting and executing proposals costs [Gas](web3.md#gas). 21 | {% endhint %} 22 | 23 | **DAOstack** - Ethereum-based DAO framework that dOrg is built on \([mainnet](https://alchemy.daostack.io/dao/0x15344ecdc2c4edfcb092e284d93c20f0529fd8a6), [xDAI](https://v1.alchemy.do/dao/0x94a587478c83491b13291265581cb983e7feb540/scheme/0xca275b54cf9e9afc2317778e3e294e01a5b25ce9e082043b64a5cc7f4c4ec2f9)\) 24 | 25 | **Builder** - anyone who holds reputation in the DAO; can be active or inactive; [view all active builders here](https://dorg.tech/membrane/) 26 | 27 | **Client** - entities who contract dOrg for web3 development services 28 | 29 | **3rd Party** - external entities that dOrg interacts with for services \(SaaS, accountants, lawyers, governments\) 30 | 31 | **Spaces** - tools utilized by active builders to synchronize workflows 32 | 33 | **Sync** - biweekly call for active builders 34 | 35 | **Open House** - open quarterly call to reflect on progress and welcome newcomers 36 | 37 | **org.json** - file that defines dOrg's global state variables 38 | 39 | ## Feedback 40 | 41 | {% hint style="success" %} 42 | We hope that this Handbook helped you better understand **dOrg** and the **Web3** ecosystem. 43 | 44 | If you have any additional comments or ideas to improve this handbook, [please let us know](https://airtable.com/shrU1YVridSPAlIHP)! 45 | {% endhint %} 46 | 47 | -------------------------------------------------------------------------------- /.archive/handbook/governance/covenant.md: -------------------------------------------------------------------------------- 1 | # Builder Covenant 2 | 3 | We as dOrg builders pledge to make participation in our community a positive experience for everyone. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. 4 | 5 | ## Our Standards 6 | 7 | Examples of behavior that contributes to a positive environment for our community include: 8 | 9 | * Demonstrating empathy and kindness toward other people 10 | * Assuming good intentions 11 | * Being respectful of differing opinions, viewpoints, and experiences 12 | * Giving and gracefully accepting constructive feedback 13 | * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience 14 | * Encouraging transparency and collaboration while preserving privacy where reasonably expected 15 | * Focusing on what is best not just for us as individuals, but for the overall community 16 | 17 | Examples of unacceptable behavior include: 18 | 19 | * Trolling, insulting or derogatory comments, and personal or political attacks 20 | * False accusations or accusations without evidence 21 | * Public or private harassment \(repeated unwanted contact\) 22 | * Spam \(unsolicited off-topic messages\) 23 | * Sexually or violently explicit content \(NSFW\) 24 | * Retaliatory downstaking, work stoppage, or public defamation 25 | * Silencing particular voices by deleting innocuous comments 26 | * Other conduct which could reasonably be considered inappropriate in a professional setting 27 | 28 | ## Expectations of professionalism 29 | 30 | * Arrive to meetings at their start time. 31 | * Communicate in a timely manner to client and teammate requests. 32 | * Give 2 weeks notice prior to changing your availability on a project. 33 | 34 | ## Scope 35 | 36 | This Builder Covenant applies within all dOrg spaces, including our Discord, Alchemy, Github, Google Drive, and all other spaces associated with dOrg. This covenant also applies when an individual is representing dOrg in public spaces, such as using an official email address, social media account, or acting as a representative at an online or offline event. 37 | 38 | Anyone who infringes on this Builder Covenant may be subject to our Escalation Protocol. 39 | 40 | ## Escalation Protocol 41 | 42 | DAO members are generally encouraged to follow this escalation protocol for infringements of the Builder Covenant: 43 | 44 | 1. Contact the infringer to reach a private accord if possible. Perhaps there is a misunderstanding or willingness to immediately resolve the situation. 45 | 2. If this is not possible, report the infringement to a Mod \(someone in the top 50th percentile of reputation holders\), who can mitigate the immediate situation by removing the relevant comments as necessary. 46 | 3. Mod schedules mediation with a mutually agreeable arbiter. Mediation gives all affected a chance to share their sides of the story and attempt to reach an accord. 47 | 4. If mediation is unsuccessful, any affected party may submit to the DAO an enforcement action privately outlining evidence of infringement \(such as screenshots\) and proposed consequences with justification. DAO members are expected to review the submission, this covenant, and related past disputes in order to make a decision that aligns with the established norms and intention of the community. Possible consequences include: 48 | 49 | | Consequence | Description | Infringement | 50 | | :--- | :--- | :--- | 51 | | Temporary Ban | Removal from dOrg spaces, no interaction with the people involved, and partial slashing of reputation. After a specified period of time, the infringer can reclaim their slashed reputation and rejoin dOrg spaces by submitting a reactivation request that demonstrates a willingness to admit fault, apologize, rectify actions and avoid similar behavior in the future. | A serious infringement of community standards, including sustained inappropriate behavior. | 52 | | Indefinite Ban | Removal from dOrg spaces and slashing of all accumulated reputation. | Demonstrating a pattern of infringement of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. | 53 | 54 | If enforcement actions do not achieve DAO consensus, then the member is considered to be in good standing, regains any access to spaces they may have lost, and no further action is necessary. 55 | 56 | ## Attribution 57 | 58 | This Code of Conduct is adapted from the [Contributor Covenant v2.0](http://contributor-covenant.org/version/2/0/code_of_conduct). 59 | 60 | -------------------------------------------------------------------------------- /.archive/handbook/governance/global-variables.md: -------------------------------------------------------------------------------- 1 | # Community Details 2 | 3 | ## Shared Spaces 4 | 5 | | Tool | Purpose | 6 | | :--- | :--- | 7 | | [Discord](https://discord.com/invite/6Kujmad) | Chat | 8 | | [Discourse Forum](https://forum.dorg.tech/) | Deliberation & Coordination | 9 | | [Snapshot](https://snapshot.org/#/dorg.eth) | Voting | 10 | | [Gnosis Safe](https://gnosis-safe.io/app/#/safes/0xdb22d2d37db92EA7fa6993C9f6Ead55FBb1eF4EA/balances) | Fund Management | 11 | | [Github](https://github.com/dorgtech) | Code, Project Boards | 12 | | Airtable | CRM | 13 | | Google Workspace | Email, Calendar, Docs/Sheets/Slides | 14 | | [PandaDoc](https://app.pandadoc.com/a/#/templates-next?sortBy=name&direction=asc&displayMode=folders_first&mainFilter=all) | Client Project SoWs & E-signing | 15 | | [Gilded](https://app.gilded.finance/auth/login) | Invoicing & Bookkeeping | 16 | 17 | ## Recurring Events 18 | 19 | You will automatically be invited to the following optional events. 20 | 21 | | Name | Frequency | Purpose | 22 | | :--- | :--- | :--- | 23 | | All Hands Meetings | Biweekly | Discuss org-wide updates, ideas, or concerns | 24 | | Open House | Quarterly | Present updates to our broader community | 25 | 26 | At our All Hands Meetings we discuss proposals and recent DAO changes that need real-time dialogue, host tech talks and project deep-dives, and bring in interesting Web3 projects for 'show and tells'. 27 | 28 | {% hint style="info" %} 29 | Contact dOrg's Experience Facilitator for a calendar invite to our All Hands meetings. 30 | {% endhint %} 31 | 32 | ## Legal Details 33 | 34 | * dOrg, LLC 35 | * 76 St. Paul St, 7th Floor, P.O. Box 369 36 | * Burlington, VT 05402 37 | * Business ID: 0357139 38 | * Tax ID: 84-2930500 39 | 40 | -------------------------------------------------------------------------------- /.archive/handbook/governance/voting-power.md: -------------------------------------------------------------------------------- 1 | # Rep & Tokens 2 | 3 | ## Reputation \(Rep\) 4 | 5 | ![](../.gitbook/assets/image%20%2823%29.png) 6 | 7 | Reputation translates to **voting power**. Agents currently receive Rep with every dollar earned from the DAO according to the `rep-rate`. 8 | 9 | Reputation is **non**-**transferable**, and will always be associated with a **specific wallet address.** Anyone with Rep can **vote** on **proposals** sent to the DAO from their address. 10 | 11 | {% hint style="info" %} 12 | View dOrg's current reputation distribution on Alchemy \([mainnet](https://alchemy.daostack.io/dao/0x15344ecdc2c4edfcb092e284d93c20f0529fd8a6/members/), [xDAI](https://alchemy-xdai.herokuapp.com/dao/0x94a587478c83491b13291265581cb983e7feb540)\) 13 | {% endhint %} 14 | 15 | ## DORG Tokens 16 | 17 | ![](../.gitbook/assets/image%20%2816%29.png) 18 | 19 | The DORG Token is an [ERC20](../glossary/web3.md#erc20-token) issued by the DAO to track **unpaid obligations**. These tokens compound overtime according to the `interest-rate` \(coming soon!\). 20 | 21 | {% hint style="info" %} 22 | [View dOrg's current token distribution on Etherscan](https://etherscan.io/token/0x3b2d0c1b652d5fad3a43f4ada7265371eac050d4) 23 | {% endhint %} 24 | 25 | -------------------------------------------------------------------------------- /.archive/handbook/lifecycle/applying.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Ready to join us? 3 | --- 4 | 5 | # Applying 6 | 7 | ![](<../.gitbook/assets/Screenshot 2022-08-08 at 21.18.33.png>) 8 | 9 | ## 1. Join our [database](https://airtable.com/shrYZEjlgxLn228cE) 10 | 11 | When the need arises for your skills and experience, we'll reach out to schedule an interview. Due to the amount of interest, we can only reach out in response to corresponding demand. If someone referred you, make sure they fill out [this form](https://airtable.com/shrY4dGORKhV8Rplp)! 12 | 13 | {% hint style="info" %} 14 | In the meantime pop into our [Discord](https://discord.com/invite/6Kujmad) and say hello 👋. 15 | {% endhint %} 16 | 17 | ## 2. Interviews rounds 18 | 19 | The first interview round is conducted by our Talent Coordinator. 20 | 21 | Once you achieve first level, you'll have an interview conducted by a dOrg member with a [_QA Lead_](../workflows/qa-lead.md) or [_Coordination Lead_](../workflows/coordination-lead.md) badge depending on whether the role is technical or not. Please be prepared to discuss details about your area of expertise and past professional experience, as well as your current web3 involvement and interests. 22 | 23 | ## 3. Wait for a proposal 24 | 25 | The interviewer will make their recommendation to the collective on whether to proceed with a vote. If the collective votes to approve your application, you will be invited to onboard. 26 | 27 | {% hint style="warning" %} 28 | If you are a dOrg member referring a friend or you have a talent need for your project, create a post describing the candidate [here](https://forum.dorg.tech/c/new-members/6). 29 | {% endhint %} 30 | 31 | ## 4. Proceed to onboarding 32 | 33 | Once your application has been approved, you'll receive an e-mail outlining next steps. 34 | -------------------------------------------------------------------------------- /.archive/handbook/lifecycle/member-status.md: -------------------------------------------------------------------------------- 1 | # Building & Chilling 2 | 3 | ![](https://media.giphy.com/media/UdGyr0ruhC9RC/giphy.gif) 4 | 5 | Membership status is updated at the end of each quarter. You can either be building or chilling: 6 | 7 | ### **Building** 🤓 🛠️ 8 | 9 | Members who have earned Rep in the past quarter (through internal or client-facing work): 10 | 11 | * Have access to all dOrg spaces and events 12 | * Are eligible for bonuses 13 | * Refer new Building Member using [this form ](https://airtable.com/app6IBhJWYR4dcak6/tblgoWb1c4MvxoV6J/viwHG1NZQOx1ePMTD?blocks=hide) 14 | 15 | ### **Chilling** 😎 🏖️ 16 | 17 | Members who have nor earned Rep in the past quarter: 18 | 19 | * Retain access to all dOrg spaces and events 20 | * Are not eligible for bonuses 21 | 22 | {% hint style="success" %} 23 | Members who are hired by a dOrg client (with referral fee paid in full by the client to dOrg) automatically have 1 year of _Building_ status. 24 | {% endhint %} 25 | -------------------------------------------------------------------------------- /.archive/handbook/lifecycle/onboarding.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: What to expect 3 | --- 4 | 5 | # Onboarding 6 | 7 | ![](https://media4.giphy.com/media/3oEduUtBxr9wzS0DZu/giphy.gif?cid=ecf05e47oo0m24vbyfz5wb19bu7zdoer71xe9ptup4oerddh\&rid=giphy.gif\&ct=g) 8 | 9 | Shortly after your activation proposal passes, you'll get a dOrg email account and Discord access. 10 | 11 | Our Experience Facilitator will then send you details of your new email account and a link to an onboarding form that lets you consent to our member agreements and walks you through the key information and points of reference so that you can confidently join the community from the start. 12 | 13 | You'll also would be able to schedule an orientation-focused call to walk through any areas of dOrg you'd like more information on and explore which projects might be the best fit to start. 14 | 15 | {% hint style="success" %} 16 | Make sure you have everything you need to be part of dOrg 17 | 18 | ✔️ dOrg **email** activated\ 19 | ✔️ dOrg **calendar** integrated to your primary calendar \ 20 | ✔️ dOrg **forum** profile created (using your dOrg email)\ 21 | ✔️ dOrg **Discord** private channels access \ 22 | ✔️ dOrg **Github** member\ 23 | ✔️ **Tax form** submitted (W-9 for US or W-8BEN for non-US) + Upload it on GDrive folder 'dOrg\_Personnel Folders'\ 24 | ✔️ **Onboarding form** submitted (including consent to member agreements) \ 25 | ✔️ **Onboarding call** scheduled 26 | {% endhint %} 27 | 28 | ### Integrating your Calendar 29 | 30 | It's important for working on teams to have your dOrg email address calendar connected with your primary calendar. If you use a different email address as your primary calendar, you can connect your dOrg calendar by: 31 | 32 | 1. Log in to your dOrg gmail and go to your calendar 33 | 2. Go to calendar settings and under "Share With Specific People" add your main email address. Set the permissions to "Make changes and manage sharing" 34 | 3. Go to your main email address inbox and click the emailed link to add the calendar to your list. You should now see your dOrg email calendar events showing in your main calendar 35 | 36 | ### Filling your W-8BEN form 37 | 38 | For non US Tax Residents W-8BEN is the way to go. Here's some help: 39 | 40 | ![Instructions for filling your W-8BEN tax form](../.gitbook/assets/unnamed.jpg) 41 | 42 | ### Filling your W-9 form 43 | 44 | US Tax Residents W-9, here's some help to fill the form: 45 | 46 | ![Instructions for filling your W-9 Tax Form](<../.gitbook/assets/2203\_W9 Form.jpg>) 47 | 48 | {% hint style="info" %} 49 | ### Admin Steps for Onboarding a new Member 50 | 51 | Here are the instructions for the Experience Facilitator and others to help onboard new members once their membership proposal has passed on Snapshot: 52 | 53 | 1. **Give them the 'dOrg Member' tag on** **Discord** (you should be able to find their handle in the corresponding forum post), along with relevant skills such as 'frontend' or 'product'. 54 | 2. **Create a @dorg.tech email address in** [**google admin**](https://admin.google.com) **** using their first name (or first plus last if its already taken). Click Add New User, enter info (include their personal email address as the secondary email), click preview and send. 55 | 3. **Add their dOrg email address to the 'All Members' Google Group**. (This triggers a Google invite to the All-Hands meetings and gives access to all shared documents.) 56 | 4. **Send out a W-9 form (if they're US-based) or a W-8BEN tax form (if they're not US-based) to their personal email address.** (contact dOrg's accountant for details on how to do this). 57 | 5. **Create & Share Personnel Folder 'dOrg\_Personnel Folders**' with Contractor Agreement + Statement of work to be signed 58 | 6. **Send the welcome email** ([find the template here](https://forum.dorg.tech/t/new-builder-onboarding-email-template/242)), which includes a link to the interactive onboarding form. At the end of the onboarding form they have the opportunity to book an onboarding-specific call with our Experience Facilitator. 59 | 7. **Check the** [**Onboarding & Experience Facilitator records sheet**](https://docs.google.com/spreadsheets/d/1dJEASJk7orOm50cb8Nnye-X3DsVUHVdt2xJ0T45R0nw/edit?usp=sharing) for form responses. 60 | 8. **Introduce new member in Discord in** `general-internal` 61 | 9. **Add as member on** [**dOrg's Github**](https://github.com/dOrgTech) **** 62 | {% endhint %} 63 | 64 | -------------------------------------------------------------------------------- /.archive/handbook/lifecycle/removal.md: -------------------------------------------------------------------------------- 1 | # Removal 2 | 3 | 4 | 5 | ![](https://media2.giphy.com/media/TrOMR6REnWN1u/giphy.gif?cid=ecf05e475olmysndp9wciiouoodkrlec1hne62jdz46l16yp\&rid=giphy.gif\&ct=g) 6 | 7 | ## Proposing Removal 8 | 9 | The DAO can vote to remove any member who is found to have infringed the [Member Covenant](../covenant.md). Use the following steps to deal with these incidents: 10 | 11 | 1. Contact the member to reach a private accord if possible. Perhaps there is a misunderstanding or willingness to immediately resolve the situation. 12 | 2. If the situation is time-sensitive, contact the Experience Facilitator or a dOrg Safe Signer to mitigate any immediate harm. 13 | 3. Schedule a mediation with a mutually agreeable arbiter. Mediation gives all affected a chance to share their sides of the story and attempt to reach an accord. 14 | 4. If mediation is unsuccessful, any affected party may propose an enforcement action privately outlining evidence of infringement (such as screenshots) and proposed consequences with justification. Members are expected to review the submission, this covenant, and related past disputes in order to make a decision that aligns with the established norms and intention of the community. Possible consequences include: 15 | 16 | | Consequence | Description | Infringement | 17 | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 18 | | Temporary Ban | Removal from dOrg spaces, no interaction with the people involved, and partial slashing of reputation. After a specified period of time, the infringer can reclaim their slashed reputation and rejoin dOrg spaces by submitting a rejoin request that demonstrates a willingness to admit fault, apologize, rectify actions and avoid similar behavior in the future. | A serious infringement of community standards, including sustained inappropriate behavior. | 19 | | Indefinite Ban | Removal from dOrg spaces and slashing of all accumulated reputation. | Demonstrating a pattern of infringement of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. | 20 | 21 | If the enforcement proposal fails to pass, then the member is considered to be in good standing, regains any access to all dOrg spaces, and no further action is necessary. 22 | 23 | ## Requesting Removal 24 | 25 | Anyone may have their own membership removed automatically upon request. 26 | 27 | 28 | 29 | {% hint style="info" %} 30 | ### Admin steps for removing a member 31 | 32 | When a member requests to be removed or is removed by DAO vote: 33 | 34 | * **Remove all Discord tags**. 35 | * **Delete Google email account.** As part of the removal process, give the member 7 days notice of deletion so that they can move any important emails or saved documents. 36 | * **Remove Forum Groups access.** Profile> Admin Settings. 37 | * **Change Forum access to trust level to 0.** This means that they will no longer have access to private threads. 38 | * **Create burn transaction** to their address from the dOrg Safe based on their exact Reputation balance. 39 | {% endhint %} 40 | -------------------------------------------------------------------------------- /.archive/handbook/links.md: -------------------------------------------------------------------------------- 1 | # Important Links 2 | 3 | ![](https://i.gifer.com/6DY.gif) 4 | 5 | ### **Comms** 6 | 7 | * [Discord](https://discord.com/invite/6Kujmad) - chat server and biweekly calls to present project demos, tech talks, and upcoming opportunities 8 | * [Forum](https://forum.dorg.tech/) - deliberate on decisions and coordinate around client projects and new initiatives 9 | 10 | ### **Governance** 11 | 12 | * [Snapshot](https://snapshot.org/#/dorg.eth) - create and vote on governance proposals 13 | * [Rep Token](https://etherscan.io/token/0x62300cec5240e5b273781ad67ce735107f3dacd4) - non-transferable erc20 used to track reputation in dOrg 14 | * [Gnosis Safe](https://gnosis-safe.io/app/#/safes/0xdb22d2d37db92EA7fa6993C9f6Ead55FBb1eF4EA/balances) - shared dOrg wallet which collects funds from each client project wallet 15 | 16 | ### **Work** 17 | 18 | * [Github](https://github.com/dorgtech) - write code and track progress with project boards 19 | * [Pandadoc](https://app.pandadoc.com/a/#/templates-next?sortBy=name&direction=asc&displayMode=folders_first&mainFilter=all) - create and send legal agreements to clients 20 | * [Gilded](https://app.gilded.finance/auth/login) - invoice clients and track payments 21 | 22 | ### **Content** 23 | 24 | * [Twitter](https://twitter.com/dorg_tech) 25 | * [LinkedIn](https://www.linkedin.com/company/28435766/) 26 | * [Medium](https://medium.com/dorg-tech) 27 | * [YouTube](https://www.youtube.com/channel/UC7mE6iz-Y66t6KFHehfWlcg) 28 | 29 | ### **Legal** 30 | 31 | * [Contractor Term Sheet](https://github.com/dOrgTech/Ops/blob/master/legal/Contractor_Term_Sheet.pdf) 32 | * [Participant Terms & Conditions](https://github.com/dOrgTech/Ops/blob/master/legal/Participation_Terms_And_Conditions.pdf) 33 | * [Client Terms & Conditions](https://github.com/dOrgTech/Ops/blob/master/legal/Client_Terms_And_Conditions.pdf) 34 | * [Operating Agreement](https://github.com/dOrgTech/Ops/blob/master/legal/Operating_Agreement.pdf) 35 | * dOrg, LLC 36 | * 76 St. Paul St, 7th Floor, P.O. Box 369 37 | * Burlington, VT 05402 38 | * Business ID: 0357139 39 | * Tax ID: 84-2930500 40 | 41 | -------------------------------------------------------------------------------- /.archive/handbook/overview/form-and-function.md: -------------------------------------------------------------------------------- 1 | # Form & Function 2 | 3 | ### dOrg exists as a reputation-weighted DAO with legal personality. 4 | 5 | ![](../.gitbook/assets/membrane.jpg) 6 | 7 | Since then some basic metabolic processes have emerged. 8 | 9 | ### Activation & Onboarding 10 | 11 | New builders are continually [activated](../lifecycle/activation.md) and [onboarded](../lifecycle/onboarding.md) into the DAO. Builders [deactivate](../lifecycle/deactivation.md) after 90 days of inactivity in the community but can always reactivate. 12 | 13 | ### Core Workflows 14 | 15 | The core activity at dOrg is [building for our portfolio of Web3 clients](../workflows/joining-1.md). We also have builders that specialize in [sourcing](../workflows/sourcing.md), [managing](../workflows/coordination-lead.md), and [leading](../workflows/qa-lead.md) projects. 16 | 17 | ### Governance 18 | 19 | The margin on paid projects grows the DAO's [savings](../governance/savings-payments.md), which builders control through [reputation](../governance/rep-and-tokens.md) accumulated over time. Builders also govern all organization-wide decisions. 20 | 21 | -------------------------------------------------------------------------------- /.archive/handbook/overview/our-values.md: -------------------------------------------------------------------------------- 1 | # Values 2 | 3 | ### Shared values lie at the heart of our community. 4 | 5 | ![](../.gitbook/assets/faye-cornish-ggv3i6oxpcg-unsplash.jpg) 6 | 7 | We practice: 8 | 9 | 1. **Peer support and collaboration.** 10 | 2. **Self-determination and individual autonomy.** 11 | 3. **Radical transparency.** 12 | 4. **Kindness and respect.** 13 | 5. **Decentralized ownership and decision-making.** 14 | 15 | We aim to become the best service provider, workplace, and example of what is possible to achieve through the internet of value. 16 | 17 | -------------------------------------------------------------------------------- /.archive/handbook/overview/principles.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: 'As dOrg continues to evolve, our guiding principles are taking root.' 3 | --- 4 | 5 | # Guiding Principles 6 | 7 | Initially an experiment in distributed organisation, we have pioneered governance, legal, and incentive structures that offer our builders \(our members\) the freedom of freelancing with the structural support that comes with being a part of a community of peers. 8 | 9 | ![](../.gitbook/assets/banyan.jpg) 10 | 11 | ### Freedom & Support 12 | 13 | Enjoy the freedoms of freelancing without sacrificing the support structures of employment. 14 | 15 | ### Act First, Ask Later 16 | 17 | If you want to start or change something, go ahead! Mistakes are usually reversible, so just try things rather than seeking permission. 18 | 19 | ### Meritocracy 20 | 21 | No titles, special privileges, or hierarchical structures. Influence is based on competence and engagement. 22 | 23 | ### Simple Models 24 | 25 | Strive for simplicity over detailed mechanisms. Better to follow high-level principles than low-level procedures. 26 | 27 | 28 | -------------------------------------------------------------------------------- /.archive/handbook/overview/purpose.md: -------------------------------------------------------------------------------- 1 | # Purpose 2 | 3 | ### dOrg is a decentralized autonomous builder collective. 4 | 5 | ![](../.gitbook/assets/imagen%20%288%29.png) 6 | 7 | Its genetic code is simple: 8 | 9 | 1. **Build on web3.** 10 | 11 | Collaborate with projects to advance the web3 stack \(DAOs, DeFi, NFTs, L2s, identity, oracles, dev tools\). 12 | 13 | 2. **Run on web3.** 14 | 15 | Directly utilize the latest web3 tech to operate \(reputation, decision-making, payments, rev-share\). 16 | 17 | 3. **Iterate and propagate.** 18 | 19 | Adopt new tools and processes to always be coordinating as effectively as possible. Share these methods with communities everywhere. 20 | 21 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/README.md: -------------------------------------------------------------------------------- 1 | # Development Best Practices 2 | 3 | ### dApp 4 | 5 | * React should always be your tool to develop a dApp unless there's an explicit reason to not do it 6 | * Use typescript always, never use vanilla javascript 7 | * Use linter \(ESLint + Prettier is the default in TS\) 8 | * For styles in react, Styled Components or CSS-in-JS is a must, unless its an Angular or Vue project 9 | * Configure husky \(Attach linter to pre commit hooks so the code is the same for all the developers on the project\) 10 | * The suite of tests of the integrations is a must and should always aim to also test the UI components, but we can be flexible with it 11 | 12 | ### Smart contracts 13 | 14 | * Use hardhat to develop your contracts 15 | * [NatSpec](https://docs.soliditylang.org/en/v0.8.7/natspec-format.html) is a must, this way it's easier when it comes to audit and to people that want to understand the code 16 | * Tests must be implemented and cover at **least** 90% of the code. [Solidity Coverage](https://github.com/sc-forks/solidity-coverage) is an excellent tool that will help you to check exactly which lines are missing 17 | * Use linter \(Prettier and [Solhint](https://github.com/protofire/solhint)\) - Note that solhint gives you lint and security validations 18 | * Good documentation. Beside of natspec and the tests, good markdown files explaining what the Smart Contracts are trying to achieve is really important; this way, the developer can give an overview of how the contracts works, hence, making it easier for auditors/other developers to collaborate and/or review 19 | * Use libraries in order to implement standards whenever possible, especially Open Zeppelin 20 | * If you are using a solidity version lower than `0.8`, make sure you use `SafeMath` in order to avoid under/overflows 21 | * Attack vectors to be aware of: [https://github.com/crytic/building-secure-contracts](https://github.com/crytic/building-secure-contracts) 22 | * This should be every SC dev's bible: [https://consensys.github.io/smart-contract-best-practices/](https://consensys.github.io/smart-contract-best-practices/) 23 | 24 | 25 | 26 | 27 | 28 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/choosing-a-hosting-platform.md: -------------------------------------------------------------------------------- 1 | # Choosing a hosting platform 2 | 3 | There are numerous hosting and deployment services available online that can run your app from. Below is a comparative list of the most typically used at dOrg: 4 | 5 | ### Netlify 6 | 7 | {% embed url="https://www.netlify.com/" %} 8 | 9 | Best for: 10 | 11 | * Front end/React applications 12 | 13 | Pros: 14 | 15 | * Very fast/easy configuration for hosting and DNS 16 | * Free SSL 17 | * Automatic deployment of PRs on staging site without needing a CI/CD 18 | * Automated deployments without needing a CI/CD 19 | * Serverless functions 20 | 21 | Cons: 22 | 23 | * Doesn't have Docker support 24 | * Doesn't support Database management \(except for their own FaunaDB\) 25 | 26 | Beware: 27 | 28 | * For CRA Applications to work properly with React Router: [https://stackoverflow.com/a/55990523](https://stackoverflow.com/a/55990523) 29 | 30 | ### Heroku 31 | 32 | {% embed url="https://www.heroku.com/" %} 33 | 34 | Best for: 35 | 36 | * Dockerized applications 37 | * Database hosting 38 | 39 | Pros: 40 | 41 | * Very fast/easy configuration for hosting and DNS 42 | * Docker support 43 | * Automated deployments, even with Docker, without needing a CI/CD 44 | * Database management 45 | 46 | Cons: 47 | 48 | * Its free tier "sleeps" when idle. That means that your hosted application will have downtime, don't use this plan on production 49 | * No serverless functions 50 | * No automated PR deployment 51 | 52 | Beware: 53 | 54 | * Free tier's sleep 55 | * For CRA Applications to work properly: [https://stackoverflow.com/questions/50327645/deploy-production-of-create-react-app-to-heroku-without-buildpacks](https://stackoverflow.com/questions/50327645/deploy-production-of-create-react-app-to-heroku-without-buildpacks) 56 | 57 | ### Vercel 58 | 59 | [https://vercel.com/](https://vercel.com/) 60 | 61 | Best for: 62 | 63 | * NextJS applications 64 | 65 | Pros: 66 | 67 | * Very fast/easy configuration for hosting and DNS 68 | * Out of the box support for NextJS 69 | * Automatic deployment of PRs on staging site without needing a CI/CD 70 | * Automated deployments without needing a CI/CD 71 | * Serverless functions 72 | 73 | Cons: 74 | 75 | * No docker or database support 76 | 77 | ### AWS 78 | 79 | {% embed url="https://aws.amazon.com/" %} 80 | 81 | Best for: 82 | 83 | * Application with multiple docker files, or with docker-compose 84 | * A very custom infrastructure is needed \(multiple dbs, or apis\) 85 | 86 | Pros: 87 | 88 | * No limits, can set up any services you want 89 | 90 | Cons: 91 | 92 | * It is not really easy to use so you need to educate yourself in order to use it 93 | * Paid service 94 | * You need to manually configure CI with Github Actions or any other CI/CD pipeline 95 | 96 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/doing-a-code-review.md: -------------------------------------------------------------------------------- 1 | # Code Reviews 2 | 3 | ## How to review 4 | 5 | The review should be done with the premise in mind that pull requests reflect the way of thinking of someone captured in form of code. Each person is unique and in software there's no such thing as unique solution, therefore review should be performed not only **objectively** but also **kindly**. 6 | 7 | Most discussions in the PR happen in an async nature that might have delay between responses, therefore, avoiding ambiguity in messages is encouraged. Conciseness can save ton of time. 8 | 9 | Reviews should aim for acceptance rather than perfection, have a high bar quality wise but also have reasonable limits. 10 | 11 | There's an [article](https://curtiseinsmann.medium.com/ive-code-reviewed-over-750-pull-requests-at-amazon-here-s-my-exact-thought-process-cec7c942a3a4) from [Curtis Einsmann](https://twitter.com/curtiseinsmann), a former AWS team lead, that really resembles the kind of code review that we find valuable the most, it is a recommended read. 12 | 13 | ## When to review 14 | 15 | At any moment the developers working on a project can ask for help and/or reviews from other devs of the organization. This process must be less frequent than the daily/periodic code review done internally by the project team, as it requires significantly more time and effort. 16 | 17 | **While this process may be really useful in certain circumstances, it should not be used to replace the need for a strong technical lead or to compensate a lower expertise team level than the project requires** 18 | 19 | ## **Type of reviews** 20 | 21 | We can differentiate two types of external builder reviews: **general/architectural review** and **feature review**. 22 | 23 | ### General Review 24 | 25 | A general code review entails a revision of the full/significant part of the project's codebase. 26 | 27 | **As a requester:** 28 | 29 | When requesting this kind of review, it's worth noting that the external builder who will perform the review does not know the specifics, nor the implementation details of the project, so the recommended process is as follows: 30 | 31 | 1. Reach out to the builder/builders to request for review 32 | 2. Schedule a time to have a call or chat to walk the reviewer through the codebase and the areas that need revision the most 33 | 34 | **Important information to share during the call:** 35 | 36 | * Project's deadlines 37 | * General architecture overview 38 | * Libraries being used in implementation 39 | * High level functionality desired 40 | 41 | **As a reviewer:** 42 | 43 | After this, the reviewer should: 44 | 45 | 1. Clone the project's repository 46 | 2. Checkout branch to review 47 | 3. Perform review and provide feedback 48 | 49 | Things to look out for when reviewing: 50 | 51 | * Does the codebase contain tests for core functionality? Do they all pass? 52 | * Is Feature Review 53 | 54 | ### Feature Review 55 | 56 | A feature code review entails a revision of a single feature/functionality of the project being developed. This is particularly helpful for unique, complex or uncommon patterns needed to achieve a feature. 57 | 58 | #### As a requester: 59 | 60 | The recommended process is as follows: 61 | 62 | 1. Open a Pull Request on GitHub that contains: 63 | * Description of high level functionality 64 | * Description of current approach and implementation 65 | * Steps to reproduce changes or test functionality 66 | * Related issues 67 | 2. Request for review through GitHub and reach out to builder for review. 68 | 69 | #### As a reviewer: 70 | 71 | The reviewer does not need to necessarily clone the project, but can perform a regular code review through GitHub diffs. 72 | 73 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/git.md: -------------------------------------------------------------------------------- 1 | # Git 2 | 3 | Git allows developers to easily contribute to a shared codebase. 4 | 5 | Knowing the good practices of how to use git can save a lot of time when new changes are added, allowing the team to commit and review these in a comfortable way. Some of these good practices are: 6 | 7 | * **Explicit commit message**: When you commit something, the message should be explicit enough so any person that reads the message can know what the change is about. It should have the following structure: `topic: short description of what you did` an example of this can be`feat: implement authentication logic` or `chore: dependencies updated` 8 | * **New change, new branch:** Every time there's a code change, you need to create a new branch with an explicit name. It should have the following structure: `topic/title-of-changes` an example of this can be `feat/auth-logic` or `fix/swap-functionality` 9 | * **Changes should not be too big**: When developing a new feature, it's normal that the pull request gets big, you should push the code in multiple commits so if anything is broken, developers can find easier where the break was introduced 10 | * **Descriptive PRs**: When opening a PR, developer must add information on what's trying to be achieved with the changes proposed 11 | 1. A detailed description of what has been done 12 | 2. Link to issue (GH Issue or task in Trello, for example) 13 | 3. Steps of how to reproduce/test the new changes 14 | * **Remove old branches**: When developing as a team, it's normal that the old branches stays there forever - They should be cleaned sporadically, so it's easier to locate the active branches 15 | 16 | 17 | 18 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/react-dapp.md: -------------------------------------------------------------------------------- 1 | # Creating a React dApp 2 | 3 | ## Set up initial project structure 4 | 5 | There are lots of great initial scaffolding repositories, like [Scaffold-ETH](https://github.com/austintgriffith/scaffold-eth#-scaffold-eth). For a more lightweight CRA scaffolding version, with Typescript and linting configured, and dOrg's preffered libraries check out [React-Dapp-Boilerplate](https://github.com/dOrgTech/react-dapp-boilerplate). Feel free to use the initial structure or scaffolding that best suits your needs 6 | 7 | -------------------------------------------------------------------------------- /.archive/handbook/resources/best-practice-overview/tests.md: -------------------------------------------------------------------------------- 1 | # Tests 2 | 3 | ### Integration Tests with Web3 4 | 5 | Testing is critical to ensure an application works as intended and reduce bugs prior to release. Here are examples of end-to-end web3 tests, that will show you how to test integrations, putting everything into a docker (contracts, ganache, a dapp, etc) to run tests that trigger button clicks and web3 transactions on a local node. 6 | 7 | [https://michalzalecki.com/integration-tests-with-web3-ganache-cli-and-jest/](https://michalzalecki.com/integration-tests-with-web3-ganache-cli-and-jest/) 8 | 9 | [https://michalzalecki.com/integration-tests-and-mocking-web3-apps/](https://michalzalecki.com/integration-tests-and-mocking-web3-apps/) 10 | 11 | -------------------------------------------------------------------------------- /.archive/handbook/resources/getting-stuff-done-in-a-dao.md: -------------------------------------------------------------------------------- 1 | # Getting Stuff Done in a DAO 2 | 3 | Working in an organization without a chain-of-command can be confusing. Here is a process that can help you translate ideas into reality– whether working through the [Swarm](../workflows/doing-internal-work/#the-swarm), a DAO-approved grant, or an [internal role](../workflows/doing-internal-work/#internal-roles): 4 | 5 | 1. **IDENTIFY a problem**. Research how things currently work, find out why they work this way, and discuss with others. 6 | 2. **FORMULATE a solution**. Write out a brief description of how you intend to solve the problem and share in a forum post or Github issue for feedback and assistance (unless it’s a small improvement, in which case just go and build). Remember to include: 7 | * what’s broken 8 | * why it matters 9 | * how you plan to fix it. 10 | 3. **EXECUTE on the solution**. After getting initial feedback, start executing on your plan– whether it’s setting up a new tool, coding up some utility, crafting a new workflow or guideline, creating a piece of content, or designing a media asset. “Work in public” as much as possible, sharing new versions as you go to keep the feedback-loop tight. The feedback you collect during execution is twofold: on the quality of the solution you’re building, but also on the problem itself. Nobody wants to spend valuable time on building a great tool that nobody needs. 11 | 4. **MERGE the solution into existing workflows**. Just because you built something awesome that solves an existing problem, it doesn’t mean anyone will use it! In addition to sharing updates in the usual channels, there are several important ways to get your changes integrated into day-to-day realities and workflows of the organization: 12 | * Make a PR to the the handbook and/or landing page Post a demo video 13 | * Organize a walkthrough call with specific people, at a Swarm sync or an All-Hands call 14 | * Ask dOrg’s People Ops or Marketing specialists to make a post in the Discord announcements channel and in the next newsletter 15 | * Setup metrics that measure whether the solution is working and schedule checkpoints to check progress and make adjustments 16 | 17 | {% hint style="info" %} 18 | Getting feedback does NOT mean requesting formal sign-off or an official vote. 19 | 20 | Only initiate a DAO proposal before step 3 if you expect your efforts to exceed the swarm scope (>10 hr/wk). 21 | 22 | Only initiate a DAO proposal before step 4 if the change has structural, legal, or financial implications for the organization. Keep in mind that while proposals can formally certify the DAO’s stance, they don’t automatically imply that people will adopt the intended behavior. Step 4 is crucial for deep behavioral changes. 23 | {% endhint %} 24 | -------------------------------------------------------------------------------- /.archive/handbook/resources/links.md: -------------------------------------------------------------------------------- 1 | # Important Links 2 | 3 | ![](https://i.gifer.com/6DY.gif) 4 | 5 | ### **Comms** 6 | 7 | * [Discord](https://discord.com/invite/bA9ZM7WXZU) - chat channels and the biweekly All-Hands call 8 | * [Forum (internal)](https://forum.dorg.tech/) - discussion threads and member profiles 9 | 10 | ### **Governance** 11 | 12 | * Treasury ([mainnet](https://gnosis-safe.io/app/eth:0xdb22d2d37db92EA7fa6993C9f6Ead55FBb1eF4EA/balances), [polygon](https://gnosis-safe.io/app/matic:0xB910593f350D0b0E32B6BB251B962cf7dc2cea3f/balances)) - shared wallet that receives funds from each client project wallet 13 | * [Rep Token](https://etherscan.io/token/0x62300cec5240e5b273781ad67ce735107f3dacd4) - non-transferable erc20 token that tracks reputation in dOrg 14 | * [Snapshot](https://snapshot.org/#/dorg.eth) - create and vote on governance proposals 15 | 16 | ### **Work** 17 | 18 | * [Github](https://github.com/dorgtech) - write code and track progress with project boards 19 | * [Pandadoc](https://app.pandadoc.com/a/#/templates-next?sortBy=name\&direction=asc\&displayMode=folders\_first\&mainFilter=all) - create and send legal agreements to clients 20 | * [Gilded](https://app.gilded.finance/auth/login) - invoice clients and track payments 21 | 22 | ### **Content** 23 | 24 | * [Twitter](https://twitter.com/dorg\_tech) 25 | * [LinkedIn](https://www.linkedin.com/company/28435766/) 26 | * [Medium](https://medium.com/dorg-tech) 27 | * [YouTube](https://www.youtube.com/channel/UC7mE6iz-Y66t6KFHehfWlcg) 28 | 29 | ### **Legal** 30 | 31 | * [Contractor Term Sheet](https://github.com/dOrgTech/Ops/blob/master/legal/Contractor\_Term\_Sheet.pdf) 32 | * [Participant Terms & Conditions](https://github.com/dOrgTech/Ops/blob/master/legal/Participation\_Terms\_And\_Conditions.pdf) 33 | * [Client Terms & Conditions](https://github.com/dOrgTech/Ops/blob/master/legal/Client\_Terms\_And\_Conditions.pdf) 34 | * [Operating Agreement](https://github.com/dOrgTech/Ops/blob/master/legal/Operating\_Agreement.pdf) 35 | * [Legal & Accounting Files (internal)](https://drive.google.com/drive/folders/1j6i0YZ\_sCy5g2zzCLJD3YfOscCpczWB3) 36 | * Business Details: 37 | * dOrg, LLC 38 | * 9200 NW 39th Ave 39 | * Ste 130 #3382 40 | * Gainesville FL 32606 41 | * Business ID: 0357139 42 | * Tax ID: 84-2930500 43 | 44 | -------------------------------------------------------------------------------- /.archive/handbook/resources/press-kit.md: -------------------------------------------------------------------------------- 1 | # Press Kit 2 | 3 | Please use the below branding assets for any graphics requirements. 4 | 5 | ## Logos 6 | 7 | ![dOrg Colored Logo on Black Background (PNG)](../.gitbook/assets/dOrg-colored-black-bg.png) 8 | 9 | ![dOrg Colored Logo on White Background (PNG)](../.gitbook/assets/dOrg-colored-white-bg.png) 10 | 11 | ![dOrg White Logo Transparent (PNG)](../.gitbook/assets/dOrg-white-transparent.png) 12 | 13 | ![dOrg Black Logo Transparent (PNG)](../.gitbook/assets/dOrg-black-transparent.png) 14 | 15 | ![dOrg Colored Logo (SVG)](../.gitbook/assets/dOrg-colored-svg.svg) 16 | 17 | ![dOrg White Logo (SVG)](../.gitbook/assets/dOrg-white-svg.svg) 18 | 19 | ![](../.gitbook/assets/dOrg-black-svg.svg) 20 | 21 | ## Banners 22 | 23 | ![dOrg Color Banner on Black (PNG)](../.gitbook/assets/dOrg-color-banner.png) 24 | 25 | ## Complete Press Kit 26 | 27 | {% embed url="https://www.dropbox.com/s/ovnvldhq50hyg50/dOrg-Press-Kit-2022.zip?dl=0" %} 28 | -------------------------------------------------------------------------------- /.archive/handbook/resources/quarterly-dorg-tax-payments.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: How to pay our quarterly estimated tax payments to IRS 3 | --- 4 | 5 | # Quarterly dOrg Tax Payments 6 | 7 | To avoid tax penalties, dOrg must submit quarterly estimated tax payments to the IRS according to the schedule below. The accountant for dOrg will make these payments but the information for how to submit the payments are included in the handbook so the DAO is aware of the process. 8 | 9 | ![](../.gitbook/assets/image.png) 10 | 11 | Per the IRS website, 12 | 13 | > "If you didn’t pay enough tax throughout the year, either through withholding or by making estimated tax payments, you may have to pay a penalty for underpayment of estimated tax. Generally, most taxpayers will avoid this penalty if they owe less than $1,000 in tax after subtracting their withholdings and credits, or if they paid at least 90% of the tax for the current year, or 100% of the tax shown on the return for the prior year, whichever is smaller. " 14 | 15 | Currently, dOrg is paying 100% of the taxes owed in the prior year to meet the IRS requirements. For 2020 our tax liability was \~$1,000 so dOrg has been making estimated payments of $250 per quarter in 2021. To submit payments directly to the IRS: 16 | 17 | 1. Go to [https://www.eftps.gov/eftps/](https://www.eftps.gov/eftps/) 18 | 2. Click "Make a payment" 19 | 3. Login using the credentials below: 20 | 1. EIN: 84-2930500 21 | 2. Pin & Internet Password can be found in the [dOrg Log-in Credentials sheet](https://docs.google.com/spreadsheets/d/18QXB9Ski8OxHRiELfxq8DcahYFhNnEKPEM20kRjeuYA/edit#gid=0) 22 | 4. Follow the payment prompts: 23 | 24 | ![](<../.gitbook/assets/dOrg estimated payments.png>) 25 | 26 | Once the payment is complete, the receipt and any other associated documentation is uploaded to the [dOrg Legal and Accounting google drive](https://drive.google.com/drive/folders/1j6i0YZ\_sCy5g2zzCLJD3YfOscCpczWB3). 27 | -------------------------------------------------------------------------------- /.archive/handbook/resources/referral-program.md: -------------------------------------------------------------------------------- 1 | # Referral Program 2 | 3 | In order to refer someone to dOrg, members should: 4 | 5 | 1. Have your referral fill out the regular [interest form](https://airtable.com/shr0eQZfACL3Yarac) 6 | 2. Fill out [this form](https://airtable.com/shrY4dGORKhV8Rplp) about the referral 7 | 8 | The recruitment process is: 9 | 10 | **First Round**\ 11 | Interview with the Talent Coordinator to ensure that the candidate is aligned with [our vision, culture](https://docs.dorg.tech), and [the Covenant](https://docs.dorg.tech/covenant). 12 | 13 | * If the feedback is positive the Talent Coordinator creates the post in the forum with all the information (email, discord, referrer, interest form, background, work sample, skills and skill level). 14 | * If the feedback is negative, the candidate will receive an email. 15 | 16 | **Second Round** 17 | 18 | This part of the process is divided into two different branches depending if the candidate has a technical or non-technical background 19 | 20 | * Technical Interview: 45 minutes with TL to ensure that the profile has the minimum skills that we are looking for based on seniority and stack. 21 | 22 | 👉 If the position is for a client project, a member from that team might join to ensure final alignment. 23 | 24 | 👉 Additional steps may be added if TL consider that a Code Challenge will give a better overview of the candidate. If so, TL needs to provide the Code Challenge to the Talent Acquisition to ensure that all stakeholders are aligned and to avoid miscommunication. 25 | 26 | * Non-Technical interview: 45 minutes with Coordination Lead to ensure that the profile has the minimum skills that we are looking for based on seniority. 27 | 28 | 👉Additional steps may be add if Coordination Lead considerate that a Business Case will give a better overview of the candidate. If so, the Coordination Lead needs to provide the Business Case to the Talent Acquisition to ensure that all stakeholders are aligned and to avoid miscommunication. 29 | 30 | **Making a decision** 31 | 32 | A poll, in the forum, will be created by the Talent Coordinator among the Members involved during the rounds to decide if the candidate is rejected or a proposal is posted in Snapshot. 33 | 34 | The poll will have the following system: 35 | 36 | ⛔ VETO - strong opinion that the candidate doesn’t meet the requirements or our Contributor Covenant 37 | 38 | 😶 Maybe - didn’t fell in love with the candidate but open to welcome the person into the organization if his/her skills match with an open position 39 | 40 | 😍 FAN - strong opinion that the candidate is an asset for dOrg 41 | 42 | _Rules:_ 43 | 44 | * It only takes one VETO to reject the candidate. Argument for this vote will be also beneficial so all the people involved can better understand this vote. 45 | * In case of a draw: after a brief discussion those who vote “maybe”, they will need to change their vote in a second poll for VETO or FAN. 46 | * If in the second poll there isn’t a clear outcome, the candidate will be rejected. 47 | 48 | **Activation/Rejection**\ 49 | If the outcome of the poll is positive, the Talent Coordinator will do the post in the Forum and the Snapshot proposal for the final approval of the DAO.\ 50 | \ 51 | Get some rep! If your referral passed the recruitment process and is activated then the process has been finalized and you receive 2000rep at the end of the quarter! 52 | -------------------------------------------------------------------------------- /.archive/handbook/resources/social-media.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: A guide to representing dOrg on social media. 3 | --- 4 | 5 | # Social Media Guidelines 6 | 7 | ![](https://media.giphy.com/media/Wsva5clCvbxcbFURFm/giphy.gif) 8 | 9 | We leverage social media platforms like Twitter to engage about tools and ideas that are relevant to our community of members and web3 projects. 10 | 11 | {% hint style="success" %} 12 | **Goal:** build an engaging brand that attracts the best members, clients, and positive attention in the web3 ecosystem. 13 | {% endhint %} 14 | 15 | **KPIs:** 16 | 17 | * Tweets per week 18 | * Follower Growth Rate (MoM) 19 | * Engagements / Engagement Rate 20 | * Earned Impressions 21 | * Traffic to site 22 | * Mentions 23 | 24 | **Types of posts** 25 | 26 | * Original content (talks, podcasts, articles) 27 | * Client signal boost 28 | * Member signal boost 29 | * Provoking conversations about web3 tools 30 | * Scroll through the recent tweets of our clients and re-tweet them. 31 | * Questions to engage conversation and debates. 32 | * Bring in new collaborators and new members. 33 | 34 | {% hint style="info" %} 35 | **Tools:** [https://tweetdeck.twitter.com/](https://tweetdeck.twitter.com/) has feeds for mentions of dOrg and tweets by our members and clients. 36 | {% endhint %} 37 | -------------------------------------------------------------------------------- /.archive/handbook/resources/upskilling.md: -------------------------------------------------------------------------------- 1 | # Upskilling 2 | 3 | ### Learn with Others 4 | 5 | * [Chainshot](https://www.chainshot.com) - bootcamp 6 | * [Consensys Academy](https://consensys.net/academy) - bootcamp 7 | * [ETHGlobal](https://ethglobal.co) - hackathons 8 | * [Token Engineering Academy](https://tokenengineeringcommunity.github.io/website/docs/academy-welcome) - seminars 9 | 10 | ### Teach Yourself 11 | 12 | * [CryptoZombies](https://cryptozombies.io) 13 | * [Ethernaut](https://ethernaut.openzeppelin.com) 14 | * [Figment Learn](https://learn.figment.io) 15 | * [Questbook Learn](https://learn.questbook.xyz/) 16 | * [ETH.Build](https://eth.build) 17 | * [Ethereum Dev Speed Run](https://medium.com/@austin\_48503/%EF%B8%8Fethereum-dev-speed-run-bd72bcba6a4c) 18 | * [The Complete Guide to Full Stack Ethereum Development](https://dev.to/dabit3/the-complete-guide-to-full-stack-ethereum-development-3j13) 19 | * [Learning Solidity](https://github.com/willitscale/learning-solidity) 20 | * [Ethereum and Solidity: The Complete Developer's Guide (Udemy)](https://www.udemy.com/course/ethereum-and-solidity-the-complete-developers-guide/) 21 | * [Discover Ethereum & Solidity (Ludu)](https://www.ludu.co/course/ethereum/what-is-ethereum) 22 | * [Buildspace](https://buildspace.so/) 23 | * [Dacade](https://dacade.org/) 24 | 25 | ### Communities & Content 26 | 27 | * [ETH Hub](https://ethhub.io) - newsletter 28 | * [Week in Ethereum](https://weekinethereumnews.com) - newsletter 29 | * [Bankless](https://newsletter.banklesshq.com) - newsletter & podcast 30 | * [BanklessDAO](upskilling.md#learn-with-others) - discord (check out their solidity learning group) 31 | * [EthernautDAO](https://discord.gg/VZMmBMUx) - discord 32 | * [Learn Web3](upskilling.md#learn-with-others) - discord 33 | -------------------------------------------------------------------------------- /.archive/handbook/structure.md: -------------------------------------------------------------------------------- 1 | # Structure 2 | 3 | ![](<.gitbook/assets/dOrg Structure.png>) 4 | 5 | ### Project Multisigs 🔐 6 | 7 | dOrg members work in small teams to execute on client projects. Each project has its own wallet for collecting and distributing revenue amongst the sourcing lead(s), execution team, and dOrg's treasury. 8 | 9 | ### Treasury 🏦 10 | 11 | The treasury is used to fund internal [roles](workflows/doing-internal-work/#internal-roles), [initiatives](workflows/doing-internal-work/#the-swarm), and [expenses](workflows/expense-reimbursement-policy.md). 12 | 13 | ### Reputation 🏅 14 | 15 | Members receive one unit of [Rep](https://etherscan.io/token/tokenholderchart/0x62300cec5240e5b273781ad67ce735107f3dacd4) for every dollar earned from dOrg (whether for internal or client-facing work). Rep units are non-transferable and represent a share of _voting power_ and _token bonuses_. 16 | 17 | ### Voting 🗳 18 | 19 | Rep enables members to govern the treasury, membership, client project approvals, and more through [Snapshot](workflows/navigating.md#snapshot). 20 | 21 | ### Bonuses 🤑 22 | 23 | Rep also grants members a proportional share of token bonuses from client projects. At the end of each quarter, we flush all tokens (other than ETH and stablecoins) from the treasury to eligible members in proportion to their Rep. 24 | 25 | ### Detailed View 26 | 27 | ![Credit to Jozef Siu of the SecureSECO initiative for putting this together!](<.gitbook/assets/2022.02.04 dOrg Governance model.jpg>) 28 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/billing.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Let's talk about money! 3 | --- 4 | 5 | # Billing 6 | 7 | For bookkeeping purposes, we prefer you use the same address for rep & payments ;) 8 | 9 | ## Swarm 10 | 11 | By the end of the month, members participating at the Swarm have to log their work hours + work done on the [dOrg Internal Improvements Budget (Swarm!) Spreadsheet](https://docs.google.com/spreadsheets/d/1j-DsSaP0riIcS-vXUm-A-roIl4CowRloUEjAZXYeNb8/edit#gid=0). 12 | 13 | {% hint style="info" %} 14 | Swarms contributors can choose how they want to receive their compensation per hour: 15 | 16 | A) 50$ in stable coin + 50 rep (dOrg token)\ 17 | B) 25$ in stable coin + 100 rep\ 18 | C) 150 rep 19 | {% endhint %} 20 | 21 | {% hint style="danger" %} 22 | Remember: every builder can bill up to 22 hours of work each month without going through a vote (equivalent to a maximum of $1,100/m for compensation option A, or $550 for option B). If you need to go beyond this limit, take a look at [how to propose a Funded Initiative](doing-internal-work/funded-initiatives.md). 23 | {% endhint %} 24 | 25 | Afterwards dOrg Treasury signers and accounting will review and approve payment requests within one week. Your compensation will appear on your wallet. 26 | 27 | Please, if you need to create an invoice for tax purposes, here's the [template](https://docs.google.com/spreadsheets/d/1-Ky77y9YqhWVERc-rTVQPy3v9NZ\_ZLM4hGKU6AI1Z3M/edit#gid=790763898). Once created email it to [accounting@dorg.tech](mailto:accounting@dorg.tech) ;) 28 | 29 | ## Client Work 30 | 31 | Every client project has its internal flow of billing. Some of them payout members every 2 weeks and others once a month. Make sure to contact your Coordination Lead to get more information on your billing details! 32 | 33 | Afterwards dOrg Treasury signers and accounting will review and approve payment requests within one week. Your compensation will appear on your wallet. 34 | 35 | Please, if you need to create an invoice for tax purposes, here's the [template](https://docs.google.com/spreadsheets/d/1-Ky77y9YqhWVERc-rTVQPy3v9NZ\_ZLM4hGKU6AI1Z3M/edit#gid=790763898). Once created email it to [accounting@dorg.tech](mailto:accounting@dorg.tech) ;) 36 | 37 | ## Internal Roles 38 | 39 | By the end of the month Internal Roles need to log their hours and + work done on their Outflow Funded Role Forum post. [Take this one as a reference](https://forum.dorg.tech/t/experience-facilitator-anna-marie-ended-dec-10/104/5)! Afterwards dOrg Treasury signers and accounting will review and approve payment requests within one week. Your compensation will appear on your wallet. \ 40 | \ 41 | Ask Internal roles to send you a recurrent monthly calendar alert to update your Forum Role work log! 42 | 43 | Please, if you need to create an invoice for tax purposes, here's the [template](https://docs.google.com/spreadsheets/d/1-Ky77y9YqhWVERc-rTVQPy3v9NZ\_ZLM4hGKU6AI1Z3M/edit#gid=790763898). Once created email it to[ accounting@dorg.tech](mailto:accounting@dorg.tech) ;) 44 | 45 | 46 | 47 | {% hint style="warning" %} 48 | **What to do if you don't see your stable coins on your wallet** 49 | 50 | 1\. Check the wallet address you introduced on the spreadsheet is correct. If it's all good let's check on your wallet. 51 | 52 | 2\. Make sure you select Ethereum Main net. 53 | 54 | 3\. Go to _Refresh list_ or _Import token_ section (at the very bottom on Metamask) and select USDC stable coin _et voilà!_ 55 | {% endhint %} 56 | 57 | {% hint style="warning" %} 58 | **What to do if you don't see dOrg token (rep) on your wallet** 59 | 60 | 1\. Go to _Import token_ section > Custom Token > Paste 0x62300ceC5240e5B273781aD67Ce735107f3DaCD4 on Token Contract Adress and done! Your dOrg tokens should appear on your wallet! \ 61 | 62 | {% endhint %} 63 | 64 | 65 | 66 | For any further doubts reach out our Accountancy Team on #accounting-legal Discord Channel or email them at accounting@dorg.tech ;) 67 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/coordination-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Comms Leads keep client projects on track. 3 | --- 4 | 5 | # Being a Coordination Lead 6 | 7 | Each project must have a member with the `Coordination Lead` (formerly `Project Manager`) badge (the Sourcing Lead can assume this role, even without this badge) to: 8 | 9 | * Own client communication. 10 | * Review work logs and process payments. 11 | * Monitor scope load and deadlines. 12 | 13 | Members can propose to issue the `Coordination Lead` badge to any member who: 14 | 15 | * Has a successful track record helping to coordinate dOrg projects and/or highly visible open source projects. 16 | * Is a confident communicator. 17 | * Has shadowed a `Coordination Lead` for at least one week on an ongoing client project. 18 | 19 | {% hint style="info" %} 20 | View the [current list of Coordination Leads here](https://forum.dorg.tech/g/Project-Manager) 21 | {% endhint %} 22 | 23 | ## Project Management Workflows 24 | 25 | As Coordination Lead, you are responsible for ensuring client and member satisfaction through quality execution and orderly payments. 26 | 27 | ### Project Setup 28 | 29 | 1. Fork the [QA Worksheet](https://docs.google.com/document/d/1NR6CZbwduSgsbRVDJFXcZBB1fXSprMeSHICob5Gfd8k/edit#heading=h.k20qb4mo4uip) and fill out the Project Details and Personnel tables. 30 | 2. Schedule a recurring weekly internal check-in (15-30 min) followed by a client check-in with all team members (30-45 min). 31 | 3. Ensure all team members are onboarded to the client’s project board and comms channels (set up if needed). 32 | 4. Fork the [Budget template](https://docs.google.com/spreadsheets/d/1T-tvQjN64HSipPBuR0SXS1ObdQmj-mElhVCUyeVhhek/edit#gid=0) and make sure it's visible to all DAO members by adding all-members@dorg.tech. 33 | 34 | ### Ongoing Quality Assurance 35 | 36 | 1. Remind team members to attend the weekly check-in. 37 | 2. At the internal portion of the check-in, fill out the Progress Tracker table with: 38 | 1. Green rows: review actuals from the previous week. 39 | 2. White rows: plans for the coming week. 40 | 3. Discuss any issues people are experiencing (scope creep, communication issues, etc.) 41 | 3. At the client portion of the check-in, review and discuss each column. 42 | 43 | ### Payment Processing 44 | 45 | 1. At the close of each pay period, make sure each team member's hours and work logs is entered. 46 | 2. The Payout tab automatically calculates the payout amount for each team member. Some projects also have bonuses in the client's native tokens — if you aren't clear on the setup, ask the Sourcing Lead. 47 | * Each payment must include a 10% payment to the Sourcing Lead(s) and 10% to the dOrg Treasury (make sure you are paying to the address on the right chain!). 48 | 3. Export the Payout tab to CSV and upload it to the Gnosis Safe's CSV Airdrop app. This will allow you to issue all payouts in one batched transaction. Once the transaction is created, ask the rest of the project's signers to review and sign the transaction, and then it can be executed. 49 | 50 | {% hint style="warning" %} 51 | We're currently working on how to reimburse gas costs through a bulk proposal from dOrg's treasury. 52 | {% endhint %} 53 | 54 | 55 | 56 | ## **QA Worksheet Guide** 57 | 58 | Here is some guidance on how to use the Project Tracker in the [QA Worksheet](https://docs.google.com/document/d/1NR6CZbwduSgsbRVDJFXcZBB1fXSprMeSHICob5Gfd8k/edit#heading=h.k20qb4mo4uip). 59 | 60 | * **Top Priorities:** What are the pieces of working software we’re going to create this week? 61 | * This is a way for us to ensure that we are working on the most critical things at the right time.\ 62 | 63 | * **Blockers:** client, 3rd party or internal blockers that are preventing us from making progress on top priorities: 64 | * Explicitly state who is responsible for clearing the blocker (client, dOrg, specific 3rd party, etc.)\ 65 | 66 | * **Testing:** 67 | * Required: Automated testing of all core functionality. 68 | * Required: Integration testing before major releases.\ 69 | 70 | * **DevOps:** Setup and maintain CI/CD tooling to ensure compliance with all testing suites and allow the client to see our progress in realtime: 71 | * Links to most recent deployment and test suite run 72 | * Notes on any changes to make to the DevOps setup (hosting, DNS, etc)\ 73 | 74 | * **Documentation:** Everything is expected to be well documented and this column is used to link the client to documentation of this week’s priorities: 75 | * Required as baseline for every project: 76 | * Documentation at the product level prior to code. 77 | * Documentation for different parts of the stack.\ 78 | 79 | * **Code Review:** After large components are completed, we will find an external code reviewer to review the code: 80 | * Note who completed the code review and include a link to the review. 81 | * Please see our \ for code review guidelines: process, timing, format, reference to original specs. 82 | 83 | ## **Risk Factors** 84 | 85 | Occasionally check-in with individual team members to see how they are feeling about the project. If you notice any of the following risk factors, immediately meet with the members and/or client to discuss solutions: 86 | 87 | * Junior devs and senior mentors: is this flow happening well? If not, address it with them and if it’s still problematic contact the sourcing lead. 88 | * Product leadership: sometimes it isn’t clear if the client or the dOrg technical lead on the project is leading product. If there is confusion, ask for clarification of leadership roles. 89 | * Client pushing too fast to get to market: Don’t cut corners on required QA baselines. The issue is that it will always be dOrg’s fault in the end. If the client is unwilling to respect our leadership on baselines, discuss stopping the engagement with the sourcing lead. 90 | * Over-allocating: Monitor hours to make sure we are not going over what the client is paying for; consider modifying the contract to have a higher hour allocation or removing a team member from the project 91 | * Under-allocating: Monitor hours to make sure we are not going under what the client is paying for; consider adding members to the project or modifying the contract to have a lower hour allocation 92 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/doing-internal-work/README.md: -------------------------------------------------------------------------------- 1 | # Doing Internal Work 2 | 3 | ![](https://i.gifer.com/4dau.gif) 4 | 5 | {% hint style="info" %} 6 | It is the builder's responsibility to make sure to understand the compensation model for each client and internal project. Ask Experience Facilitator for help if you don't find the information. 7 | {% endhint %} 8 | 9 | {% hint style="warning" %} 10 | All Forum links go to our private sections. So, only dOrg members have access. 11 | {% endhint %} 12 | 13 | ## **The Swarm** 14 | 15 | dOrg is a dev collective working primarily on external projects. However, being an organization, it also requires internal work to properly function and grow. This goes from building a new dashboard to improving internal processes, from working on business development to creating new tools that increase builders' satisfaction. 16 | 17 | Internal work is done through [The Swarm](https://forum.dorg.tech/t/swarm-bucket/237). The Swarm is an umbrella term for small teams that come together to work on internal initiatives, and then disburse when the initiative is completed. 18 | 19 | Internal work in The Swarm is divided in three categories: 20 | 21 | * **capped, permission-less work**: every builder can work **up to 22 hours each month** on whatever they think needs to be done, without asking for permission; it's still highly recommended to follow the principles outlined in the [getting stuff done in a DAO](../../resources/getting-stuff-done-in-a-dao.md) to be sure to not waste time 22 | * **internal roles**: in some specific instances, dOrg can vote to create part-time roles that lead key operational areas, like Talent, or Marcom; these roles are not subjected to the 22h/m cap 23 | * **funded initiatives (grants)**: every builder who needs to go over the 22h/m cap can propose a funded initiative to the DAO; such initiatives need to be properly aligned to dOrg strategic objectives, and their progress needs to be measured and reviewed during the initiative lifecycle. A thorough description of **how to request** dOrg to **fund** an internal project can be found [**here**](funded-initiatives.md)**** 24 | 25 | {% hint style="success" %} 26 | The Swarm is an excellent way to gain insight into and practice being part of a DAO, meeting dOrg members, and understanding current dOrg focuses and needs. We suggest that newcomers stop by the weekly Swarm sync to learn how they can contribute. 27 | {% endhint %} 28 | 29 | {% hint style="info" %} 30 | See our guide on [getting stuff done in a DAO](../../resources/getting-stuff-done-in-a-dao.md) for general guidance. 31 | {% endhint %} 32 | 33 | ## Internal Roles 34 | 35 | At any given time, we have several part-time roles that lead key operational areas. Anyone may propose to dissipate or create a new role based on dOrg's needs. 36 | 37 | {% hint style="success" %} 38 | New members who intend to hold an internal role should start off by contributing through the Swarm. Once you have gained experience with the responsibilities and what it's like to work in the DAO, you can post a proposal for the role in the forum. 39 | {% endhint %} 40 | 41 | See here for the current breakdown of roles: 42 | 43 | | Name | Role | Description | 44 | | ------------------------------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------- | 45 | | [Clara](https://forum.dorg.tech/t/experience-facilitator-clara/301) | Member Experience | Members support, improving members experience, facilitation and internal systems and processes. | 46 | | [Luís](https://forum.dorg.tech/u/sirluis/summary) | Client Experience | Client support, improving client experience and client internal systems & processes. | 47 | | [Miriam](https://forum.dorg.tech/t/talent-coordinator-internal-role-miriam/381) | Talent Coordinator | Recruitment efforts, improving candidate experience, detecting hiring necessities to support Client projects. | 48 | | [Mackenzie](https://forum.dorg.tech/t/accounting-finance-mackenzie/230) | Accounting | Bookkeeping and monthly reporting for dOrg; streamlining accounting processes and FP\&A. | 49 | | [Alex](https://forum.dorg.tech/t/general-counsel-for-dorg/366) | Legal | Legal counseling for all dOrg matters, including contract review, drafting agreements, demand letters, and any other legal needs. | 50 | 51 | {% hint style="info" %} 52 | The funded initiatives and Internal Roles sync every Tuesday at 5pm CET/ 11am EST in the Discord Member Hall. Find your calendar invitation on your Google Cal. 53 | {% endhint %} 54 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/events.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Join us! 3 | --- 4 | 5 | # Events 6 | 7 | Anyone is welcome to join our public spaces! Please check out our events calendar. 8 | 9 | {% hint style="info" %} 10 | For everyone interested on attending to our dOrg public events, add our public events to your favourite calendar: 11 | 12 | [G Calendar](https://calendar.google.com/calendar/u/1?cid=Y183aG5kN2N2aDFzdjMwMWtyMzdwbmdjbjBoZ0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t) \ 13 | [iCal version ](https://calendar.google.com/calendar/ical/c\_7hnd7cvh1sv301kr37pngcn0hg%40group.calendar.google.com/public/basic.ics) 14 | {% endhint %} 15 | 16 | Note the time is in CET, regardless of where you're located. To see the calendar in your local time, open it your personal Google calendar by clicking "+ Google Calendario" in the bottom right corner. 17 | 18 | {% embed url="https://calendar.google.com/calendar/embed?ctz=Europe%2FMadrid&src=c_7hnd7cvh1sv301kr37pngcn0hg%40group.calendar.google.com" %} 19 | 20 | dOrg members, please, make sure to integrate your dOrg email address calendar to your primary calendar to receive the biweekly All-Hands meetings calendar invite. [Here](https://docs.dorg.tech/lifecycle/onboarding) you can find the instructions to do so. 21 | 22 | ## DAO.fm on Twitter Spaces 23 | 24 | We've created a public event on our [Twitter Spaces](https://twitter.com/dOrg\_tech). There we talk about DAOs, DAO tools, governance, web 3, blockchain, smart contracts, NFTs, crypto, crypto taxes, etc. \ 25 | \ 26 | These events take place bi-weekly after our internal All Hands Meeting, on Thursdays @ 13.30pm ET / 19.30 CET in our Twitter. \ 27 | \ 28 | Attending Twitter Spaces are not required however if you are a dOrg member you could earn rep by participating in these spaces. Please, contact @Diego to participate & further details. 29 | 30 | | Participating on a one-hour Space | 50 dOrg tokens | 31 | | --------------------------------- | --------------- | 32 | | Hosting a one-hour Space | 100 dOrg tokens | 33 | 34 | ## Speaking events 35 | 36 | dOrg members are often invited to conferences, university lectures, podcasts, DAO talks, interviews, etc. In case you were invited to an outside dOrg event & you want to represent dOrg contact Comms\&Marketing role (@ernesto) for further details. Also sign up on the [spreadsheet](https://docs.google.com/spreadsheets/d/1HsfV5q1X5QAfB6lUJiK0mYZrpEJ89X7mEzGwAe6ItyE/edit#gid=1783995451) for the record. \ 37 | \ 38 | dOrg members could also earn rep for participating on speaking events. 39 | 40 | ## All Hands Meetings 41 | 42 | dOrg builders are located all around the globe and collaborate remotely 🌐 We therefore don't get the opportunity to all hang out very often.\ 43 | \ 44 | We do, however, have bi-weekly All-Hands meetings, which are held on Thursdays @ 12pm ET ️/ 6pm CET in the Discord voice channel 'All Members'. \ 45 | \ 46 | Attending All-Hands meetings are not required but we recommend you attend! New builders have a chance to introduce yourself to the rest of the collective and share what kind of work they're looking for. Plus, meet other builders and get a good overview of the projects we're working on. 47 | 48 | To participate on the All Hands Meeting, contact the Experience Facilitator or sign up yourself for a Demo, Tech Talk, Discussions or suggest a Guest Speaker on this [spreadsheet](https://docs.google.com/spreadsheets/d/1HsfV5q1X5QAfB6lUJiK0mYZrpEJ89X7mEzGwAe6ItyE/edit#gid=0). Check out previous recorded events there as well. 49 | 50 | {% hint style="info" %} 51 | **Agenda for the All Hands Meeting** \ 52 | Round Robin Icebreaker (15-20 min)\ 53 | New onboardings presentations (5 min)\ 54 | dOrg doings aka demo/product presentations (15-20 min)\ 55 | Discussions (10 min)\ 56 | Tech Talks (10 min)\ 57 | Job opportunities at dOrg (5 min) \ 58 | Announcements (5 min)\ 59 | Guest speaker talk (15+10 min Q\&A) 60 | {% endhint %} 61 | 62 | ## Upskilling Workshops 63 | 64 | Monthly upskilling workshops are hold for dOrg builders by dOrg builders. We combine tech/ non tech upskilling workshops. \ 65 | \ 66 | Attending Upskilling Workshops are not required but we highly recommend you to attend!\ 67 | \ 68 | Workshops happen monthly on Thursdays @ 12pm ET ️/ 6pm CET in the Discord voice channel 'All Members' and are recorded. Check out upcoming workshops on your calendar or [spreadsheet](https://docs.google.com/spreadsheets/d/1HsfV5q1X5QAfB6lUJiK0mYZrpEJ89X7mEzGwAe6ItyE/edit#gid=975034267). 69 | 70 | Please, if you want to host a tech/non tech workshop, contact Experience Facilitator. Hours to prepare, plus facilitating the workshop are retributed as Swarms hours. 71 | 72 | ## Retreat 73 | 74 | Since all dOrg members work remotely once per year we gather in real life for at least for a week. Please notice that dOrg retreat it's proactively managed by members who want to attend. dOrg covers the housing expenses as approved by the DAO and flying & maintenance costs are covered by each dOrg member (unless treasury gives us new updates). \ 75 | \ 76 | First dOrg retreat was on 2021 and we've already booked our place for the second dOrg retreat! Check out our [#official-links channel](https://discord.com/channels/544647726982365194/937739458760015947) for details on our 2022 Retreat & how to book your spot! 77 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/executing.md: -------------------------------------------------------------------------------- 1 | # Executing 2 | 3 | Each project has one or more builders contributing to deliverables and a single execution lead. 4 | 5 | ## As a builder 6 | 7 | Builders ultimately determine project outcomes. That's why a bias towards action is essential. These actions include: 8 | 9 | * **Communication.** Proactively update other builders in the internal chat \(Discord\), speak-up when needed in the client chat \(Telegram\), attend weekly calls. 10 | * **Organization.** Keep issues and project boards \(Github\) up-to-date with your progress. 11 | * **Execution.** Complete deliverables by the agreed to deadlines. 12 | 13 | {% hint style="success" %} 14 | ### **Tips & Tricks** 15 | 16 | * Keep a log of hours worked and contributions made as you go. This will reduce time and avoid conflict at payment checkpoints. 17 | * Regularly check-in with your squad to ensure that everyone is fulfilling their work allocations. Builder self-organization is how dOrg delivers quality work on time. 18 | * If you run into any issues, technical or otherwise, ask your squad for help. If the problem persists, tap into the dOrg hive mind by posting in the \#help channel on Discord. 19 | * If you feel that a project is going over scope or needs more time, discuss this with your squad and execution lead as soon as possible so that adjustments can be made. 20 | {% endhint %} 21 | 22 | ## As an execution lead 23 | 24 | The execution lead is responsible for keeping the project on track. This includes setting up and maintaining: 25 | 26 | * **Weekly Calls**. Share progress, discuss open issues or questions, and realign priorities with the client and builder squad each week. 27 | * **Chats**. Internal builder chat \(Discord\) and client chat \(Telegram\). 28 | * **Tasks & Deadlines.** Project board \(Github\) to track the status of each deliverable. 29 | * **Invoices & Payments**. Send client invoices and and facilitate builder payments at preset checkpoints. 30 | * Additionally, at the start of the month, in Airtable set up the transaction rows for all expected payments and builder payouts - in view [Transactions by Project](https://airtable.com/tblMrDMxVayppGF9m/viwlKi5pJJXnrifAC?blocks=hide). This will help make sure payments aren't missed. 31 | * When payments come in, and when builder payout proposals have passed and been redeemed, copy the transaction hash into the row. 32 | 33 | {% hint style="success" %} 34 | ### Kickoff 35 | 36 | Start strong by arranging a kickoff call with the builder squad to: 37 | 38 | * Confirm that the **scope of work** and **deadlines** are realistic. If not, discuss and adjust with the client. 39 | * Divide up expected **work allocations** – including tasks and time commitments. 40 | * Agree on a **budget distribution** **algorithm** and **payment checkpoints**. See [Getting Paid](getting-paid.md) for more details. 41 | {% endhint %} 42 | 43 | {% hint style="warning" %} 44 | As execution lead, you are the client's **primary point of contact**. Make sure to regularly check-in with the squad and update the client! 45 | {% endhint %} 46 | 47 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/expense-reimbursement-policy.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: >- 3 | dOrg will reimburse its contributing members for necessary DAO-related 4 | expenses incurred. 5 | --- 6 | 7 | # Reimbursing Expenses 8 | 9 | {% hint style="danger" %} 10 | This **process is currently iterating** and we are no longer using Utopia in order to avoid extra gas fees. Reach out to Mackenzie directly for instructions! 11 | {% endhint %} 12 | 13 | **Eligibility** 14 | 15 | This policy applies to all dOrg members at time of reimbursement request. 16 | 17 | **Covered Expenses** 18 | 19 | Necessary DAO-related expenses may include, but are not limited to: 20 | 21 | * SaaS services necessary in the course of completing work for dOrg. Examples include: 22 | * Github 23 | * Substack 24 | * Pandadoc 25 | * Gilded 26 | * Google 27 | * Zapier 28 | * Additional SaaS products not listed above 29 | * Fiat payments to professional services engaged for dOrg including legal advice, tax preparation, consulting, etc. These larger expenses must be approved by dOrg members in a snapshot proposal. 30 | * Gas fees for transactions associated with dOrg Safes (automatically reimbursed by dOrg) 31 | * Any other expenses deemed necessary for dOrg to continue operations. Examples include: Tax payments to the IRS Annual LLC fees 32 | 33 | **Submitting a Reimbursement Request**\ 34 | ****\ 35 | ****Members who incur DAO-related expenses are required to submit those expenses for reimbursement as follows: 36 | 37 | 1. Login to Utopia Labs through the custom link [https://app.utopialabs.com/request/payment?daoId=618a831e9fd5391eafd6c060](https://app.utopialabs.com/request/payment?daoId=618a831e9fd5391eafd6c060) 38 | 2. Verify your wallet 39 | * Enter your name, wallet address and role 40 | * Once submitted, accounting will verify the account by checking the address against our [dOrg address list](https://docs.google.com/spreadsheets/d/1wxRpk0e4TQN5YJJwjrzMY5U4Txns9OgDinzkWlr5E5g/edit?usp=sharing) 41 | * If you recently changed your address, reach out to Mackenzie (Mackenzie#0246) on Discord 42 | 3. Once verified, head to the dOrg Utopia link and fill out payment request details 43 | * Select YES for “Is this a reimbursement for the purchase you made?” 44 | * Enter date of purchase 45 | * Upload applicable receipt(s) 46 | 4. dOrg Treasury signers and accounting will review and approve payment requests within one week 47 | 48 | Utopia Labs payment [request demo](https://www.loom.com/share/183702bebd6c4c818969e532b315886a) 49 | 50 | {% hint style="danger" %} 51 | 52 | {% endhint %} 53 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/joining.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: Once onboarded, you can start contributing to ongoing projects. 3 | --- 4 | 5 | # Joining a Client Project 6 | 7 | {% hint style="info" %} 8 | It is the builder's responsibility to make sure to understand the compensation model for each client. Ask project Sourcing Lead for help if you don't find the information. 9 | {% endhint %} 10 | 11 | ## Finding a project to join 12 | 13 | 1. Express interest in any [Client Projects](https://forum.dorg.tech/c/clientproject/8) by commenting on the forum thread. You can also check for opportunities in our `job-board` channel in Discord. Lastly, you could also check our WIP [dOrg data app](https://share.streamlit.io/dorgtech/dorg\_data/app.py) - make sure to not use Brave navigator, have access to dOrg Github (if not ask Experience Facilitator), plus request access to WHYTEWYLL#7455. 14 | 2. If the _Coordination Lead_ and _QA Lead_ of that project determine that your skills and availability match the project's needs, they will reach out to schedule a walkthrough. 15 | 3. If it's a match, the _Coordination Lead_ will update the project's post with your start date, time commitment, and role. 16 | 4. Sign Statement of Work document for each new Client Project that you start. Find the document on your GDrive 'dOrg Personnel Folders' 17 | 18 | {% hint style="info" %} 19 | You can also DM our Experience Facilitator, Clara, on Discord for help with finding opportunities! 20 | {% endhint %} 21 | 22 | ## Contributing to a project 23 | 24 | 1. Familiarize yourself with the project details noted in its forum post (code repos, project boards, SoW, QA Worksheet, etc.). 25 | 2. Attend weekly syncs. Make sure you are prepared and join a few minutes early with a stable internet connection and good audio. 26 | 3. Self-assign issues in the project board while communicating with other members to avoid overlap and ensuring you are working on the highest priority tasks. 27 | 4. Log your work and time in the project's budget spreadsheet before each payment checkpoint. 28 | 5. At each payment checkpoint, review your teammates' logs and sign-off on the transaction initiated by the _Coordination Lead_. 29 | 6. Participate in periodic feedback surveys and retro sessions initiated by the _Coordination Lead_. 30 | 31 | {% hint style="success" %} 32 | #### **Tips & Tricks** 33 | 34 | * Follow [dOrg's Development Best Practices](../resources/best-practice-overview/). 35 | * Share updates and questions with the rest of the team as you build. 36 | * If you run into any issues, technical or otherwise, ask your team for help or post in the #help channel on Discord to tap into the dOrg hive mind. 37 | * If you feel that a project is going over scope or needs more time, discuss this with the _Coordination Lead_ or _QA Lead_ as soon as possible so that adjustments can be made. 38 | {% endhint %} 39 | -------------------------------------------------------------------------------- /.archive/handbook/workflows/qa-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | description: QA Leads are the quality backstop on client projects. 3 | --- 4 | 5 | # Being a QA Lead 6 | 7 | Each project must have a member with the `QA Lead` badge (formerly `Tech Lead`) that has been designated to: 8 | 9 | * Own the code quality, making sure that our work product aligns with dOrg's [Development Best Practices](../resources/best-practice-overview/). 10 | * Ensure fit between the execution team and project requirements. 11 | 12 | {% hint style="success" %} 13 | The precise responsibilities of the QA Lead will vary from project to project, but here are some recommended practices: 14 | 15 | * Make sure you understand all technical requirements, and ask if you don't. 16 | * Evaluate the experience level of each team member and offer mentorship if you see a need. 17 | * Evaluate risk and raise potential issues with other team members, the Coordination Lead, Sourcing Lead, or client as needed. 18 | * Review pull requests and assist in debugging. 19 | * Check for testing at different levels of the codebase. 20 | * Structure the continuous integration/deployment pipeline and application alerts. 21 | {% endhint %} 22 | 23 | Members can propose to issue the `QA Lead` badge to any member who: 24 | 25 | * Has a successful track record of building on dOrg projects and/or highly visible open source projects. 26 | * Is a confident communicator. 27 | * Knows the limits of their skills and how to identify expertise in others. 28 | 29 | {% hint style="info" %} 30 | View the [current list of QA Leads here](https://forum.dorg.tech/g/Tech-Lead) 31 | {% endhint %} 32 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store -------------------------------------------------------------------------------- /legal/Client_Terms_And_Conditions.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/legal/Client_Terms_And_Conditions.pdf -------------------------------------------------------------------------------- /legal/Contractor_Services_Agreement_Updated_2022.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/legal/Contractor_Services_Agreement_Updated_2022.pdf -------------------------------------------------------------------------------- /legal/Contractor_and_Operational_Agreement_NDA_Master_Services_2024.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/legal/Contractor_and_Operational_Agreement_NDA_Master_Services_2024.pdf -------------------------------------------------------------------------------- /legal/Operating_Agreement_Updated_2022.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/dOrgTech/docs/c8010ca6fa5119821553ef4586f922e0c2bb456f/legal/Operating_Agreement_Updated_2022.pdf --------------------------------------------------------------------------------