diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-November/020227.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-November/020227.html | 156 |
1 files changed, 156 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-November/020227.html b/zarb-ml/mageia-dev/2012-November/020227.html new file mode 100644 index 000000000..3184a1480 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-November/020227.html @@ -0,0 +1,156 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] what is this ???? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20what%20is%20this%20%3F%3F%3F%3F&In-Reply-To=%3C3864348.N6JAB10gNP%40localhost%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="020225.html"> + <LINK REL="Next" HREF="020228.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] what is this ????</H1> + <B>AL13N</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20what%20is%20this%20%3F%3F%3F%3F&In-Reply-To=%3C3864348.N6JAB10gNP%40localhost%3E" + TITLE="[Mageia-dev] what is this ????">alien at rmail.be + </A><BR> + <I>Sat Nov 24 20:42:40 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020225.html">[Mageia-dev] what is this ???? +</A></li> + <LI>Next message: <A HREF="020228.html">[Mageia-dev] what is this ???? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20227">[ date ]</a> + <a href="thread.html#20227">[ thread ]</a> + <a href="subject.html#20227">[ subject ]</a> + <a href="author.html#20227">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 24 november 2012 20:09:05 schreef Romain d'Alverny: +><i> 2012/11/24 PhilippeDidier <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">philippedidier at laposte.net</A>>: +</I>><i> > Sander Lepik a écrit : +</I>><i> >> 24.11.2012 18:55, PhilippeDidier kirjutas: +</I>><i> >>> NO ! +</I>><i> >>> You mean someone is paid and create a third repo for something Mageia +</I>><i> >>> doesn't want to import... +</I>><i> >>> +</I>><i> >>> If that thing brings a mess into Mageia, we will see bug reports in +</I>><i> >>> bugzilla and lot of time lost by Mageia bug-triagers, devs, packagers, +</I>><i> >>> before discovering that is not a Mageia problem but that this stuff +</I>><i> >>> brought some shit ! +</I>><i> >>> We suffer of lack of time... and this will consume more time from +</I>><i> >>> voluntary contributors to repair something badly done by someone that +</I>><i> >>> was paid for it ! +</I>><i> >> +</I>><i> >> Well, we have such repos already today and you can't stop something like +</I>><i> >> that. But you saw my example the wrong way. Mageia doesn't have to +</I>><i> >> support those repos and problems caused by such packages. +</I>><i> > +</I>><i> > That has been a problem for Mandrake with Thac repo, a problem for +</I>><i> > Mandriva with MIB repo... and sometimes it took a long (wasted) time to +</I>><i> > understand that a reported bug was induced by something imported from +</I>><i> > third repo. +</I>><i> > NB plf repo was something else : mandriva devs worked on it ! +</I>><i> +</I>><i> Still, we can't prevent that *. So perhaps should we: +</I>><i> - analyse it and find a clear model that explains it, so we can +</I>><i> change what could be changed; +</I>><i> - even embrace it, that is, have a strategy to have more such +</I>><i> external repositories to merge back into ours, or to better +</I>><i> tag/mark/recognize what can come from something we do support as +</I>><i> Mageia (because we produced it, or because it matches our +</I>><i> requirements) and from something we don't. +</I>><i> +</I>><i> * it's a symptom that means that most of Mageia (as a whole product) +</I>><i> works for some people, but some parts of it don't (so they +</I>><i> duplicate/manage things on their own to make it quick, or more +</I>><i> controlled for them). +</I>><i> +</I>><i> Still. The bottom line of having calls for bounties, people ready to +</I>><i> pay to have some requests in Mageia answered in a more controlled way, +</I>><i> is perfectly fine. Having them including in their requirements that +</I>><i> the work be merged into (if possible), or made available to the parent +</I>><i> project is even better. +</I> +i guess it needs to be policy'ed: + +like: requiring that the fixes are done in Mageia itself (no 3rd party +repository), and as usual that the fixes are done in accordance to our +policies. + +then, structure needs to be clear with a status: + +[requested] To fix bug #X (preferably option Y); <user> donates Z +[taken by <user>] To fix bug #X (preferably option Y) <user> donate Z +[solved by <user>] To fix bug #X (preferably option Y) <user> donate Z +[accepted] To fix bug #X (preferably option Y) <user> donate Z + +any other communcations or status, reject or whatever, doesn't need to be here +and is between the parties involved. + +I would also ask that if possible the user who solves it donates a part to +mageia, not required. + + +lastly, i note that the page is a draft, so this could very well mean that the +person who wrote this planned to bring this in a meeting. + + +in short, i don't really see any issue with it. +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020225.html">[Mageia-dev] what is this ???? +</A></li> + <LI>Next message: <A HREF="020228.html">[Mageia-dev] what is this ???? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20227">[ date ]</a> + <a href="thread.html#20227">[ thread ]</a> + <a href="subject.html#20227">[ subject ]</a> + <a href="author.html#20227">[ 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> |