Differences

This shows you the differences between two versions of the page.

--- communications:strategy_2011 [2011/09/24 16:24] – [Guide the development of the website and any other relevant communication vehicles.] jimcraner
+++ communications:strategy_2011 [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 30: / Line 30: @@
 Communcations Committee should take on the role of Outreach & Awareness and adopt some marketing-related strategic objectives.  This doesn't have to be corporate drone type marketing stuff but just getting the messages from the EG Community out to the non-EG community.  What messages?  A good approach is storytelling, so we can tell the story of how EG is affordable, flexible and versatile, well-supported, the backbone of a thriving and successful and growing community.  We can tell the participation stories of organizations developing new features together and tell the success stories of major implementations and migrations.  We can tell the stories of the few K-12 folks and get more K-12 folks interested. And any other stories the community has to share.
+==== Promote widespread participation by community members in the building and ongoing improvement of a semi-formal community knowledge base (in the form of a wiki) ====
+) Engage in a regular campaign to increase community participation on the wiki.  This could take the form of a quarterly reminder to the mailing list (and maybe associated blog posts on various community blogs) extolling the virtues and ease of wiki participation, and linking to these guidelines.
+) Implement the "adopt-a-page/section" plan we discussed in recent Web Team conversations.  On a related note, it might make sense for one or more people from the Web Team to "adopt-the-wiki" and be the wiki cheerleaders/community leaders.
+) Offer in-person and online-coordinated wiki improvement process analogues of "hackfests" so that non-developers can actively contribute to the EG knowledge base.  This could be managed by the wiki leaders mentioned in #2.
+) Coordinate with DIG so that there is coordination between related content updating and maintenance on the Docs site and the wiki.