On Tue, Aug 18, 2009 at 2:55 AM, Jan Lehnardtj...@apache.org wrote:
On 18 Aug 2009, at 09:10, Bernd Fondermann wrote:
On Tue, Aug 18, 2009 at 02:38, Jan Lehnardtj...@apache.org wrote:
Hi Paul,
snip/
Related:
- Do we want to foster plugins, extensions and other infrastructure
software
Sub-projects are a bad idea.
Been following this thread for awhile without being able to put my
concerns into small sentences. Each time I think about it I think
about how rapidly CouchDB is growing and how much that would hurt
sub-projects that are trying to keep up. And as others have said, we
Hi Paul,
good points!
The questions boil down to:
- Is there a notion of core CouchDB that doesn't have cluster
features?
- Do we want to ship whatever release (cluster or not or both) of
CouchDB with a small ecosystem (Futon, CouchApp)?
Related:
- Do we want to foster plugins,
My understanding is also that we want an official distribution to include
couchdb-lounge style clustering. There's two ways to go about it: 1) put it
all into the source tree and disable and enable features on build time
(--enable-cluster) or 2) have separate trees (e.g. a core and a cluster
On Mon, Aug 17, 2009 at 9:54 PM, Jan Lehnardtj...@apache.org wrote:
On 18 Aug 2009, at 03:13, Paul Davis wrote:
My understanding is also that we want an official distribution to include
couchdb-lounge style clustering. There's two ways to go about it: 1) put
it
all into the source tree and
On Fri 14 Aug 2009 21:50, Simon Metson simonmet...@googlemail.com wrote:
For example, a clear warning sign is when you start giving out
commit rights to only certain subprojects.
I don't understand this point.
Why would any sub-project NOT have commit rights?
I read this as committer A is
Hi dev@,
Chris, thanks for bobsledding this :)
--
I'd welcome all three projects as sub-projects. I'd also throw in Futon
to become a sub project, too. My understanding of a sub-project
is this:
- The development community between the main project and the
sub project should be overlapping
On Sun, Aug 16, 2009 at 18:21, Jan Lehnardtj...@apache.org wrote:
In a project as big as PHP, this makes sense and was needed
badly. CouchDB is not that big yet. I'd say let's figure out how
to incorporate sub projects into our subversion tree (e.g.
couchdb/trunk is couchdb-trunk, where do sub
On 16 Aug 2009, at 22:11, Dirkjan Ochtman wrote:
On Sun, Aug 16, 2009 at 18:21, Jan Lehnardtj...@apache.org wrote:
In a project as big as PHP, this makes sense and was needed
badly. CouchDB is not that big yet. I'd say let's figure out how
to incorporate sub projects into our subversion tree
On Sun, Aug 16, 2009 at 10:23:03PM +0200, Jan Lehnardt wrote:
I'd be -1 on client libraries to becoming sub-projects. At least for now
where there's still significant styles being worked out. Down the road,
I can see that being useful.
I am similarly -1 on this issue for now.
--
Noah Slater,
On Aug 16, 2009, at 12:21 PM, Jan Lehnardt wrote:
Chris, thanks for bobsledding this :)
Jan, great summary. Actually, this has been a well thought out
discussion by all involved. It's great to see such a vibrant community!
I have some small reservations about making couchdb-lounge a
Many Apache projects have sub-projects, for two good example see:
http://hadoop.apache.org/ which has 9 sub-projects
http://lucene.apache.org/ which has 10
I think one benefit of having sub-projects is broadening the
community. I think it also helps to give people looking at CouchDB for
the
On Fri 14 Aug 2009 14:52, Chris Anderson jch...@apache.org wrote:
I think one benefit of having sub-projects is broadening the
community. I think it also helps to give people looking at CouchDB for
the first time an easier way to see some of the really cool tools and
libraries it's offers.
2009/8/14 Chris Anderson jch...@apache.org:
Many Apache projects have sub-projects, for two good example see:
http://hadoop.apache.org/ which has 9 sub-projects
http://lucene.apache.org/ which has 10
I think one benefit of having sub-projects is broadening the
community. I think it also
No objections to couchdb-lucene being a subproject at all. I'll let
others chime in on the merit of subprojects in general.
B.
On Fri, Aug 14, 2009 at 12:23 PM, Benoit Chesneaubchesn...@gmail.com wrote:
2009/8/14 Chris Anderson jch...@apache.org:
Many Apache projects have sub-projects, for two
On Thu, Aug 13, 2009 at 11:52:42PM -0700, Chris Anderson wrote:
The CouchDB-Lounge project provides a CouchDB clustering via a smart
HTTP proxy. I can see bringing that code in, and using it as a
scaffold for our Erlang clustering infrastructure. If we do it right,
deployments will have wide
On Fri, Aug 14, 2009 at 03:37:01PM +0800, J Aaron Farr wrote:
Just to give you a heads up, the ASF has had rather mixed results with
subprojects and we've specifically tried to avoid what's been termed as
umbrella projects. Jakarta is/was the poster child example.
Thanks for the feedback.
I
Hi,
For example, a clear warning sign is when you start giving out
commit rights to only certain subprojects.
I don't understand this point.
Why would any sub-project NOT have commit rights?
I read this as committer A is given commit for sub-project 1, but not
the core project or
Are you seeing these as having substantially different development
communities? If not, it would be cleaner to have them as distinct
products of the CouchDB project and instead of distinct projects.
A lot of the umbrella projects had little dependency between sub-
projects and a
On Fri, Aug 14, 2009 at 08:55:27AM -0500, Curt Arnold wrote:
Are you seeing these as having substantially different development
communities? If not, it would be cleaner to have them as distinct
products of the CouchDB project and instead of distinct projects. A
lot of the umbrella projects
It's worth considering that most of the proposed contrib packages uses
languages other than Erlang (Python, Java, etc) and that will reduce
the number of developers that are prepared to hack on them.
On a purely selfish note, I would welcome a second person to work on
couchdb-lucene with a view
On Fri, Aug 14, 2009 at 6:43 AM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 14, 2009 at 03:37:01PM +0800, J Aaron Farr wrote:
Just to give you a heads up, the ASF has had rather mixed results with
subprojects and we've specifically tried to avoid what's been termed as
umbrella projects.
On Fri, Aug 14, 2009 at 09:55:34AM -0700, Chris Anderson wrote:
I generally agree with those principles, although I think we can get
away with being informal about them at least at first.
Creating a project as a sub-project of Apache CouchDB is a necessarily formal
affair, and on that we can't
On Fri, Aug 14, 2009 at 10:19 AM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 14, 2009 at 09:55:34AM -0700, Chris Anderson wrote:
I generally agree with those principles, although I think we can get
away with being informal about them at least at first.
Creating a project as a
On Fri, Aug 14, 2009 at 1:59 PM, Shaun Lindsaysh...@meebo.com wrote:
I'd be excited to see couchdb-lounge make it in as a subproject, especially
if the overall goal is to incorporate features from the lounge directly in
to CouchDB. Making it a subproject seems like a good intermediate step in
On Fri, Aug 14, 2009 at 03:11:45PM -0700, Will Hartung wrote:
Taking lounge as an example, if Couch intends to offer lounge
capability as a first class service, and, in the end, obsolete
lounge, then the decision needs to be made whether to incorporate and
absorb lounge, or, effectively,
On Fri, Aug 14, 2009 at 3:17 PM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 14, 2009 at 03:11:45PM -0700, Will Hartung wrote:
Taking lounge as an example, if Couch intends to offer lounge
capability as a first class service, and, in the end, obsolete
lounge, then the decision needs to be
On Fri, Aug 14, 2009 at 03:49:33PM -0700, Chris Anderson wrote:
CouchDB core should remain focused on reliability and performance on a
single node.
I disagree pretty strongly with this. Focusing on single node performance is a
good short term goal, but saying that multi-node environments are
On Fri, Aug 14, 2009 at 4:01 PM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 14, 2009 at 03:49:33PM -0700, Chris Anderson wrote:
CouchDB core should remain focused on reliability and performance on a
single node.
I disagree pretty strongly with this. Focusing on single node performance
On Fri, Aug 14, 2009 at 04:11:59PM -0700, Chris Anderson wrote:
It's encouraging that even without explicit code to deal with
clusters, people have been able to run large reliable clusters.
CouchDB can only get better at clustering from here. I think it's
important that in the near-term, the
On Fri, Aug 14, 2009 at 4:32 PM, Noah Slaternsla...@apache.org wrote:
On Fri, Aug 14, 2009 at 04:11:59PM -0700, Chris Anderson wrote:
It's encouraging that even without explicit code to deal with
clusters, people have been able to run large reliable clusters.
CouchDB can only get better at
31 matches
Mail list logo
