On Thu, Sep 5, 2013 at 2:52 AM, Joe Brockmeier <jzb(a)redhat.com> wrote:
On Thu, Sep 05, 2013 at 04:00:21PM +1000, Ankur Sinha wrote:
> The docs team keeps trac of the new features as far as I know. In the
> past, data from their "beats" was used to create talking points (I
> think). Might be less work if we could work with them on this again.
Indeed. Good point.
I think this is partially true - though it depends on which release cycle
you look at in the past.
What the docs folks choose to create beats on and what marketing chooses to
highlight may be different; sometimes there has been crossover, in which
case it's been easy to borrow and re-work some of the already-created
content. (This doesn't apply just to talking points, but also to release
announcements, etc.) But more than once the occasion has come up where
there was no existing content, or the docs content was more ...
documentation-ish in nature than would be appropriate for marketing-type
There certainly is opportunity for cross-over here, but from a process
standpoint I don't think it makes sense to want or expect absolute
consistency across two groups of content that are serving different
> +1 for reusing the trac. The milestones etc. are really helpful when it
> comes to release critical tasks.
> I don't see "Create marketing collateral" in the list. We didn't
> any last release and the ambassadors had no flyers/one page release
> notes to give out at all. Worth adding to the list?
Yeah. Suggestions on deadline? I'll see about getting those added to the
I would wait to *start* until after the "Changes 100% Completed" deadline -
likely around the time we kick off one-page release notes, if we want to
continue to produce that item. Otherwise you run the risk of creating a
lot of content - which may get translated as well - and then having a
change (formerly known as a feature) get dropped due to non-completion, and
then need to rewrite/rework/retranslate.
I think the finish-by deadline should probably be the same date as the
one-page release notes completion date; this gives folks a reasonable
amount of time to translate and fix any printing details (does the
translation fit in approximately the same area of space, etc.) before we
get to GA.
All that said - if we want to take some fresh eyeballs to the format of
existing flyers and re-think how it should/could look and get a new
template set up and ready, that can certainly be started now, in
anticipation of filling it in once we get to the appropriate point in time.
> My schedule's quite tight at the moment, but I can keep
track of the
> tickets and help where I can once they're up.
Joe Brockmeier | Open Source and Standards, Red Hat
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
marketing mailing list