diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-marketing/2011-April/000230.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000230.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2011-April/000230.html | 205 |
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 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>>: +>><i> +</I>>><i> Hmm, how many people you want to ask what has to be written in an +</I>>><i> announcement of a new version? Isn't it quite clear what has to be +</I>>><i> addressed? +</I>><i> +</I>><i> One man's clarity is another woman's obscurity... 8-). If we're +</I>><i> representing a community - which is what I think Mageia's marketing +</I>><i> is doing, in part - it's good to know whether or not the community +</I>><i> feels comfortable with the way they're being represented. It's also +</I>><i> good if the community feels that marketing is actually a useful +</I>><i> and valuable part of the community. +</I> +And how do you want to do this in practice? Announce the draft of an +announcement? + +><i> You could check out the last time Yorick and the discuss list had a +</I>><i> conversation, to get a really unmistakable feel for this - I should +</I>><i> probably not need to point out that the shrinkage to not-quite-zero +</I>><i> of the marketing team can be traced back to that conversation. A +</I>><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. + +><i> It's all in who you're talking to. If you're talking to a community +</I>><i> of which you're part, you're talking to people who are already on the +</I>><i> inside - there's an existing relationship of a kind, and they know +</I>><i> the context and what's going on and who's who. If you're talking to +</I>><i> people who aren't part of the community yet, you're extending an +</I>><i> invitation. You want to present them with a picture of the community +</I>><i> you're inviting them into (which the community doesn't need), and +</I>><i> give them reasons that might lead them to come investigate joining - +</I>><i> or they might just take the community's output and still not join... +</I>><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. + +><i> Would you feel like joining, if you felt like the announcement was +</I>><i> exclusive, geeky, very plain-ordinary and didn't actually say: we're +</I>><i> looking for people. Please join us - we have room in our community +</I>><i> for people with all sorts of interests and talents. We need you! - +</I>><i> you mightn't. It might all feel just a bit too elite. +</I> +><i> On the other hand, if you're an established coder, this kind of +</I>><i> "soft" approach might make you wonder whether you'd be comfortable +</I>><i> here - do people actually code, or package, or do anything really +</I>><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. + +>><i> We never did. We always tried to send release announcements out to +</I>>><i> everybody, geek or not geek (I'm relating to former Mandriva +</I>>><i> communication policy, around 2003-2005). As I already wrote, we +</I>>><i> spread to the geek targets but also to the general IT crowd, +</I>>><i> private users and professionals. Best examples are /., Distrowatch, +</I>>><i> online and print magazines. +</I> +><i> Yep. It was moderately successful. It could have been more so; it +</I>><i> could be for us. It all depends what the community wants to have +</I>><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. + +><i> I'd separate here the "persona" which could have anyone behind it +</I>><i> from the people who do any communication with people outside the +</I>><i> community (or in it, for that matter, from the "function" of +</I>><i> co-ordinating, writing and disseminating targeted, on-point and +</I>><i> well-constructed information about Mageia, whether graphical or +</I>><i> verbal (or audio, or Braille, or what-have-you). I was positing a +</I>><i> "persona"; 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? + +>><i> > What if we get TV interest? Who will handle that and how much +</I>>><i> > backup will they need/want from marcomm? +</I>>><i> +</I>>><i> This depends 1. on the occasion (local), 2 on the language, 3. on +</I>>><i> the kind of coverage the tv company wants to do (more general, more +</I>>><i> technical, etc. +</I>><i> +</I>><i> I'd like to see marcomm be multilingual in time - maybe working +</I>><i> together with i18n, which is currently very technically-focussed. The +</I>><i> linguistic needs of marketing are a little different from those of +</I>><i> package translators (who need to be very precise) and documenters +</I>><i> (who need a different kind of precision and communication) - it would +</I>><i> be good to have marcomm/i18n people who could look for the marketing +</I>><i> nuance as they translated (like it would be good to have documenters +</I>><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, "Cut, I have to ask our marcom team +what to say." + +><i> What you get TV to do for you (we/us) depends entirely on how well +</I>><i> you target your approach to them - same as anything marketing. If you +</I>><i> can give them an angle that will help them sell advertising, they'll +</I>><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. + +><i> What I was wondering about, though, was: suppose we're successful in +</I>><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. + +><i> Marketing is the same whether commercial or otherwise - it's about +</I>><i> getting the message out. First decide what you want it to be; +</I>><i> second, construct it; third, spread it. Simplified, but that's the +</I>><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> |