summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-marketing/2011-April/000230.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/000230.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000230.html')
-rw-r--r--zarb-ml/mageia-marketing/2011-April/000230.html205
1 files changed, 205 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-April/000230.html b/zarb-ml/mageia-marketing/2011-April/000230.html
new file mode 100644
index 000000000..c453dd876
--- /dev/null
+++ b/zarb-ml/mageia-marketing/2011-April/000230.html
@@ -0,0 +1,205 @@
+<!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=%3CBANLkTi%3D1REdxtLcWunKRo0AHTggiZqC0LA%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000229.html">
+ <LINK REL="Next" HREF="000231.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-marketing] Plan - stuff to do pre Beta 1 release</H1>
+ <B>Wolfgang Bornath</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=%3CBANLkTi%3D1REdxtLcWunKRo0AHTggiZqC0LA%40mail.gmail.com%3E"
+ TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">molch.b at googlemail.com
+ </A><BR>
+ <I>Wed Apr 6 00:15:59 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000229.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI>Next message: <A HREF="000231.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#230">[ date ]</a>
+ <a href="thread.html#230">[ thread ]</a>
+ <a href="subject.html#230">[ subject ]</a>
+ <a href="author.html#230">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2011/4/5 Patricia Fraser &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>&gt;:
+&gt;&gt;<i>
+</I>&gt;&gt;<i> Hmm, how many people you want to ask what has to be written in an
+</I>&gt;&gt;<i> announcement of a new version? Isn't it quite clear what has to be
+</I>&gt;&gt;<i> addressed?
+</I>&gt;<i>
+</I>&gt;<i> One man's clarity is another woman's obscurity... 8-). If we're
+</I>&gt;<i> representing a community - which is what I think Mageia's marketing
+</I>&gt;<i> is doing, in part - it's good to know whether or not the community
+</I>&gt;<i> feels comfortable with the way they're being represented. It's also
+</I>&gt;<i> good if the community feels that marketing is actually a useful
+</I>&gt;<i> and valuable part of the community.
+</I>
+And how do you want to do this in practice? Announce the draft of an
+announcement?
+
+&gt;<i> You could check out the last time Yorick and the discuss list had a
+</I>&gt;<i> conversation, to get a really unmistakable feel for this - I should
+</I>&gt;<i> probably not need to point out that the shrinkage to not-quite-zero
+</I>&gt;<i> of the marketing team can be traced back to that conversation. A
+</I>&gt;<i> pity, because we were full of energy and working hard and well.
+</I>
+Hmm, I can't say much about that, it was going to deep into an area I
+am not comfortable with.
+
+&gt;<i> It's all in who you're talking to. If you're talking to a community
+</I>&gt;<i> of which you're part, you're talking to people who are already on the
+</I>&gt;<i> inside - there's an existing relationship of a kind, and they know
+</I>&gt;<i> the context and what's going on and who's who. If you're talking to
+</I>&gt;<i> people who aren't part of the community yet, you're extending an
+</I>&gt;<i> invitation. You want to present them with a picture of the community
+</I>&gt;<i> you're inviting them into (which the community doesn't need), and
+</I>&gt;<i> give them reasons that might lead them to come investigate joining -
+</I>&gt;<i> or they might just take the community's output and still not join...
+</I>&gt;<i> or they might think: no thanks.
+</I>
+What you say makes sense but I still don't see the difference. Read
+previous announcements, they all were targeted at the whole crowd,
+saying geeky things but also trying to establish a relation, asking
+the people to join the fun and all that jazz.
+
+&gt;<i> Would you feel like joining, if you felt like the announcement was
+</I>&gt;<i> exclusive, geeky, very plain-ordinary and didn't actually say: we're
+</I>&gt;<i> looking for people. Please join us - we have room in our community
+</I>&gt;<i> for people with all sorts of interests and talents. We need you! -
+</I>&gt;<i> you mightn't. It might all feel just a bit too elite.
+</I>
+&gt;<i> On the other hand, if you're an established coder, this kind of
+</I>&gt;<i> &quot;soft&quot; approach might make you wonder whether you'd be comfortable
+</I>&gt;<i> here - do people actually code, or package, or do anything really
+</I>&gt;<i> interesting to me? or am I going to get stuck being a marketroid?
+</I>
+IMHO announcements have to be both, not distinguishing between target
+groups. You can do such a distinction when you hold a conference. You
+know what type of people will be in the audience and you compile your
+speech according to that. You can make a distinction in an article
+about Mageia, you know what kind of people will usually read the
+magazine, so you write the article speaking to them in their language.
+But we are talking about an announcement of a release here, aimed at everybody.
+
+&gt;&gt;<i> We never did. We always tried to send release announcements out to
+</I>&gt;&gt;<i> everybody, geek or not geek (I'm relating to former Mandriva
+</I>&gt;&gt;<i> communication policy, around 2003-2005). As I already wrote, we
+</I>&gt;&gt;<i> spread to the geek targets but also to the general IT crowd,
+</I>&gt;&gt;<i> private users and professionals. Best examples are /., Distrowatch,
+</I>&gt;&gt;<i> online and print magazines.
+</I>
+&gt;<i> Yep. It was moderately successful. It could have been more so; it
+</I>&gt;<i> could be for us. It all depends what the community wants to have
+</I>&gt;<i> happen.
+</I>
+Hmm, I think you don't know what we did then, may be not in the
+english Mandrake websites but in some localized areas. Well, what the
+community wants to have happen? What do you think? They want to
+
+ - get the feeling that it is their distribution, that they are part of it.
+ - see success, Mageia becoming what Mandrake was for a short time.
+
+&gt;<i> I'd separate here the &quot;persona&quot; which could have anyone behind it
+</I>&gt;<i> from the people who do any communication with people outside the
+</I>&gt;<i> community (or in it, for that matter, from the &quot;function&quot; of
+</I>&gt;<i> co-ordinating, writing and disseminating targeted, on-point and
+</I>&gt;<i> well-constructed information about Mageia, whether graphical or
+</I>&gt;<i> verbal (or audio, or Braille, or what-have-you). I was positing a
+</I>&gt;<i> &quot;persona&quot;; I do think the...
+</I>
+Well, this depends on what you mean exactly. Of course it would be
+nice to have an ideal setup:
+ - all technical and organisational people will report constantly to
+marcom about what they are doing in detail
+ - marcom is perfectly understanding what those people are talking
+about so marcom can communicate with the press.
+
+As of now we haven't this setup. So, press questions (like request for
+an interview) are done by the person who can do it best. You want to
+change that?
+
+&gt;&gt;<i> &gt; What if we get TV interest? Who will handle that and how much
+</I>&gt;&gt;<i> &gt; backup will they need/want from marcomm?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> This depends 1. on the occasion (local), 2 on the language, 3. on
+</I>&gt;&gt;<i> the kind of coverage the tv company wants to do (more general, more
+</I>&gt;&gt;<i> technical, etc.
+</I>&gt;<i>
+</I>&gt;<i> I'd like to see marcomm be multilingual in time - maybe working
+</I>&gt;<i> together with i18n, which is currently very technically-focussed. The
+</I>&gt;<i> linguistic needs of marketing are a little different from those of
+</I>&gt;<i> package translators (who need to be very precise) and documenters
+</I>&gt;<i> (who need a different kind of precision and communication) - it would
+</I>&gt;<i> be good to have marcomm/i18n people who could look for the marketing
+</I>&gt;<i> nuance as they translated (like it would be good to have documenters
+</I>&gt;<i> ditto).
+</I>
+Depends what you mean with documents. Id you are talking about manuals
+and HowTos there is no room for marketing, neither in authoring nor in
+translation.
+
+Back to that tv show: as I said, it will depend on the occasion. A tv
+station in France will obviously talk to french people, a tv station
+in Berlin will obviously talk to somebody speaking German, etc. In
+such an interview you can't say, &quot;Cut, I have to ask our marcom team
+what to say.&quot;
+
+&gt;<i> What you get TV to do for you (we/us) depends entirely on how well
+</I>&gt;<i> you target your approach to them - same as anything marketing. If you
+</I>&gt;<i> can give them an angle that will help them sell advertising, they'll
+</I>&gt;<i> look at you. So it depends on the kind of program you want to target.
+</I>
+This is quite different depending where you are and what type of tv
+station it is. I've done some (radio and tv) in Germany, the occasions
+that they are waiting for you are rare because a Linux distribution is
+no real news to get excited over.
+
+&gt;<i> What I was wondering about, though, was: suppose we're successful in
+</I>&gt;<i> getting a TV spot? What then?
+</I>
+This is a very different thing. There you are on the spot with all
+your thoughts about targets and all other stuff. Because advertizing
+is always a question of target.
+
+&gt;<i> Marketing is the same whether commercial or otherwise - it's about
+</I>&gt;<i> getting the message out. First decide what you want it to be;
+</I>&gt;<i> second, construct it; third, spread it. Simplified, but that's the
+</I>&gt;<i> job.
+</I>
+That's all what I was talking about. :)
+
+--
+wobo
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000229.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI>Next message: <A HREF="000231.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#230">[ date ]</a>
+ <a href="thread.html#230">[ thread ]</a>
+ <a href="subject.html#230">[ subject ]</a>
+ <a href="author.html#230">[ 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>