summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101025/001361.html
blob: 8a6652a09b9c6a4adda7cfe74c745000bd75ea48 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
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 &#233;crit :
&gt;<i> On 25 October 2010 19:44, Michael Scherer&lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt;  wrote:
</I>&gt;<i>    
</I>&gt;&gt;<i> Le lundi 25 octobre 2010 &#224; 19:29 +0200, Luca Berra a &#233;crit :
</I>&gt;&gt;<i>      
</I>&gt;&gt;&gt;<i> this is a suggestion i already made with mandriva but it landed nowhere,
</I>&gt;&gt;&gt;<i> let's try again.
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> At the moment we have 1to1 relationship in all tools between maintainer
</I>&gt;&gt;&gt;<i> and package. But for some packages we have more than one people willing
</I>&gt;&gt;&gt;<i> to work on that package. Besides, for some critical package it may be
</I>&gt;&gt;&gt;<i> useful having more than one person responsible for it.
</I>&gt;&gt;&gt;<i> Also someone might be interested in helping on package foo, but feels
</I>&gt;&gt;&gt;<i> too much inexperienced to take full reponsability for it. Peer review is
</I>&gt;&gt;&gt;<i> important.
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> The idea is not associating a package with a single maintainer, but
</I>&gt;&gt;&gt;<i> associate each package to a maintainer-group, say
</I>&gt;&gt;&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">NAME at packages.mageia.org</A>, and let maintainers subscribe to package
</I>&gt;&gt;&gt;<i> maintenance.
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> this would result that in case a ticket is opened in bugzilla vs
</I>&gt;&gt;&gt;<i> package, all interested parties would be notified, and start working on
</I>&gt;&gt;&gt;<i> a solution. (this might require a bit of coordination, but maybe just
</I>&gt;&gt;&gt;<i> assigning the bug to a real person is enough to note someone is taking
</I>&gt;&gt;&gt;<i> care of the problem)
</I>&gt;&gt;&gt;<i>        
</I>&gt;&gt;<i> +1 to the idea.
</I>&gt;&gt;<i> I just wonder how it articulate on bugzilla side ( ie, we should try to
</I>&gt;&gt;<i> avoid having a patch on bugzilla side, as this is usually causing
</I>&gt;&gt;<i> trouble ).
</I>&gt;&gt;<i> Ie, if I want to take care of a bug report, I would likely assign it to
</I>&gt;&gt;<i> me, no ?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Wouldn't it better to use cc for that ?
</I>&gt;&gt;<i> --
</I>&gt;&gt;<i> Michael Scherer
</I>&gt;&gt;<i>
</I>&gt;&gt;<i>
</I>&gt;&gt;<i>      
</I>&gt;<i> Well, if a maintainer changes to status to ASSIGNED, we can assume
</I>&gt;<i> he's working on it.
</I>&gt;<i>
</I>&gt;<i> QA team, lately, had a sort of a rule, when one of them was working on
</I>&gt;<i> a bug he'd post to the report to say so so as not to duplicate work;
</I>&gt;<i> the same was with sec team. That's a good way IMHO.
</I>&gt;<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>