diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/009261.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/009261.html | 152 |
1 files changed, 152 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/009261.html b/zarb-ml/mageia-dev/2011-October/009261.html new file mode 100644 index 000000000..b76d4c5e8 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009261.html @@ -0,0 +1,152 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Review Of Bugs + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Review%20Of%20Bugs&In-Reply-To=%3C4EAF1E27.3040208%40colin.guthr.ie%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009259.html"> + <LINK REL="Next" HREF="009260.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Review Of Bugs</H1> + <B>Colin Guthrie</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Review%20Of%20Bugs&In-Reply-To=%3C4EAF1E27.3040208%40colin.guthr.ie%3E" + TITLE="[Mageia-dev] Review Of Bugs">mageia at colin.guthr.ie + </A><BR> + <I>Mon Oct 31 23:16:07 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009259.html">[Mageia-dev] Review Of Bugs +</A></li> + <LI>Next message: <A HREF="009260.html">[Mageia-dev] Review Of Bugs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9261">[ date ]</a> + <a href="thread.html#9261">[ thread ]</a> + <a href="subject.html#9261">[ subject ]</a> + <a href="author.html#9261">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>'Twas brillig, and Michael Scherer at 31/10/11 21:44 did gyre and gimble: +><i> Le lundi 31 octobre 2011 à 21:06 +0000, Colin Guthrie a écrit : +</I>>><i> 'Twas brillig, and Maarten Vanraes at 31/10/11 20:55 did gyre and gimble: +</I>>>><i> Op maandag 31 oktober 2011 21:34:04 schreef D.Morgan: +</I>>>><i> [...] +</I>>>>>><i> But seriously, if we can't maintain/fix something like chromium-browser, +</I>>>>>><i> we should just drop it completely, maybe have a get-chromium package +</I>>>>>><i> instead +</I>>>>><i> +</I>>>>><i> why ? i package it regularly and tvignaud too. +</I>>>>><i> what about dropping all packages that have bugs ? this is just stupid +</I>>>>><i> and you should first ask ppl packaging it before giving such ideas +</I>>>><i> +</I>>>><i> ok, i get it, (allthough i did say "IF") I guess it's a misguided attempt of +</I>>>><i> myself to get more maintainership... +</I>>><i> +</I>>><i> I think the attempts to get more official partnerships by Samuel and +</I>>><i> yourself are very valuable, but by the same token, I think we need to +</I>>><i> accept that having a single maintainer for some packages just doens't +</I>>><i> make sense. +</I>>><i> +</I>>><i> For example things like initscripts, udev, systemd etc. should be +</I>>><i> maintained by a "core" team, and IMO, not a single person (tho' if +</I>>><i> someone steps up and is proven to be reliable then this is obviously not +</I>>><i> a bad thing per-se!). I'm certainly happy to help out here. +</I>><i> +</I>><i> Well, so far, the system do not support this. +</I> +Indeed. + +><i> So either this supposed team is able to organise itself to have one of +</I>><i> the member to act as a gate to take maitainership and dispatch task +</I> +I think both socially and expectation wise, being a the gatekeeper in +such context still carries a lot of responsibility that people would not +feel too comfortable with, nor would there necessarily be the social +hierarchy where said gatekeeper would feel sufficiently authorised to +dish out tasks to others. + +><i> or someone patch the maintdb script to have more than one person. +</I> +This would be better, or perhaps "team accounts" can be created which +forward mail to the members rather than having multiple maintainers.. +not sure if this is easier infrastructure wise or not but the net +outcome is the same either ways so whatever makes more sense. + +><i> As long as "being managed by several people" will be seen the same way +</I>><i> as "maintained by nobody", we will have the same problem as mandriva. +</I> +Personally I don't buy that explanation. Of course it can be true in +some cases (everyone just waits for someone else to fix it) but I +suspect the odds of things getting fixed is still much higher than when +a package is officially maintained by nobody... + +><i> Being maintained officially by someone do not prevent others to help. +</I>><i> So I do not see any good reason to have them marked as nobody. +</I> +I certainly don't expect a package maintained by a team to be marked as +nobody (well, certainly not longer term). But again, I think even +allocating a gatekeeper or a team leader puts too many social pressures +on that person, and imposes something of a hierarchy that really doesn't +seem appropriate. Also things don't happen automatically - such as all +the team members getting CC'ed on bugzilla etc which would make it quite +a lot of admin work for said gatekeeper on top of the actual bug fixes +which again I think is too much. + +I think things need to work automatically as much as possible with loose +couplings rather than appointed leaders. We need to get teams (either +via team accounts or by multiple maintainers) and ensure that when a bug +is assigned to a team, that all members get emails about it (perhaps as +separate CC's allowing someone in the team to assign the bug to +themselves but still keep the others included in the communications - +although this could also be done with the QA contact field in BZ I think +(we use it in a similar way in PA with the fd.o bugzilla) although just +ensuring everyone knows to add the team email to the CC when assigning +to themselves would be enough). + +Obviously someone needs to do the work to make the infrastructure cope +with this :s Let's form a team to see who'll do it... :p + +Col + + +-- + +Colin Guthrie +colin(at)mageia.org +<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A> + +Day Job: + Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A> +Open Source: + Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A> + PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A> + Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009259.html">[Mageia-dev] Review Of Bugs +</A></li> + <LI>Next message: <A HREF="009260.html">[Mageia-dev] Review Of Bugs +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9261">[ date ]</a> + <a href="thread.html#9261">[ thread ]</a> + <a href="subject.html#9261">[ subject ]</a> + <a href="author.html#9261">[ 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> |