diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101024/002601.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101024/002601.html | 126 |
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101024/002601.html b/zarb-ml/mageia-discuss/20101024/002601.html new file mode 100644 index 000000000..69b133aa5 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101024/002601.html @@ -0,0 +1,126 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Suggestions + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C1287910627.22938.236.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002593.html"> + <LINK REL="Next" HREF="002616.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Suggestions</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C1287910627.22938.236.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-discuss] Suggestions">misc at zarb.org + </A><BR> + <I>Sun Oct 24 10:57:07 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002593.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002616.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2601">[ date ]</a> + <a href="thread.html#2601">[ thread ]</a> + <a href="subject.html#2601">[ subject ]</a> + <a href="author.html#2601">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 23 octobre 2010 à 22:13 -0500, Dale Huckeby a écrit : +><i> > On Sun, 24 Oct 2010, Michael Scherer wrote: +</I>><i> > +</I>><i> > The patch arguent is invalid, because people can also send mail, like +</I>><i> > "here is a better description of package $FOO because I didn't +</I>><i> > understood the current one and I wanted to help". +</I>><i> +</I>><i> But you didn't say that. You said "send a patch" which is not so user +</I>><i> friendly. Oh that's right, you already addressed that. But yeah, if +</I>><i> I could just send the desired text via email that would be easy, and +</I>><i> for that matter learning to create and send patches would be pretty +</I>><i> easy to learn, too. Just never had reason to before. +</I> +Yeah, I say "send a patch" in the general sense, guess that it was too +specific, sorry for the misunderstanding. Usually, people are ok when +being contacted directly with non structured patchs, especially for +something as trivial as changing a string. And at worst, someone will +tell "please fill this in the bugtracker, I will take care of it later". + + +><i> > And I think that most of use naively think "if something is wrong, at +</I>><i> > least 1 person will say it". yet, it doesn't happen. +</I>><i> +</I>><i> Yes, you are being naive. Other packagers aren't going to say anything +</I>><i> because it's not their package and because, like you, they don't really +</I>><i> notice the missing descriptions. And ordinary users aren't part of that +</I>><i> world, so it doesn't occur to them to say anything, or to contribute +</I>><i> in any way, because it would seem presumptuous. I think Mageia should +</I>><i> make a special effort to recruit, to make to feel comfortable, users +</I>><i> who might want to contribute but don't know how, who feel kind of lost +</I>><i> at sea when it comes to knowing where to begin. +</I> +Well, we could organize some days on the forum/ml/irc/whatever where +people collectively review packages descriptions. Some people could +review current packages, some other could write proper description, a +third set will review it, and the last part of the group will organize +this with packagers and push the description to cauldron. + +And we could also have people who dedicate them self to read packages +description in changelog to notice such problems in time. + +Debian also has a set of guideline about description, that we could +reuse to improve ours : +<A HREF="http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis">http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis</A> + +( I must add that I do not volunteer to organize such days, I have +unfortunately enough work to do, but I am ok to give a hand ). + +><i> > So if we want to scale and make it work, then we need to find how to +</I>><i> > make people who are directly concerned contribute. And so, the best way +</I>><i> > to find why something didn't happen is to simply ask to people who are +</I>><i> > directly concerned. +</I>><i> +</I>><i> Exactly. There needs to be some way new users can be informed, either in +</I>><i> the install process itself or via, say, an icon on the desktop which, +</I>><i> when clicked, explains briefly what Mageia is, how users can contribute, +</I>><i> where they can go to get more information, etc. +</I> +Maybe a entry "report problem" in the menu that would send them either +to bugzilla ( but I feel this would not be ideal to new users ) or to a +forum/ml/irc ( which would be nice, but I feel that I putting the +problem on someone else shoulder and that's not nice ) ? + +Or something that point to a translated page with instructions ? + +-- +Michael Scherer + +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002593.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002616.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2601">[ date ]</a> + <a href="thread.html#2601">[ thread ]</a> + <a href="subject.html#2601">[ subject ]</a> + <a href="author.html#2601">[ 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> |