Hi,

...
> 
> > 
> > We would create an alias like go-oo-b...@openoffice.org, and anything
> > that you identify as a go-oo only bug, you'd just reassign to this
> > alias, instead of closing it as 'invalid'.  We would take care of the
> > proper assignment of the bug (all the go-oo people have an IZ account
> > too), and its solution.
> > 
> > What do you think, please?
> 
> That certainly sounds like a good idea. Perhaps a keyword in IZ as well
> like "go-oo specific" would also be useful. I'm wondering what others
> here think about it too. 

I'd prefer the alias user as Kendy suggested. It's quite easy to search 
issues that are assigned to this alias (or withit in cc). You can also
follow the alias ...

Keywords at the other hand should be a limited set - a rule that does
almost not exist anymore in OOo Issue tracker. We have lots of
not (actively) used keywords that some of us found usefull at some
time .. but then never erver used it anymore.
Don't create yet another keword that nobody is going to use ;)


> This being said, we are not going to solve the need for a direct
> communication on issues between OOo and its linux packagers, so the
> proposal that we worked out with Ubuntu is still on the table which
> is that we open a category for Linux distros, and eventually merge the
> Go-OO IZ with the OOo IZ. 

Merging the Issue trackers makes only sense if you merge the source code.
Otherwise you would not really reduce the chaos, you'll only paint it with
a limited set of colors.

(This does not mean that I see a "one and only" source repository for
OOo in near or mid future. There are several reasons to have patches
outside upstream repository - and legal reasons are not the only one)


regards,

André



-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org
For additional commands, e-mail: dev-h...@qa.openoffice.org

Reply via email to