Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of bchesneau@gmail.com
 designates 209.85.192.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F7E2B493-677F-4203-812D-CEBBFCA60111@apache.org>
References: <20140507195739.729AD165DF@urd.zones.apache.org>
 <CAJNb-9oX=W-Tan_tWMZ227ppAMQjOtqQVxX8ri0HKf7Y8C9kWQ@mail.gmail.com>
 <F7E2B493-677F-4203-812D-CEBBFCA60111@apache.org>
From: Benoit Chesneau <bchesneau@gmail.com>
Date: Thu, 29 May 2014 07:02:51 +0200
Message-ID: 
 <CAJNb-9pHU_djZt8=Q_5yECzMd1B1XP30KheKdCzQ8k0BY1ZTyA@mail.gmail.com>
Subject: Re: Summary of IRC Meeting in #couchdb-meeting
To: "dev@couchdb.apache.org" <dev@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=001a11c2cd287b8b0e04fa82d864

--001a11c2cd287b8b0e04fa82d864
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, May 28, 2014 at 11:17 PM, Robert Samuel Newson
<rnewson@apache.org>wrote:

>
> I based the rebar work on yours, though I did remove the
> cross-compile/static build bits for simplicity. I am also pretty confiden=
t
> that my work does not work on all the platforms that rebar.config.script
> implies. It=E2=80=99s certainly a work-in-progress. Since it *does* build=
 the
> bigcouch branch correctly, it now serves a valid prototype for any work y=
ou
> might wish to do on it.
>

ok sounds easy then, will see how i can go in playing with both at the same
time.

>
> for the NIF=E2=80=99s, I=E2=80=99ve no preference on the matter, as long =
as comparison is
> still fast. Make the replacement if you wish to.
>

ok

>
> couch_mrview, I=E2=80=99ve not looked at your changes deeply but it does =
seem a
> simple merge.
>

The couch_mrview part is easy. BUt this the HTTP api part [1] and the
replication part [2] . I am not what's the best way to merge them. If it
can reuse most of the code in the cluster api that would be interesting.
Maybe chewbranca can help me on that topic.


>
> I am terrible at roadmaps and timeframes, I think that=E2=80=99s no secre=
t. I can
> summarize current status as follows: the 1843-feature-bigcouch branch is =
in
> good shape for testing, for finding regressions. I=E2=80=99m now working =
to get
> authentication working against a clustered/sharded _users database rather
> than calling the node local one only. Like in bigcouch, we=E2=80=99ll cal=
l one and,
> on a 404, call the other. We could revise this going forward. After that =
is
> achieved, I=E2=80=99ll be working to import the work that Cloudant has do=
ne since
> the original Nebraska merge, our full year of code fixes and improvements=
,
> in a further IP clearance round.
>
>
ok, so nothing that stop other works which is cool.


[1]
https://github.com/rcouch/couchdb-couch-httpd/commit/70409b20e5be8f0fa5d125=
cd1e9ec2697c82d909(and
following)
[2]
https://github.com/rcouch/couchdb-couch-replicator/commit/09d7a60c29e4e800b=
6e80efd2337e9b744ae1229(and
related changes in couch_mrview)

--001a11c2cd287b8b0e04fa82d864--