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

[Mageia-dev] Maintainers policy

+ Funda Wang + fundawang at gmail.com +
+ Thu Apr 14 11:17:31 CEST 2011 +

+
+ +
2011/4/14 Anne nicolas <ennael at mageia.org>:
+> 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)
+
+If we are about to stick to subversion, then only maintainer could
+submit certain package. Of course, if package don't have maintainer,
+then anybody could submit it.
+
+If we will turn to git, then everybody could have his own clone, but
+the merge request should be reviewed by maintainer. After merging,
+anybody could submit it. The problem is that, we couldn't assure every
+package have a valid maintainer.
+
+ + + + + + + +
+

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