Not sure who said this, but I want to make a simple point.
I have been uneasy about our shopping list of needs approach to
engaging new contributors. Every open source article about attracting
and engaging contributors talk about providing a easily accessible
list of activities for contributors to get started. Yet, when ever I
read those lists (and our lists) I end up saying 'Why should I help
with this.'
This is not an either/or proposition.
Providing direction without creating passion results in a roadmap that no
one sees.
Creating passion without providing direction results in wasted energy.
Both are absolutely crucial -- but order matters. *First* create your
roadmap, and understand how contributors can help. *Then* drive as much
interest as possible in the organization's mission, and make sure that
every communication has a call to action for those who are passionate
about the mission.
Important caveat: your roadmap need not be the only roadmap, and you
should always be careful to give people room to explore their passions.
But when someone shows up and says "what can I do?" the answer had better
be crisp.
--g
--
Computer Science professors should be teaching open source.
Help make it happen. Visit http://teachingopensource.org.
_______________________________________________
Marketing mailing list
[email protected]
http://lists.sugarlabs.org/listinfo/marketing
