diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20101025/001361.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20101025/001361.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101025/001361.html | 106 |
1 files changed, 106 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101025/001361.html b/zarb-ml/mageia-dev/20101025/001361.html new file mode 100644 index 000000000..8a6652a09 --- /dev/null +++ b/zarb-ml/mageia-dev/20101025/001361.html @@ -0,0 +1,106 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] maintainer groups + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainer%20groups&In-Reply-To=%3C4CC5EA1A.6030904%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001359.html"> + <LINK REL="Next" HREF="001360.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] maintainer groups</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainer%20groups&In-Reply-To=%3C4CC5EA1A.6030904%40laposte.net%3E" + TITLE="[Mageia-dev] maintainer groups">andr55 at laposte.net + </A><BR> + <I>Mon Oct 25 22:35:38 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001359.html">[Mageia-dev] maintainer groups +</A></li> + <LI>Next message: <A HREF="001360.html">[Mageia-dev] maintainer groups +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1361">[ date ]</a> + <a href="thread.html#1361">[ thread ]</a> + <a href="subject.html#1361">[ subject ]</a> + <a href="author.html#1361">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ahmad Samir a écrit : +><i> On 25 October 2010 19:44, Michael Scherer<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>><i> +</I>>><i> Le lundi 25 octobre 2010 à 19:29 +0200, Luca Berra a écrit : +</I>>><i> +</I>>>><i> this is a suggestion i already made with mandriva but it landed nowhere, +</I>>>><i> let's try again. +</I>>>><i> +</I>>>><i> At the moment we have 1to1 relationship in all tools between maintainer +</I>>>><i> and package. But for some packages we have more than one people willing +</I>>>><i> to work on that package. Besides, for some critical package it may be +</I>>>><i> useful having more than one person responsible for it. +</I>>>><i> Also someone might be interested in helping on package foo, but feels +</I>>>><i> too much inexperienced to take full reponsability for it. Peer review is +</I>>>><i> important. +</I>>>><i> +</I>>>><i> The idea is not associating a package with a single maintainer, but +</I>>>><i> associate each package to a maintainer-group, say +</I>>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">NAME at packages.mageia.org</A>, and let maintainers subscribe to package +</I>>>><i> maintenance. +</I>>>><i> +</I>>>><i> this would result that in case a ticket is opened in bugzilla vs +</I>>>><i> package, all interested parties would be notified, and start working on +</I>>>><i> a solution. (this might require a bit of coordination, but maybe just +</I>>>><i> assigning the bug to a real person is enough to note someone is taking +</I>>>><i> care of the problem) +</I>>>><i> +</I>>><i> +1 to the idea. +</I>>><i> I just wonder how it articulate on bugzilla side ( ie, we should try to +</I>>><i> avoid having a patch on bugzilla side, as this is usually causing +</I>>><i> trouble ). +</I>>><i> Ie, if I want to take care of a bug report, I would likely assign it to +</I>>><i> me, no ? +</I>>><i> +</I>>><i> Wouldn't it better to use cc for that ? +</I>>><i> -- +</I>>><i> Michael Scherer +</I>>><i> +</I>>><i> +</I>>><i> +</I>><i> Well, if a maintainer changes to status to ASSIGNED, we can assume +</I>><i> he's working on it. +</I>><i> +</I>><i> QA team, lately, had a sort of a rule, when one of them was working on +</I>><i> a bug he'd post to the report to say so so as not to duplicate work; +</I>><i> the same was with sec team. That's a good way IMHO. +</I>><i> +</I> +Good idea. This approach is also used by transators in various projects. +It also might be a good to have a designated principle maintainer, in +the maintainer group for a package. +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001359.html">[Mageia-dev] maintainer groups +</A></li> + <LI>Next message: <A HREF="001360.html">[Mageia-dev] maintainer groups +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1361">[ date ]</a> + <a href="thread.html#1361">[ thread ]</a> + <a href="subject.html#1361">[ subject ]</a> + <a href="author.html#1361">[ 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> |