diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20100924/000186.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20100924/000186.html | 125 |
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20100924/000186.html b/zarb-ml/mageia-dev/20100924/000186.html new file mode 100644 index 000000000..e60e3ed52 --- /dev/null +++ b/zarb-ml/mageia-dev/20100924/000186.html @@ -0,0 +1,125 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Art, Logo and Branding + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Art%2C%20Logo%20and%20Branding&In-Reply-To=%3Ci7gkcg%24leg%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="000187.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Art, Logo and Branding</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Art%2C%20Logo%20and%20Branding&In-Reply-To=%3Ci7gkcg%24leg%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Art, Logo and Branding">marc at marcpare.com + </A><BR> + <I>Fri Sep 24 00:29:35 CEST 2010</I> + <P><UL> + + <LI>Next message: <A HREF="000187.html">[Mageia-dev] Art, Logo and Branding +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#186">[ date ]</a> + <a href="thread.html#186">[ thread ]</a> + <a href="subject.html#186">[ subject ]</a> + <a href="author.html#186">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-09-23 17:58, Michael Scherer a écrit : +><i> Le jeudi 23 septembre 2010 à 16:17 -0400, Marc Paré a écrit : +</I>>><i> I think in the grand scheme of things, we should all acknowledge that +</I>>><i> should the name "Mageia" not work, that a name change would be a +</I>>><i> possibility, just as a logo change is still a possibility. We have seen +</I>>><i> this from many OSS firms who went through this process. +</I>><i> +</I>><i> How do you assess that it is the name that do not work and that's not +</I>><i> anything else ? +</I>><i> +</I>>><i> We should be careful in making the distro too "cottagey" or "home grown" +</I>>><i> in looks and flavour. I would suggest that the long term vision for the +</I>>><i> distro also include a commercial aspect. There should be a community +</I>>><i> driven distro and a commercial distro (read server). +</I>><i> +</I>><i> I fear that this scheme does look like too much the one that caused +</I>><i> problem in the past within Mandriva community, with contradictions +</I>><i> between the community nature and the more commercial version. +</I>><i> +</I>><i> How would you ensure that the community version will not be seen as a +</I>><i> cheap version of the commercial one ? How would you prevent this idea +</I>><i> from destroying again the community like it did by the past ? +</I>><i> +</I>><i> If theses questions are not solved, I think all attempts to redo the +</I>><i> mistakes of the past are bound to recreate the failures of the past. +</I>><i> And I think that none of us think that's a desirable outcome. +</I>><i> +</I>><i> All people who I asked the question said that the only solution is to +</I>><i> have 2 different names and brandings. +</I>><i> Redhat do it, and it work fine from them. +</I>><i> Novell do it, and it work fine. +</I>><i> Canonical do it ( to a lesser extend , since there was +</I>><i> <A HREF="https://bugs.launchpad.net/ubuntuone-servers/+bug/375345">https://bugs.launchpad.net/ubuntuone-servers/+bug/375345</A> ), and it work +</I>><i> fine. +</I>><i> +</I>><i> Even debian based distro used a different name ( progeny, etc ). +</I>><i> +</I>><i> We didn't for Mandriva, and so started the confusion between the +</I>><i> company, the distribution and the community. And so people didn't +</I>><i> contribute because it was a business, and the idea that "updates were +</I>><i> not free" stick around for a long time because it was hard to explain to +</I>><i> people the different concept +</I>><i> +</I>><i> So if there is a business or commercial version, I think this would +</I>><i> requires a different name and branding. Using the association name for +</I>><i> that would not be right, in my opinion. +</I>><i> +</I> +Good points. + +However, we are lucky in that are just at the start of organizing the +community and it gives us the luxury of trying to plan a rational growth +path for the distro. + +Mageia is starting off from the community end of things. We should then +be looking at models where communities have grown from that end then. A +good example that I can think of is the Moodle application where it +started out as a community driven project and its commercial end is now +doing quite well. The planning for the commercial end came a little +after the Moodle community became popular and the commercial end +followed. Their logo and name are quite known now in educational +circles, both on the community OSS side and the corporate side. This +assures the community a little more financial independence with support +coming from the corporate side. + +It may be to our benefit to see if some similar growth models could be +applied to Mageia. + + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="000187.html">[Mageia-dev] Art, Logo and Branding +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#186">[ date ]</a> + <a href="thread.html#186">[ thread ]</a> + <a href="subject.html#186">[ subject ]</a> + <a href="author.html#186">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |