Communications Team

Membership

Please join, if you like.

The Communications Team is responsible to inform, explain, promote Tiki the application and Tiki the community, to attract more & more users & contributors.

This team is in charge of Marketing, Promotion and Advocacy.

Objectives

Increase Tiki visibility
Increase number of Tiki installs
Attract talent & energy to Tiki (Developers, designers, etc.)

Members

Team Communications

chibaguy
Cyril
daniam
gezza
GuyVigneault
jonnybradley
marclaporte
omstefanov
philippeback
Regis
ricks99
slordjette

And you? Add your name to join!

Release responsibilities

[-]

Make doc:Tiki7 nice
Update Fact Sheet
Publish news on info.tiki.org, SourceForge, Freshmeat, etc.
Update info on all Listings
Inform Control Panels to update (Fantastico, etc.)
Inform demo sites. (OpenSourceCMS.com, etc)
Promote on all relevant Social networking sites. (Facebook, etc.)
Promote on all Wiki and CMS-related resources (ex.: CMScritic.com)
Update Promo Sheet
Update Features list & ratings
Review Tiki Welcome, as all new registrants are sent to it after validating their email link.

Tasks (do and cross out)

[-]

2010-09 Marc Laporte Interview CMS Critic
~~Fix this by opening and using a different Kaltura account~~
Get approval on this one or delete it by december 2010 if not getting an OK to either edit more or leave as is and send it to Youtube. Here is the countdown: 502 days, 21 hours, 22 minutes, 14 seconds, since december 31st, 2010. After which this video clip will be deleted
~~Fix the Google Analytics code for all *.tiki.org sites~~
Appears to be working now for Tiki5.
Major overhaul to Wikipedia entry
See Tiki Wikipedia Entry for work in progress (and to help!).
Improve presentation of features (our strength) on info (too many clicks now and not enough graphics)
- http://dev.tiki.org/Bugs+and+wishlist+stats#By_Tiki_feature

get listed on http://www.aiimcommunities.org/e20/buyers-guide/product-index
investigate http://www.cmsmyth.com/

Projects

[-]

Develop a complete marketing, branding and promo strategy

[+]

Promote Tiki as a model and as a solution

[+]

Ongoing responsibilities

Surveys

[+]

Monitoring

[+]

Issue news releases

CMS resources

Add additional outlets to Press Releases newsletter.
Edit, review, update the pending news releases.

See Upcoming News for pending news releases.

A little aside: http://techcrunch.com/2010/09/06/meetyourfriends/ - entertaining post about what should be avoided in press releases.

Automatic

These resources are notified of Tiki news via the Press Releases newsletter:

http://www.h-online.com/ (The H)
editors at h-online.com

Manual

These resources require manual notification of Tiki news (they use a unique web form instead of email):

Other Communication Tasks

For each release, be sure to update the following items:

http://opensourcecms.com
http://php.opensourcecms.com/scripts/details.php?scriptid=63&name=TikiWiki%20CMS/Groupware
Requires developer login. Contact Rick or Marc for details.
http://en.wikipedia.org/
http://en.wikipedia.org/wiki/Tikiwiki
''also update any other pages mentioning TW and specific version number: http://en.wikipedia.org/wiki/Special:WhatLinksHere/TikiWiki
http://freshmeat.net/projects/tiki
http://sourceforge.net/projects/tikiwiki/

Awards

[+]

Outreach

[+]

Big picture ideas

Develop a Viral Tiki strategy

More ideas (from Rick)

We need more Twitter streams. I would like to re-suggest that we convert the RSS feeds from each forum into Tweets for its own account (tikiwiki_features, tikiwiki_i18n, tikiwiki_svn, etc.). The constant stream of tweets into the Twitterverse will help make Tiki appear more "alive."
Current "official" TW Tweet streams include:
- http://twitter.com/tikiwiki — Official news
- http://twitter.com/tiki_code — SVN Commits (automated)
- http://twitter.com/tiki_search — Retweets any item with tikiwiki keyword or tag (automated)
- http://twitter.com/tiki_themes
- http://twitter.com/tikifest
~~Update the two.o registration tracker to include links to all the TW-related signups (Ohloh.net, FB, etc.).~~
We should mirror the tw.o forms with the SourceForge mailing lists (this will help to raise the SF activity rating, too). We could mirror them one way (push all forum posts -> SF mailing list), which is very easy, and simply update the footer of each SF message to include a note that responses should be posted to tw.o forums.
Mirror the dev mailing list (and the others, too, but they're very low traffic) to the tw.o forum. There's LOTS of good information there that end-users could benefit from. We could make the forum read-only, with no impact to the existing dev list.