1 |
On Thursday, March 17, 2011 03:41:34 Jan Kundrát wrote: |
2 |
> On 03/17/11 08:10, Joshua Saddler wrote: |
3 |
> > On Thu, 17 Mar 2011 00:43:39 -0400 Mike Frysinger wrote: |
4 |
> >> i cant see any value in having "Documentation" and "Doc Other" be |
5 |
> >> separate products. let's simply merge the two Component lists and |
6 |
> >> be done with it. |
7 |
> > |
8 |
> > No. The GDP is sick of people reporting non-/doc/ bugs |
9 |
> > to us. Everything filed against /proj/ comes to mind. "Doc Other" is a |
10 |
> > better category, as it means we don't have to do as much work |
11 |
> > reassigning stuff that should never have been assigned to us in the |
12 |
> > first place. I'm okay with renaming it if "doc other" isn't specific |
13 |
> > enough, but I want to keep the separate categories. |
14 |
> |
15 |
> I agree with maintaining the three categories. What about a |
16 |
> "Project-specific documentation on the web" for the "Doc Other", though? |
17 |
|
18 |
it isnt just product-specific documentation, and i'm trying to make things |
19 |
clearer/simpler, not more confusing |
20 |
|
21 |
> > Translations don't always use the [lang] prefix, though, and it's one |
22 |
> > more dropdown level they'd have to drill through if the separate |
23 |
> > component was removed. We already can't rely on people using |
24 |
> > subcategories and dropdowns as it is; adding more isn't a good idea. |
25 |
> |
26 |
> I guess it'd be hard to search just for bugs affecting /doc/en/ (which |
27 |
> is what the majority of the non-translating GDP cares about) if there |
28 |
> was just a prefix. Even if it was in some category, that'd just make it |
29 |
> hard for translators to list bugs in their specific language. |
30 |
|
31 |
if the component was trans/[lang], then everything you mention here would |
32 |
still be doable |
33 |
-mike |