Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.211 as permitted sender)
From: Dave Fisher <dave2wave@comcast.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Fwd: Moving OOo Bugzilla Database into ASF Infrastructure
Date: Thu, 16 Jun 2011 11:42:54 -0700
References: <4DFA43DD.3060201@apache.org>
To: ooo-dev@incubator.apache.org
Message-Id: <7EB16D0F-69D2-4583-A8D2-39DD157FA935@comcast.net>
Mime-Version: 1.0 (Apple Message framework v1084)

Hi -

I queried the infrastructure list about what is possible, and Mark =
Thomas replied. He might have a preference based on the details of the =
current, customized OOo issue tracker.

Whoever knows the details, please reply.

Regards,
Dave

Begin forwarded message:

> From: Mark Thomas <markt@apache.org>
> Date: June 16, 2011 10:56:45 AM PDT
> To: Dave Fisher <dave2wave@comcast.net>
> Cc: Apache Infrastructure <infrastructure@apache.org>
> Subject: Re: Moving OOo Bugzilla Database into ASF Infrastructure
>=20
> On 16/06/2011 18:11, Dave Fisher wrote:
>> Hi Guys,
>=20
> Hi. I'm replying as I'm the person who currently looks after our issue
> trackers.
>=20
>> One of the big issues in moving OOo into the podling is getting an =
Issue tracker functional.
>>=20
>> There are over 100,000 issues.
>=20
> That is a reasonable number. Currently the ASF Jira has ~200k, main BZ
> ~50k and SABZ ~7k. Another 100k shouldn't be an issue unless that
> database is huge.
>=20
>> The database is currently active.
>>=20
>> The most critical migration factor is preserving the Bugzilla IDs.
>=20
> No problem. Whatever route we take, that is do-able.
>=20
>> There is no preference one way or another on JIRA vs. Bugzilla.
>=20
> I may have a preference depending on the answer to the following =
questions:
>=20
> How much customization has been applied to the OOo bugzilla. To put it
> another way, how painful is it going to be up upgrade to BZ 4.0.x? If =
it
> is going to be painful is there anyone from OOo that is willing to do
> the work and support it going forward?
>=20
> What database is currently used for the BZ instance?
>=20
> How big is a current full backup?
>=20
>> OOo issue tracker link - =
http://qa.openoffice.org/issue_handling/pre_submission.html
>>=20
>> Language is an issue. A user facing bug tracker needs to allow for =
other languages =
-http://qa.openoffice.org/issue_handling/submission_gateway.html
>=20
> I believe BZ and Jira both support that. Is there anything you need =
that
> isn't available out of the box?
>=20
>> One suggestion was to have a separate Bugzilla for OOo which would =
automatically preserve the IDs. I notice that SpamAssassin has a =
separate bugzilla.
>=20
> That is certainly an option. Importing into Jira is the other.
>=20
>> One negative to JIRA expressed on the list is that someone is labeled =
as "Project Lead". I've used JIRA at work for 9 years. and we could have =
an email list be the lead can't we?
>=20
> No. The ASF does not permit mailing lists to be used that way due to
> security concerns with password resets and public mailing lists. There
> are simple ways around this.
>=20
>> What does Infrastructure prefer? Are there already solutions =
available?
>=20
> That depends on the answer to the questions above.
>=20
> Mark
>=20
>=20