Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 59056 invoked from network); 8 Aug 2007 03:55:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Aug 2007 03:55:05 -0000 Received: (qmail 98808 invoked by uid 500); 8 Aug 2007 03:55:04 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 98777 invoked by uid 500); 8 Aug 2007 03:55:04 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 98761 invoked by uid 99); 8 Aug 2007 03:55:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 20:55:04 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [216.86.168.179] (HELO mxout-04.mxes.net) (216.86.168.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2007 03:54:56 +0000 Received: from [166.129.246.153] (unknown [166.129.246.153]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id B6505A3223; Tue, 7 Aug 2007 23:53:48 -0400 (EDT) In-Reply-To: <763AFC1F-E412-4A61-836C-841007E4B0A8@SUN.com> References: <763AFC1F-E412-4A61-836C-841007E4B0A8@SUN.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7B62723A-A9C8-4FF5-B6BF-04FA1C45F197@pobox.com> Cc: users@openjpa.apache.org Content-Transfer-Encoding: 7bit From: "Geir Magnusson Jr." Subject: Re: [DISCUSS] JPA 2.0 expert group representation Date: Tue, 7 Aug 2007 23:53:44 -0400 To: dev@openjpa.apache.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Apache can still have a formal representation on the EG. We do feel the technology is good - the problem is that Sun is, in our opinion, in violation of the JSPA and therefore shouldn't be able to lead any new JSRs until the problem is fixed. But don't let that stop you from participating. geir On Aug 7, 2007, at 9:05 PM, Craig L Russell wrote: > Does the OpenJPA community want Apache to have representation on > the JPA 2.0 EG? > > Yes, Apache voted no on JSR 317 on the principle that the proposed > Specification Lead is in violation of the JSPA by not offering a > TCK license without FOU restrictions for Java EE 5. But the OpenJPA > community can decide to try to influence the specification that > directly affects us. > > Individuals from companies on a JCP Expert Group have access to > email discussions that are distributed internally via a "lurker" > alias. Feedback is sent through an individual representative from > that company to the Expert Group. > > There would be an advantage for OpenJPA community members who are > not privy to an internal lurker alias, to be able to participate in > the discussion. > > The Specification Lead for JSR 317 would set the participation > rules, which under JCP can include Non Disclosure Agreements. Any > OpenJPA community member who wanted to participate might be bound > by an agreement not to disclose information from the Expert Group > discussion. > > In order to implement this, we might need a closed Apache-JPA mail > alias for discussion and an Expert Group representative to forward > comments from the closed alias to the expert group. > > Would any OpenJPA community members be interested in participating > in the JSR-317 Expert Group under these conditions? > > Please send comments to both dev and users aliases. > > Craig Russell > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > 408 276-5638 mailto:Craig.Russell@sun.com > P.S. A good JDO? O, Gasp! >