diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20110917/005377.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20110917/005377.html | 100 |
1 files changed, 100 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20110917/005377.html b/zarb-ml/mageia-discuss/20110917/005377.html new file mode 100644 index 000000000..5a4696198 --- /dev/null +++ b/zarb-ml/mageia-discuss/20110917/005377.html @@ -0,0 +1,100 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS ! + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%20misc%20unleashes%0A%20CERBERUS%20%21&In-Reply-To=%3C4E74529A.9020402%40unige.ch%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005376.html"> + <LINK REL="Next" HREF="005378.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !</H1> + <B>Juergen Harms</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20MANDATORY%20READ%20%3A%207%20days%20before%20misc%20unleashes%0A%20CERBERUS%20%21&In-Reply-To=%3C4E74529A.9020402%40unige.ch%3E" + TITLE="[Mageia-discuss] MANDATORY READ : 7 days before misc unleashes CERBERUS !">Juergen.Harms at unige.ch + </A><BR> + <I>Sat Sep 17 09:56:10 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005376.html">[Mageia-discuss] Chromium : Stable, beta and unstable versions in core repositories +</A></li> + <LI>Next message: <A HREF="005378.html">[Mageia-discuss] Big printing issue with HP Photosmart 7150 and Mageia +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5377">[ date ]</a> + <a href="thread.html#5377">[ thread ]</a> + <a href="subject.html#5377">[ subject ]</a> + <a href="author.html#5377">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 09/16/2011 10:43 PM, Maarten Vanraes wrote: +><i> This is exactly why Stormi's idea is a great one, welcome i should say: look +</I>><i> around for a mentor, ask andre999 about it (he's the mentoring coordinator)... +</I>><i> +</I>I will. And sorry, my message went away from my drafts folder +accidentally before it was spelled out risks to sound crude. Some more +details on my thoughts (and picking up what has been said about creating +groups): + +(1) Stormi's idea is particularly adapted to a community distro - and I +agree, if community members (nearly) at large contribute to package +maintenance, they may need some backing up. Doing this by organising +groups on the basis of implementation languages may be very helpful +while looking for maintainers. Once the work goes on, there may be more +specific needs. Take my example: with backuppc I might come on questions +to people who know the wheels in apache, or with geda I might need +putting straight with GUI questions. Might be a good idea to put some +thought into organising that - maybe just a slight twist to the mageia +dev mailing list (and maybe after an initial period of gathering +experience). + +(2) I have had a close look at the package list: throwing out "nobody" +packages in an un-organised way, just following considerations whether +incidentlally a package has been picked up or not, risks crippling +Mageia into a distro that does not stand up to other distros (just look +at editors - a distro without ed, sed, emax, xemacs ?) Before the +cerberos comes with a big guillotine, there should at least be a first +phase when a list of "absolutely required packages" has been defined, +for which maintainers need to be actively defined (using thumb screws, +chantage - what is the english word? - if need be) - and this might work +better once the present search for volonteers has established a broader +base of known candidates. That requires some time - a 1-week cerberos +would not allow for that. + +(3) Again with the example of backuppc and geda in mind: both have +strong upstream activities, active and competent mailing lists. I have +no idea, how traditionally maintainership is organised in front of such +a background. I will certainly need to sign up for these lists (again - +I quit after an initial phase - too much traffic). Do down-stream +distros have a particular standing with upstream parents? + +(4) Apropos "I have no idea": it might be helpful if a few lines of text +would exist that describe the duties and the normal way of "functioning" +of a maintainer. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005376.html">[Mageia-discuss] Chromium : Stable, beta and unstable versions in core repositories +</A></li> + <LI>Next message: <A HREF="005378.html">[Mageia-discuss] Big printing issue with HP Photosmart 7150 and Mageia +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5377">[ date ]</a> + <a href="thread.html#5377">[ thread ]</a> + <a href="subject.html#5377">[ subject ]</a> + <a href="author.html#5377">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |