summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110305/003038.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20110305/003038.html')
-rw-r--r--zarb-ml/mageia-dev/20110305/003038.html148
1 files changed, 148 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110305/003038.html b/zarb-ml/mageia-dev/20110305/003038.html
new file mode 100644
index 000000000..2e483ad6a
--- /dev/null
+++ b/zarb-ml/mageia-dev/20110305/003038.html
@@ -0,0 +1,148 @@
+<!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=%3C201103051347.32336.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="003037.html">
+ <LINK REL="Next" HREF="003041.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=%3C201103051347.32336.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:47:32 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="003037.html">[Mageia-dev] [RPM] cauldron core/release nagios-3.2.3-2.mga1
+</A></li>
+ <LI>Next message: <A HREF="003041.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3038">[ date ]</a>
+ <a href="thread.html#3038">[ thread ]</a>
+ <a href="subject.html#3038">[ subject ]</a>
+ <a href="author.html#3038">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op vrijdag 04 maart 2011 09:05:02 schreef Buchan Milne:
+&gt;<i> On Thursday, 3 March 2011 22:43:25 Maarten Vanraes wrote:
+</I>&gt;<i> &gt; I think we need to have a name and email address. however, some options:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; A. possibly &quot;cn&quot; could be editable in identity
+</I>&gt;<i>
+</I>&gt;<i> Please stop referring to possibilities that exist as if they don't ... it
+</I>&gt;<i> is depressing that people keep assuming things don't work, when one has
+</I>&gt;<i> put effort into making them work ...
+</I>
+I'm sorry, i myself have done a few patches to catdap, i know it's there,
+
+except, i heard that cn was planned to be used as a concatenation of givenName
+and sn; which i could understand as a fill-in default, but not really forced.
+
+What i meant more, is to have a &quot;display Name&quot; thing during registration, more
+visible.
+
+&gt;<i> (IOW, if users should *not* be able to edit cn, then there is one
+</I>&gt;<i> configuration entry to edit)
+</I>
+(i notice that there is no mention of successfull edit, when doing so)
+
+&gt;<i> &gt; ==&gt; this will allow people to fill in what they want, be it full name,
+</I>&gt;<i> &gt; nickname, or full name AND nickname
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; cn could then be used as the name field
+</I>&gt;<i>
+</I>&gt;<i> That is the current situation, at least in bugzilla, and should be in
+</I>&gt;<i> forum.
+</I>&gt;<i>
+</I>&gt;<i> &gt; B. an email address is required IMHO, and preferably a @mageia.org email
+</I>&gt;<i> &gt; address
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; however, if people wouldn't want to have their email address listed, an
+</I>&gt;<i> &gt; extra option is this:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; C. how about we make &lt;packagename&gt;@packages.mageia.org, which could use
+</I>&gt;<i> &gt; the maintainers database to forward the email to maintainers (in case of
+</I>&gt;<i> &gt; more) (this could also be a packagegroup. eg:
+</I>&gt;<i> &gt; <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">firefox at packages.mageia.org</A> could refer to maintainers of firefox,
+</I>&gt;<i> &gt; xulrunner, etc...) (this option might just be too complex)
+</I>&gt;<i>
+</I>&gt;<i> /me notes that this might be easier done in LDAP, as a postfix alias map.
+</I>&gt;<i> Which begs the question ... should the maintainer &quot;database&quot; be in LDAP
+</I>&gt;<i> instead?
+</I>&gt;<i>
+</I>&gt;<i> (BTW., I was thinking along the lines of package groups, with multi-valued
+</I>&gt;<i> attribute for package name and maintainer. e.g.:
+</I>&gt;<i>
+</I>&gt;<i> dn: cn=firefoxteam,ou=Packages,dc=mageia,dc=org
+</I>&gt;<i> objectClass: mageiaPackageGroup
+</I>&gt;<i> cn: firefox-team
+</I>&gt;<i> mail: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">firefox at packages.mageia.org</A>
+</I>&gt;<i> mageiaPackage: firefox
+</I>&gt;<i> mageiaPackage: firefox-en_gb
+</I>&gt;<i> mageiaPackage: firefox-ext-firebug
+</I>&gt;<i> ....
+</I>&gt;<i> mageiaMaintainer: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">foo at mageia.org</A>
+</I>&gt;<i> mageiaMaintainer: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bar at mageia.org</A>
+</I>&gt;<i> owner: uid=xxx,ou=People,dc=mageia,dc=org
+</I>&gt;<i>
+</I>&gt;<i> &gt; D. if people really want to use their own personal email address, perhaps
+</I>&gt;<i> &gt; one can be opted-in to use that one. (but this should be decided in a
+</I>&gt;<i> &gt; policy and be strict on it either YES/NO)
+</I>&gt;<i>
+</I>&gt;<i> Per-user options are difficult to administer, I would prefer the same
+</I>&gt;<i> behaviour for everyone, and the choice to provide data at the user's
+</I>&gt;<i> discretion. E.g., the current situation, where contributors are requested
+</I>&gt;<i> to provide real givenName,sn, but are free to use whatever cn they prefer,
+</I>&gt;<i> and all external tools use cn. sn and givenName are only used for
+</I>&gt;<i> account/identity validation, legal requirements etc. and all uses of the
+</I>&gt;<i> data must respect privacy policy.
+</I>&gt;<i>
+</I>&gt;<i> &gt; personally, i like:
+</I>&gt;<i> &gt; A, B, C, but vote NO for D.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; i would like to use &quot;AL13N &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at mageia.org</A>&gt;&quot; being used. my real name
+</I>&gt;<i> &gt; is kind of not linked the the email address.
+</I>&gt;<i>
+</I>&gt;<i> Well, I haven't seen any authoritative statement on whether all
+</I>&gt;<i> contributors will have @mageia.org aliases, and some work needs to be done
+</I>&gt;<i> for this if it will be provided.
+</I>
+AFAIK, i think from reading founders meetings, this is planned to be rolled
+out on a step by step basis, iirc founders/council has it, and it was planned
+to be rolled out at least to the &quot;recognised peers&quot; of each team.
+</PRE>
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="003037.html">[Mageia-dev] [RPM] cauldron core/release nagios-3.2.3-2.mga1
+</A></li>
+ <LI>Next message: <A HREF="003041.html">[Mageia-dev] Contributors using real name/working email? or not? or maybe?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#3038">[ date ]</a>
+ <a href="thread.html#3038">[ thread ]</a>
+ <a href="subject.html#3038">[ subject ]</a>
+ <a href="author.html#3038">[ 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>