| 1 |
On Thursday, March 17, 2011 03:10:06 Joshua Saddler wrote: |
| 2 |
> On Thu, 17 Mar 2011 00:43:39 -0400 Mike Frysinger wrote: |
| 3 |
> > i cant see any value in having "Documentation" and "Doc Other" be |
| 4 |
> > separate products. let's simply merge the two Component lists and |
| 5 |
> > be done with it. |
| 6 |
> |
| 7 |
> No. The GDP is sick of people reporting non-/doc/ bugs |
| 8 |
> to us. Everything filed against /proj/ comes to mind. "Doc Other" is a |
| 9 |
> better category, as it means we don't have to do as much work |
| 10 |
> reassigning stuff that should never have been assigned to us in the |
| 11 |
> first place. I'm okay with renaming it if "doc other" isn't specific |
| 12 |
> enough, but I want to keep the separate categories. |
| 13 |
|
| 14 |
considering you're getting this now, i dont see how it'd be any different if |
| 15 |
things were merged. if you really dont like bugs being assigned directly, |
| 16 |
then simply make the default go to the wranglers and let them sort it out. |
| 17 |
|
| 18 |
if anything, the current poor productization is causing people to just go to |
| 19 |
Documentation and select anything they like which makes them all go to docs- |
| 20 |
team@g.o. |
| 21 |
|
| 22 |
personally, i dont think "i dont like bugs being assigned to me" is a good |
| 23 |
enough reason to force this confusion onto end users. |
| 24 |
|
| 25 |
> > i would like to see "Doc Translations" merged in too, but i'm not |
| 26 |
> > sure how much this will impact things. does every lang really need |
| 27 |
> > its own component ? in most translation bugs i see, people start |
| 28 |
> > the summary off with "[LANG]" anyways. so if that's what the |
| 29 |
> > standard is and people are fine with it, seems like we can merge |
| 30 |
> > the translation product into the main Documentation product and |
| 31 |
> > give it a single "translations" component. -mike |
| 32 |
> |
| 33 |
> Translations don't always use the [lang] prefix, though, and it's one |
| 34 |
> more dropdown level they'd have to drill through if the separate |
| 35 |
> component was removed. We already can't rely on people using |
| 36 |
> subcategories and dropdowns as it is; adding more isn't a good idea. |
| 37 |
|
| 38 |
no it isnt. current setup: |
| 39 |
Product: Translations -> Component: [lang] |
| 40 |
proposed setup: |
| 41 |
Product: Documentation -> Component: Translations |
| 42 |
or even: |
| 43 |
Product: Documentation -> Component: trans/[lang] |
| 44 |
-mike |
Archives