From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101130/001558.html | 91 +++++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101130/001558.html (limited to 'zarb-ml/mageia-dev/20101130/001558.html') diff --git a/zarb-ml/mageia-dev/20101130/001558.html b/zarb-ml/mageia-dev/20101130/001558.html new file mode 100644 index 000000000..a95b19704 --- /dev/null +++ b/zarb-ml/mageia-dev/20101130/001558.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] Support policy + + + + + + + + + +

[Mageia-dev] Support policy

+ Samuel Verschelde + stormi at laposte.net +
+ Tue Nov 30 16:32:33 CET 2010 +

+
+ +
+Le mardi 30 novembre 2010 16:13:25, Michael Scherer a écrit :
+> 
+> Le mardi 30 novembre 2010 à 13:31 +0100, Samuel Verschelde a écrit :
+> > Hi, 
+> > 
+> > I would like to discuss the support policy for Mageia.
+> > 
+> > It would be interesting to know (or decide) where Mageia is heading, given our limited resources :
+> 
+> can you first explain what are our ressources so you can explain how
+> limited you think they are ?
+> 
+> So to me, the goal should be first to aim for quality, and then add more
+> packages, as I said, in a sustainable way ( ie no mass import without
+> being first sure that we can manage them, no rotting rpms because people
+> no longer care ).
+> 
+> Which mean option 1.
+
+I may have mistaken, but from what I understood, you explained us why option 1 is better than option 2, which is what I already said in my post.
+
+So why not option 3, which in my opinion is even better than option 1, because :
+- every package must have a maintainer like in option 1
+- QA Team focuses on a subset to provide even better support for them
+
+Regards
+
+Samuel
+
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1