Re: Hello couchDB world

[Noah Slater <ns...@apache.org>]

Hey Philippe,

Your offer of help is more than appreciated!

It's been great bashing out ideas with you on IRC for the past couple of days.

I think the best way forward is to branch or mirror CouchDB into your own git
repository (as seems to be the fashion) and work on patches or functionality
locally before merging back in with the trunk.

See here for more:

  http://github.com/jlindley/couchdb/tree/master

Best,

-- 
Noah Slater, http://people.apache.org/~nslater/

Re: Hello couchDB world

[Noah Slater <ns...@apache.org>]

On Fri, Jul 11, 2008 at 12:12:13AM +0200, Gianugo Rabellino wrote:
> Actually I'm not bothered by non-committers working on git to share
> their findings with the community. I actually think it's an interesting
> approach that might be worth some brain cycles.

Great!

> What worries me is noticing that CouchDB committers themselves seem to work on
> github. I don't know if you're syncing up git stuff with stuff coming from the
> ASF repository (which might be kosher in a way) or if you're actually using
> git as your primary development then moving code the SVN (that's a no-no in my
> book).

I can understand this. Fortunately, non of the CouchDB committers do anything
with git. We all work exclusively with the Apache SVN repository.

The only use of git in or around CouchDB is by users wanting to hack on personal
patches or branches, totally separate from the official repository.

The only reason I suggested git, and provided a link, is that it seems to be
already quite a popular thing for people to be using with the project.

I, for one, don't even have it installed. :)

I hope this clears things up a little!

Thanks,

-- 
Noah Slater, http://people.apache.org/~nslater/

Re: Hello couchDB world

[Gianugo Rabellino <gi...@apache.org>]

On Jul 10, 2008, at 8:45 PM, Noah Slater wrote:

> On Thu, Jul 10, 2008 at 06:40:13PM +0200, Gianugo Rabellino wrote:
>> Hmmm. While I'm fairly neutral and mildly interested in DSCM, I would
>> venture to say that developing stuff externally from the ASF  
>> repository
>> is quite a no-no here, according to incubator rules.
>
> All I am essentially recommending is that he prepares his patches  
> using some
> collaborative tool before presenting them to the development team  
> for comment
> and perhaps merge.
>
> This is surely no different from simply saying "patches welcome" -  
> I'm just
> dispensing some pragmatic advice at the same time.

Actually I'm not bothered by non-committers working on git to share  
their findings with the community. I actually think it's an  
interesting approach that might be worth some brain cycles. What  
worries me is noticing that CouchDB committers themselves seem to  
work on github. I don't know if you're syncing up git stuff with  
stuff coming from the ASF repository (which might be kosher in a way)  
or if you're actually using git as your primary development then  
moving code the SVN (that's a no-no in my book).

Ciao,

-- 
Gianugo Rabellino
Sourcesense - making sense of Open Source: http://www.sourcesense.com
Blogging at http://boldlyopen.com/

Re: Hello couchDB world

[Noah Slater <ns...@apache.org>]

On Thu, Jul 10, 2008 at 06:40:13PM +0200, Gianugo Rabellino wrote:
> Hmmm. While I'm fairly neutral and mildly interested in DSCM, I would
> venture to say that developing stuff externally from the ASF repository
> is quite a no-no here, according to incubator rules.

All I am essentially recommending is that he prepares his patches using some
collaborative tool before presenting them to the development team for comment
and perhaps merge.

This is surely no different from simply saying "patches welcome" - I'm just
dispensing some pragmatic advice at the same time.

Thanks,

-- 
Noah Slater, http://people.apache.org/~nslater/

Re: Hello couchDB world

[Gianugo Rabellino <gi...@apache.org>]

On Jul 10, 2008, at 6:04 PM, Noah Slater wrote:

> I think the best way forward is to branch or mirror CouchDB into  
> your own git
> repository (as seems to be the fashion) and work on patches or  
> functionality
> locally before merging back in with the trunk.

Hmmm. While I'm fairly neutral and mildly interested in DSCM, I would  
venture to say that developing stuff externally from the ASF  
repository is quite a no-no here, according to incubator rules.

Mentors?

-- 
Gianugo Rabellino
Sourcesense - making sense of Open Source: http://www.sourcesense.com
Blogging at http://boldlyopen.com/