Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 68835 invoked from network); 7 May 2007 10:31:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 May 2007 10:31:37 -0000 Received: (qmail 11480 invoked by uid 500); 7 May 2007 10:31:43 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 11287 invoked by uid 500); 7 May 2007 10:31:43 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 11267 invoked by uid 99); 7 May 2007 10:31:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2007 03:31:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2007 03:31:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 97402714066 for ; Mon, 7 May 2007 03:31:15 -0700 (PDT) Message-ID: <14770991.1178533875617.JavaMail.jira@brutus> Date: Mon, 7 May 2007 03:31:15 -0700 (PDT) From: "Nadya Morozova (JIRA)" To: commits@harmony.apache.org Subject: [jira] Commented: (HARMONY-459) OPEN Spec Submission MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HARMONY-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494013 ] Nadya Morozova commented on HARMONY-459: ---------------------------------------- the file has been here for a while. do you think we can do something about it and close the issue? i can suggest several solutions: - forget about the OPEN standard for now, store the spec somewhere on the server in an archived space - review the spec: decide whether all architectural suggestions in it are still relevant/correct/up-to-date, make changes as required - publish the doc on the website: we can call it a 'dream/prospect' or a model we're moving to or something else. the document seems of great potential value, and it'd be a shame to lose an excellent opportunity that it's offering. what do you say? nadya > OPEN Spec Submission > -------------------- > > Key: HARMONY-459 > URL: https://issues.apache.org/jira/browse/HARMONY-459 > Project: Harmony > Issue Type: New Feature > Components: Misc > Environment: All > Reporter: Rana Dasgupta > Attachments: openspec.zip > > > Intel Submission of OPEN ( Open Pluggable Extensible Interface ) specification for componentized JVM and Classlibrary->VM interface development -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.