From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110107/001995.html | 135 ++++++++++++++++++++++++++++++++ 1 file changed, 135 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110107/001995.html (limited to 'zarb-ml/mageia-dev/20110107/001995.html') diff --git a/zarb-ml/mageia-dev/20110107/001995.html b/zarb-ml/mageia-dev/20110107/001995.html new file mode 100644 index 000000000..8281076f8 --- /dev/null +++ b/zarb-ml/mageia-dev/20110107/001995.html @@ -0,0 +1,135 @@ + + + + [Mageia-dev] New bugzilla proposal + + + + + + + + + +

[Mageia-dev] New bugzilla proposal

+ andre999 + andr55 at laposte.net +
+ Fri Jan 7 06:19:59 CET 2011 +

+
+ +
Michael Scherer a écrit :
+>
+> Le jeudi 06 janvier 2011 à 17:52 +0100, Dexter Morgan a écrit :
+>> On Thu, Jan 6, 2011 at 5:39 PM, Michael Scherer<misc at zarb.org>  wrote:
+>>> Le jeudi 06 janvier 2011 à 17:05 +0100, Dexter Morgan a écrit :
+>>>> After reading the various mails i think we coulddo like this
+>>>>
+>>>>
+>>>> Product : Mageia
+>>>>
+>>>> Components:
+>>>>
+>>>>   - Documentation
+>>>>   - Installation
+>>>>   - RPM packages
+>>>>   - New Packages requests
+>>>>   - Release Media
+>>>>   - Security
+>>>>   - Translations
+>>>
+>>> Could you explain what kind of bug would go in every category ?
+>>>
+>>> For exemple, translation would apply to what kind of bug, same goes for
+>>> documentation ?
+>>
+>>
+>>> If we have a separate documentation, wouldn't it be more logical to have
+>>> it as a product, with various subcomponent like each manual ?
+>>
+>> yes good vision, we could remove documentation then.
+>>
+>>> For translation, shouldn't it be attached to either a software, a
+>>> website, a document than be separate ?
+>>
+>> so what do you suggest ? to add Translation as a product ? or to remove it ?
+>> i was more thinking of the translation of the softwares here.
+>
+> I would remove it, and put it with whatever you call "software".
+
+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 :
+
+1) problem with documentation (and not function)
+These bugs would be best corrected by those with good documentation 
+skills, not necessarily the average programmmer.
+
+2) problem with translation (and not function)
+These bugs would be best corrected by technical translators for the 
+language in question.  Again, not necessarily the average programmer.
+
+One or both could be checked for any particular bug.
+Thus facilitating a search for bugs based on these flags.
+Those wanting to ignore such bugs could equally avoid seeing them.
+
+This would tend to facilitate the correction of such bugs, which tend to 
+be lost and not corrected for long periods of time.  (At least that is 
+the case with Mandriva, and much other free/open source software.)
+(e.g.1:  A number of French translations.)
+(e.g.2:  Much documentation is essentially useless to the uninitiated.)
+
+However, in my view, documentation and translation bugs would also tend 
+to be reported by different people than those who would report function 
+bugs.
+So it would be useful if such flags were to appear on this initial page, 
+as well on the main bug entry page.
+Something like
+"This bug concerns [ ]documentation ... [ ]translation ..."
+With whatever other factors, such as security, on which we decide to focus.
+With whatever boxes are checked carried over automatically to the main 
+bug entry page.
+
+another 2 cents :)
+
+André
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1