diff --git a/.DS_Store b/.DS_Store new file mode 100644 index 0000000..ce56ff1 Binary files /dev/null and b/.DS_Store differ diff --git a/README.md b/README.md index 25b30bb..364b8dd 100644 --- a/README.md +++ b/README.md @@ -14,12 +14,12 @@ 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 - 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%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. @@ -29,17 +29,17 @@ 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** 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 -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** diff --git a/docs/.DS_Store b/docs/.DS_Store new file mode 100644 index 0000000..af9e5d8 Binary files /dev/null and b/docs/.DS_Store differ diff --git a/docs/Proposal guide.md b/docs/Proposal guide.md new file mode 100644 index 0000000..7f276a9 --- /dev/null +++ b/docs/Proposal guide.md @@ -0,0 +1,153 @@ +#### Introductory note +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/). + +# Aragon Flock proposal: Team name + +## 1. Summary + +### 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 add the previously achieved roadmap and its most recent community reports.* + +### Why us? +*In this part the applicant team should qualitatively explain why it is qualified to deliver the strategy outlined in the previous section.* + +### 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 + +### 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 1 +> | Category | Dev tools | Aragon apps | User experience | XYZ | +> |------------------------|-----------|-------------|------------------|-----| +> | Nb of deliverables | 2 | 1 | 3 | 1 | +> | Team effort allocated | 30% | 20% | 40% | 10% | + +#### 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 + +*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, 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 application.* + +> ### 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]. + + +## 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.* + +*Please also provide the payment schedule that would be requested.* + +#### Example + +*Here is an example of initiative inspired from a past Flock application.* + + +> ### Estimated operating costs for Q2 and Q3 2019 +> +> | Type | Description | Amount | +> | ----------- | :------------------------------------: | -----: | +> | 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.* + +#### 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 what and why | +|----------------------------------------------------------------------------------|--------|------------------------------| +| 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 | | | +| 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.* + +## 7. Due diligence materials + +*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.* 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](#)