Open Stack

Hey guys,

Yet another thread worth responding to.  Thread link is here:

http://lists.openstack.org/pipermail/openstack-dev/2015-May/063409.html

--Rocky

From: Anne Gentle [mailto:annegentle at justwriteclick.com]
Sent: Wednesday, May 06, 2015 06:14
To: OpenStack Development Mailing List
Subject: [openstack-dev] [all] TC Communications planning

Hi all,

In the interest of communicating sooner rather than later, I wanted to write a new thread to say that Flavio Percoco and I are going to work on a TC communications plan as co-chairs of a TC communications working group.

I think we can find a happy medium amongst meeting minutes, gerrit reviews, and irregular blog entries by applying some comms planning, so that Flavio and I can dive in.

Please answer these questions on the list if you're interested in shaping the communications plan:

Audience considerations:
Is the primary audience current OpenStack contributors or those in consumer roles?
What percentage of the audience are fairly new contributors? Fairly new to OpenStack itself?
Is the audience more likely to be an "outsider looking in" to OpenStack governance?
Is the audience wanting to click links to learn more, or do they just want the summary?
Does the audience always want an action to take, or is simply getting information their goal?

Channel considerations:
Is this audience with their goals more likely to use blogs, RSS, and Twitter or subscribe to mailing lists?
Depending on the channels chosen, is cross-posting to multiple channels a huge error, or are we leaning towards a wide net rather than laser targeting?
Is there another channel we haven't considered that is widely consumed?
Does the cadence have to be weekly, even if "not much happened with the TC" is the activity rate for the week?

Thanks all for participating and giving input.

Anne and Flavio

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://lists.openstack.org/pipermail/product-wg/attachments/20150508/175c58ba/attachment.txt>