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/20110421/004113.html | 103 ++++++++++++++++++++++++++++++++ 1 file changed, 103 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110421/004113.html (limited to 'zarb-ml/mageia-dev/20110421/004113.html') diff --git a/zarb-ml/mageia-dev/20110421/004113.html b/zarb-ml/mageia-dev/20110421/004113.html new file mode 100644 index 000000000..8f9534c7f --- /dev/null +++ b/zarb-ml/mageia-dev/20110421/004113.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] Maintainers policy + + + + + + + + + +

[Mageia-dev] Maintainers policy

+ Michael Scherer + misc at zarb.org +
+ Thu Apr 21 00:49:45 CEST 2011 +

+
+ +
Le mercredi 13 avril 2011 à 23:33 +0200, Anne nicolas a écrit :
+> Hi there
+> 
+> Following tonight's meeting, we will start one week discussion about
+> maintainers policy. Some questions to be discussed:
+> 
+> - shall we have ACL's on svn, submits?
+> - what about having co-maintenership or teams? How shall we manage this?
+> - what about sensitive packages ?
+> ...
+> 
+> Pleas make any comments and proposals we could discus to build it.
+> Final decisions will be taken during next packagers meeting (20th of
+> april)
+
+So following tnight meeting 
+
+I created this page :
+http://mageia.org/wiki/doku.php?id=packagers_policy_discussion
+
+Please do not modify it without discussing here the subject, the goal is
+to track what was discussed, not to write proposal or to discuss on the
+page.
+
+Also, while reading again the log, I was reminded about the system of
+NMU in debian :
+http://www.debian.org/doc/developers-reference/pkgs.html#nmu
+
+The way is work is the following. A debian developer decide to do a NMU,
+send the package in a special queue and the package will be uploaded
+after X days, with X decided by the person who do the NMU.
+
+Maintainer can then decide to stop the NMU or to let it go, or maybe to
+push it.
+
+So basically, that would fulfill a requirement , ie that someone that
+want to prevent a upload could do it if he disagree. 
+
+One problem is that we are much more fluid and reactive than Debian for
+the moment, and I am not sure we operate on the same timescale. Also, a
+NMU for a rpm when the maintainer is busy would not achieve much ( on
+the other hand, submit restriction wouldn't either ).
+
+I am not sure if we can do that, but that's a potential idea to explore.
+
+
+-- 
+Michael Scherer
+
+
+ + + +
+

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