diff options
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000180.html')
| -rw-r--r-- | zarb-ml/mageia-webteam/2011-January/000180.html | 124 |
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000180.html b/zarb-ml/mageia-webteam/2011-January/000180.html new file mode 100644 index 000000000..96c2d01a7 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-January/000180.html @@ -0,0 +1,124 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-webteam] Maintainers db app questions + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Maintainers%20db%20app%20questions&In-Reply-To=%3C1295894268.31817.56.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="000179.html"> + <LINK REL="Next" HREF="000184.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-webteam] Maintainers db app questions</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Maintainers%20db%20app%20questions&In-Reply-To=%3C1295894268.31817.56.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-webteam] Maintainers db app questions">misc at zarb.org + </A><BR> + <I>Mon Jan 24 19:37:48 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000179.html">[Mageia-webteam] Maintainers db app questions +</A></li> + <LI>Next message: <A HREF="000184.html">[Mageia-webteam] [Mageia-sysadm] Viewvc installation +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#180">[ date ]</a> + <a href="thread.html#180">[ thread ]</a> + <a href="subject.html#180">[ subject ]</a> + <a href="author.html#180">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 24 janvier 2011 à 18:07 +0000, Kosmas Chatzimichalis a écrit : +><i> A few questions about the maintainers db application, that are more detailed +</I>><i> than the initial spec. +</I>><i> +</I>><i> +</I>><i> - Do we need first name, surname for maintainers or we would only be +</I>><i> using email? +</I> +mhh, what about login + email ? +I do not fully understand the question + +><i> - If we do store first name, surname are they compulsory, or can be +</I>><i> omitted? +</I>I would rather fetch them from ldap, or at least, make ldap the +reference for that, and keep the information in the db as cache, so +people have one location to change everything. + +><i> - Where do we take the information from? Is there a database at the +</I>><i> moment, that we can take maintainers, packages information? +</I>We don't have anything yet. + +><i> - If information is taken initially from another database, where is the +</I>><i> new information created? Or in other words, do we create new media, +</I>><i> maintainer, package in the app or is that created somewhere else? +</I>A good question. +Maintainers list come from ldap. + +Media should IMHO be not required, but if needed, I would rather have a +list somewhere acting as a reference. ( maybe ldap ? ). Some people +spoke of having different maintainers for stable and devel, but I do not +think we are enough to have that. + +Packages are not stored anywhere yet, and I do not know if someone +planned something. But packages would likely be created on upload by a +script, with the people uploading becoming the maintainer. + +><i> - How do we integrate with ldap? +</I>for authentication I think + +><i> Would that be used to lookup for +</I>><i> administration permissions for maintainers? Or would we need different users +</I>><i> as admins that are not necessarily maintainers. +</I>I would use the following permissions : +- define a group for people who can connect on the interface ( like, +packagers ) +- define a group that can connect as admin ( like be able to change +anything, ie sysadmins ) + +That was the scheme used at Mandriva, and I think it is sufficient, +So yes, using ldap for admin permission is a good idea. + +><i> - Would the first maintainer be the admin for a particular package? +</I>That could be done, yes but some people would maybe prefer more than 1 +admin, or shared admins with everybody. I can ask during meeting on +Wednesday the opinion of others packagers. + +><i> - Can the admin of a package be changed later on? +</I>That's imho required, yes. + +-- +Michael Scherer + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000179.html">[Mageia-webteam] Maintainers db app questions +</A></li> + <LI>Next message: <A HREF="000184.html">[Mageia-webteam] [Mageia-sysadm] Viewvc installation +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#180">[ date ]</a> + <a href="thread.html#180">[ thread ]</a> + <a href="subject.html#180">[ subject ]</a> + <a href="author.html#180">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam +mailing list</a><br> +</body></html> |