diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110416/004009.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110416/004009.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110416/004009.html b/zarb-ml/mageia-dev/20110416/004009.html new file mode 100644 index 000000000..23a347f1f --- /dev/null +++ b/zarb-ml/mageia-dev/20110416/004009.html @@ -0,0 +1,116 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Maintainers policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Maintainers%20policy&In-Reply-To=%3Calpine.LMD.2.02.1104151711390.16564%40zem.cjw.nep%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="004014.html"> + <LINK REL="Next" HREF="004010.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Maintainers policy</H1> + <B>Christiaan Welvaart</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Maintainers%20policy&In-Reply-To=%3Calpine.LMD.2.02.1104151711390.16564%40zem.cjw.nep%3E" + TITLE="[Mageia-dev] Maintainers policy">cjw at daneel.dyndns.org + </A><BR> + <I>Sat Apr 16 15:30:55 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="004014.html">[Mageia-dev] Meeting for secteam start +</A></li> + <LI>Next message: <A HREF="004010.html">[Mageia-dev] Seamonkey package +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4009">[ date ]</a> + <a href="thread.html#4009">[ thread ]</a> + <a href="subject.html#4009">[ subject ]</a> + <a href="author.html#4009">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 13 Apr 2011, Anne nicolas wrote: + +><i> Following tonight's meeting, we will start one week discussion about +</I>><i> maintainers policy. Some questions to be discussed: +</I>><i> +</I>><i> - shall we have ACL's on svn, submits? +</I>><i> - what about having co-maintenership or teams? How shall we manage this? +</I>><i> - what about sensitive packages ? +</I>><i> ... +</I>><i> +</I>><i> Pleas make any comments and proposals we could discus to build it. +</I>><i> Final decisions will be taken during next packagers meeting (20th of +</I>><i> april) +</I> +There seem to be two issues here: + +1. A maintainer database, with rules for updating the db + This does not have to change package submission or svn access, + but can be used for bug assignment, mailing package check reports and + package svn commit logs, etc. + +2. Restrictions on: + a) maintainer db modifications + b) package submission and/or svn access, based on the contents of the + maintainer db + +Of course those 2 issues are related: any upload restrictions allowed by +policy must be supported in the maintainer db. We don't need to implement +everying at once, however. A maintainer db without upload restrictions +will already be a big improvement over the current situation. + + +There are 2 kinds of groups: + maintainer groups = several people listed as maintainer for one package + package groups = several packages that are maintained as if they were a + single package, so they always have the same list of + maintainers + +IMHO both features should be supported by the maintainer database: + - Restricted packages (if allowed) must have at least 2 maintainers. + This should make it less likely that change requests are simply + ignored. + - Maintainer groups can also be useful for unrestricted packages, + e.g. to divide the work on a large source package. + - Package groups are likely needed for some software systems like gnome + and X11 that are split into many smaller source packages. + +Here's a partial proposal for phase 1/unrestricted packages: + +- anyone can register as maintainer for a (source) package +- maintainers can unregister at any time +- the "oldest" maintainer (first one registered) is primary maintainer, + officially responsible for the package +- package groups are defined by the project (is there any other way?) +- the maintainer db redirects requests on a package in a group to the + package group (with an error msg?) + + + Christiaan +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="004014.html">[Mageia-dev] Meeting for secteam start +</A></li> + <LI>Next message: <A HREF="004010.html">[Mageia-dev] Seamonkey package +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4009">[ date ]</a> + <a href="thread.html#4009">[ thread ]</a> + <a href="subject.html#4009">[ subject ]</a> + <a href="author.html#4009">[ 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> |