Return-Path: Delivered-To: apmail-jcp-open-archive@www.apache.org Received: (qmail 94817 invoked from network); 16 Dec 2005 20:06:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Dec 2005 20:06:11 -0000 Received: (qmail 79105 invoked by uid 500); 16 Dec 2005 20:06:11 -0000 Delivered-To: apmail-jcp-open-archive@apache.org Received: (qmail 79071 invoked by uid 500); 16 Dec 2005 20:06:10 -0000 Mailing-List: contact jcp-open-help@apache.org; run by ezmlm Precedence: bulk Reply-To: jcp-open@apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list jcp-open@apache.org Received: (qmail 79062 invoked by uid 99); 16 Dec 2005 20:06:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2005 12:06:10 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [64.253.103.116] (HELO kongo.flamefew.net) (64.253.103.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2005 12:06:09 -0800 Received: by kongo.flamefew.net (Postfix, from userid 1000) id C793623E72; Fri, 16 Dec 2005 15:05:44 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by kongo.flamefew.net (Postfix) with ESMTP id C61E923E70 for ; Fri, 16 Dec 2005 15:05:44 -0500 (EST) Date: Fri, 16 Dec 2005 15:05:44 -0500 (EST) From: Henri Yandell X-X-Sender: hen@kongo To: jcp-open@apache.org Subject: Re: thoughts on new site In-Reply-To: Message-ID: References: <43A07F11.5080600@apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On Wed, 14 Dec 2005, Geir Magnusson Jr. wrote: > > On Dec 14, 2005, at 12:22 PM, Brett Porter wrote: > > Yes, we do need a heartbeat from the EG reps. I don't want to see that the +1 to the heartbeat. a) it's good to know for you and the board, b) it's good to know for PR (show off our jcp involvement) and c) it's good to know for asf committers (make them aware of the maturation of a jsr). > EG rep is required to report all technical status - that's really out of > scope for the ASF-level interest, and if people are interested, they should Report on events I'd say (wonder where I get that from :) ). So when they move to a new status in the JSR process, or there are people problems to report then. > As for my report to the board, this is a new thing and I'll be doing this > month (I moved it to Dec from last month). Publishable? Or likely to often be discussing private issues. -- JSR-162 is on the licsnsed page twice. Should we be linking to the projects that license a TCK? Also a section that links to the projects that implement a JSR? Probably something special and prominent for official reference implementations. Hen