-
Notifications
You must be signed in to change notification settings - Fork 6
Publicity Cabal
Meetings are Tuesdays at 13:30 GMT. Anyone is invited to add additional topics to the Conference and Event or Additional Content etherpads and to attend the weekly meetings to discuss.
Our primary agenda concerns topics that are reaching fruition - upcoming releases or events, listed below. You can also view Completed Publicity Cabal Items.
| Topic | Next Relevant Date | Comments | To Do | Contact |
|---|---|---|---|---|
| Loadays (Rome) | April 6 - 7, 2013 | http://loadays.org/, Francesco Vollero has been invited to submit | Wait to hear back | Francesco Vollero |
| Codemotion (Rome) | March 22 - 23, 2013 | http://roma.codemotion.it/, Michal Fojtik has been invited to speak | Get details, blog | Michal Fojtik |
| Red Hat Brno Developer Conference, 2013 | February 23rd - 24th, 2013 | http://www.devconf.cz/cfp; The talk by Petr Blaho/Jiri Stransky have been accepted | Create post-conference news post | Justin Clift, Tomas Sedovic |
| Red Hat Summit | Matt and Tomas has submitted a proposal | Wait and see | Matt Wagner, Tomas Sedovic |
| Topic | Category | Next Relevant Date | Comments | To Do | Contact |
|---|---|---|---|---|---|
| Deltacloud 1.2 (?) | Release | mid-February | Michal Fojtik says Deltacloud will have their own release page, which we can link to | Blog about it when it happens | Mainn Chen |
| ImageFactory ?? | Release | mid-January | No formal release since 1.0, Ian McLeod thinks they should do another one; will talk about it with Steve | Wait and see! | Mainn Chen |
| Conductor Release | Release | mid-February | Conductor | Mainn should check with release cabal now | Mainn Chen |
| Release Cabal Coordination | Release | mid-January | Co-ordinate with release cabal on release cabal-sponsored releases | Work together to create process for next release | Steve Linabery, Mainn Chen |
| EVM integration | Content | We'll want to keep an eye on this | |||
| Screencast Webpage | Content | "Thumbnails, organised by topic, in date order" | Mainn will talk with website cabal | Justin Clift | |
| Sprint 1, January 2013 | Sprint | January 30th, 2013 | end-of-Sprint delayed | ||
| Presentations from Brno | Content | provider selection blog post created | Jirka will check if there are anymore | Jirka Tomasek, Mainn Chen | |
| tuxjournal.net | Content | Francesco invited to write an article about Aeolus | in process | Francesco Vollero | |
| DevTools (Conductor on Ubuntu) | Release | Now | Crag is working on an update for this | Should be available in next end-of-Sprint demo | Crag Wolfe, Mike Orazi, Mainn Chen |
| Debian and Aeolus | Content | Being worked on by Hideki Yamane (henrich at debian dot org), mailing list at http://lists.debian.org/debian-cloud/ | Justin will work with release cabal to figure out versions of components being released, and point the Debian guys at them | Justin Clift | |
| JRuby | Content | Create content; Francesco Vollero will work with Tomas Sedovic | Tomas Sedovic |
In order to participate in a conference or event, you must first confirm the expense with your manager; or confirm that you will handle travel expenses yourself.
Once participation in an event is confirmed, we will publicize the following:
- Acceptance
- Pre-conference reminder
- Post-conference report
Upcoming events we are looking at are listed here: http://etherpad-aeolusproject.rhcloud.com/p/Aeolus_event_planning
As a product approaches release, we will create a release page on the website (see http://www.aeolusproject.org/releases/template.html for a template).
Initially, the page will provide a high-level view - a short and easily digestable summary of what to expect from the release. This page and summary will be publicized. In the following days, we will add detailed looks at features in the release - walkthroughs, use cases, technical documentation, etc. This information will come from the developers (and from the end-of-Sprint videos), and be organized on the release page by the publicity cabal. Updates will be publicized in chunks.
Finally, once the release is out the door, we will update the release page to include information on how to obtain the release. This will also be publicized.
This etherpad tracks general release date notes: https://etherpad-aeolusproject.rhcloud.com/p/all-project-release-dates
For each sprint, we will:
- Publicize the end of the sprint
End-of-sprint presenters are expected to make screencasts, if appropriate. Instructions can be found here: https://github.com/aeolusproject/aeolusproject.github.com/wiki/Screencasts-recording
Publicity will consist of blog posts and Tweets.
This etherpad tracks additional topics that we would like to talk about: http://etherpad-aeolusproject.rhcloud.com/p/Aeolus_content_planning
- Our current activities
- News from elsewhere
- Present Assets
- AOB
State of our set of social media outlets. We will determine what kind of content gets pushed where.
- http://twitter.com/aeolusproject
- http://identi.ca/aeolusproject
- http://blog.aeolusproject.org/
- https://www.facebook.com/AeolusProject
- https://plus.google.com/109718770418645820147/posts
Here are instructions on how to manage our internally hosted social media: https://aeolusproject.org/redmine/projects/aeolus/wiki/Blogaeolusprojectorg_playbook