I had planned to start slowly migrate the content from the old wiki,
but it seems I cannot edit or create new pages in new one. Do I need
to be added into some wiki group with write permissions?
--
,,,^..^,,,
On Sun, Feb 2, 2014 at 6:22 PM, Noah Slater wrote:
> We have a new wiki:
>
> https://cw
So this turned into more of a thing than I thought it'd be though I
have at least gotten couch_index split out onto a branch I think. I
need to do some diff's to make sure that its identical and then have
Benoit read the history to make sure its all sane. My notes on the
requisite git gymnastics ar
On Wed, Feb 5, 2014 at 8:27 PM, Paul Davis wrote:
> Cool. I'm gonna take a crack at getting all of the rcouch versions of
> apps split out into their respective repositories to see how hard
> it'll be to get things merged between the rcouch and bigcouch
> versions.
>
> I'll push anything I make to
On Wed, Feb 5, 2014 at 8:25 PM, Paul Davis wrote:
> On Wed, Feb 5, 2014 at 1:16 PM, Benoit Chesneau
> wrote:
> > On Wed, Feb 5, 2014 at 7:27 PM, Paul Davis >wrote:
> >
> >> Why the rename if you don't want to rename modules and all that comes
> >> with it? If you just rename the directory, couch
Cool. I'm gonna take a crack at getting all of the rcouch versions of
apps split out into their respective repositories to see how hard
it'll be to get things merged between the rcouch and bigcouch
versions.
I'll push anything I make to branches named import-rcouch and will
paste the commands I us
On Wed, Feb 5, 2014 at 1:16 PM, Benoit Chesneau wrote:
> On Wed, Feb 5, 2014 at 7:27 PM, Paul Davis wrote:
>
>> Why the rename if you don't want to rename modules and all that comes
>> with it? If you just rename the directory, couch.app.src, and
>> couch.erl I'm not sure I see the benefit.
>>
>
>
On Wed, Feb 5, 2014 at 4:00 PM, Benoit Chesneau wrote:
> I am seeing that bigcouch is splitting everything in its own repo. I could
> also do the same for rcouch quite easily. The question is how.
>
> I basically need the following repo:
>
> couch_collate
> couch_mrview
> couch_index
> couch_repl
On Wed, Feb 5, 2014 at 7:27 PM, Paul Davis wrote:
> Why the rename if you don't want to rename modules and all that comes
> with it? If you just rename the directory, couch.app.src, and
> couch.erl I'm not sure I see the benefit.
>
saying it's the core.
Why the rename if you don't want to rename modules and all that comes
with it? If you just rename the directory, couch.app.src, and
couch.erl I'm not sure I see the benefit.
On Wed, Feb 5, 2014 at 11:28 AM, Benoit Chesneau wrote:
> On Wed, Feb 5, 2014 at 5:52 PM, Paul Davis wrote:
>
>> > ok, make
On Wed, Feb 5, 2014 at 5:52 PM, Paul Davis wrote:
> > ok, make sense since i have also at some point moved it to src/couch (and
> > will be renamed to couch_core soon in rcouch).
>
> Why are you wanting to rename couch to couch_core? Erlang standard is
> to have "app/src/app_*.erl". Renaming every
> ok, make sense since i have also at some point moved it to src/couch (and
> will be renamed to couch_core soon in rcouch).
Why are you wanting to rename couch to couch_core? Erlang standard is
to have "app/src/app_*.erl". Renaming everything to couch_core_*.erl
would be a fairly massive change.
On Wed, Feb 5, 2014 at 4:38 PM, Paul Davis wrote:
> All of those repos already exist:
>
> https://git-wip-us.apache.org/repos/asf?s=couchdb
perfect
>
>
> Some but not all of those I've done the initial legwork on extracting
> source code from couch and/or rcouch. I have some time right now whil
All of those repos already exist:
https://git-wip-us.apache.org/repos/asf?s=couchdb
Some but not all of those I've done the initial legwork on extracting
source code from couch and/or rcouch. I have some time right now while
I wait on other things to pull those at into new branches named
somethin
I am seeing that bigcouch is splitting everything in its own repo. I could
also do the same for rcouch quite easily. The question is how.
I basically need the following repo:
couch_collate
couch_mrview
couch_index
couch_replicator
couch_httpd
couch_collate
(and probably soon a couch_js)
I think
On Wed, Feb 5, 2014 at 3:33 PM, Paul Davis wrote:
> No. Why would it?
>
> It may mean that we'd have to duplicate some similar components in
> couch_mrview but we can always factor out commonalities to a library
> app. Having couch_index try and be everything for indexers was the
> wrong approach.
[
https://issues.apache.org/jira/browse/COUCHDB-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892153#comment-13892153
]
Paul Joseph Davis commented on COUCHDB-2049:
We should add protection in cou
No. Why would it?
It may mean that we'd have to duplicate some similar components in
couch_mrview but we can always factor out commonalities to a library
app. Having couch_index try and be everything for indexers was the
wrong approach. Its easy to need to do things slightly differently
than couch
Its possible but given we've talked about removing the entire app I
don't see much point in putting in that much work on it till we figure
out what's going on there.
On Wed, Feb 5, 2014 at 12:10 AM, Benoit Chesneau wrote:
> hrm why not making it a behaviour instead?
>
> On Wednesday, February 5,
On Wed, Feb 5, 2014 at 3:21 PM, Paul Davis wrote:
> Its possible but given we've talked about removing the entire app I
> don't see much point in putting in that much work on it till we figure
> out what's going on there.
>
mmm does merging mrview and couch_index need to remove all the possibili
On Wed, Feb 5, 2014 at 12:55 PM, Noah Slater wrote:
> An experiment should be well defined, should have an owner
> (preferably), should have success/failure criteria, and should have an
> end date.
>
> As long as we have these things, I don't see any harm in experimenting
> to see what works.
>
There's no real way to automate it. So it would have to be a manual process.
If someone was willing to spend a bit of time each week to post all
the most relevant info, I think that'd be great. I tried to do some
roundups for a while, but they were taking up too much time.
Some things to roundup:
On 5 February 2014 13:06, Alexander Shorin wrote:
> On Wed, Feb 5, 2014 at 4:00 PM, Garren Smith wrote:
> > Would it be possible to have a summary email from commits sent to dev@.
> So basically a daily digest of any activities. That then would keep dev@in
> the loop without inundating the list
On Wed, Feb 5, 2014 at 1:00 PM, Garren Smith wrote:
> Would it be possible to have a summary email from commits sent to dev@.
> So basically a daily digest of any activities. That then would keep dev@in
> the loop without inundating the list.
>
That sounds good for me.Any idea how to handle t
On Wed, Feb 5, 2014 at 4:00 PM, Garren Smith wrote:
> Would it be possible to have a summary email from commits sent to dev@. So
> basically a daily digest of any activities. That then would keep dev@ in the
> loop without inundating the list.
Nice idea. Btw, in python-dev@ they used weekly bug
On Wed, Feb 5, 2014 at 1:00 PM, Garren Smith wrote:
> Would it be possible to have a summary email from commits sent to dev@.
> So basically a daily digest of any activities. That then would keep dev@in
> the loop without inundating the list.
>
+1
Would it be possible to have a summary email from commits sent to dev@. So
basically a daily digest of any activities. That then would keep dev@ in the
loop without inundating the list.
On 05 Feb 2014, at 1:58 PM, Dirkjan Ochtman wrote:
> On Wed, Feb 5, 2014 at 11:29 AM, Benoit Chesneau wrot
On 5 February 2014 11:08, Benoit Chesneau wrote:
>
> I see you already decided to go on this ml with some others people, so
> there is no reason to continue any discussion on that topic anyway
Not sure if you just worded this poorly, or whether you misunderstand
how decision making works. But in
On Wed, Feb 5, 2014 at 11:29 AM, Benoit Chesneau wrote:
> @Dirkjan what would be the purpose of @dev at the end in this case?
Have a place where people can keep track of high-level discussions
without having to be inundated with notifications from machines.
Cheers,
Dirkjan
An experiment should be well defined, should have an owner
(preferably), should have success/failure criteria, and should have an
end date.
As long as we have these things, I don't see any harm in experimenting
to see what works.
Communities (and other complex systems) are not like code. You cann
Benoit Chesneau created COUCHDB-2049:
Summary: latency in creation wit a quick deletion crash
couch_index_server
Key: COUCHDB-2049
URL: https://issues.apache.org/jira/browse/COUCHDB-2049
Project:
[
https://issues.apache.org/jira/browse/COUCHDB-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-2049:
-
Description:
When you quickly start to refresh an index:
{code:erlang}
refresh(#db{nam
[
https://issues.apache.org/jira/browse/COUCHDB-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-2049:
-
Description:
When you quickly start to refresh an index:
{code}
refresh(#db{name=DbNam
On Wed, Feb 5, 2014 at 11:19 AM, Andy Wenk wrote:
> On 5 February 2014 11:08, Benoit Chesneau wrote:
>
> > On Tue, Feb 4, 2014 at 12:00 PM, Noah Slater wrote:
> >
> > > I agree.
> > >
> > > If erlang@ becomes the place where newbie questions about Erlang go
> > > ignored, we should can the list
On Tue, Feb 4, 2014 at 10:40 PM, Adam Kocoloski wrote:
> Tricky. I'm fine with trying it out, but I do wonder how many casual
> followers of dev@ would miss the really interesting technical
> conversations that sometime happen on code reviews and (especially) JIRA
> tickets. Not an easy thing t
On Wed, Feb 5, 2014 at 11:16 AM, Alexander Shorin wrote:
> On Wed, Feb 5, 2014 at 2:10 PM, Benoit Chesneau
> wrote:
> > On Wed, Feb 5, 2014 at 11:03 AM, Alexander Shorin
> wrote:
> >
> >> On Wed, Feb 5, 2014 at 1:53 PM, Noah Slater wrote:
> >> > We wont know until we try. Perhaps that's why an
On 5 February 2014 11:08, Benoit Chesneau wrote:
> On Tue, Feb 4, 2014 at 12:00 PM, Noah Slater wrote:
>
> > I agree.
> >
> > If erlang@ becomes the place where newbie questions about Erlang go
> > ignored, we should can the list.
> >
>
> It's already some months since its creation without much
On Wed, Feb 5, 2014 at 2:10 PM, Benoit Chesneau wrote:
> On Wed, Feb 5, 2014 at 11:03 AM, Alexander Shorin wrote:
>
>> On Wed, Feb 5, 2014 at 1:53 PM, Noah Slater wrote:
>> > We wont know until we try. Perhaps that's why an experiment would be a
>> > good idea?
>>
>> Experiments are fun (: and t
On Wed, Feb 5, 2014 at 11:03 AM, Alexander Shorin wrote:
> On Wed, Feb 5, 2014 at 1:53 PM, Noah Slater wrote:
> > We wont know until we try. Perhaps that's why an experiment would be a
> > good idea?
>
> Experiments are fun (: and the only way to find the sweet spot or
> ensure that it had been
On Tue, Feb 4, 2014 at 12:00 PM, Noah Slater wrote:
> I agree.
>
> If erlang@ becomes the place where newbie questions about Erlang go
> ignored, we should can the list.
>
It's already some months since its creation without much activity.
> You requested examples:
>
> http://mail-archives.apac
On Wed, Feb 5, 2014 at 1:53 PM, Noah Slater wrote:
> We wont know until we try. Perhaps that's why an experiment would be a
> good idea?
Experiments are fun (: and the only way to find the sweet spot or
ensure that it had been already found.
> I still expect committers to subscribe to commits@.
Not sure it matters, to be honest, whether someone mistakes
couchdb-docs for an Erlang module for handling JSON documents. This is
the last email I will send on this, because bike shed painting is
something of a vice for me.
On 5 February 2014 10:39, Alexander Shorin wrote:
> On Wed, Feb 5, 2014
We wont know until we try. Perhaps that's why an experiment would be a
good idea?
I still expect committers to subscribe to commits@. But if a
non-committer is interested (i.e. might've commented) they are free to
subscribe too.
And yes, I hear you about mail filters. But not everybody does use
t
On Wed, Feb 5, 2014 at 1:32 PM, Andy Wenk wrote:
> I hope I did not miss something, but is there a list somewhere which repos
> do exist now?
https://git-wip-us.apache.org/repos/asf?s=couchdb
--
,,,^..^,,,
I hope I did not miss something, but is there a list somewhere which repos
do exist now?
Thanks for help !
Cheers
Andy
On 5 February 2014 00:06, Alexander Shorin wrote:
> On Thu, Jan 30, 2014 at 5:08 PM, Dirkjan Ochtman
> wrote:
> > On Thu, Jan 30, 2014 at 1:26 PM, Noah Slater wrote:
> >>
On 5 February 2014 00:25, Noah Slater wrote:
> You interested in joining the marketing team and helping out Benjamin? :)
>
> Add yourself to that wiki page! Woop!
>
+1 Go Go Go Benjamin :)
--
Andy Wenk
Hamburg - Germany
RockIt!
http://www.couchdb-buch.de
http://www.pg-praxisbuch.de
GPG finge
Hi devs!
I just extracted all sphinx-docs bits from couchdb.git to
couchdb-documentation.git and suddenly realized that I cannot just put
new Makefile there and run `make html` because:
1) Docs are uses project's VSN info and some other information bits
like project shortname (CouchDB) and fullna
46 matches
Mail list logo
