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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%0A%09misc%20unleashes%20CERBERUS%20%21&In-Reply-To=%3C201109162227.23590.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008149.html">
<LINK REL="Next" HREF="008164.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%0A%09misc%20unleashes%20CERBERUS%20%21&In-Reply-To=%3C201109162227.23590.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !">stormi at laposte.net
</A><BR>
<I>Fri Sep 16 22:27:23 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008149.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
</A></li>
<LI>Next message: <A HREF="008164.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8162">[ date ]</a>
<a href="thread.html#8162">[ thread ]</a>
<a href="subject.html#8162">[ subject ]</a>
<a href="author.html#8162">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le vendredi 16 septembre 2011 18:48:20, Colin Guthrie a écrit :
><i> 'Twas brillig, and Michael Scherer at 16/09/11 14:39 did gyre and gimble:
</I>><i> > Le vendredi 16 septembre 2011 à 12:44 +0200, Guillaume Rousse a écrit :
</I>><i> >> Le 16/09/2011 11:47, Sander Lepik a écrit :
</I>><i> >>> 15.09.2011 21:43, Maarten Vanraes kirjutas:
</I>><i> >>>> I have a script ready to set the last comittor (that's a full
</I>><i> >>>> packager) as
</I>><i> >>>> maintainer. perhaps it can be activated before the GREAT PURGE.
</I>><i> >>>
</I>><i> >>> That's not so good idea. What we maybe can do is that we send out a
</I>><i> >>> warning that if you commit to a package after the warning and the
</I>><i> >>> package has no maintainer yet then you become one. So that people would
</I>><i> >>> first check what they get on their name. Many packages were imported by
</I>><i> >>> Anne, i'm not sure that she's going to maintain them all. :)
</I>><i> >>>
</I>><i> >>> I would do something like that:
</I>><i> >>> 2 months of warning period, if you touch package that has no maintainer
</I>><i> >>> you become its maintainer. After 2 months we start dropping those
</I>><i> >>> packages that have still no maintainer.
</I>><i> >>
</I>><i> >> This whole idea of 'touch a package, become its maintainer' assumes than
</I>><i> >> anyone modifying a package has an obvious interest in it.
</I>><i> >
</I>><i> > Then we can increase the heuristic, like "upgrade to a new version", or
</I>><i> > "do several commit on it". Someone upgrading a package either :
</I>><i> > - is interested in it for the package ( and thus would be a maintainer )
</I>><i> > - is interested into having it upgraded for using on another package
</I>><i> > ( and thus, as a user of the rpm for another rpm, has a interest to not
</I>><i> > make it disappear ).
</I>><i> >
</I>><i> > And i doubt that someone would do X commit on a rpm if not interested in
</I>><i> > it.
</I>><i>
</I>><i> Are heuristics a good idea? How about just making mgarepo ask you if you
</I>><i> want to become the maintainer with a Y/n option (Y being default) when
</I>><i> you call submit on an unmaintained package.
</I>><i>
</I>><i> This should be simple enough that people genuinely maintaining it can
</I>><i> just hit return and also easy enough to opt out in the case of drive by
</I>><i> upgrades.
</I>><i>
</I>><i> Col
</I>
This is an idea I like. More visibility to the fact that the package is
unmaintained, but no mandatory assignment.
I also think, like Philippe, that groups would help here : if for example a
"games" packager group is ready to maintain all games that have no specific
maintainer, I would certainly join that group.
Best regards
Samuel
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008149.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
</A></li>
<LI>Next message: <A HREF="008164.html">[Mageia-dev] [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8162">[ date ]</a>
<a href="thread.html#8162">[ thread ]</a>
<a href="subject.html#8162">[ subject ]</a>
<a href="author.html#8162">[ 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>
|
