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/000227.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000227.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2011-April/000227.html | 225 |
1 files changed, 225 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-April/000227.html b/zarb-ml/mageia-marketing/2011-April/000227.html new file mode 100644 index 000000000..f14ea0f09 --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-April/000227.html @@ -0,0 +1,225 @@ +<!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=%3C20110405223858.7720e62f%40andromeda.localdomain%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000226.html"> + <LINK REL="Next" HREF="000228.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=%3C20110405223858.7720e62f%40andromeda.localdomain%3E" + TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">trish at thefrasers.org + </A><BR> + <I>Tue Apr 5 22:38:58 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000226.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000228.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#227">[ date ]</a> + <a href="thread.html#227">[ thread ]</a> + <a href="subject.html#227">[ subject ]</a> + <a href="author.html#227">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi Wobo, + +><i> All this reads very insightful and I do admit that some of your +</I>><i> thoughts never occurred to me because they were obvious until now. +</I> +It's a whole nother art form, true. + +><i> 2011/4/5 Patricia Fraser <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>>: +</I>><i> > +</I>><i> > Announcement doesn't just have to be written - it needs to be +</I>><i> > written in time to be passed back to the community for filtering, +</I>><i> > sanity checking and to find out whether the community likes the +</I>><i> > way it's being presented. So, it's at least a 2-step process, +</I>><i> > maybe more. +</I>><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> +One man's clarity is another woman's obscurity... 8-). If we're +representing a community - which is what I think Mageia's marketing +is doing, in part - it's good to know whether or not the community +feels comfortable with the way they're being represented. It's also +good if the community feels that marketing is actually a useful +and valuable part of the community. + +You could check out the last time Yorick and the discuss list had a +conversation, to get a really unmistakable feel for this - I should +probably not need to point out that the shrinkage to not-quite-zero +of the marketing team can be traced back to that conversation. A +pity, because we were full of energy and working hard and well. + +><i> What is the difference between an announcement to the community and +</I>><i> one going to the outside world? An Announcement has to say +</I>><i> - who announces +</I>><i> - what is tha subject of the announcement +</I> +It's all in who you're talking to. If you're talking to a community +of which you're part, you're talking to people who are already on the +inside - there's an existing relationship of a kind, and they know +the context and what's going on and who's who. If you're talking to +people who aren't part of the community yet, you're extending an +invitation. You want to present them with a picture of the community +you're inviting them into (which the community doesn't need), and +give them reasons that might lead them to come investigate joining - +or they might just take the community's output and still not join... +or they might think: no thanks. + +><i> For a release this means +</I>><i> - version and date (making a point in being on schedule, if so) +</I>><i> - main points like new versions of major software or some +</I>><i> innovative technology or whatever is the main "killer" of the +</I>><i> release +</I>><i> - if it's a test release (alpha, beta, rc) say something about the +</I>><i> main focus of this test release +</I>><i> +</I>><i> Then the usual info: +</I>><i> - errata page +</I>><i> - release notes +</I>><i> - download (what and where) +</I>><i> - other informational pages of the project, contact info +</I>><i> +</I>><i> What of these points would you change depending on the target, which +</I>><i> targets, are there different targets at all? See next paragraph. +</I> +It's all in how it's expressed. Suppose you're a person who is on the +fringes of the FLOSS community - you've tried Ubuntu, but there are +so *many* Ubuntu people it's scary to try to join in. You +might or mightn't be a coder; you might also be a potential tester, or +documenter, or... + +Would you feel like joining, if you felt like the announcement was +exclusive, geeky, very plain-ordinary and didn't actually say: we're +looking for people. Please join us - we have room in our community +for people with all sorts of interests and talents. We need you! - +you mightn't. It might all feel just a bit too elite. + +On the other hand, if you're an established coder, this kind of +"soft" approach might make you wonder whether you'd be comfortable +here - do people actually code, or package, or do anything really +interesting to me? or am I going to get stuck being a marketroid? + +On the gripping hand... + +You see what I mean, I bet. + +><i> > Sending oughtn't really to be done until we decide where. Do we +</I>><i> > stick with the standards of geek community/social media and hope +</I>><i> > for the best; +</I>><i> +</I>><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> +Yep. It was moderately successful. It could have been more so; it +could be for us. It all depends what the community wants to have +happen. + +><i> > On points 2 and 3, we could perhaps do with some kind of Mageia +</I>><i> > Persona to send out information - a press@ or communications@ +</I>><i> > persona (which could have anyone at the back end; this persona +</I>><i> > could submit stories to /., the fb page, send tweets and issue +</I>><i> > press releases to all and sundry. Just a thought. +</I>><i> +</I>><i> Yes, detaching press work to some more persons than those who do it +</I>><i> now would be nice - when we will find such persons. But parts of +</I>><i> this is already done by several people. +</I> +I'd separate here the "persona" which could have anyone behind it +from the people who do any communication with people outside the +community (or in it, for that matter, from the "function" of +co-ordinating, writing and disseminating targeted, on-point and +well-constructed information about Mageia, whether graphical or +verbal (or audio, or Braille, or what-have-you). I was positing a +"persona"; I do think the + +><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'd like to see marcomm be multilingual in time - maybe working +together with i18n, which is currently very technically-focussed. The +linguistic needs of marketing are a little different from those of +package translators (who need to be very precise) and documenters +(who need a different kind of precision and communication) - it would +be good to have marcomm/i18n people who could look for the marketing +nuance as they translated (like it would be good to have documenters +ditto). + +What you get TV to do for you (we/us) depends entirely on how well +you target your approach to them - same as anything marketing. If you +can give them an angle that will help them sell advertising, they'll +look at you. So it depends on the kind of program you want to target. + +What I was wondering about, though, was: suppose we're successful in +getting a TV spot? What then? + +><i> May be you are coming from the marketing side which results in +</I>><i> different views, I have no relation to marketing in this context (I +</I>><i> mean marketing in a non-profit world). +</I> +Marketing is the same whether commercial or otherwise - it's about +getting the message out. First decide what you want it to be; +second, construct it; third, spread it. Simplified, but that's the +job. + +Cheers! + +-- +Trish Fraser, JD9R RQ2D +52.4161N,16.9303E +di apr 5 22:16:13 CEST 2011 +GNU/Linux 1997-2010 #283226 counter.li.org +andromeda up 3 hour(s), 56 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/02d882fb/attachment-0001.asc> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000226.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000228.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#227">[ date ]</a> + <a href="thread.html#227">[ thread ]</a> + <a href="subject.html#227">[ subject ]</a> + <a href="author.html#227">[ 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> |