diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101017/002447.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101017/002447.html | 204 |
1 files changed, 204 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101017/002447.html b/zarb-ml/mageia-discuss/20101017/002447.html new file mode 100644 index 000000000..f4a3e3791 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101017/002447.html @@ -0,0 +1,204 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Mageia logo proposals and selection + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20logo%20proposals%20and%20selection&In-Reply-To=%3C201010172216.17013.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002445.html"> + <LINK REL="Next" HREF="002446.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Mageia logo proposals and selection</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20logo%20proposals%20and%20selection&In-Reply-To=%3C201010172216.17013.stormi%40laposte.net%3E" + TITLE="[Mageia-discuss] Mageia logo proposals and selection">stormi at laposte.net + </A><BR> + <I>Sun Oct 17 22:16:16 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002445.html">[Mageia-discuss] Mageia logo proposals and selection +</A></li> + <LI>Next message: <A HREF="002446.html">[Mageia-discuss] translation of the FAQ from English to Portuguese, +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2447">[ date ]</a> + <a href="thread.html#2447">[ thread ]</a> + <a href="subject.html#2447">[ subject ]</a> + <a href="author.html#2447">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le jeudi 14 octobre 2010 14:40:54, Romain d'Alverny a écrit : +><i> +</I>><i> Hey everyone, +</I>><i> +</I>><i> so, to re-frame a bit things and cool down. +</I>><i> +</I>><i> First, thank you all for this conversation. That shows you care. And +</I>><i> that's great. At times, we may disagree with each other, we may not +</I>><i> manage properly yet how we say things, we may look or be a bit slow or +</I>><i> too fast. But we still can make something together - provided we aim +</I>><i> something in common, we trust and respect each other and we know how +</I>><i> to step down and apologize when needed. +</I>><i> +</I>><i> That's not to say it's easy. It's probably the hardest part. We just +</I>><i> have to take it into account and build our way with it. +</I>><i> +</I>><i> +</I>><i> A quick note the about logo proposals thing. Right, we may pause it, +</I>><i> however everyone started to propose logos even before we talked about +</I>><i> it; so at least we reframe the proposals a bit without making a full +</I>><i> stop. That gives more info to graphic designers at this point and we +</I>><i> can refine the technical specs as well. +</I>><i> +</I>><i> +</I>><i> So... +</I>><i> +</I>><i> #1 Yes, marketing has a say in how we do things in this project. So +</I>><i> does each team. We didn't listed all these teams without intending to +</I>><i> articulate their contributions. +</I>><i> +</I>><i> One of the crucial points in this project is to make everyone respect +</I>><i> and understand each other; knowledge, feelings, opinions, unknowns are +</I>><i> all in the game and we all have to learn how to deal with this to go +</I>><i> forward. +</I>><i> +</I>><i> Marketing, communication (and coordination/inclusion into the project +</I>><i> main decisions) are indeed, in our inherited culture, not quite known +</I>><i> & understood. Each team has its own culture, process. Without all +</I>><i> becoming experts of each others' specialties, we need to understand, +</I>><i> value and trust our reciprocal contributions to benefit the whole +</I>><i> project. +</I>><i> +</I>><i> Of course we are in a Open Source project so it makes some teams more +</I>><i> in technical power of decision (because they don't approve or because +</I>><i> they don't deliver or because there are technical obstacles or...). +</I>><i> That's true and that makes even more important that all participants +</I>><i> acknowledge that we all have +</I>><i> +</I>><i> So whether it takes more time, more discussion, an agreement or it's +</I>><i> up to the Council or the Board to decide in last resort. We will +</I>><i> strive to base our decisions on three things: project mission, values +</I>><i> and facts. Feelings are here as "warning signals" of dissonance and +</I>><i> understood as such; and should be resolved hopefully. +</I>><i> +</I>><i> Disagreements may appear from diverse reasons; one may be that we've +</I>><i> not been specific enough about the direction (because we didn't or +</I>><i> because we still don't know well enough how to be specific enough; +</I>><i> that's something to refine as well). +</I>><i> +</I>><i> +</I>><i> #2. Mageia.org does not target desktop users especially. Well, we do; +</I>><i> as we do target servers and embedded devices. As well. +</I>><i> +</I>><i> Nor does it compete with other Linux distributions or other operating +</I>><i> systems. Yes, we do compete in some way. But we don't see ourselves +</I>><i> like this at first. +</I>><i> +</I>><i> The big difference we expect for Mageia.org is not to compete, but to +</I>><i> become a inter-disciplinary collaboration community of excellence for +</I>><i> free/libre projects; the Mageia Linux distribution is only one (huge, +</I>><i> central and first) "game" in this. As a project, as a platform, as a +</I>><i> product, as a showcase. +</I>><i> +</I>><i> As a hint, two teams were not listed for now, because we thought that +</I>><i> we need to roll out our first working ISO first and because we didn't +</I>><i> explained how their role would fit: ergonomics/users study and +</I>><i> electronics/hardware devices. +</I>><i> +</I>><i> The goal is not only to produce a ~horizontal Linux-based system that +</I>><i> will empower people; it's to create the conditions to build ~vertical +</I>><i> solutions with it, within or from the Mageia.org community. +</I>><i> +</I>><i> Mageia.org is not a commercial project but a community project; where +</I>><i> people/companies will bring in and bring from. Both as users and as +</I>><i> contributors. +</I>><i> +</I>><i> That does not prevent to design it through marketing, but that must be +</I>><i> aligned with the project direction. +</I>><i> +</I>><i> +</I>><i> So, to draw this in perspective now, here are the next big milestones +</I>><i> we have in sight for the coming months. That does not define long term +</I>><i> strategy (which is still buried in the announcement and in the +</I>><i> vision/mission statements being worked on) but I guess it will help: +</I>><i> +</I>><i> 1. releasing a test drive ISO before the end of November; this is to +</I>><i> test drive four things: +</I>><i> * packaging/translation/build system as a whole, +</I>><i> * community council and teams work & coordination, +</I>><i> * final product stability, +</I>><i> * concurrent discussions for future plans. +</I>><i> +</I>><i> 2. having December to cool down and prepare the next run; having end +</I>><i> of December free of any stress in this regard; +</I>><i> +</I>><i> 3. preparing coming FOSDEM in February 2011; where we shall meet more +</I>><i> people to discuss future and hot topics. +</I>><i> +</I>><i> Concurrent to these, Mageia.org community must form and learn on itself. +</I>><i> +</I>><i> For the marketing team, for instance, the first step could to market +</I>><i> the project itself toward people that will _contribute to it_, first. +</I>><i> +</I>><i> That's who we want to work with and who we want to be in love with the +</I>><i> product, the technology, the project and the processes first. That's +</I>><i> who we want to care about first. Then we will have to see how what we +</I>><i> love can be a fit for other people. +</I>><i> +</I>><i> (and no, that doesn't exclude all users, but only users that don't +</I>><i> expect to contribute to the project directly) +</I>><i> +</I>><i> That helps in three ways: +</I>><i> - helping refine the whole project vision as whole and advocate it; +</I>><i> - help contributors get a firmer grasp on who they are, and what +</I>><i> they're going to build; +</I>><i> - inform users community of what it may be going to look like. +</I>><i> +</I>><i> This, with time, will help to discuss targets with more data and more +</I>><i> perspective. For everyone. Notwithstanding that other teams have quite +</I>><i> a lot of work as well and may need to advocate it as well. +</I>><i> +</I>><i> Yes, that's a short roadmap. We can expect to have a larger one later. +</I>><i> But that's what we have to focus on at this time. +</I>><i> +</I>><i> We will dig into some of these points in dedicated meetings in the +</I>><i> next days (marketing/communication, roadmap and weekly progress). +</I>><i> +</I>><i> +</I>><i> Cheers, +</I>><i> +</I>><i> Romain +</I>><i> +</I>><i> +</I> +This somewhat buried announce could be given more visibility in its own thread or as a forum message, couldn't it ? + +Regards + +Samuel +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002445.html">[Mageia-discuss] Mageia logo proposals and selection +</A></li> + <LI>Next message: <A HREF="002446.html">[Mageia-discuss] translation of the FAQ from English to Portuguese, +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2447">[ date ]</a> + <a href="thread.html#2447">[ thread ]</a> + <a href="subject.html#2447">[ subject ]</a> + <a href="author.html#2447">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |