summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101218/001783.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101218/001783.html')
-rw-r--r--zarb-ml/mageia-dev/20101218/001783.html120
1 files changed, 120 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101218/001783.html b/zarb-ml/mageia-dev/20101218/001783.html
new file mode 100644
index 000000000..69a7859c7
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101218/001783.html
@@ -0,0 +1,120 @@
+<!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=%3C201012181339.17909.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="001782.html">
+ <LINK REL="Next" HREF="001784.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] maintainers database</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20maintainers%20database&In-Reply-To=%3C201012181339.17909.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] maintainers database">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Sat Dec 18 13:39:17 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001782.html">[Mageia-dev] maintainers database
+</A></li>
+ <LI>Next message: <A HREF="001784.html">[Mageia-dev] mageia sound tasks
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1783">[ date ]</a>
+ <a href="thread.html#1783">[ thread ]</a>
+ <a href="subject.html#1783">[ subject ]</a>
+ <a href="author.html#1783">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op zaterdag 18 december 2010 12:00:52 schreef Michael scherer:
+&gt;<i> On Fri, Dec 17, 2010 at 11:55:39PM +0100, Romain d'Alverny wrote:
+</I>&gt;<i> &gt; On Fri, Dec 17, 2010 at 23:41, Maarten Vanraes
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">maarten.vanraes at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt; &gt; imo, it could be used into mageia-app-db, allthough the purposes are a
+</I>&gt;<i> &gt; &gt; bit different.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; So it should be a separate component.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; &gt; however, if we plan on using ldap to store the maintainership (it would
+</I>&gt;<i> &gt; &gt; be more like groups for each package and people being member of
+</I>&gt;<i> &gt; &gt; it...), then perhaps it should be in catdap.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; I'm not sure this should be put into the LDAP, but I may be wrong. The
+</I>&gt;<i> &gt; data model is likely to change often enough (even if not a lot) and
+</I>&gt;<i> &gt; queries are likely to be frequent enought, to justify a separate,
+</I>&gt;<i> &gt; simple db/app for that. But here again, I may not have all the infos.
+</I>&gt;<i>
+</I>&gt;<i> I think we should use a simple sql database for now.
+</I>&gt;<i>
+</I>&gt;<i> Even if later, ldap could help use to set ACL, and tree structure for
+</I>&gt;<i> packages ( ie, the grouping feature of packages you spoke of ), I think we
+</I>&gt;<i> should aim first for a very basic application :
+</I>&gt;<i>
+</I>&gt;<i> 1 srpm -&gt; 1 to N maintainers,
+</I>&gt;<i>
+</I>&gt;<i> and that's all.
+</I>&gt;<i>
+</I>&gt;<i> Later, we can think more thoroughly about this, and likely rewrite.
+</I>&gt;<i> But the initial goal was to reuse mdvdb because
+</I>&gt;<i> it was the fastest route. So we should not forget about it. If we use a
+</I>&gt;<i> quick and dirty django application with basic CRUD to manage that, it
+</I>&gt;<i> should be fine.
+</I>
+i'm ok with quick and dirty.
+
+tbh, i would like to have this in ldap; since it's related to groups;
+especially if we will woul mailgroups for each package, the member (or
+uniqueMember) can be used to get all the maintainers for that package, and an
+extra attribute to have a primary maintainer.
+
+in effect: being co-maintainer could even be validated by the primary
+maintainer; if primary maintainer leaves, a co-maintainer can grab the primary
+maintainership; if no maintainers are there, someone can become maintainer
+without checks, and becomes primary maintainer directly. only valid packagers
+can grab maintainership (but novices can too)
+
+packagers should have an ldap attribute for the level: none, novice, full,
+security (where none can be omitted and security means he can do security
+updates)
+
+(if you haven't seen it yet; i'm a fan of having everything directly related
+to auth and groupings of users into an ldap)
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001782.html">[Mageia-dev] maintainers database
+</A></li>
+ <LI>Next message: <A HREF="001784.html">[Mageia-dev] mageia sound tasks
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1783">[ date ]</a>
+ <a href="thread.html#1783">[ thread ]</a>
+ <a href="subject.html#1783">[ subject ]</a>
+ <a href="author.html#1783">[ 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>