Hi All. I just wanted to get input on potentially taking a different approach to onboarding partners to Radicle Orgs.
At moment I am doing onboarding calls with partners to get them setup with an Org, but they are having a few issues:
- 2 hours of work for full setup
- Spending ~$1000 in gas
- something is always buggy/broken - e.g. indexing of orgs by the graph is suppppper slow
- Have to pull their infra teams into the mix to help with org node setup - MASSIVE BLOCKER and people keep giving up or delaying as a result.
There are also a few open questions and work being done that will address these issues:
- whether we will rearchitect Orgs to simplify and reduce cost
- onboarding flows are being improved
- org node deployment processes are likely to be automated
- we may be able to use a automatically generated url over needing user to update DNS
I don’t see there being a lot of value to onboarding Orgs right now ahead of having additional features that make it reliable for code distribution, collaboration, and driving contribution. I think it may do more harm than good. Also, I can certainly think of a number of better ways that $200k can be spent to drive growth (e.g. two more people working on the schlep of building relationships with partners).
I propose that we take a different approach that will probably set us up much better for the launch of contribution features next year.
- create a website that outlines a very focused pitch on DevDAOs
- Have projects that are building developer ecosystems fill out a form that shares any grant programmes, open positions (funded contributors), and funded issues (bounties) with us
- Have developers and teams that want to contribute to web3 projects fill out a form that shares details on their experience, skills, and projects they’d like to learn more about and contribute to.
- perhaps have a partner page that lists those that complete form and are approved as launch partners (like arbitrum - https://portal.arbitrum.one/)
- maybe we also add a create radicle ens name step here
this website can perhaps sit on devdao.radicle.xyz for now?
I started building this flow here: https://devdao.netlify.app/
I’ve also put rough wireframes together for what it should communicate:
I’ve already spoken about these issues with @abbey and @cloudhead, so this is a way of me presenting a case to both of you so we can decide on a way forward. Also welcome input from anyone else that’s interested.