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
|
<!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=%3C4D107488.80600%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001823.html">
<LINK REL="Next" HREF="001826.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=%3C4D107488.80600%40laposte.net%3E"
TITLE="[Mageia-dev] maintainers database">andr55 at laposte.net
</A><BR>
<I>Tue Dec 21 10:34:00 CET 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001823.html">[Mageia-dev] maintainers database
</A></li>
<LI>Next message: <A HREF="001826.html">[Mageia-dev] maintainers database
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1825">[ date ]</a>
<a href="thread.html#1825">[ thread ]</a>
<a href="subject.html#1825">[ subject ]</a>
<a href="author.html#1825">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Luca Berra a écrit :
><i>
</I>><i> On Fri, Dec 17, 2010 at 11:06:36PM +0100, Romain d'Alverny wrote:
</I>>><i> For instance:
</I>>><i> * instead of having a single maintainer for a given package, have
</I>>><i> several maintainers (with an admin maybe) over a given package (easy);
</I>><i> yes please
</I>><i>
</I>>><i> * should there be groups of packages defined? (this adds/replicates
</I>>><i> some logic that may already be somewhere else)
</I>><i> this can be useful, many desktop environments consist of more than one
</I>><i> core package and development/packaging should be coordinated, so it
</I>><i> makes sense.
</I>><i>
</I>>><i> * should there be explicity groups of maintainers? or implicit (as
</I>>><i> made of people maintaining the same package)?
</I>><i> i think explicit
</I>><i>
</I>><i> L.
</I>
We could have a structure something like this :
Primary key : name of package
Other fields, 1:1 relation :
- package rpm category (+ subcategory, if any)
- repository
- etc
Other fields, 1:N relation :
- Packager nickname + packager status (primary maintainer, trainee or
whatever) + real name + email
(The last 2 items could be in a separate table keyed by nickname.)
- Package dependancies (names of other packages)
- Package provides (names of other packages)
- etc.
Any of above fields could be chosen as secondary keys.
This is just a quick suggestion, for the purposes of discussion.
It doesn't seem that this sort of info would be useful in
mageia-app-db, which is primarily for end-users.
another 2 cents :)
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001823.html">[Mageia-dev] maintainers database
</A></li>
<LI>Next message: <A HREF="001826.html">[Mageia-dev] maintainers database
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1825">[ date ]</a>
<a href="thread.html#1825">[ thread ]</a>
<a href="subject.html#1825">[ subject ]</a>
<a href="author.html#1825">[ 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>
|
