Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 72318 invoked from network); 4 Jun 2006 15:28:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Jun 2006 15:28:22 -0000 Received: (qmail 88539 invoked by uid 500); 4 Jun 2006 15:28:22 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 88507 invoked by uid 500); 4 Jun 2006 15:28:22 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 88498 invoked by uid 99); 4 Jun 2006 15:28:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Jun 2006 08:28:21 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of plinskey@bea.com designates 63.96.162.5 as permitted sender) Received: from [63.96.162.5] (HELO ussjmh01.bea.com) (63.96.162.5) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Jun 2006 08:28:20 -0700 Received: from ussjfe01.amer.bea.com (ussjfe01b.bea.com [172.16.120.57]) by ussjmh01.bea.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id k54FRsBk022314 for ; Sun, 4 Jun 2006 08:27:59 -0700 Received: from repbex02.amer.bea.com ([10.160.26.99]) by ussjfe01.amer.bea.com with Microsoft SMTPSVC(5.0.2195.6713); Sun, 4 Jun 2006 08:27:03 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: java.util.concurrent Date: Sun, 4 Jun 2006 08:26:58 -0700 Message-ID: <7D856CDFE035FF45A0420ACBD71BDD63013733D5@repbex02.amer.bea.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: java.util.concurrent Thread-Index: AcaHGdvnoIjO7B2ORAK/IsUPHTb2nAA0Nymw From: "Patrick Linskey" To: X-OriginalArrivalTime: 04 Jun 2006 15:27:03.0181 (UTC) FILETIME=[54869BD0:01C687EB] X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.6.4.55409 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > I don't think the fact your using BEA e-mail is an issue.=20=20 > Its really the legal content of the epilogue that I think has=20 > people concerned. Understood. > Although someone in the ASF could probably do something I=20 > think you'd be the first person they did it for :) I think=20 > modifying the contents of anyone's e-mail is a bad precedent. See below. > I'm in the same boat as you as my IBM account generated lots=20 > of additional attatchements that people asked me to remove.=20=20 > I cannot configure Notes to do that so I changed to my=20 > personal account.=20=20 Based on my understanding, many people (yourself included) have run into this problem. Seems to me as though the Apache community doesn't like this, and forces all incoming developers to change the way they work in order to better fit the Apache Way. Seems awfully intrusive from a new-employee standpoint. It seems to me like it's in Apache's best interest to either collectively not care about this sort of thing, or help provide a fix on their side, rather than potentially asking every incoming developer to change the way they work. > Also, If I left IBM I would most likely=20 > continue working on the projects that I'm currently part of=20 > so a private e-mail allows me that freedom. Well, not really -- I think that it's the ICLA and the employment laws in the US that allow you to continue working on projects after leaving IBM. I'd be surprised if Apache would not allow people with new email addresses to participate in projects. -Patrick _______________________________________________________________________ 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.