summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-marketing/2011-April/000225.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-marketing/2011-April/000225.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-1be510f9529cb082f802408b472a77d074b394c0.tar
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz
archives-1be510f9529cb082f802408b472a77d074b394c0.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000225.html')
-rw-r--r--zarb-ml/mageia-marketing/2011-April/000225.html180
1 files changed, 180 insertions, 0 deletions
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 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-marketing] Plan - stuff to do pre Beta 1 release
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3C20110405210528.1fcf45c1%40andromeda.localdomain%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000224.html">
+ <LINK REL="Next" HREF="000226.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-marketing] Plan - stuff to do pre Beta 1 release</H1>
+ <B>Patricia Fraser</B>
+ <A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Plan%20-%20stuff%20to%20do%20pre%20Beta%201%20release&In-Reply-To=%3C20110405210528.1fcf45c1%40andromeda.localdomain%3E"
+ TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">trish at thefrasers.org
+ </A><BR>
+ <I>Tue Apr 5 21:05:28 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000224.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI>Next message: <A HREF="000226.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#225">[ date ]</a>
+ <a href="thread.html#225">[ thread ]</a>
+ <a href="subject.html#225">[ subject ]</a>
+ <a href="author.html#225">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>
+
+&gt;<i> 2011/4/5 Patricia Fraser &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>&gt;:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;&gt; 2011/4/5 Patricia Fraser &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>&gt;:
+</I>&gt;<i> &gt;&gt; &gt;&gt; 2011/4/5 Romain d'Alverny &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">rdalverny at gmail.com</A>&gt;:
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt; On Tue, Apr 5, 2011 at 12:35, Wolfgang Bornath
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt; &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">molch.b at googlemail.com</A>&gt; wrote:
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt;&gt;&gt; &#160; &#160; &#160; &#160; &#160;where to go to get it
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt;&gt; &#160;- link to the download page
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt; <A HREF="http://mageia.org/en/downloads/">http://mageia.org/en/downloads/</A> (not working yet, working
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt; on it, will open this afternoon before release
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt; announcement. Not localized either yet, will be done
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;&gt; afterwise, when things are square).
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt; The link to the download page is important to be in the
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;&gt; announcement.
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt; Yep. And actually, we will use <A HREF="http://mageia.org/downloads/">http://mageia.org/downloads/</A>
+</I>&gt;<i> &gt;&gt; &gt;&gt; &gt; (redirection after supported locales will be done there).
+</I>&gt;<i> &gt;&gt; &gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt;&gt; Could you pls notice i18n as soon as localisation can start?
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; I'm feeling a bit confused here.
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; Is there actually anything wanted from the marcomm team of 1,
+</I>&gt;<i> &gt;&gt; &gt; or not?
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; If not, then is there a reason to have the team at all?
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; My point of view for now :) :
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; We should prepare all process for beta2 and next releases. Time
+</I>&gt;<i> &gt;&gt; is a bit short for beta1. It took time to release isos and on my
+</I>&gt;<i> &gt;&gt; side I'm just finalizing things. What I suggest is formalize
+</I>&gt;<i> &gt;&gt; this for beta2. WDYT ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Sounds good. Marcomm needs *lots* more input and feedback from the
+</I>&gt;<i> &gt; council about what's expected; we need council support to get an
+</I>&gt;<i> &gt; actual team rebuilt - and we need to get that process formalised,
+</I>&gt;<i> &gt; yes.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I'm out of town from the middle of tomorrow until the weekend, but
+</I>&gt;<i> &gt; I'd like to get started on the pre-Beta 2 stuff at the start of
+</I>&gt;<i> &gt; next week; how does that sound?
+</I>&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;<i> I'm looking forward to your ideas. From my point of view there isn't
+</I>&gt;<i> that much to organize:
+</I>&gt;<i>
+</I>&gt;<i> 1. Announcement for forum, blog and mailing lists has/have to be
+</I>&gt;<i> written (who does this?)
+</I>&gt;<i>
+</I>&gt;<i> 2. Announcements have to be sent to these internal platforms (who
+</I>&gt;<i> does this?)
+</I>&gt;<i>
+</I>&gt;<i> 3. Entries in /. and DW have to be made/sent (who does this?)
+</I>&gt;<i>
+</I>&gt;<i> 4. Announcements will be localized and spread worldwide by i18n
+</I>&gt;<i>
+</I>&gt;<i> What else?
+</I>
+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 &amp; 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: &lt;/pipermail/mageia-marketing/attachments/20110405/8733699d/attachment.asc&gt;
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000224.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI>Next message: <A HREF="000226.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#225">[ date ]</a>
+ <a href="thread.html#225">[ thread ]</a>
+ <a href="subject.html#225">[ subject ]</a>
+ <a href="author.html#225">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-marketing">More information about the Mageia-marketing
+mailing list</a><br>
+</body></html>