diff --git a/docs/association/index.md b/docs/association/index.md index 245e8244..06e4889b 100644 --- a/docs/association/index.md +++ b/docs/association/index.md @@ -1,7 +1,44 @@ # Association -We are [in the process](https://github.com/web3privacy/association) of creating a non-profit legal entity in the Czech Republic. +:::note -## Web3Privacy Now z.s. +We are [currently working](https://github.com/web3privacy/association) on the creation of this association. The likely date of establishment is March 2024. -TBA \ No newline at end of file +::: + +Registered entity representing our initiative in communication with authorities and partners. + +- Name: **Web3Privacy Now z.s.** +- Jurisdiction: 🇨🇿 Czech Republic (🇪🇺 EU) +- Legal form: Non-profit association ("spolek") as defined in Czech Civic Law ([89/2012 Sb. § 214 - § 302](https://www.zakonyprolidi.cz/cs/2012-89#f4579519)) + +## Purpose + +### Non-financial +- officially representing our initiative and our projects +- operates our [Membership](/membership) program +- curates the [Contributors Guild](/guild) members & their weight (quarterly) +- organises [Congress](/congress) (once a year) + +### Financial +- receiving donations and membership fees +- pleding 25% of income (donations, membership fees) to [Contributors Guild](/guild) split contract +- paying basic infrastructure (services) controlled by [Core Team](/core-team) +- paying expenses of our [Workgroups](/workgroups) or projects +- fulfilling other financial & operational tasks of the [Core Team](/core-team) +- controls bank(s) and exchange(s) accounts + +## Committee + +*Committee* ("výbor") is the main executive body of the Association. + +The members of the Committee are elected by the [Congress](/congress) for a period of 5 years. In rare cases, they may be elected or removed by the [Core Team](/core-team). + +### Current committee + +* Mykola +* Tree + +## Statues + +TODO \ No newline at end of file diff --git a/docs/congress.md b/docs/congress.md new file mode 100644 index 00000000..2d165ab1 --- /dev/null +++ b/docs/congress.md @@ -0,0 +1,21 @@ +# Congress + +The main governance body of the whole organisation, which decides on the most important issues by voting. + +The Congress is held once a year and is organized by [Association](/association). + +| Congress | Date | Location | +| --- | --- | --- | +| W3PN Congress #1 (2025) | ~Feb 2025 | TBD | +| W3PN Congress #2 (2026) | ~Feb 2026 | TBD | + +## Purpose + +* a vote on the long-term direction of the initiative +* approval of the financial plan for the following year +* election of [Core Team](/core-team) members (3 year election period) +* election of members of the executive body of the [Association](/association) (*Association Committee*) (5 year election period) + +## Who makes the decisions + +* our [Members](/membership) with a voting rights \ No newline at end of file diff --git a/docs/core-team/index.md b/docs/core-team/index.md index dac873f5..05c7b47e 100644 --- a/docs/core-team/index.md +++ b/docs/core-team/index.md @@ -1,12 +1,17 @@ # Core Team -The Core Team is the team of people who manage this organization. +The Core Team is the team of people who manage this initiative. -## Email +Core Team members are elected by decision of the [Congress](/congress) for a term of 5 years. It is also exceptionally possible to recall or elect a new member by majority decision of the Core Team itself. -* web3privacynow@skiff.com - -Note: If you use Skiff/Proton Mail you can make the communication E2E encrypted. +## Purpose +* handle daily decision-making of initiative +* communicates with the general public ([Contact us](/contacts)) +* oversees and guides the [Association](/association) +* may extraordinarily elect or recall members of the [Association](/association) Committee +* control access to basic infrastructure (domains, service accounts etc.) +* control on-chain treasury ([Multi-sig wallet](/core-team/multisig)) +* hosts weekly Core Team calls ## Members @@ -35,3 +40,10 @@ Note: If you use Skiff/Proton Mail you can make the communication E2E encrypted. | **Core Team** 🔒 | Main channel - general Core Team discussion | | **Asssociation** 🔒 | Internal discussion about [Association](/association/) | | **Partnership** 🔒 | Partnership workstream discussion | + +## Contact + +### Email +* web3privacynow@skiff.com + +Note: If you use Skiff/Proton Mail you can make the communication E2E encrypted. diff --git a/docs/governance.md b/docs/governance.md new file mode 100644 index 00000000..060560dd --- /dev/null +++ b/docs/governance.md @@ -0,0 +1,48 @@ +# Governance + +In this section you will find a detailed description of how *Web3Privacy Now* governance works. + +## Structure +### Basic units + +*The Web3Privacy Now* initiative is composed of these basic governance units: + +| Name | Purpose | +| --- | --- | +| [Congress](/congress) | top organ, votes on most important issues, elects Core Team/Association executives | +| [Core Team](/core-team) | main decision-making and executive body | +| [Association](/association) | legal entity, executes Core Team requirements, accepts donations, pay expenses | + +### Support units + +| Name | Purpose | Control | +| --- | --- | --- | +| [Contributors Guild](/guild) | group of members receiving incentives | [Association](/association) | +| Marketing & Outreach | marketing and social networks | autonomous | +| Partnerships | recruitment of new (organizational) members | autonomous | +| IT Operation | operation of technical infrastructure | autonomous | +| Design department | designing graphics for our projects | autonomous | + +### Project-specific + +Additionaly, each project has its own [Workgroup](/workgroups#project-specific). + + +## Personal roles within initiative + +Sorted by competencies - from least to most. + +| Role name | Competences | Transparency | +| --- | --- | --- | +| Guest / Visitor | none | 🔒 private | +| [Member](/membership) | none | 🔒 private | +| [Member](/membership) with voting rights | voting on the [congress](/congress) | 🔒 private | +| [Workgroup](/workgroups) member (*contributor*) | decision-making within the working group | 🔒 private | +| [Contributors Guild](/guild) member* | receives financial compensation | 🥷 pseudonym (name, link) | +| [Association](/association) Committee member* | operate with finances and curate [Contributors Guild](/guild) | 👁️ public | +| [Core Team](/core-team) member* | decides on the most important issues, controls [Association](/association) | 🥷 pseudonym (name, link) | + +\* - People with these roles automatically become [Members](/membership) with voting rights: + - Contributors Guild members + - Association Committee members + - Core Team members \ No newline at end of file diff --git a/docs/guild.md b/docs/guild.md new file mode 100644 index 00000000..c4514988 --- /dev/null +++ b/docs/guild.md @@ -0,0 +1,65 @@ +# Contributors Guild + +A collective of *Web3Privacy Now* contributors receiving personal incentives. + +The Contributor Guild serves as the main financial reward system for people working for W3PN. We don't want to give ourselves paychecks, nor do we want to make a complicated system of paying by hourly rates or tasks completed, so we choose a simpler route inspired by the [Protocol Guild](https://protocol-guild.readthedocs.io/). + +This Guild is automatically funded by percentage cut from our income and anyone who does long-term activity (or “work") for W3PN have the opportunity to become a part of this guild and thus receive some financial compensation, based on simple criteria. In simplicity there is power, and we think this system can be much fairer and more scalable. Its also good that it motivates for long-term cooperation. + +## Purpose + +* reward long-term contributors + +## Income + +* XX% of W3PN [membership](/membership) fees and [donations](/donate) (pledged automatically by [Association](/association)) +* direct donations + +## Rules + +### Slot holders + +Slot holders are members of the Guild who have qualified for a placement (slot) in the split contract. Estimated to be around 10-25 individuals, however the actual number may be higher or lower. There is no cap or target for number of slots. Slots can be set to any Ethereum address, including the individual’s own, a charity, or another split contract. + +### Qualification + +Qualifying contributions are all contributions to Web3Privacy Now projects. + +### Expectations + +Members must notify each other if their contribution status changes, or if the work that afforded eligibility breaks one of the guidelines above. If you’re unsure about whether a new focus is still qualified, please ask the broader membership. + +At least once per year, members must prove ownership of the supplied address: members can claim vested funds or sign a message with their private key. This limits the impact of compromised wallets or lost keys. + +Please note that the membership list will be publicly available in order to maintain transparency and mutual trust with both the broader community and sponsors. However, addresses and their associated weights will not be shared. + +### Weighting + +Antifragility and non-gameability emerge from simple frameworks. This limits the time spent deciding appropriate categories, the methods for collecting and verifying as well as the time spent weighting contributors. Additionally, this should limit cases of ambiguity gaming that might come up in complicated weighting schemes. Based on member feedback, we’ve settled on these guidelines: + +SQRT((`eligibleMonths` - `monthsOnBreak`) * `timeWeighting`) + +- Historic contributions are considered in weightings +- `timeWeighting` can be either 1.0 for full-time, .5 for half-time contributors and .25 for part-time contributors +- Existing contributors get “diluted” as newcomers come in +- Continuing contributors get additional weight per month they are active. This means historic contributors don’t maintain their split weighting if they leave protocol development +- Anyone who stops contributing should remove themselves from the membership, and may be removed via periodic curation reviews + +### New members + +Eligible and confirmed members should be given an onboarding form link to be added to the split contract at the next quarterly update. They should also be added to the Protocol Guild’s Discord and given the proper Guild Member / Team roles. + +## Members + +For transparency purposes, we are disclosing each Guild member’s team, the name/identifier, and a link to their work. This set will evolve over time as members leave W3PN development or change teams. + +| Team | Name / Link to work | +| --- | --- | +| TBD | - | + + diff --git a/sidebars.js b/sidebars.js index 3b5bde3e..856f866e 100644 --- a/sidebars.js +++ b/sidebars.js @@ -115,16 +115,25 @@ const sidebars = { { type: "html", className: "sidebar-title", - value: "Governance", + value: "Organization", defaultStyle: true, }, - 'association/index', { type: "category", - label: "Core Team", - link: {type: 'doc', id: 'core-team/index'}, + label: "Governance", + link: {type: 'doc', id: 'governance'}, items: [ - 'core-team/multisig' + 'congress', + { + type: "category", + label: "Core Team", + link: {type: 'doc', id: 'core-team/index'}, + items: [ + 'core-team/multisig' + ], + }, + 'association/index', + 'guild', ], }, 'contacts',