Grants

[yeqbfgxjiq]

We should definitely pursue general grants, Gitcoin grants, and/or a CFDAO proposal based on the core of the 1hive project which includes documentation/onboarding resources, and a portal which allows someone to deploy a "1hive" dao as a template, similar to the existing token democracy/autark templates.

We could pose this as a general "sponsorship" of the 1hive project and community, with a recurring vested ANT distribution. I think we should try and avoid specific milestones and deliverables associated and instead leave it open ended. We are value aligned already, and with the grant being vested ANT there is further value alignment. This gives us the flexibility to work on whatever we think is most valuable to us and to the wider Aragon ecosystem.

This doesn't/shouldn't prevent us from also pursuing additional milestone/deliverable specific grants like what is being proposed in the MolochDAO Apps Suite.

Note: there is also a discussion around grants for the 1Hive DAO Kit in the grants repo

• 1Hive DAO Kit grants#8

My thinking is to start brainstorming/drafting ideas here, then go back to the grants repo to share once there's a rough draft.

[yeqbfgxjiq]

A 1Hive DAO Template we can ship to the world:

• rewrite the model described in the handbook (roles, responsibilities, etc...) to something generic that can be applied to any community/organization
• create a DAO Template for that generalized organization
• create a Docusaurus around it explaining what it does, why, and how to customize and extend it

This will allow Aragon DAO developers to:

• read the guides on the 1Hive Template website (note: this is not 1Hive.org, but a different Docusaurus website for the 1Hive Template)
• fork the repo
• deploy and configure their DAO
• update and publish the Docusaurus website in the repo, but then update it information on their DAO vs the information describing the template (kind of like how currently docusaurus-init launches a template that you customize)

All in one sentence:

• A 1Hive DAO Template that allows Aragon DAO developers to deploy a 1Hive style DAO for their organization along with a Doucsaurus that provides user guides/onboarding, application docs, and a community hub for all your social channels including a built in blog.

This would accomplish a few things:

• it would make the 1Hive model accessible to the world
• it would create a standard docs template for all 1Hive apps
• it would be provide a foundation to do the same thing when anyone wants to ship a DAO template to the world, which will benefit us directly when we ship the MolochDAO Suite

[yeqbfgxjiq]

1Hive Kit Grants Proposal

Abstract 🎨

• Who? What? When? Where? Why?

At 1Hive we have been researching and building DAO models for sustainable community driven development of the open source commons. This is no easy task, but we feel like the time has come to make it happen. Our first project is the 1Hive model itself: an Aragon DAO that uses homemade and TPS apps. We use this model every day to govern our own organization (1Hive).

While this is very exciting, it's only the tip of the iceberg. Most open source software projects want to innovate at the bleeding edge of whatever cool project they're building. They don't, however, want to reinvent the wheel on governance and community building. With this in mind, we are creating the 1Hive DAO Kit: a 1 stop shop to deploy a DAO, documentation, and website for your open source project.

This will allow open source developers to easily make governance decisions, engage and reward contributors, and provide easy to read up to date documentation for users; everything an open source project needs that isn't directly related to the building project itself. This means more time building and less time spent doing everything else. It also means less drama, more engaged users, and sustainable token models to maintain and grow the project.

Deliverables

• What does this look like concretely? 🤔

We are creating this for the 1Hive community, the Aragon community, and the open source community as a whole. Concretely this looks like:

• A DAO template that makes it easy for anyone to recreate a generic version of the DAO that 1Hive uses.
• A documentation standard/guide that Aragon app developers can follow to create easy to ready easy to use documentation for their new Aragon apps.
• A Docusaurus website template that will explain how the generic 1Hive DAO template works, how the documentation standard works, and how the Docusaurus website itself works. The idea is that you fork the Kit, then immediately have guides on how to use it. Then you can use those guides to customize the website's content to use it for your own project/community.

Creating these will not only allow open source projects to empower their communities with Aragon DAOs, but will also serve as a model that other Aragon projects can use to share their work in a cohesive and accessible manner. Imagine if every Aragon project could have a developer hub as good as hack.aragon. We're building a template to make that possible.

1Hive DAO Template 🖧

An easy to deploy DAO template that ships with the current 1Hive model.

• Should be as easy to deploy as npx create-hive-org or going to https://rinkeby.1hive.bzz/#/

1Hive Documentation Standard 📜

Part of the mission of 1Hive is to create tools that make it easier for people to learn about, use, and build DAOs to empower their communities. As such, it makes sense that the 1Hive DAO Kit ships with basic docs, user onboarding guides, and templates for both. This standard documentation framework will be used to document all the apps used in the 1Hive DAO model. This will also include a doc creation guide that will help communities create new docs that are organized and informative as they extend and modify the DAO.

• A docs template that will ship with the 1Hive DAO Kit that will allow people to easily create documentation for their own apps/projects.
• This docs template will be used to document new 1Hive apps.
• If successful, this docs template could be expanded to improve documentation for apps across the Aragon ecosystem.

To explain what I mean when I say "expanded to improve documentation for apps across the Aragon ecosystem", hack.aragon syncs docs from various Aragon repos into hack.aragon and then displays it using that websites custom CSS. I've recreated that for 1Hive, and am thinking that it would be easy for other projects to do so as well. This would create a framework for every Aragon project to have their own hack.aragon style developer hub that syncs in documentation from the apps that their DAO uses.

• The source of truth for documentation would live in the repo for each Aragon app.
• When people create DAOs they could then easily syncs the docs for the apps in that DAO. These docs would be displayed within the context of the project's website using their custom themes/css. This keeps users engaged with the main project they're focused on.
• Essentially this would mean that projects could install apps to their DAO, and then "install" the documentation for that app into their website. Hack.aragon style dev hubs for all Aragon projects 🚀

This model would work a lot better if all the docs for Aragon apps are more or less in a standard format, so starting to reach out to people to see if there's interest in exploring/creating this. This requires understanding the interests of a diverse group of stake holders and then building a framework that works for everyone. We would like some support to make that happen :)

1Hive Docusaurus Template 🦕

A Docusaurus that can be easily be forked and filled with the content of any organization. It will ship with docs/guides for the 1Hive DAO Kit itself, which users can keep or overwrite.

• This will include a guide on how to use the sync script that hack.aragon uses to pull in docs from various Aragon repos into the website. This means that each app/project/thing can maintain their own documentation, and then any projects that use the app can easily pull the documentation for it into their website/docusaurus and display it with the theme/styling and context of their project/experience (like hack.aragon does currently).
• Recommended resources to help projects optimize/customize their Docusaurus website (potentially even shipping pre-built "themes" that work out of the box). This will also include resources for community development and outreach (best practices, tools, etc).
• 1Hive DAO model docs explaining how the DAO is set up, why, and how projects can customize them for their specific goals.

Development timeline

• Where are we now and where are we going? 🌍

Currently

We are working on the docs standard and the Docusaurus template. The DAO template deployer is TBD.

Estimated time to completion: ~3-4 months (adding an extra month for snafus and unknown unknowns)

• Docusaurus Template: ~ 1 month (work has already started, but a lot has to be done to make it easy to recreate and hack on)
• DAO Template: ~ 1 month (requires finalizing the 1Hive model, then rolling that out into a CLI command and web interface)
• Documentation Standard: ~ 2-3 months to gather feedback, iterate on models, and reach consensus on a "standard" (this would happen along side the Docusaurus Template and DAO Template work)

Grant size

• Fuel in the tank to get us to the destination 🚀

Ask: $50k

• $10k for work that has already been done
• $10k for the Docusaurus Template
• $10k for the DAO Template
• $10k for the Documentation Standard
• $10k success reward

Ideally this would be split 80/20 DAI/ANT

[yeqbfgxjiq]

TODO

• modify this to conform to the Nest Grant proposal submission guide
• share with 1Hive team
• propose as Nest Grant and get feedback from the broader Aragon ecosystem
• create a request for funding
• get it done

[lkngtn]

My feedback is that this feels a bit underwhelming as a standalone grant application.

Docusaurus Template: ~ 1 month (work has already started, but a lot has to be done to make it easy to recreate and hack on)
DAO Template: ~ 1 month (requires finalizing the 1Hive model, then rolling that out into a CLI command and web interface)

I think we should take this a bit slower, and roll this into the other grant application. Being able to point to our process which we have validated by using it to work on a dev projects would make the idea of a grant to package it for easy replication much more compelling. We also may learn a lot from that process and make significant changes improvements.

When people create DAOs they could then easily syncs the docs for the apps in that DAO. These docs would be displayed within the context of the project's website using their custom themes/css. This keeps users engaged with the main project they're focused on.

I'm not sure it makes sense for open source projects to replicate application specific documentation into their project page. I would imagine for most open source projects they would probably want to have specific process documentation (like our contribution section, which may link out or reference application specific documentation elsewhere) and then have documentation on their specific open source project.

The Aragon app documentation standard and syncing does seem like it would be useful for Aragon as it allows application devs to manage their docs in the application repo, and then hack.aragon.org or wiki.aragon.org could sync those docs to a single documentation hub.

By itself this feels like a reasonable one off proposal to make to the CFDAO.

[yeqbfgxjiq]

Slowing down is not an option. I have time now, and I see a problem I can fix now, so it makes sense to work on it. I will not have this much time in the future. Either I can make a commitment to work on this now, or move on to other opportunities. Since I've spent the last few months learning about the Aragon ecosystem and understand the current problems around documentation and developer UX, it makes sense for me to move forward on this rather than something else.

The mission of 1Hive is to help open source communities thrive by making it easy for them to learn about, build, and use DAOs. I think this Kit could help a lot with that. If the team disagrees, I could roll this out on my own as separate kit that provides hack.aragon for any Aragon related project. It's well within my current understanding of JS, React, and dev UI/UX. Rather than just making it an arbitrary Kit, it would be more powerful if it shipped with a demo. This would be a great opportunity to share the 1Hive model with the world.

Regarding integrating this with the Aragon MolochDAO Suite, they're different projects. This project is to create an arbitrary framework that allows anyone to roll a Kit (template, docs, website) for their project. As a bonus the 1Hive model can be rolled in as an example. Then, once there's a framework that makes it easy to roll out kits, the Aragon MolochDAO Suite could also roll out a kit. Then so could the next project we work on, and the next, and the next. In fact, any Aragon project that wants to present their work in a cohesive manner would be able to roll out a Kit explaining what they did, how it works, and how to build/hack on it.

As mentioned, the CFDAO is not in a position to fund a long term projects (> 1 month) at this scale. If creating hack.aragon for everyone was easy, it would be done. Hack.aragon was not created in a week, or even a month. It took time. Creating a Kit that makes it easy to deploy your own hack.aragon in a few days or a week is going to be just as hard. It's also going to be just as impactful. As Aragon scales, it's going to be more and more important that there's infrastructure to help devs easily learn about and build on Aragon. I want to get ahead of that and create tools that will help us scale gracefully.

Again, I think it makes sense to roll this in the context of 1Hive so that we can dogfood the Kit with our own projects. It's complimentary to everything we're doing. Currently the dev team is weighing time commitments for Aragon app development. ATM it doesn't look like there's going to be much left over for documentation or anything else. I'm happy to fill that void, but only if we're all on the same page and moving forward together.

[yeqbfgxjiq]

Edit: thoughts slightly changed after the meeting, so update coming soon :)

[yeqbfgxjiq]

Ok... so after the meeting I'm seeing more how it could make sense to roll this all into 1 (maxed out 150k DAI + 30k ANT) grant. We would be proposing to create a suite of apps, as well as a document standard to document those apps, and a kit that makes it easy to learn about, deploy, and use a DAO model around those apps.

That being said, this would make the grants suite the main focus for the next 3 months or so. It would also mean that the 1Hive kit would not be a focus. I guess if we really wanted we could ship the arbitrary Kit framework, and then have the 1Hive Kit and the Grants Kit as examples of that... but that seems like a lot for a Nest Grant:

• Documentation Standard
• Generic Aragon Projects Kit (a model to create a hack.aragon dev hub for any project)
• 1Hive DAO model
• Grants Kit DAO model
• 2 DAO deployment templates (for above DAO models)
• 3 Docusauruses (to describe the generic kit, 1hive kit, and grants kit)
• 5 new Aragon apps

Also, we're a team of 5. Most Nest Grants I browsed through seem to be much smaller in scope and team. Is there any current or past Nest Grant that has delivered this much stuff?

[yeqbfgxjiq]

Looking at current Nest Grants

in review:aragon/nest#161
There's one objective, a simple scope, and a team of 2. Asking for 150k DAI and 30k ANT.

funded: aragon/nest#134
Delivering 2 apps for $50k DAI and $20k ANT. This includes architecture design work, which we're doing up front. We've also delivered on 1 app, for free, before even submitting a grant!

also funded: aragon/nest#93
1 app + web UI, 3 months, 100k ETH + 50K ANT.

I mean these are all really cool projects so I'm not trying to put them down in any way. I'm really glad that they're all being worked on an funded. What I am saying that we're selling ourselves short. The computer science industry is one of the fastest growing fields in the world, and the blockchain space is one of the fastest growing spaces in computer science. We're providing real value for the Aragon ecosystem. Value that has network effects and grows beyond just the concrete deliverables we'll provide in 3 months.

Also, Aragon is sitting on 50mm in ETH/ANT/cash. One of the primary objectives of Aragon is improving adoption and dev UX. The cash exists to fund that work. We're helping them to make that happen. Let's make sure we can do so to the best of our ability in a sustainable way. We're creating something amazing, we're doing it for the right reasons, and it will have a huge positive impact. Let's not sell ourselves short.

[lkngtn]

Slowing down is not an option. I have time now, and I see a problem I can fix now, so it makes sense to work on it. I will not have this much time in the future. Either I can make a commitment to work on this now, or move on to other opportunities. Since I've spent the last few months learning about the Aragon ecosystem and understand the current problems around documentation and developer UX, it makes sense for me to move forward on this rather than something else.

This doesn't feel like a very collaborative attitude. You are basically saying you are going to to do what you want to do regardless of feedback, which is fine... but while I generally support the initiative if this is the response to constructive feedback I think treating it as a solo project might be a better fit.

FWIW I'm not suggesting slowing down in general, but rather slowing down on trying to create a general framework for replicating our process and instead focusing on refining and validating the process. It seems premature to assume that the process is even worth replicating, as we have not even operationalized the process as is, we haven't gotten feedback from anyone outside of our small team, and we haven't really gone through the process of onboarding someone new and seeing whether they find the process or documentation structure confusing.

My feeling is that we should be prioritizing the following:

• creating a template for deploying the 1hive DAO so that we can deploy and test quickly without having to go through the incredibly time consuming CLI deployment process , this becomes more important as we add redemptions and payroll to the dao, as we will want to test those first without risking breaking the org that we are actively using.
• refining the structure and content of 1hive.org and our github to make the process of getting involved (finding issues to work on, interacting with team members, coordinating work, earning honey, and eventually becoming a bee) is both clear and intuitive, and that we feel good about the process (do people feel like it improves efficiency? do they feel fairly compensated? do they feel like have greater impact/ownership over the project then they do in other open source communities?)

Anyways... I guess the way I see it is there are two approaches:

1. Treat the general kit and documentation standard as a standalone project (and frame it as solving the issue of a lack of solid documentation for the many Aragon apps that have been or are being developed.) and perhaps integrate that into the wiki/hack.argon.org or a standalone aragon app documentation hub.

2. Focus on the grants/moloch/dandelion project and use it to refine our processes and documentation strategy in the context of 1hive. Then if successful and happy with that process, point to it as a success and make it easy for other projects/teams in the community to replicate and standardize around aragon app documentation.

I think for us to make the case to non-aragon, non-crypto open source projects we need to be able to point to a project/community (1hive) which has operationalized and clearly benefitted from the process in order to get them to incorporate into their community/project process. So 2 feels like the right focus for 1hive right now, but if there is interest among the other teams building aragon apps (Aragon Black, Aragon One, Autark) to create a documentation standard then doing 1 now and applying for a seperate grant makes sense.

[lkngtn]

As far as the scope of other Nest grants and teams. It's always going to be an apples to oranges comparison if you are just looking at number of team members or number of deliverables. What matters is the scope/complexity/impact of deliverables and the time commitment and qualifications of the contributors.

This is why it's important for us to understand what we are building and properly estimate scope. I don't think we are selling ourselves short, we are setting up a strong foundation for success and making sure that we are able to deliver on what we commit to (despite being a new team that hasn't worked together before using an experimental and unproven process).

[yeqbfgxjiq]

This doesn't feel like a very collaborative attitude.

Just trying to be as direct as possible so that you know where I'm at and don't have to guess. That way we can both be on the same page. I'm not saying I'm going to do whatever I want in the context of 1Hive. I'm saying that I have time I want to invest and I need to figure out how to allocate that time.

FWIW I'm not suggesting slowing down in general, but rather slowing down on trying to create a general framework for replicating our process and instead focusing on refining and validating the process.

This is valuable information and that distinction really helps me understand the problem. My thinking is that creating a general framework for our process will force us to get the model working asap, learn as we go, and get more feedback from a wider group of people. You seem to be saying that we're not ready for that yet. Happy to disagree and commit on that front lol :)

Regarding what would make us ready, I imagine you're thinking:

• finish upgrading the Rinkeby DAO so that it conforms to the model outlined on the website
• upgrade that Rinkeby DAO to mainnet
• Hello World "launch" and subsequent feedback

Then, if all that goes well... we can generalize and ship a Kit for 1Hive.

That's my guess, but I don't actually know.
What do you feel would make us ready?
What concrete steps need to be taken so that you would feel comfortable generalizing and shipping the 1Hive model?

I think for us to make the case to non-aragon, non-crypto open source projects we need to be able to point to a project/community (1hive) which has operationalized and clearly benefitted from the process in order to get them to incorporate into their community/project process. So 2 feels like the right focus for 1hive right now, but if there is interest among the other teams building aragon apps (Aragon Black, Aragon One, Autark) to create a documentation standard then doing 1 now and applying for a separate grant makes sense.

I agree. The dev hub Kit idea is cool, and does further people's ability to learn about, build, and use DAOs... but it's not geared specifically towards open source communities. It's more of a generalized framework for Aragon projects. Also, a "documentation standard" and dev hub requires feedback from a wide variety of stakeholders, not just 1Hive, so it doesn't make sense in that context. As such, I think it makes sense to develop that separately.

That being said, I would really like to see a version of this tailored towards the open source community. With that in mind, it 100% makes sense to improve the 1Hive model and focus that on sustainable open source, particularly user/dev UX and onboarding. Eventually that might involve creating a generalized Kit around that, but we're not ready yet. First things first.

We're all spending lots of time on lots of different things, so none of this is a problem. It's all complimentary. Once 1Hive is ready to generalize, I'll help with that. When we're ready to build docs and a Kit for the grants/moloch suite, I'll help with that. Until then I'll continue helping with the general stuff to keep the project moving forward as a whole.

it's important for us to understand what we are building and properly estimate scope. I don't think we are selling ourselves short, we are setting up a strong foundation for success and making sure that we are able to deliver on what we commit to

I think that keeping the scope tight and focused is the best way to achieve success here. For the 1Hive Nest Grant, the product we are delivering is a DAO suite. The apps we're building in that suite combine to create something greater than the sum of it's parts. We can deliver those apps in a package with a working demo, deployment template, docs, website, etc... The focus is not to build general infrastructure for everyone, but to deliver a suite of apps in a package that open source projects can use to empower their communities and grow sustainably.
Does that more or less align with your thinking and sound like a workable plan?

[lkngtn]

Regarding what would make us ready, I imagine you're thinking:

finish upgrading the Rinkeby DAO so that it conforms to the model outlined on the website
upgrade that Rinkeby DAO to mainnet
Hello World "launch" and subsequent feedback

Pretty much. Assuming the finish upgrading the rinkeby dao and upgrading to mainnet also implies that we have successfully operationalized the model by actively using the projects app to assign work and allocate honey, have weekly allocation votes which actually pass, and have payroll working. In other words its not sufficient to deploy it, we also have to be successfully and actively using it!

Does that more or less align with your thinking and sound like a workable plan?

Yeah after this back and forth I think we are aligned as far as I can tell. 🥂

[yeqbfgxjiq]

Awesome 🥂

From the end of the meeting yesterday it sounded like the dev team wants to have another meeting in the next few days to further sketch out the scope for all the apps. While they do that, do you want to start collaborating on a high level draft for the Nest Grant? Then we can fill it in the scope/timeline details next week, then review and edit the final draft as a group, and then submit it for official feedback 🚀

EDIT:

• started working on the 1Hive Nest Grant here
• moved the "dev hub" and "docs standard" project to a new repo here

Also, since 1Hive is going to use the docs standard and dev kit, but not build them internally, does it make sense to move that stuff outside of the 1Hive repos and/or archive/delete them?

Also saw that you created a dandelion-kit repo. Do you want to move some of the stuff in this repo over there, and then archive/delete this one, or did you have other ideas for that?

[lkngtn]

While they do that, do you want to start collaborating on a high level draft for the Nest Grant? Then we can fill it in the scope/timeline details next week, then review and edit the final draft as a group, and then submit it for official feedback

Sure, though I'll be busy most of today and flying tomorrow. So earliest can work on that is probably Monday.

Also, since 1Hive is going to use the docs standard and dev kit, but not build them internally, does it make sense to move that stuff outside of the 1Hive repos and/or archive/delete them?

Yeah that makes sense to me, keeps things clean and less cluttered.

Also saw that you created a dandelion-kit repo. Do you want to move some of the stuff in this repo over there, and then archive/delete this one, or did you have other ideas for that?

I can take a look at what's in here and move into 1hive/dandelion-kit or 1hive/dao (I think for just the basic deployment template for the 1hive org this would be right repo).

[yeqbfgxjiq]

Ok great. I'll just copy and archive the "standards" repo then.

• DONE

Regarding this repo, I'd say let's just copy out whatever we want and then archive it sometime next week?

• on my end I'll just be copying out the doc sync script stuff and a few notes
• ended up closing a lot of the open Issues as they weren't really relevant anymore

Since the "dao-template" repo is already it's own thing, do you want to copy anything useful there into the dandelion-kit and then archive it?