You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Jan Lehnardt <ja...@apache.org> on 2009/08/23 19:08:00 UTC

contrib files, svn layout

Hi dev@,

while debugging the continuous replication issue with Robert I wrote
two scripts* that setup N number of CouchDB instances in /tmp/couchN
and then set up continuous replication for these nodes. I think these
would be of general interest and I'd like to add the them to the
CouchDB source tree. Where should they go?

Locally, I've put them under `svnroot/couchdb/contrib/scripts` but I can
see an argument for not putting them into the source tree. Maybe
`svnroot/contrib/trunk` is a better place (starting a new layout where
projects "next to" CouchDB live in parallel directories in SVN.

I can always put them on my personal GitHub page, but I feel having
this in the ASF SVN gives them better visibility and I can see more and
more useful scripts accumulate and we should have a place for them

Cheers
Jan
--
*http://www.friendpaste.com/5d1cbZglgi42AASqGg6dCg &
  http://www.friendpaste.com/6iC7KyOglqHFexivY9g1W


Re: contrib files, svn layout

Posted by Elliot Murphy <el...@canonical.com>.
On 08/23/2009 01:08 PM, Jan Lehnardt wrote:
> I can always put them on my personal GitHub page, but I feel having
> this in the ASF SVN gives them better visibility and I can see more and
> more useful scripts accumulate and we should have a place for them

Having those scripts available in svn would be great, when I worked on
mysql we also included scripts for setting up common replication
topologies right out of the tree to make it easier to test those types
of configurations.
-- 
Elliot Murphy | https://launchpad.net/~statik/


Re: contrib files, svn layout

Posted by Noah Slater <ns...@apache.org>.
On Mon, Aug 24, 2009 at 09:28:00AM -0500, Curt Arnold wrote:
> A contribs directory as part of the distribution can become a dumping
> ground of obsolete code that no one can support.  But once it is in the
> distribution, you can feel compelled to never remove it since someone
> perhaps might depend on it.
[..]
> Once we have specific stuff that is worthy for release, hopefully it
> would then become obvious whether it should go in the trunk, or whether
> it fits in as a separate plugin or feature distributed separately from
> the main release or packaged with other things into a tools, examples or
> other companion to couchdb .

Having a directory in trunk does not necessarily mean that it is in the release.

-- 
Noah Slater, http://tumbolia.org/nslater

Re: contrib files, svn layout

Posted by Curt Arnold <ca...@apache.org>.
On Aug 23, 2009, at 9:02 PM, Noah Slater wrote:

> On Sun, Aug 23, 2009 at 07:08:00PM +0200, Jan Lehnardt wrote:
>> Locally, I've put them under `svnroot/couchdb/contrib/scripts` but  
>> I can
>> see an argument for not putting them into the source tree. Maybe
>> `svnroot/contrib/trunk` is a better place (starting a new layout  
>> where
>> projects "next to" CouchDB live in parallel directories in SVN.
>
> A contrib directory is usually reserved for user modules that have  
> been included
> from external sources. I would vote for putting them under couchdb/ 
> trunk/tools
> or couchdb/trunk/dev or something similar.
>
> Best,
>
> -- 
> Noah Slater, http://tumbolia.org/nslater


A contribs directory as part of the distribution can become a dumping  
ground of obsolete code that no one can support.  But once it is in  
the distribution, you can feel compelled to never remove it since  
someone perhaps might depend on it.

I had mentioned having a sandbox or labs directory as a place for  
collaborative development on experimental features or anything that  
isn't ready for the trunk.

Stuff that might be useful, but that we can't support and don't intend  
to develop further could go in couchdb/attic.

Once we have specific stuff that is worthy for release, hopefully it  
would then become obvious whether it should go in the trunk, or  
whether it fits in as a separate plugin or feature distributed  
separately from the main release or packaged with other things into a  
tools, examples or other companion to couchdb .

Re: contrib files, svn layout

Posted by Noah Slater <ns...@apache.org>.
On Sun, Aug 23, 2009 at 07:08:00PM +0200, Jan Lehnardt wrote:
> Locally, I've put them under `svnroot/couchdb/contrib/scripts` but I can
> see an argument for not putting them into the source tree. Maybe
> `svnroot/contrib/trunk` is a better place (starting a new layout where
> projects "next to" CouchDB live in parallel directories in SVN.

A contrib directory is usually reserved for user modules that have been included
from external sources. I would vote for putting them under couchdb/trunk/tools
or couchdb/trunk/dev or something similar.

Best,

-- 
Noah Slater, http://tumbolia.org/nslater

Re: contrib files, svn layout

Posted by Dirkjan Ochtman <di...@ochtman.nl>.
On 23/08/2009 19:08, Jan Lehnardt wrote:
> Locally, I've put them under `svnroot/couchdb/contrib/scripts` but I can
> see an argument for not putting them into the source tree. Maybe
> `svnroot/contrib/trunk` is a better place (starting a new layout where
> projects "next to" CouchDB live in parallel directories in SVN.

I think putting this kind of thing in the repository is a good thing, 
but I don't really see the value of a root/contrib/trunk kind of thing. 
Since these scripts are intended for use by CouchDB developers and 
people interested in hacking on CouchDB, why make it harder on them by 
having to check out a separate working dir? I don't think putting them 
in couchdb/contrib(/scripts?) comes with some cost that justifies that.

Cheers,

Dirkjan