From derby-dev-return-190-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Wed Sep 01 20:52:12 2004
Return-Path:
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 79988 invoked from network); 1 Sep 2004 20:52:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur-2.apache.org with SMTP; 1 Sep 2004 20:52:11 -0000
Received: (qmail 48869 invoked by uid 500); 1 Sep 2004 20:51:53 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 48723 invoked by uid 500); 1 Sep 2004 20:51:51 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help:
list-unsubscribe:
list-post:
List-Id: "Derby Development"
Reply-To: "Derby Development"
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 48578 invoked by uid 99); 1 Sep 2004 20:51:50 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=
X-Spam-Check-By: apache.org
Received-SPF: unknown (hermes.apache.org: error in processing during lookup of jta@bristowhill.com)
Received: from [66.75.162.133] (HELO ms-smtp-01-eri0.socal.rr.com) (66.75.162.133)
by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 01 Sep 2004 13:51:50 -0700
Received: from [192.168.2.51] (dt089n06.san.rr.com [204.210.25.6])
by ms-smtp-01-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id i81Kpk6j018612
for ; Wed, 1 Sep 2004 13:51:46 -0700 (PDT)
Message-ID: <41363662.2060908@bristowhill.com>
Date: Wed, 01 Sep 2004 13:51:46 -0700
From: "Jean T. Anderson"
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040819)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Derby Development
Subject: Derby document submission guidelines
References: <41348535.80906@bristowhill.com> <000a01c48f6c$220465d0$6501a8c0@brianxp> <41349AF6.6040604@bristowhill.com> <4134E2A0.9010907@bristowhill.com> <8D4190A2-FB95-11D8-A58D-000393B4C1D8@red-bean.com> <41350A80.9060005@bristowhill.com> <5EC8293A-FBBC-11D8-A58D-000393B4C1D8@red-bean.com>
In-Reply-To: <5EC8293A-FBBC-11D8-A58D-000393B4C1D8@red-bean.com>
X-Enigmail-Version: 0.85.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm starting a new thread based on the "Where I can get the Derby
design document?" thread.
I'd like to discuss guidelines for doc submissions to the Derby site,
then document them on the Derby web site to encourage submissions, and
include information for committers on how to get docs into forrest so
I don't become the log jam getting content onto the site.
But there's a ways to go before I could begin to submit suggestions
for a VOTE.
My starting point is the http://db.apache.org/source.html page, which
has guidelines for doc and code submissions.
Based on the earlier "Where I can get the Derby design document?"
thread, I think we want to ask contributors to include the document in
the body of the document, not as an attachment or an URL. Although not
stated specifically in the db.apache.org guidelines, I think it would
be reasonable for document submissions to have a subject starting with
[DOC] -- the wording on that page specifically covers [PATCH].
But I have one main question. The http://db.apache.org/source.html
page says "Any code, document, or binary that is committed to the
Project's repositories, but not being donated to the ASF, must be
clearly marked as such. All contributors should have a Contributor
License Agreement on file."
So, I'd just like to clarify this. If somebody figures out how to do
something cool with Derby and he/she writes up a short white paper and
posts it to derby-dev or derby-user for inclusion on the web site,
must he/she have a CLA on file for me to add it to the repository?
Sorry to ding the list with questions that smack of legalise, but it'd
probably be best to work the details out now, then make it easy for
people to contribute content.
~ -jean
p.s. my key is uploaded to www.keyserver.net. I'll additionally upload
to the servers Ken Coar mentioned.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBNjZhF0L6u5lYbCYRAhpsAKCTZT1xEitfCIAvGxPROrTYU/apLQCfYBXY
EtK8ijmmCmwlaM5PdarHVKo=
=1+hU
-----END PGP SIGNATURE-----