summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/2011-January/000180.html
blob: 96c2d01a7c8f0d644c8c70e4a639824dac66133a (plain)
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
<!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 &#224; 18:07 +0000, Kosmas Chatzimichalis a &#233;crit :
&gt;<i> A few questions about the maintainers db application, that are more detailed
</I>&gt;<i> than the initial spec.
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i>    - Do we need first name, surname for maintainers or we would only be
</I>&gt;<i>    using email?
</I>
mhh, what about login + email ? 
I do not fully understand the question

&gt;<i>    - If we do store first name, surname are they compulsory, or can be
</I>&gt;<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.

&gt;<i>    - Where do we take the information from? Is there a database at the
</I>&gt;<i>    moment, that we can take maintainers, packages information?
</I>We don't have anything yet.

&gt;<i>    - If information is taken initially from another database, where is the
</I>&gt;<i>    new information created? Or in other words, do we create new media,
</I>&gt;<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.

&gt;<i>    - How do we integrate with ldap? 
</I>for authentication I think

&gt;<i> Would that be used to lookup for
</I>&gt;<i>    administration permissions for maintainers? Or would we need different users
</I>&gt;<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.

&gt;<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.

&gt;<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>