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
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Contributors using real name/working email? or not? or maybe?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Contributors%20using%20real%20name/working%20email%3F%20or%0A%09not%3F%20or%20maybe%3F&In-Reply-To=%3C201103051357.58315.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="003032.html">
<LINK REL="Next" HREF="003036.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Contributors using real name/working email? or not? or maybe?</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Contributors%20using%20real%20name/working%20email%3F%20or%0A%09not%3F%20or%20maybe%3F&In-Reply-To=%3C201103051357.58315.maarten.vanraes%40gmail.com%3E"
TITLE="[Mageia-dev] Contributors using real name/working email? or not? or maybe?">maarten.vanraes at gmail.com
</A><BR>
<I>Sat Mar 5 13:57:58 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="003032.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe?
</A></li>
<LI>Next message: <A HREF="003036.html">[Mageia-dev] Rpmlint configuration, false positives
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3039">[ date ]</a>
<a href="thread.html#3039">[ thread ]</a>
<a href="subject.html#3039">[ subject ]</a>
<a href="author.html#3039">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op zaterdag 05 maart 2011 10:41:24 schreef Buchan Milne:
[...]
><i> So, the issues are:
</I>><i>
</I>><i> 1)What to use in the From tag in the mail to the changelog list.
</I>><i>
</I>><i> Mandriva: From: Full Name <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">devel at mandriva...</A>>
</I>><i> Mageia: From: Mageia Team <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">buildsystem-daemon at mageia....</A>>
</I>><i>
</I>><i> IMHO, it is beneficial to have the "name" of the submitter of the package
</I>><i> in the From tag, you can easily, from just looking at the list of mails in
</I>><i> a folder, see what packages were updated, and if they are packages you
</I>><i> maintain, who submitted them, without even having to open the mail. Having
</I>><i> a generic static text here is of no benefit ...
</I>><i>
</I>><i> What we use as the "name" of the user is worth discussing, but I don't see
</I>><i> any reason to limit it to being the username.
</I>><i>
</I>><i> I don't see a need to have the email address in the From be dedicated to
</I>><i> the packager/submitter.
</I>><i>
</I>><i> Proposal 1.1:
</I>><i> From: $user{cn} <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">packages at mageia.org</A>>
</I>><i> e.g.
</I>><i> From: Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">packages at mageia.org</A>>
</I>><i>
</I>><i> If we want to rather try and build teams who work on specific groups of
</I>><i> packages, it may be better to have use:
</I>><i>
</I>><i> Proposal 1.2:
</I>><i> From: $user{cn} <%<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">name at packages.mageia.org</A>>
</I>><i> e.g.
</I>><i> From: Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">openldap at packages.mageia.org</A>>
</I>><i>
</I>><i> and have per-package aliases tied to the maintainer database. This may make
</I>><i> it easier to assign bugs in bugzilla, without having to re-assign bugs
</I>><i> whenever someone joins/leaves/changes roles.
</I>><i>
</I>><i> Additionally, assuming Reply-To is not set, replying to the changelog mail
</I>><i> would get you to all the contributors who maintain the package. With
</I>><i> Reply-To set, Reply-All would get you to a mailing list, as well as the
</I>><i> alias. In my case, I filter mail based on mailing list tags, so this would
</I>><i> mean mails about my packages would not hit the mailing list folder, but
</I>><i> could hit a different folder with a better priority.
</I>><i>
</I>><i> It might be a bit overkill in some situations (e.g. kde-i18n-
</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">af at packages.mageia.org</A>), but maybe we could look up the maintainer team
</I>><i> from the package name, and that could be <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">i18n-af at mageia.org</A> or
</I>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">kde at packages.mageia.org.</A>
</I>><i>
</I>><i> But, if we want to focus on team work rather than individuals, maybe:
</I>><i> Proposal 1.3
</I>><i> From: Mageia %name team <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">openldap at packages.mageia.org</A>>
</I>><i> e.g.
</I>><i> From: Mageia openldap team <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">openldap at packages.mageia.org</A>>
</I>><i>
</I>><i> Again, we could possible look up the maintainer team name, e.g. "Mageia
</I>><i> Afrikaans localisation team" or "Mageia KDE team" using the example above,
</I>><i> or "Mageia Server team" or "Mageia LDAP team" or similar in this example:
</I>><i> From: Mageia %name{cn} <%name{mail}>
</I>><i>
</I>><i> But, this loses some of the easy-overview-by-folder-view.
</I>><i>
</I>><i> Finally, there is always the totally personal, spam-attracting option:
</I>><i> Proposal 1.4
</I>><i> From: $user{cn} <$user{mail}>
</I>><i> e.g.
</I>><i> From: Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at xxx</A>>
</I>><i>
</I>><i> Now, which email address this is is another issue. If we are going to offer
</I>><i> all contributors (anyone who can commit to svn), then we can use a Mageia
</I>><i> alias everywhere by default, and have these as aliases to the contributor's
</I>><i> personal email address. However, if a contributor receives a direct mail to
</I>><i> their contributor address, do they expect to be able to reply from that
</I>><i> address? E.g., our work mail system does sender validation, so I can only
</I>><i> send from an address that is an alias on the account which I authenticate
</I>><i> as. For Mandriva, I ssh port forward into the cluster to send mail from my
</I>><i> Mandriva alias ...
</I>><i>
</I>><i> If users have to reply from their personal address, it defeats the
</I>><i> anonymity/privacy goal.
</I>><i>
</I>><i>
</I>><i> My preference: 1.2 or 1.3
</I>><i>
</I>><i> 2)What to use in the %packager tag.
</I>><i>
</I>><i> All the proposals above apply, but let's refer to them as 2.1 through 2.4.
</I>><i>
</I>><i> My preference: 1.2 or 1.4
</I>><i>
</I>><i> 3)What to use in the %changelog section of the spec file
</I>><i>
</I>><i> Mandriva:
</I>><i> Full Name <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">usermail at mandriva....</A>> %version-%release:
</I>><i> + Revision: XXX
</I>><i>
</I>><i> Mageia:
</I>><i> uid <uid> %version-%release:
</I>><i> + Revision: XXX
</I>><i>
</I>><i> My preference would be that people who are happy to disclose their real
</I>><i> names be able to have the full name expanded in the changelog entries,
</I>><i> however there isn't necessarily a requirement to keep a valid email
</I>><i> address.
</I>><i>
</I>><i> Proposal 3.1:
</I>><i> $user{cn} <$user{uid}> %version-%release
</I>><i> e.g.
</I>><i> Buchan Milne <buchan> 3.5.7-1mga
</I>><i>
</I>><i> Porposal 3.2:
</I>><i> $user{cn} <$user{mail}> %version-%release
</I>><i> e.g.
</I>><i> Buchan Milne <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bgmilne at mageia.</A>>
</I>><i>
</I>><i>
</I>><i> 4)LDAP implications
</I>><i>
</I>><i> 4.1)As far as I know, we don't currently use givenName or sn outside
</I>><i> <A HREF="https://identity.mageia.org">https://identity.mageia.org</A> at all at present. Within
</I>><i> <A HREF="https://identity.mageia.org,">https://identity.mageia.org,</A> the givenName and sn are visible to the user,
</I>><i> and to Account Admins, and possibily Group Admins. All emails sent to the
</I>><i> user currently use cn, but it may be more personal to use "givenName sn"
</I>><i> instead?
</I>><i>
</I>><i> Bugzilla uses cn and mail
</I>><i> Forum should use cn and mail
</I>><i>
</I>><i> 4.2)I am not prepared to do work to remove sn and givenName, if you don't
</I>><i> want users to have to supply values that will never be exposed, but
</I>><i> personalise account management communication, submit a patch, or fork.
</I>><i>
</I>><i> Users can edit cn immediately on account creation anyway, and always have
</I>><i> been able to.
</I>><i>
</I>><i> 4.3)I don't see the utility of having 2 email addresses at present, while
</I>><i> we don't have aliases. If we are going to have Mageia aliases, let's
</I>><i> discuss that first, there are more issues than just users who want to use
</I>><i> two different email addresses for privacy reasons.
</I>><i>
</I>><i> However, if we do have aliases, then we will most likely introduce a
</I>><i> mailForwardingAddress attribute. This would then contain the real email
</I>><i> address, mail would contain the Mageia address for contributors, and mail
</I>><i> to the alias would be forwarded to the mailAlternateAddress
</I>><i>
</I>><i> Please indicate if this would be sufficient, or if you think
</I>><i> non-contributor users would require the ability to have a different email
</I>><i> address (for identity account management, e.g. password recovery, only).
</I>><i> Note that non- contributors mails would be used by bugzilla and sympa. But
</I>><i> they are free to use a Mageia-specific account/address, no one has ever
</I>><i> required it to be a personal address that goes to your work server, or
</I>><i> personally identifies you.
</I>><i>
</I>><i>
</I>><i> I don't want to waste any more time on this, and I will not make any
</I>><i> changes to CatDap for this unless there is consensus on a specification on
</I>><i> which I can base (manual for now) testing.
</I>><i>
</I>><i> Regards,
</I>><i> Buchan
</I>
I greatly thank you for this very long and elaborate but clear proposal
overview, imo if this goes on too long, we should vote for it and move on.
because i'm pretty sure i read that we will get @mageia.org email addresses,
i'll differentiate it from X.4 by calling "$user{uid}@mageia.org" X.5
perhaps we can just all list our personal preferences in this subthread, so
it'll immediately be clear who wants which options.
personal preferences:
1) 1.2 or 1.3
2) 2.2 or 2.5
3) 3.5 (again uid + @mageia.org)
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="003032.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe?
</A></li>
<LI>Next message: <A HREF="003036.html">[Mageia-dev] Rpmlint configuration, false positives
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#3039">[ date ]</a>
<a href="thread.html#3039">[ thread ]</a>
<a href="subject.html#3039">[ subject ]</a>
<a href="author.html#3039">[ 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>
|
