[Mageia-marketing] Plan - stuff to do pre Beta 1 release

[Patricia Fraser]

Hi Wobo,

> Comments inside:

And mine:
 
> 2011/4/4 Patricia Fraser <trish at thefrasers.org>:
> > Hi all,
> >
> > Two things to be written - the release announcement, and the
> > wrapper words for the testing day procedure (to make a testing day
> > announcement).
> >
> > Help welcome!
> >
> > Testing day is Friday/Saturday (08/09-04-11), and we want to
> > announce it on release day (tomorrow) and propagate the
> > announcement widely.
> >
> > Comms plan: release announcement/testing day announcement
> >
> > What: release (alpha, beta or otherwise)
> >
> > Who to: Mageia community
> >        Open source communities
> >        wider community
> >
> > How:    Mageia blog
> >        Distrowatch
> >        slashdot
> >        other tech news sites
> >        Mageia lists - ask list members to forward it to their
> > communities (any we've missed) and i18n team, propagate in their
> > languages please
> 
> I'd structure this a little bit different, although we mean the
> same:
> 
> The "Who" is quite clear: the main announcer (ennael?)
> Text proposed by marcomm.

The who I meant is "to whom are we speaking with this announcement?"

From the roadmap, this release is for: packagers, developers, testers
(as per Alphas 1 and 2) and (new) test users. 

So, are we unleashing Beta 1 on the general public? How public do we
want this announcement to be?

Next: the text of the actual announcement vs. the marketing/comms
text; where do we get hold of the actual announcement to write up a
release notice that a) refers to the announcement and b) can be
released?

Next: who should see the marcomm text before it gets released, to say
yea/nay?

> 
> Where:
> 
>  - internally
>  - - Blog
>  - - Forum
>  - - Mageia lists
> 
>  - externally
>  - - Distrowatch
>  - - slashdot
>  - - other sites
> 
>  - through i18n:
>  - - translations of the blog and the download page (as has been
> done for previous announcements)
>  - - spreading the announcement to local communities (lists,
> forums), local news sites and online magazines
> 
> > Content:  what's being released
> >          what's new
>  - with link to the release notes
> 
> >          where to go to get it
>  - link to the download page
> 
> >          welcome to new users
> >          encourage new makers / contributors
> >          about Mageia
> 
> To achieve worldwide attention (we should reach this until final) it
> should all be spread within a very tight time span, on the same day.
> People must be plastered with the Mageia announcement, wherever they
> look at that day.

Yep. And today is release day, so I need to get cracking...

> 
> For the future we should implement a procedure where such
> announcements will be sent to the translators 1 day in advance.

*If* I can get the info above, I'll have something for people to look
at/critique/translate by early afternoon. If not, not.

 
> > Extra for testing day:
> >        damsweb's testing procedure
> >        inside marcomm wrapper
> >
> > Time to write: marcomm bit, ready by 05-04-11
> >                testing wrapper, soon as I see damsweb's doc
> 
> The same procedure in spreading as for the beta announcement,
> following as a sequel - people have to regard both announcements as
> related, the testing day as a follow-up to the release.
 
Sure...

Cheers!

-- 
Trish Fraser, JD9R RQ2D
52.4161N,16.9303E
di apr  5 07:03:32 CEST 2011
GNU/Linux 1997-2010 #283226 counter.li.org
andromeda up 13 hour(s), 6 min.
kernel 2.6.33.7-desktop-2mnb
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: </pipermail/mageia-marketing/attachments/20110405/49824f63/attachment.asc>