From open-jpa-dev-return-446-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Aug 22 15:41:58 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 59661 invoked from network); 22 Aug 2006 15:41:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Aug 2006 15:41:57 -0000 Received: (qmail 30550 invoked by uid 500); 22 Aug 2006 15:41:57 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 30516 invoked by uid 500); 22 Aug 2006 15:41:57 -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 30507 invoked by uid 99); 22 Aug 2006 15:41:57 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 08:41:57 -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.176.25 as permitted sender) Received: from [63.96.176.25] (HELO uslcmh01.bea.com) (63.96.176.25) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Aug 2006 08:41:56 -0700 Received: from ussjfe01.amer.bea.com (ussjfe01b.bea.com [172.16.120.57]) by uslcmh01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id k7MFfR8g003046 for ; Tue, 22 Aug 2006 11:41:32 -0400 Received: from repbex02.amer.bea.com ([10.160.26.99]) by ussjfe01.amer.bea.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 22 Aug 2006 08:41:31 -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: status of OpenJPA documentation Date: Tue, 22 Aug 2006 08:39:57 -0700 Message-ID: <7D856CDFE035FF45A0420ACBD71BDD6301C7528E@repbex02.amer.bea.com> In-Reply-To: <9330761F-86C1-462A-A07E-834714046D38@apache.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: status of OpenJPA documentation Thread-Index: AcbFeRqAHtHCyZnXRcOezTCFzy8qQwAh7rNQ From: "Patrick Linskey" To: X-OriginalArrivalTime: 22 Aug 2006 15:41:31.0047 (UTC) FILETIME=[7072B370:01C6C601] X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.8.10.91432 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > My original idea was to generate the documentation from its current=20=20 > location (at openjpa-project/src/doc/manual/manual.xml), and=20 > generate=20=20 > the site and docs together using the "mvn site" process (the output=20=20 > of which can be seen at http://people.apache.org/~mprudhom/openjpa/=20 > site/ ). Other people suggested that we keep the site and docs in a=20=20 > separate, parallel Subversion directory, so I waited to do any=20=20 > further work until we had come to some consensus on how the project=20=20 > site and documentation should be handled. >=20 > Everything that I've done is currently checked into Subversion,=20=20 > though. Any changes/additions to the docs can be made to openjpa-=20 > project/src/doc/manual/manual.xml , which I expect we will relocate=20=20 > to wherever we decide is the best place for it. My feeling is that the documentation (including tutorials and samples) belongs with the product, and content about OpenJPA the project should be separate from the product. I do not think that docs should move into a wiki, although I do think that there are a bunch of advantages to keeping the site content (i.e., the stuff that's not versioned along with the product) all in a wiki, since I find wikis more accessible for editing than HTML + SVN etc. -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.