Re: Goals for 2014

[Nicolas Dufour <nr...@gmail.com>]

Thanks Dirkjan,

Speaking of the merge, is there any updates for both (rcouch and bigcouch)?

Thanks,

Nicolas


On Wed, Jan 22, 2014 at 7:19 AM, Dirkjan Ochtman <di...@ochtman.nl> wrote:

> Following up to the 2013 retrospective thread:
>
> - Get more commit activity, especially in the core
> - Merge the forks (rcouch and bigcouch)
> - Improve the release process to make it take less work/time
>
> Cheers,
>
> Dirkjan
>

Re: Goals for 2014

[Robert Samuel Newson <rn...@apache.org>]

Gotcha, sounds fair. This is the kind of mistake that arises when we don’t talk and merely see bits go by.

Once a few more folks confirm that 1843-feature-bigcouch stands up and can at least do validate_doc_update on a few other platforms, I’ll consider the rebar.config.script work in a good enough shape to discuss it for merging. It’s broadly what you had except it turns out rebar itself can do the os:type selection using regex’s and it’s possible to pass different environments for each port (so couch_icu_driver is no longer linked to spidermonkey for no reason).

B.

On 4 Feb 2014, at 16:06, Benoit Chesneau <bc...@gmail.com> wrote:

> On Tue, Feb 4, 2014 at 4:50 PM, Robert Samuel Newson <rn...@apache.org>wrote:
> 
>> Hi,
>> 
>> It's largely because we're all busy with wholly bigcouch internal things
>> on our 1843-feature-bigcouch branch, there's nothing *yet* to
>> cooperate/feedback about. The closest thing is the bit I'm hacking on
>> ("Build with rebar").
>> 
>> I agree that we should not be inventing new things during the merge, but
>> then I saw you were splitting out parts of couch_httpd elsewhere, which
>> counts as that.
>> 
> 
> Actually :
> 
> https://github.com/refuge/couch_core/tree/master/apps/couch_httpd
> 
> The difference is that couch_changes is not its own app like it is in
> rcouch:
> 
> https://github.com/refuge/couch_core/tree/master/apps/couch_changes
> 
> because i ported the latest but non released in that branch yet of the
> code. I also not integrated the usage of barrel, to easy any merge. So
> nothing really new in that split. I just simplified it compared to rcouch
> (if you see in the history this is how it started anyway) in view of
> speeding the final merge and propose other changes as patches later.
> 
> 
> 
>> 
>> Before bigcouch can be merged, it needs to build and run and perform as
>> many of the features as possible, that simply can't happen until 'make'
>> works. I deliberately started from your rebar.config.script rather than the
>> code that bigcouch uses (which uses Scons) as it's the right approach. That
>> it's not identical is not a problem, in my opinion, but we can judge that
>> at merge time. It needs to work first.
>> 
>> I appreciate your "during 2 years" comment but let's not go there, I can
>> pull a larger value, as can everyone else at Cloudant, but that's going to
>> be tiresome and divisive and it achieves nothing.
>> 
>> Short version: If it was as simple as dropping in the rcouch versions of
>> these pieces, I'd have finished a week ago. Software is not so simple.
>> 
> 
> 
> ok... I will forget to answer to that part. I will rather focus on
> finishing these latest patches.
> 
> - benoit

Re: Goals for 2014

[Benoit Chesneau <bc...@gmail.com>]

On Tue, Feb 4, 2014 at 4:50 PM, Robert Samuel Newson <rn...@apache.org>wrote:

> Hi,
>
> It's largely because we're all busy with wholly bigcouch internal things
> on our 1843-feature-bigcouch branch, there's nothing *yet* to
> cooperate/feedback about. The closest thing is the bit I'm hacking on
> ("Build with rebar").
>
> I agree that we should not be inventing new things during the merge, but
> then I saw you were splitting out parts of couch_httpd elsewhere, which
> counts as that.
>

Actually :

https://github.com/refuge/couch_core/tree/master/apps/couch_httpd

The difference is that couch_changes is not its own app like it is in
rcouch:

https://github.com/refuge/couch_core/tree/master/apps/couch_changes

because i ported the latest but non released in that branch yet of the
code. I also not integrated the usage of barrel, to easy any merge. So
nothing really new in that split. I just simplified it compared to rcouch
(if you see in the history this is how it started anyway) in view of
speeding the final merge and propose other changes as patches later.



>
> Before bigcouch can be merged, it needs to build and run and perform as
> many of the features as possible, that simply can't happen until 'make'
> works. I deliberately started from your rebar.config.script rather than the
> code that bigcouch uses (which uses Scons) as it's the right approach. That
> it's not identical is not a problem, in my opinion, but we can judge that
> at merge time. It needs to work first.
>
> I appreciate your "during 2 years" comment but let's not go there, I can
> pull a larger value, as can everyone else at Cloudant, but that's going to
> be tiresome and divisive and it achieves nothing.
>
> Short version: If it was as simple as dropping in the rcouch versions of
> these pieces, I'd have finished a week ago. Software is not so simple.
>


ok... I will forget to answer to that part. I will rather focus on
finishing these latest patches.

- benoit

Re: Goals for 2014

[Robert Samuel Newson <rn...@apache.org>]

Hi,

It’s largely because we’re all busy with wholly bigcouch internal things on our 1843-feature-bigcouch branch, there’s nothing *yet* to cooperate/feedback about. The closest thing is the bit I’m hacking on ("Build with rebar").

I agree that we should not be inventing new things during the merge, but then I saw you were splitting out parts of couch_httpd elsewhere, which counts as that.

Before bigcouch can be merged, it needs to build and run and perform as many of the features as possible, that simply can’t happen until 'make' works. I deliberately started from your rebar.config.script rather than the code that bigcouch uses (which uses Scons) as it’s the right approach. That it’s not identical is not a problem, in my opinion, but we can judge that at merge time. It needs to work first.

I appreciate your "during 2 years" comment but let’s not go there, I can pull a larger value, as can everyone else at Cloudant, but that’s going to be tiresome and divisive and it achieves nothing.

Short version: If it was as simple as dropping in the rcouch versions of these pieces, I’d have finished a week ago. Software is not so simple.

B.

On 4 Feb 2014, at 15:43, Benoit Chesneau <bc...@gmail.com> wrote:

> On Tue, Feb 4, 2014 at 4:13 PM, Robert Samuel Newson <rn...@apache.org>wrote:
> 
>> "Recent commits in the bigcouch branch redoing some
>> work already done in rcouch (coming from a 2 years experience"
>> 
>> Work done in rcouch is not sacred, does not necessarily go into couchdb
>> master without editing or review by anyone else, and that applies to
>> bigcouch as well. As you should know, bigcouch also builds with rebar but
>> *differently*. I am expending time and effort to find a way to make it all
>> work together. Please stop this attitude.
>> 
> 
> 
> Sorry? Where do you see I am saying it's sacred.
> 
> All I am saying is that it would be a lot more productive time for both
> if instead of putting code from each other branches without
> consultations, we could sit around a branch and start to put the code
> where we have the experience in.
> 
> And don't get me wrong here, I don't imply you don't know what you do.
> But I put a lot of time, working on this code with others in rcouch,
> during 2 years, so it is a lot easier for me to go on it. I don't see
> the point at all to start a new thing on a branch which wasn't planned
> at the beginning of the merge. This is why I didn't included any
> optimizations from rcouch and bigger changes in couch core so it can be
> merged easily.
> 
> I was hoping from more cooperation and feedback, like commenting on the
> code or saying if a particular piece is wrong and alike.

Re: Goals for 2014

[Benoit Chesneau <bc...@gmail.com>]

On Tue, Feb 4, 2014 at 4:13 PM, Robert Samuel Newson <rn...@apache.org>wrote:

> "Recent commits in the bigcouch branch redoing some
> work already done in rcouch (coming from a 2 years experience"
>
> Work done in rcouch is not sacred, does not necessarily go into couchdb
> master without editing or review by anyone else, and that applies to
> bigcouch as well. As you should know, bigcouch also builds with rebar but
> *differently*. I am expending time and effort to find a way to make it all
> work together. Please stop this attitude.
>


Sorry? Where do you see I am saying it's sacred.

All I am saying is that it would be a lot more productive time for both
if instead of putting code from each other branches without
consultations, we could sit around a branch and start to put the code
where we have the experience in.

And don't get me wrong here, I don't imply you don't know what you do.
But I put a lot of time, working on this code with others in rcouch,
during 2 years, so it is a lot easier for me to go on it. I don't see
the point at all to start a new thing on a branch which wasn't planned
at the beginning of the merge. This is why I didn't included any
optimizations from rcouch and bigger changes in couch core so it can be
merged easily.

I was hoping from more cooperation and feedback, like commenting on the
code or saying if a particular piece is wrong and alike.

Re: Goals for 2014

[Robert Samuel Newson <rn...@apache.org>]

"Recent commits in the bigcouch branch redoing some
work already done in rcouch (coming from a 2 years experience"

Work done in rcouch is not sacred, does not necessarily go into couchdb master without editing or review by anyone else, and that applies to bigcouch as well. As you should know, bigcouch also builds with rebar but *differently*. I am expending time and effort to find a way to make it all work together. Please stop this attitude.

B.

On 4 Feb 2014, at 14:24, Benoit Chesneau <bc...@gmail.com> wrote:

> On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour <nr...@gmail.com> wrote:
> 
>> Thanks Dirkjan,
>> 
>> Speaking of the merge, is there any updates for both (rcouch and bigcouch)?
>> 
>> Thanks,
>> 
>> Nicolas
>> 
>> 
>> On Wed, Jan 22, 2014 at 7:19 AM, Dirkjan Ochtman <di...@ochtman.nl>
>> wrote:
>> 
>>> Following up to the 2013 retrospective thread:
>>> 
>>> - Get more commit activity, especially in the core
>>> - Merge the forks (rcouch and bigcouch)
>>> - Improve the release process to make it take less work/time
>> 
> 
> There have been some  progress on both branches. But for now all the work
> happened in parallel without too much consultations from each others parts
> (ie Cloudant and me). Recent commits in the bigcouch branch redoing some
> work already done in rcouch (coming from a 2 years experience) let me think
> it's about time to start a new branch to start the real merge. Hopefully we
> will be able to manage a meeting soon to organize the work between all the
> devs around.
> 
> About rcouch
> 
> I will have finished the merge by tomorrow. Last week I finished to
> refactor the view changes so it can be easily included in the current
> couchdb and be embedded in other Erlang applications. What still need to be
> done are the following:
> 
> - replace couch.app.src.escript by couch.app.src to fix errors with
> travis-ci
> - replace logging by lager
> - add the erlang vm stats
> - add validate_on_read
> 
> 
> Hope it helps,
> 
> - benoit

Re: Goals for 2014

[Benoit Chesneau <bc...@gmail.com>]

On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour <nr...@gmail.com> wrote:

> Thanks Dirkjan,
>
> Speaking of the merge, is there any updates for both (rcouch and bigcouch)?
>
> Thanks,
>
> Nicolas
>
>
> On Wed, Jan 22, 2014 at 7:19 AM, Dirkjan Ochtman <di...@ochtman.nl>
> wrote:
>
> > Following up to the 2013 retrospective thread:
> >
> > - Get more commit activity, especially in the core
> > - Merge the forks (rcouch and bigcouch)
> > - Improve the release process to make it take less work/time
>

There have been some  progress on both branches. But for now all the work
happened in parallel without too much consultations from each others parts
(ie Cloudant and me). Recent commits in the bigcouch branch redoing some
work already done in rcouch (coming from a 2 years experience) let me think
it's about time to start a new branch to start the real merge. Hopefully we
will be able to manage a meeting soon to organize the work between all the
devs around.

About rcouch

I will have finished the merge by tomorrow. Last week I finished to
refactor the view changes so it can be easily included in the current
couchdb and be embedded in other Erlang applications. What still need to be
done are the following:

- replace couch.app.src.escript by couch.app.src to fix errors with
travis-ci
- replace logging by lager
- add the erlang vm stats
- add validate_on_read


Hope it helps,

- benoit

Re: Goals for 2014

[Nicolas Dufour <nr...@gmail.com>]

Oh ok. I thought there would have been some update posts somewhere about it.

Hey Robert, anything that is testable already in couch from bigcouch?
Anything to add about how rebar is used here?
Thanks Benoit from the heads up on rcouch.

Nicolas


On Tue, Feb 4, 2014 at 8:56 AM, Dirkjan Ochtman <di...@ochtman.nl> wrote:

> On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour <nr...@gmail.com> wrote:
> > Speaking of the merge, is there any updates for both (rcouch and
> bigcouch)?
>
> There's a lot of stuff happening right now. If you want to know more,
> browse the mailing list archives.
>
> Cheers,
>
> Dirkjan
>

Re: Goals for 2014

[Dirkjan Ochtman <di...@ochtman.nl>]

On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour <nr...@gmail.com> wrote:
> Speaking of the merge, is there any updates for both (rcouch and bigcouch)?

There's a lot of stuff happening right now. If you want to know more,
browse the mailing list archives.

Cheers,

Dirkjan