Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 6874 invoked from network); 2 May 2005 17:29:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 May 2005 17:29:37 -0000 Received: (qmail 94211 invoked by uid 500); 2 May 2005 17:30:18 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 94175 invoked by uid 500); 2 May 2005 17:30:18 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 94132 invoked by uid 99); 2 May 2005 17:30:17 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_30_40,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from web81309.mail.yahoo.com (HELO web81309.mail.yahoo.com) (206.190.37.84) by apache.org (qpsmtpd/0.28) with SMTP; Mon, 02 May 2005 10:30:17 -0700 Message-ID: <20050502172844.14317.qmail@web81309.mail.yahoo.com> Received: from [32.97.110.142] by web81309.mail.yahoo.com via HTTP; Mon, 02 May 2005 10:28:44 PDT Date: Mon, 2 May 2005 10:28:44 -0700 (PDT) From: Susan Cline Subject: Re: [RESULT] [VOTE] accept derby client contribution To: Derby Development In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1948560353-1115054924=:14230" X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --0-1948560353-1115054924=:14230 Content-Type: text/plain; charset=us-ascii Hi Satheesh, Okay, I'll modify the Papers tab to include a Derby Network Client section and add a link to the functional spec which is in raw html, unless you want to format it in forrest.xml. My feeling is whoever contributes a paper should take the responsibility to format it in the desired way prior to asking someone to update the site, just like patches need to be in a specific format prior to submission. Susan Satheesh Bandaram wrote: Hi Susan, Thanks for taking this up. I am OK with your suggestion. Should it be forrest generated or posted as is? May be we could put the current version for now and then modify it later? ;-) Satheesh Susan Cline wrote: Hi Satheesh, I can get this ready for Jean to commit. I was thinking it could go under the 'Papers' tab, http://incubator.apache.org/derby/papers/index.html, and we could create a new category called 'Derby Network Client'. It wouldn't be appropriate under the 'Derby Engine' section. Or, we could have a new 'Functional Spec' category where any future Functional Spec for anything could go as well. Do either of those sound okay? If not, please suggest where you would like the functional spec to go. Susan Satheesh Bandaram wrote: Submitted Derby client source to trunk. Post any problems you notice with Derby client. Enjoy! Please use the functional spec for usage. I will work with Jean to host it at Derby website. Satheesh --0-1948560353-1115054924=:14230 Content-Type: text/html; charset=us-ascii
Hi Satheesh,
 
Okay, I'll modify the Papers tab to include a Derby Network Client section and add a link to the functional spec which is in raw html, unless you want to format it in forrest.xml.
 
My feeling is whoever contributes a paper should take the responsibility to format it in the desired way prior to asking someone to update the site, just like patches need to be in a specific format prior to submission.
 
Susan
 
Satheesh Bandaram <satheesh@Sourcery.Org> wrote:
Hi Susan,

Thanks for taking this up. I am OK with your suggestion. Should it be forrest generated or posted as is? May be we could put the current version for now and then modify it later? ;-)

Satheesh

Susan Cline wrote:
Hi Satheesh,
 
I can get this ready for Jean to commit.
 
I was thinking it could go under the 'Papers' tab, http://incubator.apache.org/derby/papers/index.html,
and we could create a new category called 'Derby Network Client'.  It wouldn't be
appropriate under the 'Derby Engine' section.  Or, we could have a new 'Functional Spec'
category where any future Functional Spec for anything could go as well.
 
Do either of those sound okay?  If not, please suggest where you would like the functional
spec to go.
 
Susan

Satheesh Bandaram <satheesh@Sourcery.Org> wrote:
Submitted Derby client source to trunk. Post any problems you notice
with Derby client.

Enjoy! Please use the functional spec for usage. I will work with Jean
to host it at Derby website.

Satheesh
--0-1948560353-1115054924=:14230--