From d6f7506b385c5fd93b6333a234129ade78bc61c8 Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Tue, 28 May 2019 18:29:40 +0200 Subject: [PATCH 01/20] Guide update --- .DS_Store | Bin 0 -> 6148 bytes docs/.DS_Store | Bin 0 -> 6148 bytes docs/Proposal guid.md | 117 ++++++++++++++++++++++++++++++++++++++++ docs/guides/proposal.md | 27 ---------- docs/templates/team.md | 23 -------- 5 files changed, 117 insertions(+), 50 deletions(-) create mode 100644 .DS_Store create mode 100644 docs/.DS_Store create mode 100644 docs/Proposal guid.md delete mode 100644 docs/guides/proposal.md delete mode 100644 docs/templates/team.md diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000000000000000000000000000000000000..eeb9ef37e229b333181b5c1fa9bf0743e682018e GIT binary patch literal 6148 zcmeHK!D<^Z5FI&ot92>$A&?yRQs}`18@CB11U9a7$e~cWr8%@E+0B|}VY3R}bxh;9 z>~AE0kWa}M^mE!bl4=^Ky_!%oFnXiWjD(&RX@`hJf1GrQT0|tFj5QC}TpY&Qy#(Pw3>~Gr(t8r-T$8Q?YP<+ZcQCQ;XinJT9ITXZDc@kUugHqYtj^dB$aB|pMeWUU+O7r1J zC#T5}A)gP@JW-Rr8s|x&=LyY#l%DhsTkF$lZ?o6-yRTl)+WvHFtJC&h_BLlTPp&=h z?(83(e!G}n&c0unvk>@DwLG)<8?Ir@H+UY7@=WDl;p2FZ-qRlK(tzFqH|Ug-1*&ck z^(R#gDrra&A{R&%YYUO+I&lm*1{?#+X24#B^2xFncI!C?90L!Y0lpu6C}Uu;GN`W( zG`a);*5TFyTmSk4eRco?im~M;T|Gj_L|96vI&oST__^%ic^+7o3V@vjJy|+1jYklYu ql!fCegYy&^`YA>%KgH`%E%5tn00WDaL3kkUM?lly8pps=8TbX**>g$& literal 0 HcmV?d00001 diff --git a/docs/.DS_Store b/docs/.DS_Store new file mode 100644 index 0000000000000000000000000000000000000000..2a139b2f3ba018550e0f159ba9a145edeb13d158 GIT binary patch literal 6148 zcmeH~KTE_w5XIl<6$duQRhC;?iC5c%;}op@0P6ig!C*wVKAj(1-^{FHh=P@cyn)%b zJDJHQzao0n7kQ>8^P7VQhZgePjnUVpKZs@rWBdV23+wN7>&8ympRDwCJ!I z)bH?uGc0h5XFTEls_i!Gwp%mbANHJn@)pLKOaw$g1VlgtMBujsy!Xk>asviO8A`^kXAn*=n868^y literal 0 HcmV?d00001 diff --git a/docs/Proposal guid.md b/docs/Proposal guid.md new file mode 100644 index 0000000..a0cf2f9 --- /dev/null +++ b/docs/Proposal guid.md @@ -0,0 +1,117 @@ +# Aragon Flock proposal: Team name + +## 1. Summary + +- This section should include the high level strategy of the proposal in simple terms. +- It can be accompanied by a few references from past team achievements. In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports. + + +## 2. Deliverables + +### Deliverables summary table +*This table aims at giving a visual summary of the focus of the team and the allocation of team effort to each category of deliverables. Evaluating such future data is difficult, but the thought exercise provides a good idea of the mindset of the team and its general focus.* + +#### Example +> | Category | Dev tools | Aragon apps | User experience | XYZ | +> |------------------------|-----------|-------------|------------------|-----| +> | Nb of deliverables | 2 | 1 | 3 | 1 | +> | Team effort allocated | 30% | 20% | 40% | 10% | + +Note: categories can be invented as needed by the applicant team. + +### Initiatives + +*In this section are provided all the concrete elements the applicant team is planning to work on. These should be listed as initiatives by order of priority.* + +For each initiative, in order to justify it is relevant please detail shortly: +- Value proposition - *How it will provide value to the end user (i.e. developer or end user)* +- Deliverables - *What precisely will be implemented in regard of this initiative* +- Background - *A link to a Github issue, a Flock roadmap item, a Nest proposal, user feedback, or any material backing its relevancy* +- Long-term vision of initiative - *This last item is optional* + +#### Example + +*Here is an example of initiative inspired from a past Flock proposal* + +> ### I01 - Fundraising +> +> The goal of this topic is to provide a library and a standalone dApp any Aragon DAO can use to raise funds through a Continuous Funding scheme. +> +> #### Deliverables +> +> **Fundraising library:** Develop a modular fundraising library providing low-level building-blocks: curves, taxation mechanisms, withdrawal mechanisms, etc. +> +> **Fundraising app:** Develop an opinionated but ready-to-use fundraising app - based on the previous library - implementing the [Apiary][link] scheme designed by [@lkngtn][link]. +> +> #### Background +> +> A PoC of such a fundraising app is already available [here][link] and demoed [here][link]. + + +## 3. Grant Size + +*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would need to incentivize the team long term commitment* + +#### Example + +> ### Estimated operating costs for Q2 and Q3 2019 +> +> | Type | Description | Amount | +> | ----------- | :------------------------------------: | -----: | +> | Payroll | | \$410k | +> | Contractors | DevOps \| Design \| Legal \| etc. | \$10k | +> | Services | GitHub \| Google Suite \| Chat \| etc. | \$5k | +> | Travel | Offsites \| Conferences \| etc. | \$10k | +> | Equipment | Laptop \| etc. | \$15k | +> | **Total** | | \$450k | + + +*Regarding the ANT package please be sure to provide the number of ANT per team member per year.* + +> ### ANT package +> +> We would like to request **25k ANT per team member per year** for incentivization purpose, i.e. **125k ANT** for this six months long proposal. We are committed to the Aragon Network in the long-term and therefore accept a 4-years vesting schedule. + +## 4. Team + +*This is the basic structure you should follow when creating your proposal where you briefly describe of the current team members and their relevancy for the role with links to their relevant social media channels (github, twitter, etc) and provide info of future openings if you plan to hire more people during the year.* + +### AraEagles Example Team + +- #### John Doe — Project Lead + +John has 20 years of experience coding Solidity. He bought Bitcoin in 1995, therefore inventing the blockchain. He admits to be the real Craig Wright. + +**Socials**: [GitHub](#) [Twitter](#) + +- #### Satoshi Nakamoto — Frontend Dev + +Satoshi loves React and React Native. He met John 5 years ago in a hackathon + +**Socials**: [GitHub](#) [Twitter](#) + +- #### Maria Garcia — Security Researcher + +Maria has been working on different projects in the Ethereum both creating and auditing smart contracts. She would like to work full time on pure research. + +**Socials**: [GitHub](#) [Twitter](#) + +## 5. Requirements + +*List of aragon accounts, channels, tools, assets, domains and infrastructure that you need in order to operate* + +| Access to | Yes/No | If Yes, precise requirement | +|----------------------------------------------------------------------------------|--------|------------------------------| +| Blog access on blog.aragon.org | | | +| Social media access | | | +| Website access on all Aragon domains | | | +| Repo access on the entire @aragon organization | | | +| Unrestricted use of the Aragon trademark | | | +| Publish access to aragonpm.eth | | | +| Access to Aragon servers and cloud infrastructure | | | +| Access to Aragon DNS and ENS domains | | | +| Admin/moderator access on aragon.chat, forum.aragon.org, and /r/AragonProject | | | + +## 6. Organization structure + +*Under What type of organization, if any, is the team organized* diff --git a/docs/guides/proposal.md b/docs/guides/proposal.md deleted file mode 100644 index 1b9ef46..0000000 --- a/docs/guides/proposal.md +++ /dev/null @@ -1,27 +0,0 @@ -# Aragon Flock proposal: Team name - -## Summary - -*Brief description of the main points of the proposal* - -## Deliverables - -*List and briefly describe the parts of the Aragon project your team wants to work on* - -*In an effort not to duplicate information, all the product-related deliverables must go through the AIP1 process. In the meantime, we can use this forum thread as the reference for deliverables for the Aragon client* - -## Grant Size - -*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would need to incentivize the team long term commitment* - -## Requirements - -*List of aragon accounts, channels, tools, assets, domains and infrastructure that you need in order to operate* - -## Team - -*Link to the files team.md submitted in your pull request* - -## Organization structure - -*Under What type of organization, if any, is the team organized* diff --git a/docs/templates/team.md b/docs/templates/team.md deleted file mode 100644 index 5e67087..0000000 --- a/docs/templates/team.md +++ /dev/null @@ -1,23 +0,0 @@ -# Team template - -This is the basic structure you should follow when creating your team.md where you briefly describe of the current team with links to their relevant social media channels (github, twitter, etc) and provide info of future openings if you plan to hire more people during the year. - -## AraEagles Example Team - -- ### John Doe — Project Lead - -John has 20 years of experience coding Solidity. He bought Bitcoin in 1995, therefore inventing the blockchain. He admits to be the real Craig Wright. - -**Socials**: [GitHub](#) [Twitter](#) - -- ### Satoshi Nakamoto — Frontend Dev - -Satoshi loves React and React Native. He met John 5 years ago in a hackathon - -**Socials**: [GitHub](#) [Twitter](#) - -- ### Maria Garcia — Security Researcher - -Maria has been working on different projects in the Ethereum both creating and auditing smart contracts. She would like to work full time on pure research. - -**Socials**: [GitHub](#) [Twitter](#) From 5bd8d54a6fb97e07b3a720d6d6ee532e1f401ada Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Tue, 28 May 2019 18:40:57 +0200 Subject: [PATCH 02/20] udpate proposal guide --- docs/{Proposal guid.md => Proposal guide.md} | 71 ++++++++++---------- 1 file changed, 37 insertions(+), 34 deletions(-) rename docs/{Proposal guid.md => Proposal guide.md} (77%) diff --git a/docs/Proposal guid.md b/docs/Proposal guide.md similarity index 77% rename from docs/Proposal guid.md rename to docs/Proposal guide.md index a0cf2f9..c104a22 100644 --- a/docs/Proposal guid.md +++ b/docs/Proposal guide.md @@ -2,8 +2,9 @@ ## 1. Summary -- This section should include the high level strategy of the proposal in simple terms. -- It can be accompanied by a few references from past team achievements. In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports. +This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements. + +In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports. ## 2. Deliverables @@ -24,27 +25,27 @@ Note: categories can be invented as needed by the applicant team. *In this section are provided all the concrete elements the applicant team is planning to work on. These should be listed as initiatives by order of priority.* For each initiative, in order to justify it is relevant please detail shortly: -- Value proposition - *How it will provide value to the end user (i.e. developer or end user)* -- Deliverables - *What precisely will be implemented in regard of this initiative* -- Background - *A link to a Github issue, a Flock roadmap item, a Nest proposal, user feedback, or any material backing its relevancy* -- Long-term vision of initiative - *This last item is optional* +- **Value proposition** - *How it will provide value to the end user (i.e. developer or end user)* +- **Deliverables** - *What precisely will be implemented in regard of this initiative* +- **Background** - *A link to a Github issue, a Flock roadmap item, a Nest proposal, user feedback, or any material backing its relevancy* +- **Long-term vision for initiative** - *This last item is optional* #### Example *Here is an example of initiative inspired from a past Flock proposal* > ### I01 - Fundraising -> +> #### Value proposition > The goal of this topic is to provide a library and a standalone dApp any Aragon DAO can use to raise funds through a Continuous Funding scheme. -> +> > #### Deliverables -> +> > **Fundraising library:** Develop a modular fundraising library providing low-level building-blocks: curves, taxation mechanisms, withdrawal mechanisms, etc. -> +> > **Fundraising app:** Develop an opinionated but ready-to-use fundraising app - based on the previous library - implementing the [Apiary][link] scheme designed by [@lkngtn][link]. -> +> > #### Background -> +> > A PoC of such a fundraising app is already available [here][link] and demoed [here][link]. @@ -52,10 +53,12 @@ For each initiative, in order to justify it is relevant please detail shortly: *Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would need to incentivize the team long term commitment* +*Regarding the ANT package please be sure to provide the number of ANT per team member per year.* + #### Example > ### Estimated operating costs for Q2 and Q3 2019 -> +> > | Type | Description | Amount | > | ----------- | :------------------------------------: | -----: | > | Payroll | | \$410k | @@ -66,35 +69,35 @@ For each initiative, in order to justify it is relevant please detail shortly: > | **Total** | | \$450k | -*Regarding the ANT package please be sure to provide the number of ANT per team member per year.* + > ### ANT package -> +> > We would like to request **25k ANT per team member per year** for incentivization purpose, i.e. **125k ANT** for this six months long proposal. We are committed to the Aragon Network in the long-term and therefore accept a 4-years vesting schedule. ## 4. Team *This is the basic structure you should follow when creating your proposal where you briefly describe of the current team members and their relevancy for the role with links to their relevant social media channels (github, twitter, etc) and provide info of future openings if you plan to hire more people during the year.* -### AraEagles Example Team - -- #### John Doe — Project Lead - -John has 20 years of experience coding Solidity. He bought Bitcoin in 1995, therefore inventing the blockchain. He admits to be the real Craig Wright. - -**Socials**: [GitHub](#) [Twitter](#) - -- #### Satoshi Nakamoto — Frontend Dev - -Satoshi loves React and React Native. He met John 5 years ago in a hackathon - -**Socials**: [GitHub](#) [Twitter](#) - -- #### Maria Garcia — Security Researcher - -Maria has been working on different projects in the Ethereum both creating and auditing smart contracts. She would like to work full time on pure research. - -**Socials**: [GitHub](#) [Twitter](#) +#### AraEagles Example Team + +> - #### John Doe — Project Lead +> +> John has 20 years of experience coding Solidity. He bought Bitcoin in 1995, therefore inventing the blockchain. He admits to be the real Craig Wright. +> +> **Socials**: [GitHub](#) [Twitter](#) +> +> - #### Satoshi Nakamoto — Frontend Dev +> +> Satoshi loves React and React Native. He met John 5 years ago in a hackathon +> +> **Socials**: [GitHub](#) [Twitter](#) +> +> - #### Maria Garcia — Security Researcher +> +> Maria has been working on different projects in the Ethereum both creating and auditing smart contracts. She would like to work full time on pure research. +> +> **Socials**: [GitHub](#) [Twitter](#) ## 5. Requirements From 2d847a840ce06365fdcbe0606ffae02ecac289d8 Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Tue, 28 May 2019 18:46:34 +0200 Subject: [PATCH 03/20] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 25b30bb..d1a0903 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ The application process is open and public and it will take place in this dedica **How to submit your proposal** - Fork the Aragon Flock GitHub repository - Create a new directory with the team’s name inside the *teams/* folder -- Inside the directory, create one file: *team.md* ([see template](https://github.com/aragon/flock/blob/master/docs/templates/team.md)), where you present the team +- Inside the directory, create one file: *proposal.md* ([see proposal guide](https://github.com/LouisGrx/flock/blob/master/docs/Proposal%20guid.md)), where you present the overall application and team - Create a pull request to merge your submission into the Flock repository. In that pull request fill in all the relevant info described in the template - Amendments to the initial proposal can be made by creating a pull request over the existent pull request for the relevant review. @@ -29,7 +29,7 @@ The Aragon Association and representatives of the current Aragon teams will revi **Operation costs** -Part of the funding is intended to cover the annual operating cost of each team. The minimum amount of funds available for operations is $1 million paid in ETH or DAI. +Part of the funding is intended to cover the annual operating cost of each team. The minimum amount of funds available for operations is $300K paid in ETH or DAI. **Incentivization package** @@ -39,7 +39,7 @@ After the definitive approval of funding as per the AGP-1 process, funds for ope ## Decision rationale -Decisions are made by the Aragon Association and representatives of the independent teams that are already part of the Aragon project. Everybody will participate in the review process. All decisions must be consistent with the [goals and values](https://github.com/aragon/AGPs/blob/master/AGPs/AGP-0.md) of the Aragon project and represent the interests of the Aragon community. +Decisions are made by the Aragon Association in a process which includes gathering opinions from members of the independent teams that are already full-time contributors to the Aragon project. Everybody will participate in the review process. All decisions must be consistent with the [goals and values](https://github.com/aragon/AGPs/blob/master/AGPs/AGP-0.md) of the Aragon project and represent the interests of the Aragon community. **What do we look for in teams** From 5aeeed93562fd8faa2b869313fc83fd71b202e61 Mon Sep 17 00:00:00 2001 From: Louis Grx Date: Tue, 28 May 2019 18:48:36 +0200 Subject: [PATCH 04/20] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d1a0903..39d2b16 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ The application process is open and public and it will take place in this dedica **How to submit your proposal** - Fork the Aragon Flock GitHub repository - Create a new directory with the team’s name inside the *teams/* folder -- Inside the directory, create one file: *proposal.md* ([see proposal guide](https://github.com/LouisGrx/flock/blob/master/docs/Proposal%20guid.md)), where you present the overall application and team +- Inside the directory, create one file: *proposal.md* ([see proposal guide](https://github.com/LouisGrx/flock/blob/master/docs/Proposal%20guide.md)), where you present the overall application and team - Create a pull request to merge your submission into the Flock repository. In that pull request fill in all the relevant info described in the template - Amendments to the initial proposal can be made by creating a pull request over the existent pull request for the relevant review. From 624d8cdff6f223f560c2d4184e55a241bd7576dc Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Fri, 31 May 2019 17:23:05 +0200 Subject: [PATCH 05/20] proposal guide update --- docs/.DS_Store | Bin 6148 -> 6148 bytes docs/Proposal guide.md | 33 ++++++++++++++++++--------------- 2 files changed, 18 insertions(+), 15 deletions(-) diff --git a/docs/.DS_Store b/docs/.DS_Store index 2a139b2f3ba018550e0f159ba9a145edeb13d158..af9e5d8526999cac4abf001dcc352b467857aabb 100644 GIT binary patch delta 126 zcmZoMXfc=|#>B`mu~2NHo+2aD!~pAw4;m&Lh_FoTcd->@2w*5;$Y&@3;$ntGh8zY3 zhIEEfhD?SOhExVUhFpde&z$_^q@4UD1_lNJAYKW?8vnsy$^ZZW delta 63 zcmZoMXfc=|#>CJ*u~2NHo+2aT!~knX#>qU4?whAE7P3uVz<78wI|n}pP{rnnjNh3j T^NScVGEBDNk=`65vVs`^I-(Jr diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index c104a22..cc0f84b 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -2,15 +2,15 @@ ## 1. Summary -This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements. +*This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements. -In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports. +In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* ## 2. Deliverables ### Deliverables summary table -*This table aims at giving a visual summary of the focus of the team and the allocation of team effort to each category of deliverables. Evaluating such future data is difficult, but the thought exercise provides a good idea of the mindset of the team and its general focus.* +*This table aims at giving a visual summary of the applicant team's effort allocation over the different categories of deliverables.* #### Example > | Category | Dev tools | Aragon apps | User experience | XYZ | @@ -22,17 +22,17 @@ Note: categories can be invented as needed by the applicant team. ### Initiatives -*In this section are provided all the concrete elements the applicant team is planning to work on. These should be listed as initiatives by order of priority.* +*In this section, the applicant team should detail in concrete terms the different initiatives it is planning to work on. They should be listed by order of priority.* -For each initiative, in order to justify it is relevant please detail shortly: -- **Value proposition** - *How it will provide value to the end user (i.e. developer or end user)* -- **Deliverables** - *What precisely will be implemented in regard of this initiative* -- **Background** - *A link to a Github issue, a Flock roadmap item, a Nest proposal, user feedback, or any material backing its relevancy* -- **Long-term vision for initiative** - *This last item is optional* +For each initiative, the applicant team should cover the following items: +- **Value proposition** - *How it will provide value to the end user (i.e. developer or Aragon DAO user)* +- **Deliverables** - *What precisely will be implemented in to fulfill this initiative* +- **Background** - *A link to a Github issue, Flock roadmap item, Nest proposal, user feedback, or any other material backing the initiative's relevancy* +- **Long-term vision for initiative** - *This last item is optional and can provide more insights on future developments built on top of the initiative* #### Example -*Here is an example of initiative inspired from a past Flock proposal* +*Here is an example of initiative inspired from a past Flock application* > ### I01 - Fundraising > #### Value proposition @@ -51,12 +51,15 @@ For each initiative, in order to justify it is relevant please detail shortly: ## 3. Grant Size -*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would need to incentivize the team long term commitment* +*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would be needed to incentivize the team's long term commitment* -*Regarding the ANT package please be sure to provide the number of ANT per team member per year.* +*Regarding the ANT package please be sure to provide an amount per team member per year.* #### Example +*Here is an example of initiative inspired from a past Flock application* + + > ### Estimated operating costs for Q2 and Q3 2019 > > | Type | Description | Amount | @@ -77,7 +80,7 @@ For each initiative, in order to justify it is relevant please detail shortly: ## 4. Team -*This is the basic structure you should follow when creating your proposal where you briefly describe of the current team members and their relevancy for the role with links to their relevant social media channels (github, twitter, etc) and provide info of future openings if you plan to hire more people during the year.* +*Below is the basic structure the applicant team should follow when creating a Flock proposal. It includes a brief description the current team members and their relevancy for the role, with links to relevant materials (github, twitter, projects, etc) and provides info on future openings if the applicant team plans to hire more people during their Flock mandate.* #### AraEagles Example Team @@ -103,7 +106,7 @@ For each initiative, in order to justify it is relevant please detail shortly: *List of aragon accounts, channels, tools, assets, domains and infrastructure that you need in order to operate* -| Access to | Yes/No | If Yes, precise requirement | +| Access to | Yes/No | If Yes, precise why | |----------------------------------------------------------------------------------|--------|------------------------------| | Blog access on blog.aragon.org | | | | Social media access | | | @@ -117,4 +120,4 @@ For each initiative, in order to justify it is relevant please detail shortly: ## 6. Organization structure -*Under What type of organization, if any, is the team organized* +*Under what type of organization, if any, is the team organized* From 8b71ae19bc0c0f9af0d35f6311556b5030371f76 Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Fri, 31 May 2019 18:39:46 +0200 Subject: [PATCH 06/20] Update Proposal guide.md --- docs/Proposal guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index cc0f84b..de7eb2c 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -2,9 +2,9 @@ ## 1. Summary -*This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements. +*This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements.* -In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* +*In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* ## 2. Deliverables From d1bf1737f7e03440d57b70ba6e08105c6b9d1966 Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Fri, 31 May 2019 18:40:35 +0200 Subject: [PATCH 07/20] Update Proposal guide.md --- docs/Proposal guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index de7eb2c..ba5e8b7 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -2,7 +2,7 @@ ## 1. Summary -*This section should include the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements.* +*This section should detail the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements.* *In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* From 56fecb0fcc152a45bf58408404cc5bca8497164b Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Fri, 31 May 2019 18:45:48 +0200 Subject: [PATCH 08/20] Update Proposal guide.md --- docs/Proposal guide.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index ba5e8b7..2fdea8c 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -106,12 +106,12 @@ For each initiative, the applicant team should cover the following items: *List of aragon accounts, channels, tools, assets, domains and infrastructure that you need in order to operate* -| Access to | Yes/No | If Yes, precise why | +| Access to | Yes/No | If Yes, precise what and why | |----------------------------------------------------------------------------------|--------|------------------------------| -| Blog access on blog.aragon.org | | | -| Social media access | | | -| Website access on all Aragon domains | | | -| Repo access on the entire @aragon organization | | | +| Blog accesses: | | | +| Social media accesses: | | | +| Website accesses: | | | +| Repo accesses: | | | | Unrestricted use of the Aragon trademark | | | | Publish access to aragonpm.eth | | | | Access to Aragon servers and cloud infrastructure | | | From 8d74f0ba33a1b8f4cb08faf77173b9a61d2ad99c Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Wed, 5 Jun 2019 16:58:17 +0200 Subject: [PATCH 09/20] Proposal guide.md --- .DS_Store | Bin 6148 -> 6148 bytes docs/Proposal guide.md | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/.DS_Store b/.DS_Store index eeb9ef37e229b333181b5c1fa9bf0743e682018e..79c8897c668bfbe93ba4cfa9c3580ee1e13c32e7 100644 GIT binary patch delta 45 zcmZoMXffE}&BS${>`~Xdp B4zU0L delta 97 zcmZoMXffE}&BS(r$lwNv6-=sf}yEpt&T#qxw(Okf{C$NZ7nBM8XF_ge hRdr2m-Ao2BU}S{Q4E#_UM$OtR%>0REGdss$egKtC6uSTb diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 2fdea8c..cf8bd76 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -51,7 +51,7 @@ For each initiative, the applicant team should cover the following items: ## 3. Grant Size -*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that you would be needed to incentivize the team's long term commitment* +*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that would be needed to incentivize the team's long term commitment* *Regarding the ANT package please be sure to provide an amount per team member per year.* From 7de9bf1b07d51f3cd56f3272ca77e7d3b272aa46 Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Wed, 5 Jun 2019 18:21:33 +0200 Subject: [PATCH 10/20] proposal guide update --- .DS_Store | Bin 6148 -> 6148 bytes docs/Proposal guide.md | 31 +++++++++++++++++++++---------- 2 files changed, 21 insertions(+), 10 deletions(-) diff --git a/.DS_Store b/.DS_Store index 79c8897c668bfbe93ba4cfa9c3580ee1e13c32e7..f67f466f614798fbda5a6fd2931e31617467d39e 100644 GIT binary patch delta 97 zcmZoMXffE}&BS(r$lwNsfDSIf}yEpt&T#qxw(Okf{C$NZ7nBM8XF_ge hRdr2m-Ao2BU}S{Q4E#_UM$OtR%>0REGdss$egKyz6u|%h delta 45 zcmZoMXffE}&BS${>`~Xdp B4zU0L diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index cf8bd76..92d65b3 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -2,10 +2,15 @@ ## 1. Summary -*This section should detail the high level strategy of the proposal in simple terms. It can be accompanied by a few references from past team achievements.* +### Strategy +*This section should detail the high level strategy and rational behind the proposal in simple terms. It can be accompanied by a few short references to past team achievements.* *In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* +### Working in the Aragon Community +*In this part the applicant team should qualitatively explain why it is qualified to deliver the strategy outlined in the previous section.* + +*Members of the Aragon community are united through their alignment with the [Aragon Manifesto](https://blog.aragon.org/the-aragon-manifesto-4a21212eac03/) and the values of openness, freedom and goodwill. While there are no requirements to refer to the above explicitly, teams are encourage to speak from their heart, technicals are not the only thing!* ## 2. Deliverables @@ -32,7 +37,7 @@ For each initiative, the applicant team should cover the following items: #### Example -*Here is an example of initiative inspired from a past Flock application* +*Here is an example of initiative inspired from a past Flock application.* > ### I01 - Fundraising > #### Value proposition @@ -51,13 +56,13 @@ For each initiative, the applicant team should cover the following items: ## 3. Grant Size -*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that would be needed to incentivize the team's long term commitment* +*Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that would be needed to incentivize the team's long term commitment.* *Regarding the ANT package please be sure to provide an amount per team member per year.* #### Example -*Here is an example of initiative inspired from a past Flock application* +*Here is an example of initiative inspired from a past Flock application.* > ### Estimated operating costs for Q2 and Q3 2019 @@ -80,7 +85,7 @@ For each initiative, the applicant team should cover the following items: ## 4. Team -*Below is the basic structure the applicant team should follow when creating a Flock proposal. It includes a brief description the current team members and their relevancy for the role, with links to relevant materials (github, twitter, projects, etc) and provides info on future openings if the applicant team plans to hire more people during their Flock mandate.* +*Below is the basic structure the applicant team should follow when creating a Flock proposal. It includes a brief description the current team members and their relevancy for the role, with links to relevant materials (github, twitter, projects, etc.) and provides info on future openings if the applicant team plans to hire more people during their Flock mandate.* #### AraEagles Example Team @@ -108,10 +113,10 @@ For each initiative, the applicant team should cover the following items: | Access to | Yes/No | If Yes, precise what and why | |----------------------------------------------------------------------------------|--------|------------------------------| -| Blog accesses: | | | -| Social media accesses: | | | -| Website accesses: | | | -| Repo accesses: | | | +| Blog accesses | | | +| Social media accesses | | | +| Website accesses | | | +| Repo accesses | | | | Unrestricted use of the Aragon trademark | | | | Publish access to aragonpm.eth | | | | Access to Aragon servers and cloud infrastructure | | | @@ -120,4 +125,10 @@ For each initiative, the applicant team should cover the following items: ## 6. Organization structure -*Under what type of organization, if any, is the team organized* +*Under what type of organization, if any, is the team organized.* + +## 7. Due diligence materials + +*In an organized fashion, the applicant team is invited to provide links to materials that can support its Flock application.* + +*These can be links to projects, references, or any material judged relevant.* From 6b6b56f935c852f30a69742f0f962adffb7d960e Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Wed, 5 Jun 2019 18:27:19 +0200 Subject: [PATCH 11/20] Update Proposal guide.md --- docs/Proposal guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 92d65b3..88fd56c 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -10,7 +10,7 @@ ### Working in the Aragon Community *In this part the applicant team should qualitatively explain why it is qualified to deliver the strategy outlined in the previous section.* -*Members of the Aragon community are united through their alignment with the [Aragon Manifesto](https://blog.aragon.org/the-aragon-manifesto-4a21212eac03/) and the values of openness, freedom and goodwill. While there are no requirements to refer to the above explicitly, teams are encourage to speak from their heart, technicals are not the only thing!* +*Members of the Aragon community are united around the [Aragon Manifesto](https://blog.aragon.org/the-aragon-manifesto-4a21212eac03/) and values of openness, freedom and goodwill. While there are no requirements to refer to the above explicitly, teams are encourage to speak from their heart, technicals are not the only thing!* ## 2. Deliverables From 3953edd50ffcc9514f185a0376bc556b505a2d5b Mon Sep 17 00:00:00 2001 From: Louisgrx Date: Wed, 5 Jun 2019 18:29:11 +0200 Subject: [PATCH 12/20] Update Proposal guide.md --- docs/Proposal guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 88fd56c..2fc4d2a 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -129,6 +129,6 @@ For each initiative, the applicant team should cover the following items: ## 7. Due diligence materials -*In an organized fashion, the applicant team is invited to provide links to materials that can support its Flock application.* +*In a structured way, the applicant team is invited to provide links to materials that can support its Flock application.* *These can be links to projects, references, or any material judged relevant.* From b5674c00741af9eef456bd06834d59d82ae0ce08 Mon Sep 17 00:00:00 2001 From: louis giraux Date: Wed, 26 Jun 2019 10:55:22 +0200 Subject: [PATCH 13/20] proposal guide update --- .DS_Store | Bin 6148 -> 6148 bytes docs/Proposal guide.md | 52 +++++++++++++++++++++++++++-------------- 2 files changed, 35 insertions(+), 17 deletions(-) diff --git a/.DS_Store b/.DS_Store index f67f466f614798fbda5a6fd2931e31617467d39e..2bca7f2ece8f45c356cdc653261376c9ea8b1b04 100644 GIT binary patch delta 21 ccmZoMXffDuo{7WQ*i=Ws*wkS2btYX=07{q!KL7v# delta 21 ccmZoMXffDuo{7WM!c<4W(A0ACbtYX=0811GO#lD@ diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 2fc4d2a..effa075 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -1,3 +1,7 @@ +**Introductory note**: This guide can be used by Flock program applicants to draft their ideal application. However, the structure and content of the proposal can be adapted as much as necessary by the applicant team. Above all, applications should be **clear and concise**. + +Don't forget to share the proposal as early as possible with the [community](https://forum.aragon.org/). + # Aragon Flock proposal: Team name ## 1. Summary @@ -5,25 +9,39 @@ ### Strategy *This section should detail the high level strategy and rational behind the proposal in simple terms. It can be accompanied by a few short references to past team achievements.* -*In case the applicant team is an ongoing Flock team it can join the previously achieved roadmap and its most recent community reports.* +*In case the applicant team is an ongoing Flock team it can add the previously achieved roadmap and its most recent community reports.* -### Working in the Aragon Community +### Why us? *In this part the applicant team should qualitatively explain why it is qualified to deliver the strategy outlined in the previous section.* -*Members of the Aragon community are united around the [Aragon Manifesto](https://blog.aragon.org/the-aragon-manifesto-4a21212eac03/) and values of openness, freedom and goodwill. While there are no requirements to refer to the above explicitly, teams are encourage to speak from their heart, technicals are not the only thing!* +### Working in the Aragon Community + +*In this section, teams should succintly explain why their time is better spent contributing to Aragon.* + +*Members of the Aragon community are united around the [Aragon Manifesto](https://blog.aragon.org/the-aragon-manifesto-4a21212eac03/) and values of openness, freedom and goodwill. While there are no requirements to refer to the above explicitly, teams are encouraged to speak from their heart. Technicals are not the only thing!* ## 2. Deliverables -### Deliverables summary table +### Projected capacity table *This table aims at giving a visual summary of the applicant team's effort allocation over the different categories of deliverables.* -#### Example +#### Example 1 > | Category | Dev tools | Aragon apps | User experience | XYZ | > |------------------------|-----------|-------------|------------------|-----| > | Nb of deliverables | 2 | 1 | 3 | 1 | > | Team effort allocated | 30% | 20% | 40% | 10% | -Note: categories can be invented as needed by the applicant team. +#### Example 2 +| Initiative | Projected Capacity (%) | +| ---------------------------- | ----: | +| 01 - Working on initiative 01 | 34 | +| 02 - Working on initiative 02 | 28 | +| 03 - Working on initiative 03 | 16 | +| 04 - Working on initiative 04 | 14 | +| 05 - Working on initiative 05 | 8 | + + +Note: there is no strict format required for the table. ### Initiatives @@ -58,7 +76,7 @@ For each initiative, the applicant team should cover the following items: *Your estimated operating cost for successfully building the Aragon Project and the estimated ANT package that would be needed to incentivize the team's long term commitment.* -*Regarding the ANT package please be sure to provide an amount per team member per year.* +*Please also provide the payment schedule that would be requested.* #### Example @@ -69,20 +87,20 @@ For each initiative, the applicant team should cover the following items: > > | Type | Description | Amount | > | ----------- | :------------------------------------: | -----: | -> | Payroll | | \$410k | -> | Contractors | DevOps \| Design \| Legal \| etc. | \$10k | -> | Services | GitHub \| Google Suite \| Chat \| etc. | \$5k | -> | Travel | Offsites \| Conferences \| etc. | \$10k | -> | Equipment | Laptop \| etc. | \$15k | -> | **Total** | | \$450k | - - +> | Payroll | | \$Xk | +> | Contractors | DevOps \| Design \| Legal \| etc. | \$Xk | +> | Services | GitHub \| Google Suite \| Chat \| etc. | \$Xk | +> | Travel | Offsites \| Conferences \| etc. | \$Xk | +> | Equipment | Laptop \| etc. | \$Xk | +> | **Total** | | \$Xk | > ### ANT package > > We would like to request **25k ANT per team member per year** for incentivization purpose, i.e. **125k ANT** for this six months long proposal. We are committed to the Aragon Network in the long-term and therefore accept a 4-years vesting schedule. +Note: Flock team ANT package policy is subject to change over time. Please ask the Aragon Association for more information. + ## 4. Team *Below is the basic structure the applicant team should follow when creating a Flock proposal. It includes a brief description the current team members and their relevancy for the role, with links to relevant materials (github, twitter, projects, etc.) and provides info on future openings if the applicant team plans to hire more people during their Flock mandate.* @@ -129,6 +147,6 @@ For each initiative, the applicant team should cover the following items: ## 7. Due diligence materials -*In a structured way, the applicant team is invited to provide links to materials that can support its Flock application.* +*In a structured way, the applicant team is invited to provide links to materials that can support its Flock application. **This should include a risk assessment document**, where the Flock team details the main challenges and risks tied to its proposal.* -*These can be links to projects, references, or any material judged relevant.* +*These can also be links to projects, references, or any material judged relevant.* From d3b1a31c2b87863d2050ccbbb4f02cc77b78c577 Mon Sep 17 00:00:00 2001 From: louis giraux Date: Wed, 26 Jun 2019 11:11:44 +0200 Subject: [PATCH 14/20] Update Proposal guide.md --- docs/Proposal guide.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index effa075..6d7ccb6 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -1,4 +1,5 @@ -**Introductory note**: This guide can be used by Flock program applicants to draft their ideal application. However, the structure and content of the proposal can be adapted as much as necessary by the applicant team. Above all, applications should be **clear and concise**. +#### Introductory note +This guide can be used by Flock program applicants in order to draft their ideal proposal. However, the structure and content of the proposal can be adapted as much as necessary by the applicant team. Above all, applications should be **clear and concise**. Don't forget to share the proposal as early as possible with the [community](https://forum.aragon.org/). From 9c9ade0a6bba20b12b465c36e3ea305ca832c4fc Mon Sep 17 00:00:00 2001 From: louis giraux Date: Wed, 26 Jun 2019 11:14:23 +0200 Subject: [PATCH 15/20] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 39d2b16..fd305ce 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ The focus of the program is the selection of independent teams that will work on - An incentivization package in ANT ## Application process -The application process is open and public and it will take place in this dedicated GitHub repository. If you expect your proposal to be approved in the next Aragon Network Vote you should submit your proposal to the Flock program at least one month before Aragon Governance Proposals are due, to give reviewers enough time to properly consider your proposal. You can find information about dates for the next Aragon Network Vote on the [Governance page](https://wiki.aragon.org/documentation/governance/) in the Aragon Wiki. +The application process is open and public and it will take place in this dedicated GitHub repository. **If you expect your proposal to be approved in the next Aragon Network Vote you should submit your proposal to the Flock program at least one month before Aragon Governance Proposals are due**, to give reviewers enough time to properly consider your proposal. You can find information about dates for the next Aragon Network Vote on the [Governance page](https://wiki.aragon.org/documentation/governance/) in the Aragon Wiki. **How to submit your proposal** - Fork the Aragon Flock GitHub repository From e7bf23154d2b9d79c33cc4a9171b41db0924b8c6 Mon Sep 17 00:00:00 2001 From: Louis Grx Date: Wed, 10 Jul 2019 12:28:53 +0200 Subject: [PATCH 16/20] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fd305ce..364b8dd 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ Part of the funding is intended to cover the annual operating cost of each team. To align the interests of the teams with the creation of value of the Aragon Network, increase the team motivation and incentivize long term commitment, every team will be given an incentivization package in ANT. This incentivization package gives the team governance power over the project and the potential for greater financial upside. This incentive will be subject to vesting. -After the definitive approval of funding as per the AGP-1 process, funds for operating costs will be disbursed to the approved teams in a lump sum. +After the definitive approval of funding as per the AGP-1 process, funds for operating costs will be disbursed to the approved teams in a lump sum or in tranches. ## Decision rationale From 33c286ca9c7d6e8f4eea498a3985bce6ca4cebb9 Mon Sep 17 00:00:00 2001 From: louis giraux Date: Mon, 9 Sep 2019 13:07:16 +0200 Subject: [PATCH 17/20] Proposal guide - AA signature add --- .DS_Store | Bin 6148 -> 6148 bytes docs/Proposal guide.md | 8 ++++++++ 2 files changed, 8 insertions(+) diff --git a/.DS_Store b/.DS_Store index 2bca7f2ece8f45c356cdc653261376c9ea8b1b04..ce56ff1fc4e74a7fd151e7d54519f3291a0812b8 100644 GIT binary patch delta 39 vcmZoMXfc@J&&akhU^gQp+h!gnQAW;`;^ds9{QMlo&7#bASvIqC{N)D#<%|o! delta 32 ocmZoMXfc@J&&awlU^gQp>t-G%QO3 Date: Mon, 9 Sep 2019 13:08:21 +0200 Subject: [PATCH 18/20] Update Proposal guide.md --- docs/Proposal guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 995ed7d..65d4b6e 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -152,10 +152,10 @@ Note: Flock team ANT package policy is subject to change over time. Please ask t *These can also be links to projects, references, or any material judged relevant.* -### Aragon Association signature +### [Aragon Association signature field] *In order to be submitted to the Community Review stage of the AGP process, the above application must satisfy the Flock track AGP timeline. Its scope and structure must also match the way the Flock program operates.* -*If so, the Aragon Association will create a pull request containing PGP signature signing: -- a GitHub link to the specific commit height of the application -- a SHA-256 hash of the raw application text at the time of approval* +*If so, the Aragon Association will create a pull request containing PGP signature signing:* +- *a GitHub link to the specific commit height of the application* +- *a SHA-256 hash of the raw application text at the time of approval* From 26c91267247f4154460b6f9712754f8f702caf8f Mon Sep 17 00:00:00 2001 From: louis giraux Date: Mon, 9 Sep 2019 13:13:06 +0200 Subject: [PATCH 19/20] Update Proposal guide.md --- docs/Proposal guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 65d4b6e..471d9da 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -1,5 +1,5 @@ #### Introductory note -This guide can be used by Flock program applicants in order to draft their ideal proposal. However, the structure and content of the proposal can be adapted as much as necessary by the applicant team. Above all, applications should be **clear and concise**. +This guide can be used by Flock program applicants in order to draft their ideal **Flock Tragck AGP**. The structure and content of the proposal can be adapted as much as necessary by the applicant team. Above all, applications should be **clear and concise**. Don't forget to share the proposal as early as possible with the [community](https://forum.aragon.org/). From 4b82493ded14b69a069552165001663e635106eb Mon Sep 17 00:00:00 2001 From: louis giraux Date: Tue, 10 Sep 2019 16:19:22 +0200 Subject: [PATCH 20/20] Update Proposal guide.md --- docs/Proposal guide.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md index 471d9da..7f276a9 100644 --- a/docs/Proposal guide.md +++ b/docs/Proposal guide.md @@ -151,11 +151,3 @@ Note: Flock team ANT package policy is subject to change over time. Please ask t *In a structured way, the applicant team is invited to provide links to materials that can support its Flock application. **This should include a risk assessment document**, where the Flock team details the main challenges and risks tied to its proposal.* *These can also be links to projects, references, or any material judged relevant.* - -### [Aragon Association signature field] - -*In order to be submitted to the Community Review stage of the AGP process, the above application must satisfy the Flock track AGP timeline. Its scope and structure must also match the way the Flock program operates.* - -*If so, the Aragon Association will create a pull request containing PGP signature signing:* -- *a GitHub link to the specific commit height of the application* -- *a SHA-256 hash of the raw application text at the time of approval*