hrm why not making it a behaviour instead?
On Wednesday, February 5, 2014, wrote:
> Updated Branches:
> refs/heads/import aeb7911eb -> 510599f10
>
>
> Remove old notes module
>
> This module was never intended to be compiled. Including it just
> confuses rebar so we'll remove it.
>
>
> Project
Sorry for a bit offtopic start, but looking on all these talks about
ML I wonder why people don't use mail filters in their clients? This
is the awesome way to organize email by topics in the way you liked
and don't care about from which address it arrived. Adv. off (:
While I feel that idea is go
You interested in joining the marketing team and helping out Benjamin? :)
Add yourself to that wiki page! Woop!
On 4 February 2014 16:12, Benjamin Young wrote:
>
> On 1/22/14, 7:38 PM, Jens Alfke wrote:
>>
>> On Jan 22, 2014, at 3:23 PM, Simon Metson wrote:
>>
>>> Most recent posts are 1 post a
I know there are some people who really struggle with the workload of
dev@, who would be interested in general project discussion, but feel
swamped by JIRA, etc.
I think if there's a chance that we can gain even one more person
because dev@ is easier to cope with (and assuming no significant
downs
On Thu, Jan 30, 2014 at 5:08 PM, Dirkjan Ochtman wrote:
> On Thu, Jan 30, 2014 at 1:26 PM, Noah Slater wrote:
>> Wow. "couchdb-documentation" is very long! Why not "couchdb-docs"? :)
>
> +1 for -docs...
While -docs looks nicer and sounds shorter (and I'm also +1 for it),
the -documentation name
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 to
measure.
Adam
On Feb 4, 2014, at 3:53 AM, Noah Slater wro
[
https://issues.apache.org/jira/browse/COUCHDB-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell Branca closed COUCHDB-2045.
---
> Trace trap error while starting CouchDB
>
>
>
[
https://issues.apache.org/jira/browse/COUCHDB-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891033#comment-13891033
]
Russell Branca commented on COUCHDB-2045:
-
Thanks Newson, I can confirm the patc
[
https://issues.apache.org/jira/browse/COUCHDB-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson resolved COUCHDB-2045.
Resolution: Fixed
rebar.config.script used the same environment variables for icu, etc, a
[
https://issues.apache.org/jira/browse/COUCHDB-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on COUCHDB-1998 started by Robert Newson.
> Scripts and docs to boot dev cluster
>
>
> Key: COUCHDB-1998
>
[
https://issues.apache.org/jira/browse/COUCHDB-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson reassigned COUCHDB-1998:
--
Assignee: Robert Newson
> Scripts and docs to boot dev cluster
>
[
https://issues.apache.org/jira/browse/COUCHDB-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson reassigned COUCHDB-2001:
--
Assignee: Paul Joseph Davis
Since you're on this already.
> Finish the size calculat
Sue Lockwood created COUCHDB-2048:
-
Summary: Create UI for List functions
Key: COUCHDB-2048
URL: https://issues.apache.org/jira/browse/COUCHDB-2048
Project: CouchDB
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/COUCHDB-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sue Lockwood updated COUCHDB-2047:
--
Description:
http://docs.couchdb.org/en/latest/couchapp/ddocs.html#show-functions
Make a UI
Sue Lockwood created COUCHDB-2047:
-
Summary: UI for creating show functions
Key: COUCHDB-2047
URL: https://issues.apache.org/jira/browse/COUCHDB-2047
Project: CouchDB
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/COUCHDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sue Lockwood updated COUCHDB-2046:
--
Description:
Documentation
http://docs.couchdb.org/en/latest/couchapp/ddocs.html#filter-func
[
https://issues.apache.org/jira/browse/COUCHDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sue Lockwood updated COUCHDB-2046:
--
Description: Documentation
http://docs.couchdb.org/en/latest/couchapp/ddocs.html#filter-funct
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 en
[
https://issues.apache.org/jira/browse/COUCHDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sue Lockwood updated COUCHDB-2046:
--
Summary: Add Filter UI to Fauxton (was: Add Filter UI to Fauxton
Documentation
http://docs.
Sue Lockwood created COUCHDB-2046:
-
Summary: Add Filter UI to Fauxton
Documentation
http://docs.couchdb.org/en/latest/couchapp/ddocs.html#filter-functions
Like Views, we need a UI around filters
Key: COUCHDB-2046
On Tue, Feb 4, 2014 at 4:50 PM, Robert Samuel Newson 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 reba
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 me
On Tue, Feb 4, 2014 at 4:13 PM, Robert Samuel Newson 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 anyon
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 wr
"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, bi
and here :) http://people.apache.org/gallery.html
2014-02-04 Andy Wenk :
> and wouldn't it be great if all committers add themselves here?
>
> http://people.apache.org/projects.html
>
>
> On 4 February 2014 15:37, Andy Wenk wrote:
>
>> Hi,
>>
>> is there a specific reason why Apache CouchDB is no
I have added some info. I would like to help with the mailinglist stats but
I guess to make this one needs to be admin
Cheers
Andy
On 1 February 2014 14:39, Noah Slater wrote:
> Andy, here's the last one:
>
> https://wiki.apache.org/couchdb/Board_Report/2013_11
>
> Wasn't linked from the wiki
Hi,
is there a specific reason why Apache CouchDB is not listet here?
http://projects.apache.org/indexes.html
Thanks & Cheers
Andy
--
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
and wouldn't it be great if all committers add themselves here?
http://people.apache.org/projects.html
On 4 February 2014 15:37, Andy Wenk wrote:
> Hi,
>
> is there a specific reason why Apache CouchDB is not listet here?
>
> http://projects.apache.org/indexes.html
>
> Thanks & Cheers
>
> Andy
On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour 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
> wrote:
>
> > Following up to the 2013 retrospective thread:
> >
On Tue, Feb 4, 2014 at 2:35 PM, Nicolas Dufour 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
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 wrote:
> Following up to the 2013 retrospective thread:
>
> - Get more commit activity, especially in the core
> - Merge the forks (rco
Official LinkedIn page coming up tonight then; or if anyone is opposed, just
"-1" in the meantime! If anyone else ought to be added as manager of that or
the Facebook page let me know.
Ashley
Sent from my iPhone
+1
On 04 Feb 2014, at 1:04 PM, Andy Wenk wrote:
> On 4 February 2014 12:00, Noah Slater wrote:
>
>> I agree.
>>
>> If erlang@ becomes the place where newbie questions about Erlang go
>> ignored, we should can the list.
>>
>> You requested examples:
>>
>> http://mail-archives.apache.org/mod
Oops.
See the email I just sent: "GitHub, Git, and contributor workflows"
Also, interested to her what Humbedooh thinks about this. CCed him.
On 23 January 2014 16:31, Benjamin Young wrote:
> I had the good fortune of being in the #couchdb-meeting channel yesterday
> when the meeting kicked off
Hi folks,
There's an interesting discussion going on on general@incubator right now.
http://markmail.org/search/?q=list%3Aorg.apache.incubator-*+%22best+development+methodology+for+Apache+git%3F%22+order%3Adate-forward
These were mentioned, which may be of interest:
https://wiki.apache.org/jclo
On 4 February 2014 12:00, Noah Slater wrote:
> I agree.
>
> If erlang@ becomes the place where newbie questions about Erlang go
> ignored, we should can the list.
>
> You requested examples:
>
> http://mail-archives.apache.org/mod_mbox/openoffice-marketing/
>
> http://mail-archives.apache.org/mod
+1
On Tuesday, 4 February 2014 at 11:00, Noah Slater wrote:
> I agree.
>
> If erlang@ becomes the place where newbie questions about Erlang go
> ignored, we should can the list.
>
> You requested examples:
>
> http://mail-archives.apache.org/mod_mbox/openoffice-marketing/
>
> http://mail-a
I agree.
If erlang@ becomes the place where newbie questions about Erlang go
ignored, we should can the list.
You requested examples:
http://mail-archives.apache.org/mod_mbox/openoffice-marketing/
http://mail-archives.apache.org/mod_mbox/cloudstack-marketing/
Andy, how about two review dates?
On 4 February 2014 11:45, Noah Slater wrote:
> Success criteria:
>
> - The mailing lists are occasionally used, and when questions are
> posted there, replies are received.
> - People who might not otherwise have been active start to become active.
>
> Failure criteria:
>
> - Mails posted to the
Ashley,
Splitting this off to get back to what we were talking about. :)
On 2 February 2014 17:11, Ashley Parkes wrote:
> Sounds awesome!!
>
> Twitter -> Facebook: you first connect it to your main profile, then it gives
> you the option to reconnect it to a Page you manage. It's weird. From th
On Tue, Feb 4, 2014 at 11:45 AM, Noah Slater wrote:
> Nick, I don't think you are filibustering. You raise a good point that
> has not come up yet.
>
actually I already raised it. And took the Erlang ml as an example of a
very little traffic list. The advocacy list on postgresql, is also very
li
Nick, I don't think you are filibustering. You raise a good point that
has not come up yet.
Namely: what do we consider to be the success criteria of mailing
lists? And perhaps more importantly: what are the failure criteria?
Here's my attempt at answering those questions.
Success criteria:
- T
On Tue, Feb 4, 2014 at 11:30 AM, Nick North wrote:
> I'm probably going to regret jumping into this, especially as I'm
> modifying my earlier view a bit, but how about getting some objectivity by
> basing a decision on whether to go ahead on the record of the other
> spin-off lists that have alre
On Tue, Feb 4, 2014 at 11:35 AM, Robert Samuel Newson wrote:
>
> I don't see why the idea needs that much momentum behind it to get a pass
> / why there's so much inertia to do nothing new.
> Try it, see what happens, mailing lists can always be deleted.
>
> B.
>
>
I am not sure we can call a 1
PS I don't want to be seen as filibustering here so, if people consider this to
be a waste of time, I'm +1 on creating the list if the people who want to do
the work want it. (Even though it's not my own inclination.)
Nick
> On 4 Feb 2014, at 17:30, Nick North wrote:
>
> I'm probably going to
I don’t see why the idea needs that much momentum behind it to get a pass / why
there’s so much inertia to do nothing new.
Try it, see what happens, mailing lists can always be deleted.
B.
On 4 Feb 2014, at 10:30, Nick North wrote:
> I'm probably going to regret jumping into this, especially
I'm probably going to regret jumping into this, especially as I'm modifying my
earlier view a bit, but how about getting some objectivity by basing a decision
on whether to go ahead on the record of the other spin-off lists that have
already been created? I have no idea how much traffic they hav
On Tue, Feb 4, 2014 at 10:35 AM, Noah Slater wrote:
> Benoit, it's not that you're "the bad guy" for disagreeing. The
> problem is when you filibuster people until they run out of energy.
> This has been a problem for a long time now.
>
> As we continue to grow CouchDB we need to get out of this
I think the phrase is "disagree and commit". Make the list, if it’s not used or
causes problems close it.
FWIW I like “topic” lists and think marketing@ is a good idea, especially to
encourage non-technical involvement.
On Tuesday, 4 February 2014 at 09:35, Noah Slater wrote:
> Benoit, it
Benoit, it's not that you're "the bad guy" for disagreeing. The
problem is when you filibuster people until they run out of energy.
This has been a problem for a long time now.
As we continue to grow CouchDB we need to get out of this mindset that
unanimity is required to proceed on any action. Yo
On Tue, Feb 4, 2014 at 9:55 AM, Robert Samuel Newson wrote:
>
> +1 to all that, Noah. I can only imagine what this looks like to casual
> readers.
>
> Few things require unanimity and this is not one of them.
>
> The reason I've stayed quiet on the proposal is that while I don't feel
> strongly fo
We came to an agreement on what "[NOTICE]" means in this thread:
http://markmail.org/message/o27dls6t3pqtxjew
The first paragraph in this thread was:
"This is a notice that I am going to assume lazy consensus on the
proposal to create a marketing@ list. If you have a formal objection
to raise, p
On Tue, Feb 4, 2014 at 9:48 AM, Noah Slater wrote:
>
>
>
> "Also no formal ask about this mailing-list has been done in its own
> thread. Which I request."
>
> This is it. I've already done that. We're on that thread.
>
> No you sent a notice about its creation. Which is a way different.
- beno
+1 to all that, Noah. I can only imagine what this looks like to casual readers.
Few things require unanimity and this is not one of them.
The reason I’ve stayed quiet on the proposal is that while I don’t feel
strongly for it, I don’t feel strongly against it. It’s not my time or effort
being
We should have some success/failure criteria?
Success:
- Conversion continued to happen around JIRA
- PRs were not ignored (any more so than they already are)
- Review Board threads were not ignored
Failure:
- Participation/review frequency dropped noticeably
On 4 February 2014 09:37, Dirkj
I'd probably try it for a quarter.
On 4 February 2014 09:37, Dirkjan Ochtman wrote:
> On Tue, Feb 4, 2014 at 9:31 AM, Noah Slater wrote:
>> Not presupposing the answer here. But perhaps we could run an experiment?
>
> You mean, trying it out for a few weeks?
--
Noah Slater
https://twitter.c
On Mon, Feb 3, 2014 at 11:34 AM, Nick North wrote:
> I'd be in favour of keeping the number of lists small until it becomes clear
> that some topic needs to spin off into its own list. While the volume of
> marketing emails is low, it's not hard for devs who aren't that interested in
> marketin
Let's talk about that hostility. This email thread is an example of
that hostility. And what appears to be a knee-jerk over-reaction on my
part is my learnt reaction to this hostility.
To make it clear: CouchDB is paralysed. The PMC is paralysed. And it
has been for a long time. It seems we are un
On Tue, Feb 4, 2014 at 9:42 AM, Garren Smith wrote:
> Benoit, Andy and Noah
>
> Benoit has been the only one to raise an objection to this, so can we not
> assume that everyone else is ok with this? If so can we move on.
>
no i am not:
>> Nick North nort...@gmail.com
11:34 AM (22 hours ago)
Benoit, Andy and Noah
Benoit has been the only one to raise an objection to this, so can we not
assume that everyone else is ok with this? If so can we move on.
Cheers
Garren
On 04 Feb 2014, at 10:29 AM, Benoit Chesneau wrote:
> On Tue, Feb 4, 2014 at 9:03 AM, Andy Wenk wrote:
>
>> Hi Noah
On Tue, Feb 4, 2014 at 9:31 AM, Noah Slater wrote:
> Not presupposing the answer here. But perhaps we could run an experiment?
You mean, trying it out for a few weeks?
What about Review Board notifications?
My only concern is that conversation is happening in PRs, Review Board
emails, JIRA comments and so on.
If we move them to commits@ can we be sure that these things won't be
forgotten about?
Not presupposing the answer here. But perhaps we could run an expe
On Tue, Feb 4, 2014 at 9:03 AM, Andy Wenk wrote:
> Hi Noah and Benoit,
>
> I want to drop a personal note here. I do agree with both your targets and
> I am sure that both of you have very much more experience in this project
> regarding communication and organization. But what I feel right here
I think we should move the following email to the commits list:
- Wiki diffs
- Jira email
And possibly also:
- Github-generated email
IMO it would be best if the dev@ list was mostly used for human
discussion only, making it easier to digest for casual contributors.
If people want the firehose,
Hi Noah and Benoit,
I want to drop a personal note here. I do agree with both your targets and
I am sure that both of you have very much more experience in this project
regarding communication and organization. But what I feel right here is,
that Benoit feels kind of unheard and Noah doesn't want
[
https://issues.apache.org/jira/browse/COUCHDB-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890481#comment-13890481
]
Garren Smith commented on COUCHDB-2044:
---
This sounds like a great idea. If you nee
67 matches
Mail list logo
