[ooo-build] Infrastructure

[Kohei Yoshida]

Hi Rail,

On Wed, 2009-06-10 at 18:56 +0400, Rail Aliev wrote:
> Hi all,
> 
> I would like to propose and discuss the following two issues.
> 
> 1. Public bug tracking system for ooo-build.
> 
> Currently "apply" file contains some "links" to Novell's bugzilla, some
> of them accessible only for registered users, some only by Novell's
> employees. It's very hard to review such patches.

FYI, Those bugs that are only accessible to Novell employees are
customer-related bugs.  They are not public because they contain
sensitive information about the customer we are not allowed to disclose.
So, I don't think we can realistically open up those bugs to the public,
whether it's anonymous or not.

(Actually I didn't know that some bugs are accessible only to the
registered users...  I always thought that all public bugs were
accessible anonymously, but I may be wrong...)

Having said that, there shouldn't be too many of them referenced in the
apply file because we try to keep as many bugs public as we possibly
can.  When handling non-public bugs, I myself try to be as descriptive
as I can in the commit log, or file it upstream and describe it therein,
to work around the situation.

In the future, I'd like to see our bug tracking system separated from
the Novell bugzilla, and perhaps to the freedesktop one.  That would
keep our non-public bugs away.  In fact, I have already proposed that to
my fellow Novellians, and the response was all favorable.  So, I'm
pretty sure that's the direction we are heading. :-)

> It'll be great if all of the mentioned bugs may be accessed anonymously
> (by bts bots, for example) and linked to/from upstream/downstream
> (OOo/distros).

I believe we link upstream/downstream as much as we can, though I
imagine occasionally it gets forgotten by accident. 

> 
> 
> 2. Localization work flow.
> 
> ooo-builds adds/modifies the UI, so we have ~500 messages which are not
> translated in most languages. Distros suffer from this.
> 
> Localization work flow should be clearer and maybe use some web
> interface.

Yup, good point.  Ideally we should have a localization framework for
stuff that needs translation.  Do you, or anybody else who's reading
this, have any suggestions on how to improve our localization work flow?
I would also like to throw in the help content here.  That one also
suffers from a similar problem.

Kohei

-- 
Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc.
<kyoshida at novell.com>