This is a very helpful document. If Apache were an office, I think it
would be hanging on the wall. This should make a good checklist for us
as we prepare the 0.9 release.
-- Forwarded message --
From: Craig L Russell
Date: Mon, Feb 2, 2009 at 3:24 PM
Subject: Re: Code contributi
On Mon, Feb 2, 2009 at 1:47 PM, Antony Blakey wrote:
>
> On 03/02/2009, at 12:42 AM, C. Florian Ebeling wrote:
>
>> that's one idea I was thinking about myself a while back
>> but I didn't get around trying it. I wonder how happy you
>> are with this "gems as generic package manager" approach?
>>
On 03/02/2009, at 12:42 AM, C. Florian Ebeling wrote:
that's one idea I was thinking about myself a while back
but I didn't get around trying it. I wonder how happy you
are with this "gems as generic package manager" approach?
It would be cool if you could post examples into some pastebin,
if s
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson closed COUCHDB-233.
--
Resolution: Fixed
applied in r740094
> add the current line number of displayed row in lists
On Mon, Feb 2, 2009 at 4:39 AM, Antony Blakey wrote:
>
> On 02/02/2009, at 10:34 PM, Jan Lehnardt wrote:
>
>>
>> On 2 Feb 2009, at 12:45, Antony Blakey wrote:
>>
>>>
>>> On 02/02/2009, at 10:09 PM, Noah Slater wrote:
>>>
That's fine with me. (Says the man who's not going to develop it.)
>>>
>
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-233:
Attachment: couchdb-lists-linenumber.diff
new version of the patch. This time make sure w
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-233:
Attachment: couchdb-lists-linenumber.diff
nbrow -> row_number.
> add the current line nu
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-233:
Attachment: (was: couchdb-lists-linenumber.diff)
> add the current line number of dis
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-233:
Attachment: couchdb-lists-linenumber.diff
rename nbrow -> row_number as per suggestion of
Hi Antony,
> I have
> couchdb/erlang/icu etc packaged as ruby gems that deploys couch using
> dependcies, and the class that controls couchdb allows multiple instances in
> self-contained locations. It looks a bit like this:
that's one idea I was thinking about myself a while back
but I didn't ge
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669597#action_12669597
]
Benoit Chesneau commented on COUCHDB-233:
-
this patch could also been found in my
On 2 Feb 2009, at 13:39, Antony Blakey wrote:
On 02/02/2009, at 10:34 PM, Jan Lehnardt wrote:
I hope you can push for an agreed-upon design and give a rough todo
list
and maybe start with it and leave open work items with a good
description
in JIRA for others to pick up. Would that work?
[
https://issues.apache.org/jira/browse/COUCHDB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-233:
Attachment: couchdb-lists-linenumber.diff
> add the current line number of displayed row
add the current line number of displayed row in lists
---
Key: COUCHDB-233
URL: https://issues.apache.org/jira/browse/COUCHDB-233
Project: CouchDB
Issue Type: New Feature
Compon
On 02/02/2009, at 10:34 PM, Jan Lehnardt wrote:
On 2 Feb 2009, at 12:45, Antony Blakey wrote:
On 02/02/2009, at 10:09 PM, Noah Slater wrote:
That's fine with me. (Says the man who's not going to develop it.)
Unfortunately requiring a bigger commitment to this feature than I
can manage
On 2 Feb 2009, at 12:45, Antony Blakey wrote:
On 02/02/2009, at 10:09 PM, Noah Slater wrote:
That's fine with me. (Says the man who's not going to develop it.)
Unfortunately requiring a bigger commitment to this feature than I
can manage at this time.
I hope you can push for an agreed-
On 02/02/2009, at 10:09 PM, Noah Slater wrote:
That's fine with me. (Says the man who's not going to develop it.)
Unfortunately requiring a bigger commitment to this feature than I can
manage at this time.
Antony Blakey
-
CTO, Linkuistics Pty Ltd
Ph: 0438 840 787
A Buddhist w
On Mon, Feb 02, 2009 at 10:06:48PM +1030, Antony Blakey wrote:
>
> On 02/02/2009, at 9:48 PM, Noah Slater wrote:
>
>> I think I agree with a comment earlier in this thread. I don't think
>> command
>> options are the place for this type of configuration. Ideally, you'd
>> want all
>> the configurat
On 02/02/2009, at 9:48 PM, Noah Slater wrote:
I think I agree with a comment earlier in this thread. I don't think
command
options are the place for this type of configuration. Ideally, you'd
want all
the configuration in the ini file.
That means that the plugin system needs to be written
On Mon, Feb 02, 2009 at 09:31:36PM +1030, Antony Blakey wrote:
>>> -D add all the plugins in $DEFAULT_PLUGIN_DIR
>>> -G DIR add all the plugins in DIR
>>> -P DIR add the plugin DIR
>>
>> Why have you chosen all capitals?
>
> Because all the obvious lower case options have been used. I wan
On 02/02/2009, at 8:56 PM, Noah Slater wrote:
I've found this thread a little hard to follow so far, but why not
configure the
plugins from /etc/couchdb/local.ini itself, including the
configuration that
tells CouchDB which plugins to work. I'm not sure I'm comfortable
with the idea
of Cou
On 02/02/2009, at 8:51 PM, Noah Slater wrote:
This sounds pretty good.
On Mon, Feb 02, 2009 at 04:10:56PM +1030, Antony Blakey wrote:
-C clean the plugins list
What does this do? I think it needs more explanation.
clear the plugin list.
The plugin list is by default all the plugins
On Mon, Feb 02, 2009 at 06:07:37PM +1030, Antony Blakey wrote:
> My concern is how to allow plugins to be updated without stomping on
> user configuration, which is why I suggest having the local plugin
> configuration be outside of the plugin's directory. Maybe that's a
> deployment required that'
This sounds pretty good.
On Mon, Feb 02, 2009 at 04:10:56PM +1030, Antony Blakey wrote:
> -C clean the plugins list
What does this do? I think it needs more explanation.
> -D add all the plugins in $DEFAULT_PLUGIN_DIR
> -G DIR add all the plugins in DIR
> -P DIR add the plugi
24 matches
Mail list logo
