├── AGP-24_Deprecate_0_5_Rinkeby_DAOs.md ├── AGP-2_Aragon_Community_Governance_Model.md ├── AGP-5_Migration_from_Slack ├── Riot.md ├── RocketChat.md ├── Slack.md └── Template.md ├── AGP-5_Migration_to_Open_Source_Messaging_Platform.md ├── AGP-7_Merge_Aragon_HQ_and_Community_meetings.md ├── Code_of_Conduct.md ├── ISSUE_TEMPLATE.md ├── LICENSE └── README.md /AGP-24_Deprecate_0_5_Rinkeby_DAOs.md: -------------------------------------------------------------------------------- 1 | ## Preamble 2 | 3 | AGP: 24 4 | Title: Deprecation of 0.5 Rinkeby DAOs 5 | Author: Brett Sun 6 | Type: Product / Communication 7 | Status: Final, v1.0 8 | Created: 2018-09-27 9 | Last updated: 2018-10-16 10 | Requires: 11 | 12 | ## Abstract 13 | 14 | Updates to aragonOS (`aragonOS@4`) are backwards-incompatible (e.g. non-upgradeable) with the current base contracts and proxy contracts deployed on Rinkeby, affecting any DAOs created via the 0.5 [democracy kit](https://rinkeby.etherscan.io/address/0x344bc497128f1e373639fa0621a12331f65bdc7a) or [multisig kit](https://rinkeby.etherscan.io/address/0x876556bbea9e66e8580adfe1f960dc87c3652bfd). 15 | 16 | A decision has been made to deprecate these old DAOs, and communicate to users the extent of this deprecation as well as how to recreate their DAOs on Rinkeby. 17 | 18 | ## Specification 19 | 20 | ### Goals 21 | 22 | - Effectively communicate to the user base that this deprecation is happening, and allow them to respond 23 | - Make the switch over to the new contracts as painless as possible 24 | 25 | ## Description 26 | 27 | `aragonOS@4` introduces a number of breaking changes from `aragonOS@3`. We'll be deploying these new, backwards-incompatible contracts on both Rinkeby and Mainnet. 28 | 29 | With the upcoming release of Aragon Core v0.6, enough breaking changes have been introduced such that old organizations will be properly loaded anymore. Most important are the contract changes: 30 | 31 | - Old organizations won't be able to upgrade to new versions of any contracts (either internal to aragonOS, like the Kernel or ACL, or any Apps), without there being internal state inconsistencies 32 | - Old organizations won't have access to the recovery vault functionality 33 | - Old organizations will have a number of inconsistencies in declared constants 34 | 35 | As part of the migration, a new root ENS registry, as well as Aragon Package Manager, will be deployed. A new root ENS registry will allow users to recreate DAOs with their old ENS names (although there is the issue with squatting these now known names). 36 | 37 | ### Roadmap 38 | 39 | **Oct. 16, 2018:** 40 | 41 | - Deploy contracts based on `aragonOS@4` to Rinkeby, with new ENS and Aragon Package Manager instances 42 | - Provide a git tag, release, and branch for the deprecated version 43 | - Add [deprecation warning to the current Aragon Core 0.5 frontend](https://github.com/aragon/aragon/issues/364) and additional information in the new Aragon Core if a [DAO could not be found](https://github.com/aragon/aragon/issues/271) 44 | - Blog post, social media posts, outreach, etc. 45 | 46 | **Oct. 29, 2018:** 47 | 48 | - Upgrade Aragon Core, and move Aragon Core v0.5 to a new URL (e.g. app-v05.aragonpm.eth) 49 | - Disable onboarding for the deprecated Aragon Core v0.5 50 | 51 | **Mar. 29, 2019:** 52 | 53 | - Stop hosting Aragon Core v0.5 54 | 55 | ## Uncertainties 56 | 57 | If any users are currently relying on their 0.5 Rinkeby DAOs. We will be listening closely to social media as well as any outreach from users, and help them with this migration. 58 | 59 | ## Contributions 60 | 61 | Thanks to all [5 participants](https://github.com/aragon/governance/issues/33) who contributed to the discussion, as well the attention of those in the all devs call when this was brought up for review. 62 | 63 | ## References 64 | 65 | 1. [https://github.com/aragon/governance/issues/33](https://github.com/aragon/governance/issues/33) 66 | 67 | ## Copyright 68 | 69 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 70 | -------------------------------------------------------------------------------- /AGP-2_Aragon_Community_Governance_Model.md: -------------------------------------------------------------------------------- 1 | ## Preamble 2 | 3 | AGP: 2 4 | Title: Aragon Community Governance Model 5 | Author: Tatu Kärki, Luis Cuende, Jorge Izquierdo 6 | Type: Governance Model 7 | Status: Final, v1.2 8 | Created: 2017-07-12 9 | Last updated: 2017-12-19 10 | Requires: 11 | 12 | ## Abstract 13 | 14 | Community Governance Model, how we plan to achieve transparency and inclusion for the community 15 | 16 | ## Specification 17 | 18 | ### Goals 19 | 20 | We want a productive, happy and agile community that can welcome and bring forth new ideas. 21 | 22 | We will rely on 5 key principles: 23 | 24 | #### Independence 25 | - Decision-making structure 26 | - Independence from employment relations 27 | #### Pluralism 28 | - Diversity of contributors 29 | - Management of conflict 30 | - Determination of leadership—processes and turnover 31 | #### Representation 32 | - Membership structure and rights 33 | - Ways in which those in authority are accountable to contributing members 34 | - Degree to which members can exercise voice on community members 35 | #### Decentralized decision-making 36 | - How contributors gain code commit and #frontline rights 37 | - How contributors gain access to the project’s decision-making structure 38 | - The degree to which project communications and activities are publicly available 39 | #### Autonomous participation 40 | - Newcomer joining rate 41 | - Newcomer socialization opportunities 42 | - Rate of idea generation 43 | 44 | ### Description 45 | 46 | Our Code of Conduct and Community Guidelines act as a basis for all our community activity, how to participate, how to grow our community, how to represent Aragon to others outside the community. 47 | 48 | ## Meetings 49 | 50 | ### **Community Meeting** 51 | - **Monthly, first Friday of the month. Time 17.00 CET.** 52 | 53 | > Team members will produce a write-up of the most important things they have worked on since last Community Meeting, the problems they have found and what they plan to do in the next weeks (that can be a bit blurry, and that's fine). These write-ups will be published as a [blog post](https://blog.aragon.one/) for the community to review on Monday before Friday's meeting. 54 | 55 | > Meeting agenda will be created based on the topics the team members present in their write-ups and discussion entailed around these topics will take place in the meeting. Live chat audience of the meeting is encouraged to participate and comment on the discussion during the meeting. 56 | 57 | > Following all the other things in the meeting agenda, an AMA (Ask Me Anything) will take place where the team answers questions by the community. The AMA questions can be posted at a dedicated thread on [/r/aragonproject](https://www.reddit.com/r/aragonproject/). 58 | 59 | - **Facilitator**: Project Lead 60 | - **Participants**: All Aragon team members + possible relevant contributors 61 | - **Viewers**: Public on [Youtube](https://www.youtube.com/c/AragonProject) 62 | 63 | ### **Team hangout** 64 | - *Weekly, Friday. Time 15.00 CEST* 65 | > Relaxed weekly meeting with the team where anyone can talk about things they feel are current 66 | - **Facilitator**: If needed, any of the participants 67 | - **Participants**: Project Lead + anyone from the Aragon team who wants to participate 68 | - **Viewers**: Non-public 69 | 70 | **Aragon HQ** Meetings were held previously once a month, but have been merged into one Community Meeting as per _[AGP7: Merge Aragon HQ and Community meetings](https://github.com/aragon/governance/issues/15)_. 71 | 72 | ## Structures 73 | - Project Lead or Tech Lead will have final call on all things pertaining to their area of expertise. 74 | - Decisions made after thorough conversation on Meetings, informal vote to be taken if necessary, possible conflicts discussed if necessary, final vote if needed and decision confirmed by Project/Tech Lead. 75 | - Facilitators are responsible for gathering the agenda for the Meetings where applicable, as well as either taking notes of the Meeting and decisions made or delegating this responsibility to another participant 76 | - Use (The Etherian’s or our own) Colony to have community members participate and get rewarded for their non-code contributions 77 | - Implement a system similar to [Maker’s Actions](http://makerdao.com/actions/) and post a monthly transparency report about the use of funds to the blog 78 | - Institute Aragon Improvement Proposal, AIP, system for community members to create proposals about Aragon. Take a similar approach for governance with [Aragon Governance Proposals](https://github.com/aragon/governance/issues) (like this one). GitHub Issues will be used as a forum to discuss proposals by community and team members 79 | - Proposals and ideas from the team and community members will be go through the AIP/AGP process and will then be discussed in the relevant Meetings 80 | - Community Meetings will be AMA styled video meetings where team members will answer questions by the community members. Questions will be submitted through [Reddit](https://www.reddit.com/r/aragonproject/) and answered live 81 | - We’ll have templates that can/will be used for the basis of agendas in Meetings so the Facilitator can easily fill out each Meetings info, like who will be presenting what, who has slides etc. 82 | - Facilitator of the Meeting will make sure that the discussion stays on rails, everyone gets a chance to speak their mind, everything on the agenda is discussed, necessary decisions are made and that the Meeting length stays on a reasonable length 83 | 84 | 85 | ## Uncertainties 86 | 87 | None right now, version 1.0 is finalized! 88 | 89 | ## Contributions 90 | 91 | Thanks to @kennyrowe for the feedback on this! 92 | 93 | ## References 94 | 95 | 1. https://blog.aragon.one/aragons-community-governance-model-2971df8f7817 96 | 97 | ## Copyright 98 | 99 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 100 | -------------------------------------------------------------------------------- /AGP-5_Migration_from_Slack/Riot.md: -------------------------------------------------------------------------------- 1 | # [Riot](https://riot.im) 2 | 3 | ### Projects currently using this platform 4 | 5 | - [Parity](https://parity.io) 6 | - [Polkadot](https://polkadot.network) 7 | - [Raiden Network](https://raiden.network) 8 | 9 | ### Pros 10 | - Federated architecture: Any user in any community could talk to another one in another different community, seamlessly 11 | - Decentralized infrastructure; Even though matrix.org provides everything needed for Projects and users, self-deployed instances are also supported and widely used on the Matrix standard 12 | - Server Deployment supported: Be in control of your own data 13 | - End-to-end encryption for private messages and public as well as closed group chats: Useful for internal communications, for example 14 | - Built using React, easy to maintain and work on 15 | - Numeral user-levels, easy to set different levels for usergroups, ie. 50 for Moderator, 100 for Admin 16 | - Communities: Ability to create Communities provides the project ability to create multiple channels within their Community and visible to users within the Community, removes bloating from the interface 17 | - Communities will provide ability to do Community wide bans (Unsure if a community can join a community to create an umbrella community for ie. Ethereum Community wide bans) 18 | - They have message pinning, message editing and reactions coming by the end of 2017 19 | - Reactions coming by the end of 2017 20 | - Basic moderation and rich moderation API 21 | - Roadmap for upvotes/downvotes on messages and per-member reputation 22 | - Usernames can contain flags, similar to Reddit, to signal status in the community 23 | - Notifications: Work on web, desktop and mobile, includes notifications inbox 24 | - A huge range of clients that support the Matrix standard, Riot is just one of them 25 | - Bridges: Allows you to mirror the messages from Slack, Gitter, IRC, Twitter, Telegram, SMS and more 26 | - Native mobile clients for Android and iOS, and [desktop too](https://github.com/mujx/nheko) 27 | - Mobile clients are superior to Rocket.Chat's, work well 28 | - Has arbitrarily finely grained ACLs (based on a 'power level' system where users get a numeric power level from 0 to 100) 29 | 30 | ### Cons 31 | 32 | - UX is bad, specially for newcomers 33 | - Encryption / key exchange is buggy and keeps causing issues in encrypted channels, unfortunately 34 | - Lack of message pinning, editing and reactions, but as seen above, they're coming by the end of 2017 35 | - They are having [funding](https://github.com/vector-im/riot-web/issues/2977) [issues](https://matrix.org/blog/2017/07/07/a-call-to-arms-supporting-matrix/) and require a very significant amount of capital to continue with the project for the next 18 months, at least. *This might be a lesser issue, but not confirmed* 36 | - No customization options in the client for Projects 37 | - Self-deployed instances aren't necessary, but would incur monthly costs if used 38 | -------------------------------------------------------------------------------- /AGP-5_Migration_from_Slack/RocketChat.md: -------------------------------------------------------------------------------- 1 | # [Rocket.Chat](https://rocket.chat/) 2 | 3 | ### Projects currently using this platform 4 | 5 | - [MakerDAO](https://makerdao.com/) 6 | - [Storj](https://storj.io/) 7 | - [Basic Attention Token](https://basicattentiontoken.org/index/) 8 | 9 | ### Pros 10 | - [Slack Import](https://rocket.chat/docs/administrator-guides/import/slack): Import your current data, users and channels to Rocket Chat 11 | - [Registration](https://rocket.chat/docs/user-guides/registration): Multiple options can be used: Manual registration using email. OAuth registration using GitHub, GitLab, Google, Facebook, Twitter, LinkedIn, Meteor 12 | - Room Info: Easily set Topic, Announcement & Description for every channel individually. Any room can be set as Private, Read Only or Archived 13 | - [Off-The-Record](https://rocket.chat/docs/user-guides/off-the-record): OTR - encrypted conversations 14 | - [Search history](https://rocket.chat/docs/user-guides/searching-messages): Not limited to just last 10,000 messages in the platform 15 | - [Notifications](https://rocket.chat/docs/user-guides/notifications): Seperate settings for Audio, Desktop, Mobile, Email & Unread alert 16 | - [Roles](https://rocket.chat/docs/administrator-guides/permissions): Roles Available - Admin, Moderator, Owner, User, Bot. Multiple permission available that can be set 17 | - [Permissions](https://rocket.chat/docs/) Granular permissions for different uses classes 18 | - [UI and Theming](https://rocket.chat/docs/developer-guides/ui-and-theming): Projects can have customized, personalized themes set for themselves 19 | - [Slack Bridge](https://rocket.chat/docs/administrator-guides/import/slack/slackbridge): Allows you to mirror the messages received in a Slack channel or private group into Rocket.Chat in real-time 20 | - Messages can be [pinned](https://rocket.chat/docs/user-guides/pinning-messages) and [starred](https://rocket.chat/docs/user-guides/starring-messages) 21 | - [Reactions](https://rocket.chat/docs/user-guides/reactions): Quickly respond to any message with an emoji reaction 22 | - [Server Deployment required](https://rocket.chat/docs/installation/minimum-requirements): Be in control of your own data 23 | - [Supports integrations via WebHooks](https://rocket.chat/docs/administrator-guides/integrations) 24 | - [End-to-End Encryption](https://github.com/RocketChat/Rocket.Chat/pull/7181) has a Pull Request at Github 25 | - Will likely integrate the same Matrix network that Riot uses into their backend at some point 26 | 27 | ### Cons 28 | - [Slack Import](https://rocket.chat/docs/administrator-guides/import/slack): Can't import DM's and private channels 29 | - [OTR](https://rocket.chat/docs/user-guides/off-the-record) requires both participants requires both sides to be online 30 | - [OTR](https://rocket.chat/docs/user-guides/off-the-record): Improvements to End-to-End Encryption Implemenation still needed 31 | - [Requires a Server Deployment](https://rocket.chat/docs/installation/minimum-requirements): [Manual or PaaS options available](https://rocket.chat/docs/installation/paas-deployments) for deployment 32 | - Server Deployment will incur monthly costs, ballpark approximation could be $50/month 33 | - Centralized Server Deployment can create a single-point of failure for a Project 34 | - Mobile Apps for Android and iOS are available, have received bad reviews from users 35 | - [UI and Theming](https://rocket.chat/docs/developer-guides/ui-and-theming) is still an incomplete feature 36 | -------------------------------------------------------------------------------- /AGP-5_Migration_from_Slack/Slack.md: -------------------------------------------------------------------------------- 1 | # [Slack](https://slack.com/) 2 | 3 | ### Projects currently using this platform 4 | 5 | - [Numerai](https://numer.ai/) 6 | 7 | ### Pros 8 | - Allows 3rd party integrations/extensions 9 | - Group mentions (@channel @everyone) with limit for admins 10 | - Custom emojis, reactions, message pinning and starring 11 | - Custom theming 12 | - Well working web, desktop and mobile clients 13 | 14 | ### Cons 15 | - No intent to ever support public facing communities; Slack is meant for internal use of teams with only trusted members in the community 16 | - No built in moderation tools (requires 3rd party integrations) 17 | - 10k message limit unless paid 18 | - Easy to abuse bots (`/remind @user MyEtherWallet has been hacked. Please visit scamlink.com to resolve in 1 minute`) 19 | - Easy to create official sounding usernames (@MyEtherWalletBot) 20 | - Proprietary software, no way to extend or maintain it ourselves 21 | - Limited to one channel that can be Read Only so that only Admins can post 22 | - Only three types of Roles: Owners, Admins and Users (Guests are available but rarely used) 23 | - Centralized platform, single-point of failure, if Slack has issues with servers or connectivity, everything goes offline 24 | - No possible way to create a wider umbrella community, ie. Ethereum Community under which Projects can live 25 | - Horrible Admin tools that require usage of web version 26 | - [Usernames are now deprecated](https://api.slack.com/changelog/2017-09-the-one-about-usernames) and not seen in the client - only Display Names or Full Names, neither of which are required to be unique (allowing for very easy impersonation of team members or other users) 27 | -------------------------------------------------------------------------------- /AGP-5_Migration_from_Slack/Template.md: -------------------------------------------------------------------------------- 1 | # [Platform Name](http://linktoplatform.com) 2 | 3 | ### Projects currently using this platform 4 | 5 | - [Project Name](http://linktoproject.com) 6 | - [Project2 Name](http://linktoproject2.com) 7 | 8 | ### Pros 9 | - Awesome feature 1: Description here 10 | - Awesome feature 2: Description here 11 | 12 | ### Cons 13 | - Horrible feature 1: Description here 14 | - Horrible feature 2: Description here 15 | 16 | -------------------------------------------------------------------------------- /AGP-5_Migration_to_Open_Source_Messaging_Platform.md: -------------------------------------------------------------------------------- 1 | ## Preamble 2 | 3 | AGP: 5 4 | Title: Migration to Open Source Messaging Platform 5 | Author: Tatu Kärki 6 | Type: Governance Enhancement / Communication 7 | Status: Final, v1.1 8 | Created: 2017-10-10 9 | Last updated: 2017-12-19 10 | Requires: 11 | 12 | ## Abstract 13 | 14 | Migrate the community chat to an open source messaging platform. 15 | 16 | Initiate discussion within the Ethereum ecosystem and establish a joint effort with other projects in the space to find an alternative that fit the needs of these cryptocurrency projects. 17 | 18 | ## Specification 19 | 20 | ### Goals 21 | 22 | - Migrate the community from Slack to [Rocket.Chat](https://github.com/RocketChat) or [Riot](https://github.com/vector-im) 23 | - Create a Rocket.Chat client app in collaboration with other Ethereum projects with a project selector if Rocket.Chat is the chosen platform 24 | - Begin the process together with the [Rocket.Chat](https://github.com/RocketChat) team to create _[Rocket.Chat for Cryptocurrency Communities](https://github.com/RocketChat/Rocket.Chat/issues/8284)_ 25 | 26 | ## Description 27 | 28 | As Slack was designed for internal use of projects, the tools to run public facing communities are lacking in features that these projects would benefit from having. Migration to a open source project, [Rocket.Chat](https://rocket.chat/) or [Riot](https://github.com/vector-im), will help us manage and govern our communities more efficiently. 29 | 30 | Our idea is to fork of the [Rocket.Chat Electron app](https://github.com/RocketChat/Rocket.Chat.Electron) and together in collaboration with other interested projects create a new app for the Ethereum community to have a project selector similar to Slack. The selector could be pre-filled with a list of Ethereum community projects for ease of use. This would help community members by only having one app for the projects that choose to use Rocket.Chat instead of other alternative chat apps and thus bringing the community closer to each other by using a shared tool that can be updated by anyone via Pull Requests to the community driven repository. Projects using this could also pool resources together and support the development of Rocket.Chat, as well as making it more usable. 31 | 32 | Initially we would like to hear from other projects in the space to see how much interest there is in such a tool and migration process. Setting up Rocket.Chat requires projects to set up their infrastructure for the service, more information can be found in the [Rocket.Chat Documentation](https://rocket.chat/docs/) and there's an [Import tool](https://rocket.chat/docs/administrator-guides/import/slack) that can easily migrate your users and channels to Rocket.Chat (but not DM's and private channels). 33 | 34 | [Riot](https://github.com/vector-im) does not require such efforts as Rocket.Chat, but has the option to run your own infrastructure. 35 | 36 | ### Documents for comparison 37 | Two documents were created so projects can evaluate the features and possibilities provided by the two open source projects, [Rocket Chat](https://github.com/rocketchat) and [Riot](https://github.com/vector-im). 38 | 39 | Read about [RocketChat](https://github.com/aragon/governance/blob/master/AGP-5_Migration_from_Slack/RocketChat.md). 40 | 41 | Read about [Riot](https://github.com/aragon/governance/blob/master/AGP-5_Migration_from_Slack/Riot.md). 42 | 43 | ## Uncertainties 44 | 45 | None right now, version 1.0 is finalized! 46 | 47 | ## Contributions 48 | 49 | Thanks to all the [45 participants](https://github.com/aragon/governance/issues/7) who contributed to the discussion. 50 | 51 | Big thank you to all the projects that contributed and initially joined in on this migration plan and made it a reality. 52 | 53 | - [**Auctus Project**](http://auctus.org/) / [Announcement](https://medium.com/auctus/announcing-our-migration-to-an-open-source-messaging-platform-d061844837d5) 54 | - [**Cofound.it**](https://cofound.it) / [Announcement]() 55 | - [**Decentraland**](https://decentraland.org) / [Announcement](https://twitter.com/decentraland/status/911254767430709248) 56 | - [**FOAM**](https://www.foam.space/) / [Announcement](https://blog.foam.space/announcing-our-involvement-in-the-joint-migration-to-rocket-chat-ee4d99364c39) 57 | - [**Golem**](https://golem.network/) / [Announcement](https://blog.golemproject.net/farewell-to-slack-rocket-here-we-come-d5b82aac6c24) 58 | - [**Indorse**](https://indorse.io) / [Announcement](https://medium.com/joinindorse/announcing-the-indorse-migration-from-slack-to-rocket-chat-e6a643d87f39) 59 | - [**OmiseGO**](https://www.omise.co/) / [Announcement](https://blog.omisego.network/omisego-migrating-to-rocket-chat-11f5ae229191) 60 | - [**Santiment**](https://santiment.net) / [Announcement](https://medium.com/santiment/goodbye-slack-hello-open-source-messaging-platform-c97398a20ce9) 61 | - [**Streamr**](https://www.streamr.com/) / [Announcement](http://blog.streamr.com/2017/09/goodbye-slack-goodbye-scammers-hello-rocket-chat/) 62 | 63 | - [**0xproject**](https://0xproject.com) / [Announcement](https://twitter.com/0xproject/status/923273503721140224) 64 | 65 | ## References 66 | 67 | 1. [https://github.com/aragon/governance/issues/7](https://github.com/aragon/governance/issues/7) 68 | 2. [https://blog.aragon.one/announcing-our-migration-to-an-open-source-messaging-platform-420b25e74284](https://blog.aragon.one/announcing-our-migration-to-an-open-source-messaging-platform-420b25e74284) 69 | 3. [https://blog.aragon.one/aragon-chat-is-now-open-d75558df1874](https://blog.aragon.one/aragon-chat-is-now-open-d75558df1874) 70 | 71 | ## Copyright 72 | 73 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 74 | -------------------------------------------------------------------------------- /AGP-7_Merge_Aragon_HQ_and_Community_meetings.md: -------------------------------------------------------------------------------- 1 | ## Preamble 2 | 3 | AGP: 7 4 | Title: Merge Aragon HQ and Community meetings 5 | Author: Luis Cuende, Jorge Izquierdo, Tatu Kärki 6 | Type: Governance Enhancement / Communication 7 | Status: Final, v1.0 8 | Created: 2017-11-14 9 | Last updated: - 10 | Requires: 11 | 12 | ## Abstract 13 | 14 | The tl;dr about the HQ meeting is as follows: 15 | 16 | > Discussion about the state of Aragon, near future plans and decisions that need to be made. 10 min presentations with slides from team members, in which each one will run through the most important things we have done during the month 17 | 18 | Since we're mostly running through slides, it makes sense for all team members to just work on them and publish them online. We can publish them on Mon, and then leave the whole week for the community to review it and prepare questions for the Community meeting on Fri. 19 | 20 | Every team member should look at each other's slides and prepare for the call, asking any questions that may have emerged. The community should do the same. 21 | 22 | This way, we both save time in meetings, while being even more accountable, since accessing slides would be easier for the community than watching a very long call. 23 | 24 | ## Specification 25 | 26 | ### Goals 27 | 28 | - Replace most part of the Aragon HQ meeting with publicly-accessible slides 29 | - Leave all discussion related to the Aragon HQ meeting to the Community meeting, in order to unify them and reduce the time we spend on calls and "office" bureaucracy 30 | 31 | ## Description 32 | 33 | Team members will produce a write-up of the most important things they have worked on since last Community Meeting, the problems they have found and what they plan to do in the next weeks (that can be a bit blurry, and that's fine). These write-ups will be published as a [blog post](https://blog.aragon.one/) for the community to review on Monday before Friday's meeting. 34 | 35 | Meeting agenda will be created based on the topics the team members present in their write-ups and discussion entailed around these topics will take place in the meeting. Live chat audience of the meeting is encouraged to participate and comment on the discussion during the meeting. 36 | 37 | Following all the other things in the meeting agenda, an AMA (Ask Me Anything) will take place where the team answers questions by the community. The AMA questions can be posted at a dedicated thread on [/r/aragonproject](https://www.reddit.com/r/aragonproject/). 38 | 39 | ## Uncertainties 40 | 41 | Should there be a break between discussion and AMA segments. 42 | 43 | ## Contributions 44 | 45 | Thanks to @shylybugs for commenting on the proposal. 46 | 47 | ## References 48 | 49 | 1. http://wiki.aragon.one/documentation/Community_Governance_Model/ 50 | 51 | ## Copyright 52 | 53 | Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). 54 | -------------------------------------------------------------------------------- /Code_of_Conduct.md: -------------------------------------------------------------------------------- 1 | # Aragon Code of Conduct 2 | 3 | Contributors are expected to follow the Aragon Code of Conduct, which can be found in our wiki: 4 | 5 | http://wiki.aragon.one/documentation/Code_of_Conduct/ 6 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ### Goals 2 | 3 | Describe the overall goals of the AGP here, preferably in a list of a few concise bullet points. 4 | 5 | - Goal 1 6 | - Goal 2 7 | - Goal 3 8 | 9 | ### Description 10 | 11 | Go into detail here. Explain what the AGP does and why. 12 | 13 | ### Uncertainties 14 | 15 | Describe some unsolved problems or points of discussion, if there are any. 16 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Aragon Governance 2 | 3 | This repo has been deprecated. You can find the new Aragon governance repo [here](https://github.com/aragon/AGPs). 4 | --------------------------------------------------------------------------------