[OpenRelief Outreach] [PR / UX] Pressing requirements to grow non-tech community

[Jane Johnston]

Agreed.

On 24 March 2012 09:40, Shane Coughlan <shane at openrelief.org> wrote:

> Hi Jane
>
> On Mar 20, 2012, at 4:57 PM, Jane Johnston wrote:
> > 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
> solutions.
> > 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.
>
> All good points.
>
> Regarding who we need to reach (assuming my last email about PR was
> correct):
> - Technologists who can help design, refine and advocate the OpenRelief
> solutions
> - Commercial enterprises who can put these solutions into production (or
> build some of them)
> - Volunteer and professional emergency relief crews who need to deploy and
> use the solutions
>
> When it comes to recruitment of non-technical people who are not
> specialized in either outreach or development (in other words our general
> audience), I suggest we place them on the "user" list. It exists but is
> currently inactive. This list can then be used to summarize developments
> and to engage with questions and feedback.
>
> Regarding the landing page, www.openrelief.org should take that function
> as we move towards the June launch. I'm working on a rejigged slide set and
> page this evening. If you could provide feedback on that it would be great.
> I will mail this list when it is active. If it makes sense from the PR
> perspective, then we can check with the developer list to make sure
> everyone is happy, and regarding this as the foundation of our outreach
> heading towards launch. Agreed?
>
> Regards
>
> Shane
> _______________________________________________
> Outreach mailing list
> Outreach at openrelief.org
> http://openrelief.org/mailman/listinfo/outreach_openrelief.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openrelief.org/pipermail/outreach_openrelief.org/attachments/20120328/fb0ef0b0/attachment.html>