Weāre here because weāre excited about Radicle, because we find it compelling, because we want to see this vision materialize. All of us became aware of Radicle through one way or another, but now as a group we need to turn our sights to the objective of helping others learn of Radicle because without increased awareness we will not see Radicle becoming a standard.
So how do we increase awareness? I think at minimum there are two efforts we can engage in, one which looks like funding individuals or groups for āDeveloper Relationsā roles on behalf of Radicle, and the other is more akin to content marketing.
Before we proceed to a formal proposal about funding, I wanted to bring this up to the community and gauge the reception. Would love to get feedback and hear thoughts.
I definitely think that there is a lot to be done to increase awareness for Radicle, especially as the network becomes more stable in Q4 from a tech standpoint.
I personally would love to see a working group around that topic. It could be part of the growth working group that is being discussed, although āawarenessā is simply the top of the funnel, while āgrowthā could capture initiatives around awareness ā adoption ā engagement ā retention ā evangelism.
Beyond the ideas you mentioned (dev relations and content), we also need to consider a more structured approach on 1. Events (hackathons, conferences, meetups) and 2. Partnerships (especially with other DAOs or projects that increase awareness for Radicle).
Well events are always temporal and usually are overflown with things happening there but you need to exposed there. I think for starters we should focus on all other devs building on crypto and try to lure them over from centralised services. Itās not too difficult to scrab GH usernames and emails and run a drill campaign but itās quite brute force and intrusive. I guess itās better to post a friendly post on other discord channels or just open GH issue.
I like the idea of opening github issues to engage with projects that we feel would benefit from our vision. Itās probably quite a labor intensive approach but feels more inline with what we stand for.
I think this is a good first step. Perhaps whatās missing though is for us to agree on what we need on the Radicle side of things that we think will be enticing enough for developers to mirror some projects over. It should be a sort of package that includes some basic but useful features.
What you donāt want is for 10,000 developers to try it out and end up having a poor experience.
Definitely a measured response - where you understand each type of users + their needs - at first is best. Probably best to build a few dozen good experiences with users/DAOs, then go wild.
I really like some of the ideas from @nas recent post for this
Yeah, I have used them extensively. They are a new breed of community CRMs, but are targeted to help manage your own community over the many platforms/channels.
Before reaching out, I would create some pieces about how to use Radicle with real-life use-cases. Move beyond the docs āhowā and write about the why in a real-life scenario that is relevant to web3/daos.
Do we have examples by now of teams that have migrated over to radicle?
One or two success stories might actually be the incentive for teams that already care about ādecentralizationā to consider the jump.
āWe donāt rely on microsoft/github any moreā is a very powerful message - for both the team in question, as well as radicle itself - and isnāt āin your faceā kind of marketing imho.
