[OpenRelief Outreach] [PR / UX] Pressing requirements to grow non-tech community
jane.backhouse at gmail.com
Tue Mar 20 07:57:52 GMT 2012
A clear difference between OpenRelief and other open source projects is
that we need the buy-in of non-tech communities for it to succeed. By
non-tech, I mean non-coders or those not familiar with open source
Our first adopters will be from this community.
I propose we therefore prioritise recruitment of potential first adopters.
We need this community to shape the project as much as the technologists.
Requirements for Initial Recruitment:
- A simple call to action on OpenRelief.org /.com - What do we want them
to do (now)? Subs. to a list?
I believe it should be - we need them to understand how open source
projects communicate. And to start contributing to the conversation.
- So, which list? Is there a case for a "key decisions" list - both tech
and outreach - to which our first adopters can contribute?
We need their experience on both sides of the conversation - but they will
only be motivated to engage with big picture decisions. Overwhelm them and
we'll lose their contribution.
If so, we need to ask our community to think in terms of a
cross-pollination / key decisions list. Would this work? Has it been used
in other projects? Anyone with experience in this?
- A simplified "landing page". With one story to get behind.
We need to send out a link. Something that can be shared. A video would be
ideal. It needs to summarise the "now" project we're working on. This can
be any one of the modules / transport systems / analysis systems but it
can't be all of them, not upfront. We need one hook project that can be
easily visualised. And that is easy to visualise for a non-techie.
We need our tech community to agree on this project. And to understand why
it's needed. It's a rallying call. A simple story for Wired Magazine. It
doesn't have to be the full picture.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Outreach