blob: b6d2bdf48d20149bfc6a037943dea08fbc485b85 (
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
|
<!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=%3C201010252017.51375.maarten.vanraes%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001361.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] maintainer groups</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainer%20groups&In-Reply-To=%3C201010252017.51375.maarten.vanraes%40gmail.com%3E"
TITLE="[Mageia-dev] maintainer groups">maarten.vanraes at gmail.com
</A><BR>
<I>Mon Oct 25 20:17:51 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001361.html">[Mageia-dev] maintainer groups
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1360">[ date ]</a>
<a href="thread.html#1360">[ thread ]</a>
<a href="subject.html#1360">[ subject ]</a>
<a href="author.html#1360">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op maandag 25 oktober 2010 19:29:18 schreef Luca Berra:
><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> In this case a package will become unmaintained if no-one is subscribed
</I>><i> to the group.
</I>><i>
</I>><i> we could even use refint_nothing in ldap to redirect
</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">NAME at packages.mageia.org</A> to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">unmaintained at packages.mageia.org</A> when noone
</I>><i> is subscribed to a package.
</I>><i>
</I>><i> Regards,
</I>><i> L.
</I>
I am not averse to the idea.
however i would also like to have a way to check who's on that list (it could
be integrated with <A HREF="http://maint.mageia.org">http://maint.mageia.org</A> ) perhaps we need to abandon the
idea of single maintainer and have "maintainers" (with primary maintainer) ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001361.html">[Mageia-dev] maintainer groups
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1360">[ date ]</a>
<a href="thread.html#1360">[ thread ]</a>
<a href="subject.html#1360">[ subject ]</a>
<a href="author.html#1360">[ 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>
|
