Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of plinskey@bea.com designates
 63.96.176.25 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: should I make some changes to the JIRA configuration?
Date: Mon, 31 Jul 2006 20:24:46 -0700
Message-ID: <7D856CDFE035FF45A0420ACBD71BDD6301A3A5A3@repbex02.amer.bea.com>
In-Reply-To: <9e3862d80607312022p700e616ah7af9113d7480f160@mail.gmail.com>
Thread-Topic: should I make some changes to the JIRA configuration?
Thread-Index: Aca1Gdbt7lBGv06qTC6adfazCtLG0AAADBdQ
From: "Patrick Linskey" <plinskey@bea.com>
To: <open-jpa-dev@incubator.apache.org>

Yes and yes, I'd say.

-Patrick

--=20
Patrick Linskey
BEA Systems, Inc.=20=20

> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]=20
> Sent: Monday, July 31, 2006 8:23 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: should I make some changes to the JIRA configuration?
>=20
> Hi,
>=20
> Upon not seeing OPENJPA-3 turn up on the dev list I took a=20
> look at the notification scheme.
>=20
> Currently:
> - notifications for all events are sent to those in=20
> openjpa-developers. shall I change that to mail=20
> open-jpa-dev@incubator.apache.org instead?
>=20
> - the permissions give a couple of unnecessary powers to=20
> jira-users (they can be assigned issues which is ok, but they=20
> can also resolve issues they didn't open and view who has=20
> voted/watched an issue), and the rest either go to=20
> jira-administrators or nobody. Shall I Set this up in a more=20
> standard configuration for openjpa-developers?
>=20
> Cheers,
> Brett
>=20
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.