diff options
Diffstat (limited to 'zarb-ml/mageia-marketing/2011-April/000226.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2011-April/000226.html | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-April/000226.html b/zarb-ml/mageia-marketing/2011-April/000226.html new file mode 100644 index 000000000..be7f1ef0e --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-April/000226.html @@ -0,0 +1,125 @@ +<!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=%3CBANLkTin_4pDPNBmYpVwyNE9QwCAipuKfgQ%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="000225.html"> + <LINK REL="Next" HREF="000227.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=%3CBANLkTin_4pDPNBmYpVwyNE9QwCAipuKfgQ%40mail.gmail.com%3E" + TITLE="[Mageia-marketing] Plan - stuff to do pre Beta 1 release">molch.b at googlemail.com + </A><BR> + <I>Tue Apr 5 21:58:41 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000225.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000227.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#226">[ date ]</a> + <a href="thread.html#226">[ thread ]</a> + <a href="subject.html#226">[ subject ]</a> + <a href="author.html#226">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>All this reads very insightful and I do admit that some of your +thoughts never occurred to me because they were obvious until now. + +2011/4/5 Patricia Fraser <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>>: +><i> +</I>><i> Announcement doesn't just have to be written - it needs to be written +</I>><i> in time to be passed back to the community for filtering, sanity +</I>><i> checking and to find out whether the community likes the way it's +</I>><i> being presented. So, it's at least a 2-step process, maybe more. +</I> +Hmm, how many people you want to ask what has to be written in an +announcement of a new version? Isn't it quite clear what has to be +addressed? + +What is the difference between an announcement to the community and +one going to the outside world? An Announcement has to say + - who announces + - what is tha subject of the announcement + +For a release this means + - version and date (making a point in being on schedule, if so) + - main points like new versions of major software or some innovative +technology or whatever is the main "killer" of the release + - if it's a test release (alpha, beta, rc) say something about the +main focus of this test release + +Then the usual info: + - errata page + - release notes + - download (what and where) + - other informational pages of the project, contact info + +What of these points would you change depending on the target, which +targets, are there different targets at all? See next paragraph. + +><i> Sending oughtn't really to be done until we decide where. Do we stick +</I>><i> with the standards of geek community/social media and hope for the +</I>><i> best; +</I> +We never did. We always tried to send release announcements out to +everybody, geek or not geek (I'm relating to former Mandriva +communication policy, around 2003-2005). As I already wrote, we spread +to the geek targets but also to the general IT crowd, private users +and professionals. Best examples are /., Distrowatch, online and print +magazines. + +><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@ persona +</I>><i> (which could have anyone at the back end; this persona could submit +</I>><i> stories to /., the fb page, send tweets and issue press releases to +</I>><i> all and sundry. Just a thought. +</I> +Yes, detaching press work to some more persons than those who do it +now would be nice - when we will find such persons. But parts of this +is already done by several people. + +><i> What if we get TV interest? Who will handle that and how much backup +</I>><i> will they need/want from marcomm? +</I> +This depends 1. on the occasion (local), 2 on the language, 3. on the +kind of coverage the tv company wants to do (more general, more +technical, etc. + +May be you are coming from the marketing side which results in +different views, I have no relation to marketing in this context (I +mean marketing in a non-profit world). + +-- +wobo +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000225.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI>Next message: <A HREF="000227.html">[Mageia-marketing] Plan - stuff to do pre Beta 1 release +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#226">[ date ]</a> + <a href="thread.html#226">[ thread ]</a> + <a href="subject.html#226">[ subject ]</a> + <a href="author.html#226">[ 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> |