summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110325/003669.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110325/003669.html')
-rw-r--r--zarb-ml/mageia-dev/20110325/003669.html101
1 files changed, 101 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110325/003669.html b/zarb-ml/mageia-dev/20110325/003669.html
new file mode 100644
index 000000000..9ab5af926
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110325/003669.html
@@ -0,0 +1,101 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3CAANLkTimuXj7VGVN1rvw8ZJsJPxaXK0K4_4Jwx_1DmWAL%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="003663.html">
+ <LINK REL="Next" HREF="003662.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)</H1>
+ <B>Romain d'Alverny</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qt3-devel%20needed%20for%20Trinitydesktop%20%28KDE%203.5%0A%09successor%29&In-Reply-To=%3CAANLkTimuXj7VGVN1rvw8ZJsJPxaXK0K4_4Jwx_1DmWAL%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)">rdalverny at gmail.com
+ </A><BR>
+ <I>Fri Mar 25 12:07:28 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="003663.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
+</A></li>
+ <LI>Next message: <A HREF="003662.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3669">[ date ]</a>
+ <a href="thread.html#3669">[ thread ]</a>
+ <a href="subject.html#3669">[ subject ]</a>
+ <a href="author.html#3669">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Fri, Mar 25, 2011 at 11:33, Tux99 &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tux99-mga at uridium.org</A>&gt; wrote:
+&gt;<i> Quote: rdalverny wrote on Fri, 25 March 2011 10:53
+</I>&gt;&gt;<i> If you can't work here by that, or if you are not happy with how
+</I>&gt;&gt;<i> things go here, you are free to discuss this openly with members of
+</I>&gt;&gt;<i> the council or of the board to sort it out.
+</I>&gt;<i>
+</I>&gt;<i> Is there a procedure for that somewhere?
+</I>&gt;<i> I would think such discussions are supposed to happen on the MLs (rather
+</I>&gt;<i> than in private) and given that board/council members posted in this
+</I>&gt;<i> thread I would assume that this discussion is happening here.
+</I>
+That's still a discussion, where views and directions are given. No
+strict decision.
+
+Because I'm a board member does not mean that everything I say in any
+discussion is a de-facto board view/decision (thankfully). It can hint
+about what my views are and how I would express them in a board
+meeting; but it doesn't mean that this will necessarily be what I'll
+vote for either.
+
+&gt;<i> Are you saying that the members of the council that posted here in this
+</I>&gt;<i> thread would give a different answer if I contacted them formally (how?)
+</I>&gt;<i> as members of the council?
+</I>
+Not necessarily, but it can happen.
+
+As a reminder:
+ - council meeting/decisions are made by team representatives, that
+express their team's views;
+ - board meeting/decisions are made by board members, that express
+their own views, with consideration given to the council (hence teams)
+and community views at large + project objectives &amp; means.
+
+That does not prevent individual members of each, out of these
+instances, to express their own views, without these having the force
+of a rule at once (again, thankfully).
+
+&gt;<i> I have no problem co-maintaining the package (with regards to the devel
+</I>&gt;<i> side of it) but I'm not aware of any formal procedure to take maintenance
+</I>&gt;<i> of a package.
+</I>&gt;<i> Is there such a procedure formalized somewhere?
+</I>
+See that with your mentor.
+
+Romain
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="003663.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
+</A></li>
+ <LI>Next message: <A HREF="003662.html">[Mageia-dev] qt3-devel needed for Trinitydesktop (KDE 3.5 successor)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3669">[ date ]</a>
+ <a href="thread.html#3669">[ thread ]</a>
+ <a href="subject.html#3669">[ subject ]</a>
+ <a href="author.html#3669">[ 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>