Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dennis.hamilton@acm.org
 designates 75.98.160.130 as permitted sender)
Reply-To: <dennis.hamilton@acm.org>
From: "Dennis E. Hamilton" <dennis.hamilton@acm.org>
To: <ooo-dev@incubator.apache.org>
References: <4E687EB9.1070206@hdsnet.hu> <4E68C630.70001@wtnet.de>
In-Reply-To: <4E68C630.70001@wtnet.de>
Subject: RE: [DISCUSS] Bug reporting, handling rules
Date: Thu, 8 Sep 2011 11:03:31 -0700
Organization: NuovoDoc
Message-ID: <011a01cc6e51$9ed83e80$dc88bb80$@acm.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQDI14OMRfeFtvYQJYpsGdA5Wu6EIwLEpXPvlzTK5XA=
Content-Language: en-us

There's some great material there.  I did not review closely.

It is my thinking that this material should be preserved in an =
appropriate way.

I agree that the top level should make it easy to file a bug and offer =
links to progressively-deeper detail elsewhere.  Users with interest in =
knowing more can go there; others need not be distracted by too much =
information in their way.

Many of the current links don't work and no discussion has occurred on =
what would replace "QA team" and "QA project" if anything.  Also, is =
there a counterpart of the QA review of issue postings in the Apache OOo =
Bugzilla handling?  Should there be?

Meanwhile, there is a disconnect between that material and the new =
Bugzilla. =20

Since these pages and OpenOffice.org are going to be there for an =
indeterminate time, maybe it is good to look into being more deliberate, =
seeking migration progressions that don't leave so many broken or =
inappropriate connections. =20

It is my thinking that some survey of interdependencies is appropriate =
so that damage-control can be injected and the users are not disturbed.

QUESTION: Is it possible to perform maintenance on these pages where =
they now are or must change of hosting occur so that repairs can be =
made?

 - Dennis

-----Original Message-----
From: Marcus (OOo) [mailto:marcus.mail@wtnet.de]=20
Sent: Thursday, September 08, 2011 06:42
To: ooo-dev@incubator.apache.org
Subject: Re: [DISCUSS] Bug reporting, handling rules

Am 09/08/2011 10:37 AM, schrieb Reizinger Zolt=C3=A1n:
> Hi all,
>
> Start again, the my earlier try was alienated.
>
> As a first builds starts, and OOo Bugzilla migrated to Apache, needs =
to
> think about how we will use it.
>
> On OOo QA site can be found three page which says about issues/bug
> issuing "rules" which the OOo project followed, and Bugzilla was
> customized accordingly:
> http://qa.openoffice.org/issue_handling/project_issues.html
> http://qa.openoffice.org/issue_handling/bug_writing_guidelines.html
> http://qa.openoffice.org/issue_handling/basic_rules.html
>
> This time the bugzilla migrated, could stick to these rules, which
> worked in most cases.
>
> We want to change it?
>
> It is a time to start to think about.
>
> Regards,
> Zoltan

IMHO 3 pages are 2 too much. A single page that describes the howto=20
should be enough, especially for non-dev's. Normally these just want to=20
forward a bug, feature request, etc. to us.

BTW:
I don't find a sentence that only English language is accepted to=20
describe the problem. Surely a chance to add this.

Marcus