diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101025/002654.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101025/002654.html | 168 |
1 files changed, 168 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101025/002654.html b/zarb-ml/mageia-discuss/20101025/002654.html new file mode 100644 index 000000000..0386a6fb6 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101025/002654.html @@ -0,0 +1,168 @@ +<!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=%3C4CC5FD10.9020408%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002649.html"> + <LINK REL="Next" HREF="002640.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Suggestions</H1> + <B>andre999</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Suggestions&In-Reply-To=%3C4CC5FD10.9020408%40laposte.net%3E" + TITLE="[Mageia-discuss] Suggestions">andr55 at laposte.net + </A><BR> + <I>Mon Oct 25 23:56:32 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002649.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002640.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2654">[ date ]</a> + <a href="thread.html#2654">[ thread ]</a> + <a href="subject.html#2654">[ subject ]</a> + <a href="author.html#2654">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Wolfgang Bornath a écrit : +><i> +</I> +><i> 2010/10/25 Wayne Sallee <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">Wayne at waynesallee.com</A>>: +</I> +><i> > Wolfgang Bornath wrote on 10/25/2010 12:24 PM: +</I> +><i> >> +</I> +><i> >> I don't think it would help. There is (was) the tag "Doc" +</I>(or + +><i> >> similar) in Bugzilla which already marked the bug as +</I>something + +><i> >> related to documentation. Somebody who is concerned and +</I>ignored + +><i> >> that would also ignore a separate section and vice versa. +</I>I like + +><i> >> a more general approach involving the users and packagers +</I> +><i> >> likewise: +</I> +><i> > +</I> +><i> > Yea I think that having it all in the same bugzilla is best, +</I>though + +><i> > most newbees are not going to think of posting the issue in a +</I>bug + +><i> > report. Most newbees are going to think that bug reports are +</I>for + +><i> > the software not working right. So I think we need to somehow +</I>let + +><i> > the newbees know that bugzilla is the place to report +</I>improvements + +><i> > needed in rpm documentation. +</I> +><i> +</I> +><i> That's where the part is coming in which you cut from the quote of +</I>my + +><i> mail :) +</I> +What about "docuzilla", a place to treat documentation ? + +There is a fundamental difference between software bugs, and +documentation considerations. +Software bugs often do not have an obvious cause, and generally require +a level of technical + expertise that surpasses the average user. +For documentation, the problem, and its solution, are generally obvious +to an average user who understands + the language in question. +There is the problem, for the package description, of knowing what the +program does, but although + the developers can give a technical description, this often has to be +reworked to be in a form + the average non-technical user can understand. + +1) Documentation and text displayed in programs have to be localised. +Program logic does not. + (At least, beyond doing internationised coding.) + +2) Documentation has to be presented in a manner that non-technical +users can understand. + Program logic has to be presented in a manner that technical people +can follow. + +3) Problems with documentation is generally best corrected by +non-technical users. + Program logic is the domain of technical specialists. + +4) Documentation is best developed and corrected together, in +essentially the same process. + Program development and debugging are different processes, although +they can involve the + same people. + +Bugzilla could be used for both types of problems. Maybe just +separating the input and + correction interfaces would suffice, but it seems to me that we really +need to take a + different approach to the 2 types of problems. + +Here we are all technical people (not necessarily developers), and we +have no problem with bug +reports, etc. +But many documenters and translaters are essentially non-technical, and +they should have a good +sense of presentation to non-technical users in order to make credible +contributions. +And when they contribute corrections, they have no need of the +formalised process of bugzilla. +A correction is generally a quick glance, verify the context, and it's done. + +Whence my proposal for a separate section of bugzilla. More accessible +for non-technical users, +who thus risque to contribute more actively to Mageia. + +But if anyone has a better idea ... + +Another 2 cents :) + +- André + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002649.html">[Mageia-discuss] Suggestions +</A></li> + <LI>Next message: <A HREF="002640.html">[Mageia-discuss] Suggestions +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2654">[ date ]</a> + <a href="thread.html#2654">[ thread ]</a> + <a href="subject.html#2654">[ subject ]</a> + <a href="author.html#2654">[ 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> |