summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20101004/002134.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20101004/002134.html')
-rw-r--r--zarb-ml/mageia-discuss/20101004/002134.html202
1 files changed, 202 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101004/002134.html b/zarb-ml/mageia-discuss/20101004/002134.html
new file mode 100644
index 000000000..e818389df
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20101004/002134.html
@@ -0,0 +1,202 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] Mageia governance model draft
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20governance%20model%20draft&In-Reply-To=%3CAANLkTikm6jXG2eE%3D02%2BLPhHi60USnGBd9GUEsMs9%2BXV4%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="002132.html">
+ <LINK REL="Next" HREF="002154.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] Mageia governance model draft</H1>
+ <B>Romain d'Alverny</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Mageia%20governance%20model%20draft&In-Reply-To=%3CAANLkTikm6jXG2eE%3D02%2BLPhHi60USnGBd9GUEsMs9%2BXV4%40mail.gmail.com%3E"
+ TITLE="[Mageia-discuss] Mageia governance model draft">rdalverny at gmail.com
+ </A><BR>
+ <I>Mon Oct 4 15:26:39 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="002132.html">[Mageia-discuss] Wish List
+</A></li>
+ <LI>Next message: <A HREF="002154.html">[Mageia-discuss] Mageia governance model draft
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2134">[ date ]</a>
+ <a href="thread.html#2134">[ thread ]</a>
+ <a href="subject.html#2134">[ subject ]</a>
+ <a href="author.html#2134">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Hi everyone,
+
+it's been two weeks now since we announced Mageia and, again, thank you.
+
+We are still amazed by the amount of contributions, discussions and enthusiasm
+here. We hope it will enable us to build a strong, great Linux distribution
+that benefits users, upstream and adjacent projects.
+
+As well as working on/setting up the legal side, founding docs, the very first
+pieces of infrastructure, meeting people, we have discussed and thought about
+the governance model for the project. Here is the result.
+
+It is not a rigid structure and we are definitely open to comments and
+adjustements as things go (hence the &quot;draft&quot;); but we do mean to start
+with this schema for the first year.
+
+As stated in the announcement, this model has two targets:
+
+ * ensure that the project direction &amp; management is done by volunteer people
+ that are recognized by their peers as having valuable role and insight
+ into the project (no 3rd party take-over);
+
+ * enable the project to learn and improve on itself.
+
+
+Of course, that only won't prevent heated discussions, decisions to be taken
+(and justified) or failure - all this construction will only work because of
+reciprocal trust, goodwill and desire of all participants, plus a working schema
+for discussion, decision and conflict resolution.
+
+To summarize, the whole project is organized in several groups:
+
+ * Mageia project Teams (developers, packagers, docs, translators, designers,
+ etc. sponsored/mentored from the whole community),
+
+ * Mageia project Community Council (people elected from each team),
+
+ * Mageia association members (basically, founding association members &amp; past
+ members of the council who can be on and elect the board),
+
+ * Mageia project &amp; association Board (direction of the project).
+
+
+Because things are organized this way does not mean that there is a strict
+hierarchical relationship between entities. This governance model is here
+to coordinate the work of everyone and identify who is in charge of what.
+
+Here is the doc: <A HREF="http://mageia.org/wiki/doku.php?id=org">http://mageia.org/wiki/doku.php?id=org</A>
+
+
+Now, having read all this, beyond other discussion, here is a little point
+about Teams, where actually everything starts; here are teams we have already
+on the wiki:
+ * Packaging team
+ * Security team
+ * Developers team
+ * Documentation team
+ * Translation team
+ * QA team
+ * Triage team
+ * Users communities management and representation team; this one is pretty
+ big so it may need to organize into three dedicated groups:
+ * forums
+ * mailing-lists
+ * IRC
+ * local groups
+ * Web team
+ * Designers
+ * Marketing team
+ * Communication team
+
+
+That makes for a lot of people; about 300 at this time if we count everyone
+who enlisted.
+
+Now, this is practically a bit odd for a start, of course, since no team exist
+formally yet. So we will go to freeze today's list of members of each team
+and those will be the first round teams.
+
+Each team will have to decide on itself, for the next two weeks:
+
+ * what is in the mentoring program exactly (for instance, Packaging team
+ has to take into account alternative packaging practices and explain
+ why/how it is expected to work in Mageia and how it could evolve);
+
+ * how/who to sponsor (don't sponsor just a good friend, but someone who
+ can bring great things to your team and the project);
+
+ * for their Council Representative, Team leader and Team backup;
+
+ * for a list of ranked work topics to submit to the Council and Board
+ for the project and for the first distribution release (we will
+ announce Board's plans about that a bit later); these will be sorted
+ through for the long-term roadmap and will help to get a picture
+ of what we could do; see see <A HREF="http://en.wikipedia.org/wiki/MoSCoW_Method">http://en.wikipedia.org/wiki/MoSCoW_Method</A>
+ for simple priorities;
+
+ * propose/ask the tools they would need to explore/use to work collectively
+ (in- and cross-teams; see at the end of this post).
+
+
+Ok... This is already a LOT of information. We may post more specific
+discussion about:
+ * Community Council and Board roles, Board nomination and communication
+ channels (all lists are not active for now);
+ * Teams sponsoring/mentoring process, election and constitution process;
+ * tools; again, this is a per-team definition but we can certainly share
+ that;
+ * something else?
+
+Your input is welcome and PLEASE:
+ * quote the original message,
+ * use text-only,
+ * be specific in your answers.
+
+Cheers,
+
+Romain
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="002132.html">[Mageia-discuss] Wish List
+</A></li>
+ <LI>Next message: <A HREF="002154.html">[Mageia-discuss] Mageia governance model draft
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#2134">[ date ]</a>
+ <a href="thread.html#2134">[ thread ]</a>
+ <a href="subject.html#2134">[ subject ]</a>
+ <a href="author.html#2134">[ 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>