couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <...@apache.org>
Subject Re: [DISCUSS] merge all the forks
Date Wed, 16 Apr 2014 20:53:35 GMT
And we are live: https://blogs.apache.org/couchdb/entry/merging_rcouch

Please tweets and stuffs! :)

Thanks
Jan
--

On 16 Apr 2014, at 22:49 , Jan Lehnardt <jan@apache.org> wrote:

> Thanks Benoit! :)
> 
> Glad you like it. Will post now.
> 
> Best
> Jan
> -- 
> 
> On 16 Apr 2014, at 22:41 , Benoit Chesneau <bchesneau@gmail.com> wrote:
> 
>> awesome. LGTM.
>> 
>> Thanks Jan!
>> 
>> 
>> On Wed, Apr 16, 2014 at 10:29 PM, Jan Lehnardt <jan@apache.org> wrote:
>> 
>>> Here’s a draft. It’s already in the blog, formatted and all. Awaiting your
>>> approval/edits/fixes, thanks!
>>> 
>>> 
>>> https://blogs.apache.org/roller-ui/authoring/preview/couchdb/?previewEntry=merging_rcouchif
you have access there.
>>> 
>>> Source:
>>> 
>>> <p>rcouch is a variant of CouchDB that is derived from the main Apache
>>> CouchDB code base. One way to look at it is as a “future port” of CouchDB,
>>> that is for two reasons:
>>> </p>
>>> 
>>> <p>
>>> <ol>
>>> <li>The internals are <strong>greatly improved</strong>. In
simple terms,
>>> if CouchDB would be started to day, it would look a lot like rcouch.</li>
>>> <li>It comes with a number of <strong>nice new features</strong>.</li>
>>> </ol>
>>> </p>
>>> 
>>> <p>So whether you are a CouchDB user or a CouchDB Erlang developer, rcouch
>>> is <strong>good news</strong> for you!</p>
>>> 
>>> <p>Since CouchDB has been around for a while, the internal codebase is
a
>>> little crufty. We are constantly working on improving that, but one of the
>>> larger efforts have been done within the rcouch project by Apache CouchDB
>>> committer <a href="https://twitter.com/benoitc">Benoit Chesneau</a>.</p>
>>> 
>>> <p>At the same time, Benoit added a number of nice little features that
>>> benefit CouchDB users, just to name a few:</p>
>>> 
>>> <p>
>>> <ul>
>>> <li>_changes for views.</li>
>>> <li>Replication from views.</li>
>>> <li>Write-only “Drop-Box” databases.</li>
>>> <li>Request validation on-read.</li>
>>> <li>_db_changes (actually, we nicked that one for Apache CouchDB 1.4
>>> already :).</li>
>>> </ul>
>>> </p>
>>> 
>>> <p>For more information, see the <a href="http://rcouch.org">rcouch
>>> website</a>.</p>
>>> 
>>> <p>Benoit has generously donated the rcouch project back to Apache CouchDB
>>> and has worked on merging the rcouch and the CouchDB codebases. Now it is
>>> time to review the merged code and get it into Apache CouchDB proper and
>>> put it into a new release.</p>
>>> 
>>> <p>With that, <strong>we need your help</strong>.</p>
>>> 
>>> <p>How you can help, you ask? Easy!</p>
>>> 
>>> <p>If you are a CouchDB user, and are not afraid to build CouchDB
>>> yourself, give the rcouch merge branch a spin:</p>
>>> 
>>> <code>
>>> <pre>
>>> git clone https://github.com/apache/couchdb.git
>>> cd couchdb
>>> git checkout -b 1994-merge-rcouch origin/1994-merge-rcouch
>>> 
>>> # Read the <a href="
>>> https://github.com/apache/couchdb/blob/master/DEVELOPERS">DEVELOPERS</a>
>>> file to install all dependencies
>>> 
>>> # build:
>>> make
>>> make rel
>>> 
>>> # run:
>>> ./rel/apache-couchdb/bin/couchdb start
>>> 
>>> # now CouchDB is running at <a href="http://127.0.0.1:5984">
>>> http://127.0.0.1:5984/_utils/</a>, as usual, you just won’t see any
>>> output.
>>> 
>>> </pre>
>>> </code>
>>> 
>>> <hr>
>>> 
>>> <p><strong>If you are an Erlang developer</strong>, we could
use your help
>>> with code reviews. Any small chunks will help!</p>
>>> 
>>> <p>Please see <a href="https://issues.apache.org/jira/browse/COUCHDB-1994">the
>>> associated JIRA ticket for more information</a>.</p>
>>> 
>>> <p>Thanks so much!</p>
>>> 
>>> <hr>
>>> 
>>> <h3>FaQ: how does this relate to BigCouch?</h3>
>>> 
>>> <p>It doesn’t really, the BigCouch merge is ongoing and we will announce
>>> updates and requests for review when the time is right. Well, actually, if
>>> we can convince you to help with the review of the rcouch merge, we can put
>>> even more resources on the BigCouch merge :)</p>
>>> 
>>> 
>>> 
>>> 
>>> On 16 Apr 2014, at 16:34 , Benoit Chesneau <bchesneau@gmail.com> wrote:
>>> 
>>>> On Wed, Apr 16, 2014 at 3:56 PM, Noah Slater <nslater@apache.org> wrote:
>>>> 
>>>>> What about doing a blog post?
>>>>> 
>>>> 
>>>> My time is very limited these days, if anyone want to take the lead on
>>>> this, that would be cool.
>>>> 
>>>> - benoit
>>>> 
>>>> 
>>>> 
>>>>> 
>>>>> On 16 April 2014 15:36, Andy Wenk <andy@nms.de> wrote:
>>>>>> On 16 April 2014 15:28, Benoit Chesneau <bchesneau@gmail.com>
wrote:
>>>>>> 
>>>>>>> On Tue, Apr 8, 2014 at 12:05 PM, Noah Slater <nslater@apache.org>
>>>>> wrote:
>>>>>>> 
>>>>>>>> Benoit, if you'd like review, can you put some info together?
We can
>>>>>>>> circulate this on dev@ at first, and then do a blog post,
and
>>> promote
>>>>>>>> via social media.
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> I did many posts during the merge here asking for a review:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>> https://www.mail-archive.com/search?l=dev%40couchdb.apache.org&q=rcouch+status
>>>>>>> 
>>>>>>> That should help any dev interested in the review.
>>>>>>> 
>>>>>>> COUCHDB-1994 can be used to track any review. wohali started
some
>>> here:
>>>>>>> 
>>>>>>> https://issues.apache.org/jira/browse/COUCHDB-1994
>>>>>>> 
>>>>>>> Any information on the rcouch wiki are still valid also:
>>>>>>> 
>>>>>>> https://wiki.refuge.io/display/RCOUCH/rcouch
>>>>>>> 
>>>>>>> Hope it helps.
>>>>>>> 
>>>>>>> - benoit
>>>>>>> 
>>>>>>> 
>>>>>> in addition one could have a look into this for testing
>>>>>> https://www.mail-archive.com/dev%40couchdb.apache.org/msg29495.html
>>>>>> 
>>>>>> 
>>>>>>> On 6 April 2014 10:22, Benoit Chesneau <bchesneau@gmail.com>
wrote:
>>>>>>>>> On Fri, Mar 28, 2014 at 2:43 PM, Dave Cottlehuber <
>>>>> dch@jsonified.com>
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Hi again,
>>>>>>>>>> 
>>>>>>>>>> Benoit's mentioned that the rcouch import is more
or less complete
>>>>>>> from
>>>>>>>>>> his perspective. No doubt we'll have some mucking
around wrt docs,
>>>>>>>> fauxton,
>>>>>>>>>> build etc to sort out, but he feels its ready to
go.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> More or less from my perspective is nothing. I would
be more
>>>>> interested
>>>>>>>> to
>>>>>>>>> see any activity from other developers in reviewing that
code
>>>>> instead
>>>>>>> of
>>>>>>>>> adding new changes (except fixes) to the current code
base. Right
>>>>> now
>>>>>>>>> neither the couchdb project or me see any benefit in
my gift since
>>>>>>> noone
>>>>>>>> to
>>>>>>>>> my knowledge did a real (and public) review it,  started
to use it
>>>>> or
>>>>>>>> even
>>>>>>>>> considered to start to merge it upstream. Instead of
spending all
>>>>> this
>>>>>>>> time
>>>>>>>>> for free in cleaning the code I could have just took
a long vacation
>>>>>>> and
>>>>>>>>> continue to ad improvements on my own, which I did since.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> How are things going in bigcouch?
>>>>>>>>>> 
>>>>>>>>>> To be clear, we *should* make a decision of this
magnitude in a
>>>>>>> separate
>>>>>>>>>> VOTE thread, but let's discuss
>>>>>>>>>> further here and I will try to summarise & shepherd
towards a
>>>>>>> consensus.
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> We already have a consensus actually something near a
consensus
>>>>> defined
>>>>>>>>> months ago:
>>>>>>>>> 
>>>>>>>>> https://issues.apache.org/jira/browse/COUCHDB-1999
>>>>>>>>> 
>>>>>>>>> In my perspective, we can probably start to define these
milestones.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> - benoit
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> Noah Slater
>>>>>>>> https://twitter.com/nslater
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Andy Wenk
>>>>>> Hamburg - Germany
>>>>>> RockIt!
>>>>>> 
>>>>>> http://www.couchdb-buch.de
>>>>>> http://www.pg-praxisbuch.de
>>>>>> 
>>>>>> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>>>>>> 
>>>>>> https://people.apache.org/keys/committer/andywenk.asc
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Noah Slater
>>>>> https://twitter.com/nslater
>>>>> 
>>> 
>>> 
> 


Mime
View raw message