diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110107/002001.html')
-rw-r--r-- | zarb-ml/mageia-dev/20110107/002001.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110107/002001.html b/zarb-ml/mageia-dev/20110107/002001.html new file mode 100644 index 000000000..e534c9266 --- /dev/null +++ b/zarb-ml/mageia-dev/20110107/002001.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] New bugzilla proposal + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3C4D274407.6040901%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002000.html"> + <LINK REL="Next" HREF="002003.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] New bugzilla proposal</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3C4D274407.6040901%40laposte.net%3E" + TITLE="[Mageia-dev] New bugzilla proposal">andr55 at laposte.net + </A><BR> + <I>Fri Jan 7 17:49:11 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002000.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI>Next message: <A HREF="002003.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2001">[ date ]</a> + <a href="thread.html#2001">[ thread ]</a> + <a href="subject.html#2001">[ subject ]</a> + <a href="author.html#2001">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frederic Janssens a écrit : +><i> +</I>><i> On Fri, Jan 7, 2011 at 06:19, andre999<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote: +</I>>><i> +</I>>><i> As for documentation and translations, a while back I suggested a similar separation, but on reflection I think it would be more useful to have flags : +</I>>><i> +</I>>><i> 1) problem with documentation (and not function) +</I>>><i> These bugs would be best corrected by those with good documentation skills, not necessarily the average programmmer. +</I>>><i> +</I>>><i> 2) problem with translation (and not function) +</I>>><i> These bugs would be best corrected by technical translators for the language in question. Again, not necessarily the average programmer. +</I>>><i> +</I>>><i> One or both could be checked for any particular bug. +</I>>><i> Thus facilitating a search for bugs based on these flags. +</I>>><i> Those wanting to ignore such bugs could equally avoid seeing them. +</I>>><i> +</I>>><i> This would tend to facilitate the correction of such bugs, which tend to be lost and not corrected for long periods of time. +</I>>><i> (At least that is the case with Mandriva, and much other free/open source software.) +</I>>><i> (e.g.1: A number of French translations.) +</I>>><i> (e.g.2: Much documentation is essentially useless to the uninitiated.) +</I>>><i> +</I>>><i> However, in my view, documentation and translation bugs would also tend to be reported by different people than those who would report function bugs. +</I>>><i> So it would be useful if such flags were to appear on this initial page, as well on the main bug entry page. +</I>>><i> Something like +</I>>><i> "This bug concerns [ ]documentation ... [ ]translation ..." +</I>>><i> With whatever other factors, such as security, on which we decide to focus. +</I>>><i> With whatever boxes are checked carried over automatically to the main bug entry page. +</I>><i> +</I>><i> +</I>><i> I am working on a script intended to make it easyer to report bugs usefully. +</I>><i> +</I>><i> Technically, would these flags be new fields, +</I>><i> or standardized entries in the Keywords field, +</I>><i> such as NEEDINFO in the present Mandriva bugzilla ? +</I> +Just verified with bugzilla to make sure. + +Documentation and translations are listed as options under "components". +However any such bug could also be associated with another component, +such as "core packages" or "release media". +We could even have translation bugs of documentation. + +So it would seem better if these were independant flags, instead of options. +It that case they would be new fields. + +As for security, there are already 2 such flags, at the bottom of the +main bug entry page. (Under the title "privacy".) +Checking either of these flags will cause a bug to be hidden from most +users, as explained beside the check boxes. +(For this reason, it would be better to _not_ duplicate these particular +flags elsewhere.) + +see <A HREF="https://qa.mandriva.com/enter_bug.cgi?product=Mandriva">https://qa.mandriva.com/enter_bug.cgi?product=Mandriva</A> +Linux&format=guided + +Good luck with your script :) + +André +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002000.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI>Next message: <A HREF="002003.html">[Mageia-dev] New bugzilla proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2001">[ date ]</a> + <a href="thread.html#2001">[ thread ]</a> + <a href="subject.html#2001">[ subject ]</a> + <a href="author.html#2001">[ 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> |