Closed parkwil89 closed 6 years ago
Hi @mariapao thank you for taking the time to review and consider the request. Please find some responses to your questions below.
Understood, please note that portion of the request has been removed.
Please see some updates to the request above to include a more detailed roadmap and payments based on milestones. Let me know if just updating it above was okay or if you would like the information presented in another way.
Yes we will continue applying to other grants but only to expand development further. At the moment this is the only request submitted and future requests will not duplicate the deliverables or funding needs included here.
Hi @parkwil89 thank you for replying to all my questions and comments. After reviewing the application and the new information added I'm pleased to let you know that we have decided to approve your request for funding. This for sure will speed up the path to the decentralization of the development of the Aragon project.
Next steps: I'll send you an email to schedule a call this week to go over some minor details to close this process and discuss the payouts/disbursements of the grant.
Welcome to nest! :)
Hi @mariapao we were wondering if you would be agreeable to adjusting the CLA to reflect the GNU General Public License v3.0 : All work, contributions and any background technology developed with this grant will be licensed under GPL v3.0. We feel that clause # 7 does not exactly align with our idea of how the Giveth DApp software will be used.
Hi @YalorMewn you are talking about the nest agreement, right? Just for me to confirm
Yes, @mariapao the agreement that you sent over for us to sign Titled:
Aragon Nest Grant Program Agreement Terms & Conditions
@YalorMewn sure we can modify it to expressly mention the specific license but that clause # 7 allows for you to go GPL ;)
@mariapao @YalorMewn these two links are not reachable/available -
Yes, I have the same problem with those links. For the first one, I'm seeing this error in the console, in case it helps:
Loading failed for the <script> with source “https://alpha.giveth.io/static/js/main.ae24dd4c.js”
About the second one, although that branch doesn't seem to exist, I see a lot of Aragon stuff in master
branch, at least since last February (commit 369e6ae6). Can we assume then than the branch to check is master
?
Thanks.
I think I can answer myself:
master
branch
Team Name: Giveth
Wiki: DApp product definition
Video explanation
Proof of Concept
https://alpha.giveth.io (our current DApp) https://alpha.giveth.io/campaigns/fzOahNwFVyY7qLTI (The DApp Campaign, with links to everything you could want to know about the DApp) https://github.com/Giveth/giveth-dapp (our DApp’s Repo) https://github.com/Giveth/liquidpledging/tree/aragon (The Aragon Specific Fork for LP) https://github.com/Giveth/liquidpledging (The current DApp’s LP codebase)
Grant Size
Request for Funds $154,500
Create an AragonAPP version of LiquidPledging and begin testing the UI
Integrate the AragonAPP version of LiquidPledging into current Live Giveth DApp to do more internal testing with a focus on building documentation but with real funds at risk
Create the Aragon DAC to fund the decentralized development of the Aragon Platform
Research and select 5 external organizations for onboarding to the DApp. Begin training and communicating the onboarding process with each organization to prepare them to join the platform
Establish detailed testing protocols for the DApp, add features such as ANT token support, full scale documentation of our process and on board 10 more external organizations to the DApp
Legal Structure: non-legal entity, Governance structure
DApp Development Team
Roadmap: Introduced in video explanation, details in payment request above
Proposal
Giveth is re-engineering the non-profit funding system, by creating an entirely free, open-source DApp on the Ethereum and Rinkeby Blockchains. Our DApp utilizes LiquidPledging and a series of DACs, campaigns and milestones (described in product definition) to automate away bureaucracy and enable Change Makers (nonprofits, community based organizations, faith-based organizations, social services agencies, etc.) to operate with a high level of transparency and accountability. The DApp’s LiquidPledging smart contract system provides Givers the power to veto fund allocations and even withdraw funds at any point until the moment they are locked in and dedicated to a specific cause. This functionality forms the foundation of the DApp and creates a better world for parties on both sides of a transaction, the Change Makers and those that give to them.
Giveth has been developing our DApp since October 2016 and in May of 2017 the LiquidPledging design was created to better fulfill the systems needs. In late January this year we decided to restructure it as an AragonApp to provide added desired functionality (specifically, convenient access control schemes and upgradability). The goal moving forward is to finish building the DApp, creating an open source environment that will add additional levels of accountability, transparency, decentralized governance and community for users without requiring traditional legal structures.
In recent conversations with the Aragon team we’ve discussed using the DApp to grow the Aragon ecosystem by developing an Aragon DAC. The goal of this DAC would be to decentralize Aragon Development and build the Aragon Community.
The DApp is nearly usable by non-Giveth groups, we are testing the bridge on Ropsten and Rinkeby right now. The Aragon DAC would be one of the first DACs on the platform. The Aragon DAC would utilize LiquidPledging to fund and govern the decentralized development of the Aragon platform. As the DApp evolves and adds greater functionality the Aragon DAC will be able to have its issues addressed and continue to evolve itself.
To finish the DApp and make the Aragon DAC a reality we are requesting funds to cover the development time spent on turning LiquidPledging into an AragonApp, as well as additional funding to cover DApp development for the next 6 months. We have to finish fully integrating LiquidPledging into an AragonApp, migrate the DApp’s user interface and making necessary upgrades to finalize the the DApp.
A full description of our proposal, the work that has taken place and the work that is yet to come is included in our video submission linked above.