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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-sysadm] perl team alias?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20perl%20team%20alias%3F&In-Reply-To=%3C1313576023.22483.53.camel%40akroma.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="003865.html">
<LINK REL="Next" HREF="003871.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-sysadm] perl team alias?</H1>
<B>Michael Scherer</B>
<A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20perl%20team%20alias%3F&In-Reply-To=%3C1313576023.22483.53.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-sysadm] perl team alias?">misc at zarb.org
</A><BR>
<I>Wed Aug 17 12:13:43 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003865.html">[Mageia-sysadm] perl team alias?
</A></li>
<LI>Next message: <A HREF="003871.html">[Mageia-sysadm] perl team alias?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3867">[ date ]</a>
<a href="thread.html#3867">[ thread ]</a>
<a href="subject.html#3867">[ subject ]</a>
<a href="author.html#3867">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le mercredi 17 août 2011 à 10:11 +0200, Buchan Milne a écrit :
><i> On Wednesday, 17 August 2011 00:51:48 Michael Scherer wrote:
</I>><i> > Le dimanche 14 août 2011 à 14:15 +0200, Jerome Quelin a écrit :
</I>><i> > > hi,
</I>><i> > >
</I>><i> > > up till now, i was the only one taking care of the perl stack within
</I>><i> > > mageia. however, kharec is joining me in this effort, and i have a
</I>><i> > > padawan interested to help perl packaging in mageia.
</I>><i> > >
</I>><i> > > to that end, i was wondering whether it'd be possible to have an alias
</I>><i> > > such as <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">perl at xxx.mageia.org</A> - or whatever scheme you want, i don't
</I>><i> > > really care. this would allow to assign perl bugs to this alias when
</I>><i> > > triaging them. or add this alias as cc: to make sure the perl team is
</I>><i> > > aware of them.
</I>><i> > >
</I>><i> > > i don't want a mailing list, since dev questions, comments and other
</I>><i> > > should go to -dev. however, if you have another solution to provide,
</I>><i> > > let me know!
</I>><i> >
</I>><i> > While I would not be against creating sub team ( because that's what it
</I>><i> > is ), I would rather have people first think to the various governance
</I>><i> > issues and problem before proposing a technical solution.
</I>><i> >
</I>><i> > Aliases are obscure per definition, and assigning something to a aliases
</I>><i> > would mean that most people would not know who is in CC ( especially
</I>><i> > with regards to our privacy policy ).
</I>><i> >
</I>><i> > We do need to decide who decide a new aliases should be given, and what
</I>><i> > it entails ( ie, what would perl take in account ? all perl modules ?
</I>><i> > all perl software ? ). And who decide who goes in the aliases/team.
</I>><i> > This would also have a impact on the maintainer db at various level,
</I>><i> > technical and organisational, etc.
</I>><i>
</I>><i> Is there yet a maintainer DB? I would be in favour of a system of maintainer
</I>><i> groups, where a group may have multiple maintainers, and multiple packages,
</I>><i> and have an alias, and/or aliases for each package in the group, with
</I>><i> recipients being the members of the group.
</I>
Boklm coded a quick hack in bash for that.
See around
<A HREF="http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/maintdb?view=log">http://svnweb.mageia.org/adm/puppet/modules/buildsystem/templates/maintdb?view=log</A>
Maybe we should start to think splitting the build system module in
smaller chunks.
I think everybody agreed on having maintainers group, so the next step
is to decide on what that mean exactly, and then to code it.
><i> Such a group may also require an owner, who would have the ability to add or
</I>><i> remove packages or maintainers.
</I>
That would make ldap suitable for that I guess, and would be in favor of
pushing this to ldap rather than bash, but it was easier to do in bash.
But that still do not solve the issue about team governance, and add the
problem of editing the team ( even if catdap was enhanced for that,
since i18n team is almost auto managed ).
><i> > To me, the answer would still be to have auto assignement of CC based on
</I>><i> > maint db + a subscription database, but so far, no one coded it.
</I>><i>
</I>><i> Well, I would think it *should* be the maintainer database, and just have a
</I>><i> postfix alias map for it.
</I>
This would put some restriction since the maintainer db is restricted to
maintainers ( ie, not apprentice ) and I think we need a richer system
that does more for bugzilla. IMHO, people that are not maintainers could
be interested into getting notification of bugs on some rpms.
For example :
- while not wanting to take care of a library, a packager would want
to be notified of error on it, because some of his packages use it
- while not being packager, a upstream developer could subscribe to
our bugzilla to get notification ( was done at plf for upload on some
package )
- users who are testers, or advanced users of a software would
subscribe to be able to confirm or test bugs. This also goes with some
ideas of madb, to ease collaboration of users and packagers.
- apprentices, who are not maintainers ( and so cannot be added to the
maint db ), could get bug about rpm they want to help.
So while not everything can be done right now, I think we should keep
those goal in mind when designing the system. Especially make clear what
is the goal of the aliases, and make a way to see who is behind it, and
when to use it, and when to not use it. For example, I am not sure that
assigning a bug to a team is not equivalent to assigning it to no
one :/
IMHO, the easiest would be to indeed add group maintainer to the current
code base for maintainer db, and find some way to do auto assignement in
bugzilla. For example, a cron job to modify bugzilla when something is
assigned to triage ?
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003865.html">[Mageia-sysadm] perl team alias?
</A></li>
<LI>Next message: <A HREF="003871.html">[Mageia-sysadm] perl team alias?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3867">[ date ]</a>
<a href="thread.html#3867">[ thread ]</a>
<a href="subject.html#3867">[ subject ]</a>
<a href="author.html#3867">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm
mailing list</a><br>
</body></html>
|
