From dev-return-16663-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Tue Jun 14 16:39:51 2011 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 47FA46CDD for ; Tue, 14 Jun 2011 16:39:51 +0000 (UTC) Received: (qmail 75723 invoked by uid 500); 14 Jun 2011 16:39:50 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 75683 invoked by uid 500); 14 Jun 2011 16:39:50 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 75675 invoked by uid 99); 14 Jun 2011 16:39:50 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2011 16:39:50 +0000 Received: from localhost (HELO [192.168.1.34]) (127.0.0.1) (smtp-auth username nslater, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Jun 2011 16:39:50 +0000 Subject: Re: [Couchdb Wiki] Trivial Update of "CouchDB_in_the_wild" by wentforgold Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Noah Slater In-Reply-To: <8CA8C71F-AC47-43F0-A0AD-57F62CA177B0@apache.org> X-Noah: Awesome Date: Tue, 14 Jun 2011 17:39:47 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5843AB8C-723C-4933-912E-2040D7A74DFE@apache.org> References: <20110613070433.1622.84988@eos.apache.org> <02E53EA0-4601-437F-9B18-72A74803D712@apache.org> <9AAB7C41-34B8-4252-B623-B88C8C3F97D3@apache.org> <8CA8C71F-AC47-43F0-A0AD-57F62CA177B0@apache.org> To: dev@couchdb.apache.org X-Mailer: Apple Mail (2.1084) On 14 Jun 2011, at 17:29, Jan Lehnardt wrote: > That is common practice already and I don't see a problem with this as = long all criteria for ASF commits are fulfilled. Okay. > That said, I'd not keep the docs in the CouchDB source repo, but on = the side (like site/) and only pull things together on release-time. Disagree very strongly. If you don't include the docs within the CouchDB instance directory, = then we will have no record of the docs at a point in time. Say, if you = wanted to see the docs for CouchDB 1.3, specifically. Secondly, if they're no in the instance directory, then you cannot build = them. That means that people doing a source checkout will not be able to = build the docs without going to special lengths. And it means that we = wont be able to include them in the release artefacts, because you can't = be pulling things from outside the source tree. > I'd also propose to not bother with SVN on this one as long as the = technical side of things is taken care of (Paul?). Not sure what you mean here.=