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-March/000181.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-March/000181.html')
| -rw-r--r-- | zarb-ml/mageia-marketing/2011-March/000181.html | 145 |
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-marketing/2011-March/000181.html b/zarb-ml/mageia-marketing/2011-March/000181.html new file mode 100644 index 000000000..81ecfe528 --- /dev/null +++ b/zarb-ml/mageia-marketing/2011-March/000181.html @@ -0,0 +1,145 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-marketing] Mageia product naming/scoping + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Mageia%20product%20naming/scoping&In-Reply-To=%3CAANLkTimTi2wZa69qA8EM11aD6rt8OJ5yPLjBt%2B6cM5ET%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="000180.html"> + <LINK REL="Next" HREF="000182.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-marketing] Mageia product naming/scoping</H1> + <B>Romain d'Alverny</B> + <A HREF="mailto:mageia-marketing%40mageia.org?Subject=Re%3A%20%5BMageia-marketing%5D%20Mageia%20product%20naming/scoping&In-Reply-To=%3CAANLkTimTi2wZa69qA8EM11aD6rt8OJ5yPLjBt%2B6cM5ET%40mail.gmail.com%3E" + TITLE="[Mageia-marketing] Mageia product naming/scoping">rdalverny at gmail.com + </A><BR> + <I>Wed Mar 16 21:33:40 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000180.html">[Mageia-marketing] Mageia product naming/scoping +</A></li> + <LI>Next message: <A HREF="000182.html">[Mageia-marketing] 2011/week 11 meeting: websites, products, comm plan, action +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#181">[ date ]</a> + <a href="thread.html#181">[ thread ]</a> + <a href="subject.html#181">[ subject ]</a> + <a href="author.html#181">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi Patricia, + +and thanks a lot for your insights. + +On Wed, Mar 16, 2011 at 20:19, Patricia Fraser <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-marketing">trish at thefrasers.org</A>> wrote: +><i> I'm conflating answers to package naming and website stuff together, +</I>><i> because I think the two have some cross-over. +</I> +To some extent. But the product ought to live without this website, +and the website is not only about the final (but about the process to +get there, and go beyond). At some point, we may even consider to have +a dedicated website for the product, but we're not there yet. + +><i> One of the reasons a person new to Mageia will visit the site is to +</I>><i> find out about Mageia and its various flavours/iterations, and +</I>><i> whether they fit the visitor's use case, or appeal to their wish to +</I>><i> join a project. So, whatever we call the "products" <shudder>, we +</I>><i> need to communicate about them really, really effectively. +</I> +Totally, yes. + +>><i> Goal of this topic is double: +</I>>><i>  * study/propose/find a name for the product as such (Mageia? Mageia +</I>>><i> something? something?) +</I>><i> +</I>><i> Skirting around this for the moment, except to say that I favour the +</I>><i> style Mageia {flavour} {n}; can our names follow the Mageia-Cauldron +</I>><i> lineage maybe? Alchemy for the one where you have to roll your own +</I>><i> kernel... 8-) I'm afraid I don't find the explication on the wiki +</I>><i> very helpful - are we going to have flavours, for different use +</I>><i> cases, or just what is it we're naming? +</I> +I may not have been very specific on what is meant by a "use case" +here. It's not about targetting a gamers group, or a developr group, +or a hitchhikers group, etc. It's more about how experienced one is +(not at all, or to some extent) and how the linux distribution is made +available for testing/installation: install DVD, live/install CD or +USB key, netboot install, etc. + +This, because at this point at least, the only kind of "flavour" we +would have is this: how to download and use the very same product +(that is, the same tree of packages, available either through a +physical medium, either through the network). + +Well, that's true for the ISO meant to use live or install the system. +It's a little bit different for the pluggable storage (USB key for +now) that provides a different experience: you can use it live, +install it _and_ have a persistent storage for your data. + +So my naming question, to frame it better (and feel free to indicate +me how/where to make this more clear on the web page) is more about: + * how do we name those different access/install experiences? the same +(Mageia) + a casual description (DVD, LiveCD, netinstall, minimal, +mobile)? (I favour this, but) or more inspirational names? + * and how do we frame them to the new visitor that wants to "download +Mageia" ? + +><i> Whatever "products" we have on our list (I hate that word. Can we +</I>><i> find another, less commercial generic term for the various flavours +</I>><i> of Mageia?), +</I> +We could, but "product" is the result of some "production". Nothing +commercial in this. "artefact" wouldn't qualify I guess. No particular +idea here. + +><i>        - most of this info should be available from the packagers - +</I>><i>          can we ask them to give the comms team a heads-up in some +</I>><i>          way when they add/change things, so information on flavour +</I>><i>          pages can be updated? +</I> +That would rely on checking each package changelog and getting in +touch with the packagers. I don't know how to put some incentive (or +how to integrate these changelogs) as to make this more easily +informative. I believe mageia-app-db work done by Stormi can help a +lot here. + +><i> - have a progression from less to more technical/detailed info - links +</I>><i>  to package info, for instance, especially the Drak packages and +</I>><i>  their derivatives and other Mageia/Mandriva specialist packages - +</I>><i>  I've had msec installed for umpty years and I still haven't ever +</I>><i>  found decent documentation! +</I> +Yes! To find the right balance, and delivering it as a useful, clear, +to the point doc, still attractive and welcoming. We can do it. We can +do it. There's a lot to learn from Rails and similar modern web dev +tools online documentation that is far ahead. + + +Romain +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000180.html">[Mageia-marketing] Mageia product naming/scoping +</A></li> + <LI>Next message: <A HREF="000182.html">[Mageia-marketing] 2011/week 11 meeting: websites, products, comm plan, action +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#181">[ date ]</a> + <a href="thread.html#181">[ thread ]</a> + <a href="subject.html#181">[ subject ]</a> + <a href="author.html#181">[ 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> |