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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] maintainers database
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainers%20database&In-Reply-To=%3C4D0BFE8A.4030502%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Next" HREF="001776.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] maintainers database</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainers%20database&In-Reply-To=%3C4D0BFE8A.4030502%40laposte.net%3E"
TITLE="[Mageia-dev] maintainers database">andr55 at laposte.net
</A><BR>
<I>Sat Dec 18 01:21:30 CET 2010</I>
<P><UL>
<LI>Next message: <A HREF="001776.html">[Mageia-dev] Choosing packagers representatives
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1775">[ date ]</a>
<a href="thread.html#1775">[ thread ]</a>
<a href="subject.html#1775">[ subject ]</a>
<a href="author.html#1775">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Romain d'Alverny a écrit :
><i>
</I>><i> On Fri, Dec 17, 2010 at 23:41, Maarten Vanraes
</I>><i> <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>> wrote:
</I>>><i> imo, it could be used into mageia-app-db, allthough the purposes are a bit
</I>>><i> different.
</I>><i>
</I>><i> So it should be a separate component.
</I>><i>
</I>>><i> however, if we plan on using ldap to store the maintainership (it would be
</I>>><i> more like groups for each package and people being member of it...), then
</I>>><i> perhaps it should be in catdap.
</I>><i>
</I>><i> I'm not sure this should be put into the LDAP, but I may be wrong. The
</I>><i> data model is likely to change often enough (even if not a lot) and
</I>><i> queries are likely to be frequent enought, to justify a separate,
</I>><i> simple db/app for that. But here again, I may not have all the infos.
</I>><i>
</I>>><i> however, we will have need of this soon; and it should also take into account
</I>>><i> co-maintainers...
</I>><i>
</I>><i> That's the group thing, yes (be it explicit or implicit).
</I>><i>
</I>><i> Romain
</I>
Why not have a field for primary/secondary maintainer ?
By default, the first maintainer would be primary, subsequent
maintainers secondary.
This field being changable as desired.
That way, there is total flexability to have whatever mix of
primary/secondary maintainers the group of packagers for a particular
package wishes.
I suspect that it would be better to have a separate database for this
than mageia-app-db, to avoid contamination of errors, etc.
By keeping it separate, the packagers would have total control to
maintain the list according to what is actually packaged by Mageia.
Note that mageia-app-db will probably be listing 3rd party packages, not
carried by mageia.
In any case, it would be better to have a separate table for packager info.
my 2 cents :)
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Next message: <A HREF="001776.html">[Mageia-dev] Choosing packagers representatives
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1775">[ date ]</a>
<a href="thread.html#1775">[ thread ]</a>
<a href="subject.html#1775">[ subject ]</a>
<a href="author.html#1775">[ 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>
|