From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-marketing/2011-April/000225.html | 180 ++++++++++++++++++++++++ 1 file changed, 180 insertions(+) create mode 100644 zarb-ml/mageia-marketing/2011-April/000225.html (limited to 'zarb-ml/mageia-marketing/2011-April/000225.html') diff --git a/zarb-ml/mageia-marketing/2011-April/000225.html b/zarb-ml/mageia-marketing/2011-April/000225.html new file mode 100644 index 000000000..db6f7b9f1 --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-April/000225.html @@ -0,0 +1,180 @@ + + + + [Mageia-marketing] Plan - stuff to do pre Beta 1 release + + + + + + + + + +

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

+ Patricia Fraser + trish at thefrasers.org +
+ Tue Apr 5 21:05:28 CEST 2011 +

+
+ +
+
+> 2011/4/5 Patricia Fraser <trish at thefrasers.org>:
+> >
+> >
+> >> 2011/4/5 Patricia Fraser <trish at thefrasers.org>:
+> >> >> 2011/4/5 Romain d'Alverny <rdalverny at gmail.com>:
+> >> >> > On Tue, Apr 5, 2011 at 12:35, Wolfgang Bornath
+> >> >> > <molch.b at googlemail.com> wrote:
+> >> >> >>>>>          where to go to get it
+> >> >> >>>>  - link to the download page
+> >> >> >>>
+> >> >> >>> http://mageia.org/en/downloads/ (not working yet, working
+> >> >> >>> on it, will open this afternoon before release
+> >> >> >>> announcement. Not localized either yet, will be done
+> >> >> >>> afterwise, when things are square).
+> >> >> >>
+> >> >> >> The link to the download page is important to be in the
+> >> >> >> announcement.
+> >> >> >
+> >> >> > Yep. And actually, we will use http://mageia.org/downloads/
+> >> >> > (redirection after supported locales will be done there).
+> >> >>
+> >> >> Could you pls notice i18n as soon as localisation can start?
+> >> >
+> >> > I'm feeling a bit confused here.
+> >> >
+> >> > Is there actually anything wanted from the marcomm team of 1,
+> >> > or not?
+> >> >
+> >> > If not, then is there a reason to have the team at all?
+> >>
+> >> My point of view for now :) :
+> >>
+> >> We should prepare all process for beta2 and next releases. Time
+> >> is a bit short for beta1. It took time to release isos and on my
+> >> side I'm just finalizing things. What I suggest is formalize
+> >> this for beta2. WDYT ?
+> >
+> > Sounds good. Marcomm needs *lots* more input and feedback from the
+> > council about what's expected; we need council support to get an
+> > actual team rebuilt - and we need to get that process formalised,
+> > yes.
+> >
+> > I'm out of town from the middle of tomorrow until the weekend, but
+> > I'd like to get started on the pre-Beta 2 stuff at the start of
+> > next week; how does that sound?
+> >
+> 
+> I'm looking forward to your ideas. From my point of view there isn't
+> that much to organize:
+> 
+> 1. Announcement for forum, blog and mailing lists has/have to be
+> written (who does this?)
+> 
+> 2. Announcements have to be sent to these internal platforms (who
+> does this?)
+> 
+> 3. Entries in /. and DW have to be made/sent (who does this?)
+> 
+> 4. Announcements will be localized and spread worldwide by i18n
+> 
+> What else?
+
+Announcement doesn't just have to be written - it needs to be written
+in time to be passed back to the community for filtering, sanity
+checking and to find out whether the community likes the way it's
+being presented. So, it's at least a 2-step process, maybe more.
+
+Before anything can be written (at least, before anything approaching
+sensible can be written), the writer needs to have some idea what
+they're writing about, and who their readership is (see my first post
+early today). It's not good enough to assume that they're writing to
+current members of the community who already know enough to fill in
+the gaps or who know the context; from everything I've seen since day
+1, we also want at some stage to talk to people outside our community
+- that means communicating with people who don't know the context or
+enough to fill in the gaps.
+
+Sending oughtn't really to be done until we decide where. Do we stick
+with the standards of geek community/social media and hope for the
+best; do we add mainstream media, and if so, who are we talking to
+and what message are we trying to convey? How inclusive will we be,
+and are we ready for the possiblity of a large influx of
+users/developers/testers; how's our community going to hold up if we
+have a lot of sudden change?
+
+So, before we do your points 1 & 2, there's some thinking and prep to
+do - possibly quite a lot.
+
+On points 2 and 3, we could perhaps do with some kind of Mageia
+Persona to send out information - a press@ or communications@ persona
+(which could have anyone at the back end; this persona could submit
+stories to /., the fb page, send tweets and issue press releases to
+all and sundry. Just a thought.
+
+The mechanism of spreading is the last stage of the journey - there's
+quite a bit to do before that. Once there's something to spread, and
+a clear notion of where it's to go and who should send it (and who
+should do backup to fill the holes), it's fairly straightforward. 
+
+What if we get TV interest? Who will handle that and how much backup
+will they need/want from marcomm? 
+
+We'd like to make a splash with the final release of Mageia 1,
+wouldn't we? Will we be ready?
+
+Cheers,
+
+-- 
+Trish Fraser, JD9R RQ2D
+52.4161N,16.9303E
+di apr  5 20:54:38 CEST 2011
+GNU/Linux 1997-2010 #283226 counter.li.org
+andromeda up 2 hour(s), 35 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/8733699d/attachment.asc>
+
+ + + +
+

+ +
+More information about the Mageia-marketing +mailing list
+ -- cgit v1.2.1