blob: 5bb8686e575b91a345ba460b6781c3d99cd629b4 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<!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=%3CAANLkTikUSnXx6K%2BL%3DuKZDYuR5zqgZ2cZGTSOO2T%3Dhp3t%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001979.html">
<LINK REL="Next" HREF="001978.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] New bugzilla proposal</H1>
<B>Wolfgang Bornath</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3CAANLkTikUSnXx6K%2BL%3DuKZDYuR5zqgZ2cZGTSOO2T%3Dhp3t%40mail.gmail.com%3E"
TITLE="[Mageia-dev] New bugzilla proposal">molch.b at googlemail.com
</A><BR>
<I>Thu Jan 6 17:56:21 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="001979.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="001978.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1976">[ date ]</a>
<a href="thread.html#1976">[ thread ]</a>
<a href="subject.html#1976">[ subject ]</a>
<a href="author.html#1976">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>2011/1/6 Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>:
><i> Le jeudi 06 janvier 2011 à 17:05 +0100, Dexter Morgan a écrit :
</I>>><i> After reading the various mails i think we coulddo like this
</I>>><i>
</I>>><i>
</I>>><i> Product : Mageia
</I>>><i>
</I>>><i> Componments:
</I>>><i>
</I>>><i>  - Documentation
</I>>><i>  - Installation
</I>>><i>  - RPM packages
</I>>><i>  - New Packages requests
</I>>><i>  - Release Media
</I>>><i>  - Security
</I>>><i>  - Translations
</I>><i>
</I>><i> Could you explain what kind of bug would go in every category ?
</I>><i>
</I>><i> For exemple, translation would apply to what kind of bug, same goes for
</I>><i> documentation ?
</I>><i>
</I>><i> If we have a separate documentation, wouldn't it be more logical to have
</I>><i> it as a product, with various subcomponent like each manual ?
</I>
I think he is referring to errors in the documentation like wrong
screenshots or whatever. This could go into the rpm section, provided
that the official documentation will bne distributed as a package (as
in mandriva-doc-*)
><i> For translation, shouldn't it be attached to either a software, a
</I>><i> website, a document than be separate ?
</I>
This is more a philosophical question. If translation bugs are filed
in a separate category it makes it easy for the translators and normal
package section is not clogged by this.
Example: translation bugs could be generally triaged to i18n group if
in a separate category. If the translation bug of foo.rpm is in the
normal package category trieage team has to read the description to
find out that it is not a program/packager bug but a translation but,
then hand it to i18n.
--
wobo
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001979.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="001978.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1976">[ date ]</a>
<a href="thread.html#1976">[ thread ]</a>
<a href="subject.html#1976">[ subject ]</a>
<a href="author.html#1976">[ 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>
|
