n.
On Mon, Sep 28, 2015 at 3:22 PM, Jason Smith
wrote:
> On Mon, Sep 28, 2015 at 5:11 AM, ermouth wrote:
>
>> I‘ve taken that PR, cleaned it up, modified for chttpd and fixed several
>> most hitting performance issues. Right now performance isn‘t so terrible.
>>
&
On Mon, Sep 28, 2015 at 5:11 AM, ermouth wrote:
> I‘ve taken that PR, cleaned it up, modified for chttpd and fixed several
> most hitting performance issues. Right now performance isn‘t so terrible.
>
At first glance, my guess about performance is that there are two problems
(both stemming from
Hi, Ermouth. Cool!
I'd like to focus specifically on your access control comment.
On Mon, Sep 28, 2015 at 5:11 AM, ermouth wrote:
> Solves a lot of inherent couchapp problems: enables access control on early
> stage, query-based rewrites,
Can you unpack "access control"? I'd like to have a
100% sure why they really fail (and deploys broken releases
> therefore). But I have worked with people that were so deep into the
> testsuites and the project they maintained in the past that they were able
> to predict that.
>
> In short I support whatever you decide for I just wa
Hi, Dale.
On Tue, Sep 15, 2015 at 7:26 PM, Dale Harvey wrote:
>
> I just wanted to clarify, are you speaking about removing as a "pre-commit
> hook", or removing the requirements for those checks to pass before
> merging?
>
I am speaking about removing the pre-commit hook only--the mechanical t
Hi, list!
I want to share my plan for preparing to work on couchdb-nano. Briefly, I
want to fix a thing or two in the project, but I think a more urgent change
is the pre-commit hooks enforcing coding style and test coverage.
The Nano project has several brilliant checks that it can do:
https://g
Thanks, Jan.
On Tue, Sep 15, 2015 at 5:18 PM, Jan Lehnardt wrote:
>
> 3. if you disagree with employing a “Yes, and…”-style in the CouchDB
> community, make a counter proposal that you think gets us to a better
> culture.
>
TL;DR = We are doing that; but what is "better"? To me, it means fun and
On Mon, Sep 14, 2015 at 11:49 PM, ermouth wrote:
> > Have you ever played "Dungeons and Dragons"?
>
> Sorry, I played Civilization. What I learned was that saying ‘No’ at right
> moment is much more important to have excellent score, then saying ‘Yes’
> each time )
>
:)
Cool. Well, anyway, I fi
Have you ever played "Dungeons and Dragons"?
I think the "yes-and" style is more about continuing the momentum of the
conversation, and also having fun!
The "yes-and" style is independent of your opinion about the matter, or the
facts of its consequences. To me, it is about being Socratic: say "S
On Thu, Sep 10, 2015 at 8:58 PM, Ilya Khlopotov wrote:
> > Is there a way to publish an Erlang module for downstream users
> independently of git? If yes, we could move back to a single-git-tree
> model for
> CouchDB, but we can still release parts as independent modules. I know
> there have
> b
On Thu, Sep 10, 2015 at 4:40 PM, Dale Harvey wrote:
> I do think multirepos is an issue and that solution is not so simple, we
> went through the same issues with pouchdb as we attempted to split out our
> repository.
>
If I understand correctly, this is what we do now...
>
> 1. Dont split out
Hi, Robert. Well, that was very long and I read every word! Thank you for
your thoughtful assessment and feedback!
You make many points across several different areas of concern. It sounds
to me like the primary thrust of your argument is about continuous
integration--somehow making it more easy a
Right, good point, Alexander.
In that case, I would say, let's not do an actual GitHub "transfer." There
are only a few tickets. I think we could move the key ones over by hand
ourselves; and in the fullness of time, it won't much matter.
On Wed, Aug 12, 2015 at 2:39 AM, Robert Kowalski wrote:
Hi, dev@. And hi, Johannes (hope you see this).
Last month, you asked what to do about releasing Apache Nano (or Apache
CouchDB Nano, or whatever its name is).
I would like to get involved in that effort, and to help push it forward.
Nuno and the team graciously donated the project to the ASF. I
Congratulations to the Nano project and to everyone involved!
On Wed, Jul 15, 2015 at 6:56 AM, Robert Kowalski wrote:
> Hi!
>
> I am happy to welcome nano as a new subproject of the CouchDB project!
>
> Nano is a minimalistic Node.js client for CouchDB.
>
> The code is located at
> https://git-w
That is awesome! Visualizing the revision tree will greatly help people to
understand CouchDB (particularly since more people are familiar with tools
like Git, which have similar structures).
Thanks very much for this work!
On Sat, May 30, 2015 at 6:07 PM, Nadeeshaan Gunasinghe <
nadeeshaangunasi
correctly, expand the new Query
> Server
>to also handle Views. At this point, adding view support should not be
> too
>complicated anymore.
>
>
> Things to watch out for:
>
> - map/reduce functions for CouchDB views need to be “pure”, e.g. we need
> to guara
ore colors than just red or blue
> >
> > Kevin
> > On Oct 30, 2014 6:11 AM, "Brad Noble" wrote:
> >
> >> *SyncDB*
> >> The database that syncs.
> >>
> >> Logo would embody that idea.
> >>
> >>
> >>
>
On Thu, Oct 30, 2014 at 12:52 AM, Noah Slater wrote:
> Blue is nice. :) But then that tempts me to change the name too. I
> mean, if we're ever going to do this, now is the time. It's important
> to note though that we have a very STRONG brand, and changing it in a
> big will be expensive.
>
Cha
I have been thinking about Brad's point for a long time now. What exactly
is relaxing? Since CouchDB came out, web APIs, NoSQL and JavaScript have
become [more] mainstream. Today's users are not impressed that they can
store an unstructured JSON blob, or that they can use JavaScript on the
server.
Welcome!
On Tue, Sep 9, 2014 at 10:36 PM, Nick North wrote:
> Welcome Jenn!
>
> Nick
>
> > On 9 Sep 2014, at 15:06, Noah Slater wrote:
> >
> > Dear community,
> >
> > I am pleased to announce that the CouchDB Project Management Committee
> > has elected Jenn Schiffer as a CouchDB committer.
> >
Hi, Russell. This is okay for a starting point but it is a bit vague. Could
you perhaps flesh out the plan and make it more comprehensive?
^^ That is a joke!
Seriously, thank you very much for this analysis and plan. This is very
exciting! (Not least because the http codebase is the part I know b
On Mon, Aug 4, 2014 at 3:30 PM, Robert Samuel Newson
wrote:
> +1
>
> My preference to simplify some of the technical terms in the CoC do not
> prevent me voting for the intent behind them, and I recognise that no list
> of diversity axes can be complete.
>
I agree. I would hope to say "do not be
เมื่อ วันจันทร์ที่ 4 สิงหาคม ค.ศ. 2014, Nicolas Dufour
เขียนว่า:
> This text is well written but completely unnecessary unless the couchdb
> community needs more than common sense to police itself.
Hi, Nicholas. Thanks for your vote!
You got it! The CouchDB community needs more than common sen
+1
Thank you very much to everybody who has worked on this and debated it back
and forth. I am very grateful for your work and very proud of our community.
On Sun, Aug 3, 2014 at 8:18 AM, Joan Touzet wrote:
> Voting period starts 03:00:00 UTC on Sunday, August 3, 2014
> Votes must be r
+1
เมื่อ วันอังคารที่ 29 กรกฎาคม ค.ศ. 2014, Joan Touzet
เขียนว่า:
> Noah asked me to clarify what I mean here.
>
> I vote +1, with the understanding that the clarification he has listed
> below is the intent of the rule.
>
> -Joan
>
> - Original Message -
> From: "Joan Touzet" >
> To: de
+1
Thanks, Noah!
On Mon, Jul 28, 2014 at 11:25 PM, Jan Lehnardt wrote:
> Sensible. Thanks for catching this!
>
> +1
>
> Best
> Jan
> --
>
> > On 28.07.2014, at 16:55, Noah Slater wrote:
> >
> > Hello folks,
> >
> > In a discussion between myself, Joan, and Bob on IRC today, it became
> > clea
r
> Paul Davis
> Jan Lenhardt
> Robert Newson
> Alexander Shorin
> Noah Slater
> Joan Touzet
> Andy Wenk
>
>
> -1: 0
> -
>
>
> Abstentions: 4
> --
> Benoit Chesneau
> Adam Kocoloski
> Ted Leung
> Jason Smith
>
>
> The vote
On Mon, Jul 21, 2014 at 9:56 AM, Benoit Chesneau
wrote:
> Anyway I don't want to discuss about psychology. I don't think we should
> base a code of conduct on a psychology term prone to conflict. It should be
> neutral and precise.
>
Le mieux, c'est l'ennemi du bien.
HI, all. I am moving to my final Airbnb of this trip. I should be finished
by 12 and go to the office after that.
[
https://issues.apache.org/jira/browse/COUCHDB-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009480#comment-14009480
]
Jason Smith commented on COUCHDB-2248:
--
Often, speakers of English as a se
On Tue, May 20, 2014 at 9:44 PM, Dave Cottlehuber wrote:
>
> > On May 11, 2014, at 8:35, Noah Slater wrote:
> >
> > > Community,
> > >
> > > Please do take the time to review this document. It's not that long,
> > > or that complex. An online reading time calculator said it's about 14
> > > minut
Hi, Joan. Thanks for this!
First, a perhaps trivial note: the document switches once or twice to and
from the Oxford comma. ("...twitter, and"; "...friendly and")
I have two comments about specific guideline 5 ("words we choose").
Can we get profanity explicity listed here? It is generally consi
Noah, in section 3.4, Vetos:
> Any change to the source code that we distribute in our official releases
may be vetoed by casting a -1 vote on it.
Is that a -1 *binding* vote? Only committers can veto commits, right?
> The validity of a veto can be put to a vote.
Which kind of vote is this? It
On Tue, Apr 29, 2014 at 6:56 PM, Mike Rhodes wrote:
> On 29 April 2014 11:18, Jason Smith wrote:
>
> > Rule: No profanity
> >
> > Secondly, this is only a suspicion, but I think profanity (and also cocky
> > faux hatred), is a shibboleth indicating manhood and that
scratching your groin.
Men generally curb that behavior in mixed company. It reminds me of bulls
locking horns to impress a mate. Maybe F-bombs and the anger it stands for
are scaring some women away from software. Could be wrong, though.
On Tue, Apr 29, 2014 at 4:57 PM, Jason Smith wrote:
> TL
TL;DR = Is immediate removal from the project really worth thinking about?
Noah, can you think of an example infraction that could plausibly trigger
an immediate removal from the project, for a first offense? Yes we can all
think of hypothetical examples, but something plausible from this communit
[
https://issues.apache.org/jira/browse/COUCHDB-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882160#comment-13882160
]
Jason Smith commented on COUCHDB-2037:
--
I wrote up some operational advice a
[
https://issues.apache.org/jira/browse/COUCHDB-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882159#comment-13882159
]
Jason Smith commented on COUCHDB-2037:
--
Interestingly, CouchDB already has
Congratulations, Nick. Welcome!
On Thu, Jan 2, 2014 at 7:16 AM, Sue wrote:
> Welcome Nick! :D
>
>
> On Wed, Jan 1, 2014 at 6:29 PM, Robert Newson wrote:
>
> > Welcome!
> >
> > On 1 Jan 2014, at 20:20, Simon Metson wrote:
> >
> > > w00t!
> > >
> > >
> > > On Wednesday, 1 January 2014 at 19:24,
lve such collision I may
> tag
> > >>> my commit message:
> > >>>
> > >>> Docs: add foo/bar config option // now you know what have changed!
> > >>>
> > >>> or imagine something like:
> > >>>
> > >>> Add
pdate code, tests, and documentation. A useful tag might be [ui]
but I could get the same thing by looking at the history of src/fauxton/.
It is marginally useful at a very dear cost: 4-10 characters per commit
message.
On Wed, Dec 4, 2013 at 11:24 PM, Jason Smith wrote:
> -1
>
> We d
-1
We do this at Nodejitsu and I find it tedious and unhelpful. It's a bit of
ceremony with little benefit. For me at least, I never want to see "only
[foo] commits" I want to see "only commits in subdirectory foo/". Otherwise
I see the commits through `git blame`.
That's my opinion, but I am com
vice". Are we talking about
> partial mirroring instead then? If so, filtered replication has you
> covered, right? If you just want a local mirror of the things you use,
> then pull through a caching proxy (squid3 is nice).
>
> B.
>
>
> On 27 November 2013 14:07, Jason
Damien used to say, "there are vitamins and there are pain pills."
Bigcouch is a vitamin[1]: a long-term fix to the general health and
robustness of the system.
npm needs a pain pill. And it is going to get one. Why do I respect the
Node.js community? Certainly not because of the language! No, be
I am on-record as supportive of npm's needs here but still skeptical or at
least unclear on the fix.
Pain points:
1. Replicating the registry can have problems. Best-case scenario you have
to download 100GB of data (and growing exponentially)
2. Bandwidth costs of the primary service
Both probl
[
https://issues.apache.org/jira/browse/COUCHDB-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778473#comment-13778473
]
Jason Smith commented on COUCHDB-1894:
--
[~wohali] This code does explic
[
https://issues.apache.org/jira/browse/COUCHDB-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778376#comment-13778376
]
Jason Smith commented on COUCHDB-1894:
--
[~chewbranca], can you add some spec
[
https://issues.apache.org/jira/browse/COUCHDB-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777374#comment-13777374
]
Jason Smith commented on COUCHDB-1894:
--
A note on terminology (at least t
For my money I rather like the sync and the async API. It could be
more orthogonal but it's not so bad. If I only have a few doc ids to
replicate, I prefer the sync way (_replicate) rather than creating a
document and watching it by polling or _changes or something.
On Mon, Sep 23, 2013 at 5:44 PM
[
https://issues.apache.org/jira/browse/COUCHDB-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774418#comment-13774418
]
Jason Smith commented on COUCHDB-1893:
--
Note, compaction is not the only t
[
https://issues.apache.org/jira/browse/COUCHDB-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774395#comment-13774395
]
Jason Smith commented on COUCHDB-1893:
--
[~kxepal] I think he wants to repli
[
https://issues.apache.org/jira/browse/COUCHDB-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774392#comment-13774392
]
Jason Smith commented on COUCHDB-1893:
--
Thanks, Stéphane.
I like this. B
For what it's worth, in my node_couchdb branch I completely removed
"JavaScript" (couchjs) from the project because Couch expects you to
install your own couchjs binary yourself (presumably the one from Node
npm, but in principle it could be any view server).
On Sat, Sep 21, 2013 at 4:48 PM, Benoi
+1
Some sort of "CouchDB Core" project or something?
On Thu, Sep 19, 2013 at 4:51 PM, Benoit Chesneau wrote:
> Hi,
>
> I am thinking to make all this extra C optional in couchdb. By extra C I
> mean:
>
> - snappy compression
> - couch compare function using ICU
> - JS views
> - JSON encoding
>
[
https://issues.apache.org/jira/browse/COUCHDB-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764471#comment-13764471
]
Jason Smith commented on COUCHDB-907:
-
Thanks for your help, Brian!
It is
[
https://issues.apache.org/jira/browse/COUCHDB-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749347#comment-13749347
]
Jason Smith commented on COUCHDB-1377:
--
Oh yes, I meant 1.5 I just misspelle
[
https://issues.apache.org/jira/browse/COUCHDB-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749338#comment-13749338
]
Jason Smith commented on COUCHDB-1377:
--
This has been in production at Iris C
[
https://issues.apache.org/jira/browse/COUCHDB-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748514#comment-13748514
]
Jason Smith commented on COUCHDB-906:
-
What do people think of making a rel
Jan and anyone else, if you want to review my changes (20ish lines of code)
to your plugin branch, see
https://github.com/jhs/couchdb/compare/1867-feature-plugins...plugins
It is also in ASF Git.
A plugin can have priv/couch_plugin.config which is sent to Erlang as an
application config. Thi
On Mon, Aug 19, 2013 at 8:23 PM, Jan Lehnardt wrote:
>
> On Aug 19, 2013, at 06:58 , Dave Cottlehuber wrote:
>
> > +1 let's do this.
> >
> > Russell + others, do you think Fauxton is ready for mentioning as
> > "experimental" in release notes, and possibly providing link or access to
> > try it
Love it. Relaxing and ticking.
On Mon, Aug 19, 2013 at 3:53 PM, Dave Cottlehuber wrote:
> It means you need to Relax and tick the box.
>
>
> On 19 August 2013 09:41, Jason Smith wrote:
>
> > In the call for speakers on http://conf.couchdb.org/ there is a required
>
In the call for speakers on http://conf.couchdb.org/ there is a required
boolean field, "I'm a Couch." What does that mean?
Thanks.
[
https://issues.apache.org/jira/browse/COUCHDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742980#comment-13742980
]
Jason Smith commented on COUCHDB-1867:
--
Yes, I have a common install of Cou
[
https://issues.apache.org/jira/browse/COUCHDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742967#comment-13742967
]
Jason Smith commented on COUCHDB-1867:
--
Sure. As long as I can enable/dis
[
https://issues.apache.org/jira/browse/COUCHDB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742917#comment-13742917
]
Jason Smith commented on COUCHDB-1867:
--
The blacklist exists so you can spe
On Fri, Aug 16, 2013 at 4:49 PM, Volker Mische wrote:
> On 08/16/2013 11:32 AM, Alexander Shorin wrote:
> > On Fri, Aug 16, 2013 at 1:12 PM, Benoit Chesneau
> wrote:
> >> I agree, (modulo the fact that I would replace a string by a binary ;)
> but
> >> that would be only possible if we extract th
Welcome, Sue!
On Thu, Aug 15, 2013 at 12:50 AM, Octavian Damiean wrote:
> Congratulations Sue! Well done.
> On Aug 14, 2013 6:13 PM, "Noah Slater" wrote:
>
> > Dear community,
> >
> > I am pleased to announce that the CouchDB Project Management Committee
> has
> > elected Sue Lockwood as a Couc
I would also prefer that the wiki run on free software; however if we had a
decent import/export feature I would be satisfied.
On Mon, Aug 12, 2013 at 3:39 PM, Benoit Chesneau wrote:
> Like said Dave this has been discussed in may. I have no strong opinion on
> that. Apart the speed which is qui
FWIW I avoid the wiki because of the pain and slowness.
Speed is a feature, and the wiki is slow. It is slow to execute, but also
it is slow to sign in (every time I sign in, it begins with a "forgot
password" step). And it is slow to join. New editors must email asking for
permission.
Often, whe
On Thu, Aug 8, 2013 at 7:45 PM, Paul Davis wrote:
> A behavior isn't quite right because as Jan points out, you may not
> want to implement every hook.
Did you see my followup where I compare to gen_server behavior, with only
two (significant) hooks to implement, handle_call/3 and handle_cast/2?
ion, Key, Value])
, update_my_config_db(Section, Key, Value)
;
on(Unknown) -> ok
, io:format("Did you know there is a ~p hook?\n", [element(1, Unknown)])
.
On Thu, Aug 8, 2013 at 5:42 PM, Jan Lehnardt wrote:
>
> On Aug 8, 2013, at 12:39 , Jason Smith wrote:
okay bang-for-buck; only not much bang or much buck.
On Thu, Aug 8, 2013 at 5:26 PM, Jan Lehnardt wrote:
> how would this look in code?
>
> On Aug 8, 2013, at 12:21 , Jason Smith wrote:
>
> > Perhaps a custom behaviour to help catch API problems at compile time?
>
Perhaps a custom behaviour to help catch API problems at compile time?
-behaviour(couchdb_plugin).
On Thu, Aug 8, 2013 at 3:47 PM, Jan Lehnardt wrote:
> Heya,
>
> I’m toying with the idea of moving some of my experimental into
> bona-fide plugins. One of them is my log_to_db branch that o
http://git-wip-us.apache.org/repos/asf/couchdb/commit/a653e8d0
> > Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/a653e8d0
> > Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/a653e8d0
> >
> > Branch: refs/heads/master
> > Commit: a653e8d0fcf0e8560
Given how old this plugin is (it came out right after BrowserID was
announced IIRC), I kind of want to merge it in, then refactor it out
if/when plugins improve.
On Mon, Jul 29, 2013 at 11:24 PM, Dirkjan Ochtman wrote:
> On Mon, Jul 29, 2013 at 5:24 PM, Dale Harvey wrote:
>> On the topic of brow
support have
> been around a long time but are mostly only available to the dedicated few
> (cors did eventually get merged), I would love to see a couchdb where the
> browser_id plugin was available to all users of couchdb the day you
> finished writing it, not (3?) years later
>
>
>
Perfect, that is exactly what I will need. However, the first
milestone is rewrite my plugin in a branch, and hit the first
milestone.
On Mon, Jul 29, 2013 at 5:19 PM, Dirkjan Ochtman wrote:
> On Mon, Jul 29, 2013 at 12:02 PM, Jason Smith wrote:
>> To clarify, "tinfoil hat&quo
that stuff.
On Mon, Jul 29, 2013 at 4:03 PM, Dirkjan Ochtman wrote:
> On Mon, Jul 29, 2013 at 6:13 AM, Jason Smith wrote:
>> Thanks, Jim. That is basically my plan. To be clear, I would ship
>> "outsourced mode" (browserid.org hosted JavaScript and verification)
>>
On Mon, Jul 29, 2013 at 6:22 AM, Benoit Chesneau wrote:
> Also yes I really think that the "I have a dream" quote is already too much
> tarnished to not mention it further even if people had the better
> intentions when they mention it.
One cannot argue with such statements. One can only underlin
Oh, for God's sake.
On Mon, Jul 29, 2013 at 1:05 PM, Benoit Chesneau wrote:
> any mention to martin luther king should be removed.Please don't associate
> his vision to something as ridiculous as a vision for a product.
>
> For the rest shouldn't this document link tothe still running thread and
from Mozilla.
>
> +1 if someone wants to build a plugin that implements the full BrowserID
> protocol inside CouchDB.
>
> Jim Klo
> Senior Software Engineer
> SRI International
> p: 805.542.9330 x121
> t: @nsomnac
>
> On Jul 28, 2013, at 8:30 PM, "Jason Smith
ll in house" solution is preferred since it will
> allow private local area networks to use such auth for CouchDB without
> need to access some remote resources. With browserid / persona it will
> be possible to have CouchDB as auth server for other instances, right?
> --
> ,,,^..^
ll in house" solution is preferred since it will
> allow private local area networks to use such auth for CouchDB without
> need to access some remote resources. With browserid / persona it will
> be possible to have CouchDB as auth server for other instances, right?
> --
> ,,,^..^
(Breaking off from the "IRC meeting" thread.)
Credit where it's due: The initial push for Persona in CouchDB came
from Randall Leeds.
Dirkjan says to use the hosted include.js file instead of serving it
internally. I kind of agree, but note that CouchDB hosts its own
JQuery. The priority is not t
Thanks. I would like to ask about merging in my longstanding "plugins" for
authentication: Mozilla Persona and OAuth. (Well, the latter is from
Ocasta. I just made it into a plugin. Xylophone)
On Tuesday, July 23, 2013, Alexander Shorin wrote:
> Hi all,
>
> We'll be having the usual meeting in #c
Thanks. I would like to ask about merging in my longstanding "plugins" for
authentication: Mozilla Persona and OAuth. (Well, the latter is from
Ocasta. I just made it into a plugin. Xylophone)
On Tuesday, July 23, 2013, Alexander Shorin wrote:
> Hi all,
>
> We'll be having the usual meeting in #c
Was the meeting just now (13:00 UTC)? I didn't see anybody.
On Tue, Jul 9, 2013 at 2:01 PM, Alexander Shorin wrote:
>
> Hi all,
>
> We'll be having the usual meeting in #couchdb-meeting on
> irc.freenode.org at 13:00 UTC, Wednesday as usual.
>
> The meeting room:
>
> irc://irc.freenode.net/c
Thank you very much for this excellent update!
On Wed, Jun 19, 2013 at 1:16 PM, Russell Branca wrote:
> (Also gisted at https://gist.github.com/chewbranca/5816534)
>
> # Fauxton Tidings
>
> It's been some time since we've had a Fauxton update. There's been a
> number of exciting updates with act
Peed my pants.
Also, yes I too am excited about Jan's announcement.
On Fri, Jun 7, 2013 at 6:54 PM, Noah Slater wrote:
> Ooh, exciting!
>
>
> On 7 June 2013 12:36, Jan Lehnardt wrote:
>
> >
> > On Jun 7, 2013, at 12:16 , Noah Slater wrote:
> >
> > > Aha! Looks like we never shared this with
Agreed!
On Thu, Jun 6, 2013 at 5:48 PM, Robert Newson wrote:
> Ok, I think everyone is over-reading my suggestion to drive release
> notes from commit messages. I'm sure there will always be a manual,
> human step to convert the commit messages between two points into
> release notes, I'm just
se notes, could we not
> mark specific commit messages e.g. [Release Notes] so that only specific
> commit messages get added into the release notes and other commits get
> ignored.
>
> Cheers
> Garren
>
> On 05 Jun 2013, at 5:53 AM, Jason Smith wrote:
>
> > To a first a
To a first approximation, I like Bob Newson's idea (option 1 in the
OP). It seems the most workable for a large distributed team of
volunteers.
I am probably a bad teammate, but I always find myself forgetting or
misunderstanding policies and changes to policies. So I like the
simplest, most intui
On Wed, Jun 5, 2013 at 5:40 AM, Joan Touzet wrote:
> Today, if I GET http://localhost:5984/ , I get:
>
>
> {"couchdb":"Welcome","uuid":"b1b1dbe964914a9cb1467bfd4f297fed","version":"1.3.0","vendor":{"version":"1.3.0","name":"The
> Apache Software Foundation"}}
>
> If I GET from http://mozauto.iris
Thanks
On Wednesday, June 5, 2013, Noah Slater wrote:
> Jason, we're alternating between 19:00 UTC and 13:00 UTC. This week we're
> doing 19:00.
>
>
> On 4 June 2013 18:11, Jason Smith >
> wrote:
>
> > Thanks, Alex.
> >
> > What is the current
Thanks, Alex.
What is the current policy about rotating times? Thanks.
On Tue, Jun 4, 2013 at 5:43 PM, Alexander Shorin wrote:
> Hi all,
>
> We'll be having the usual meeting in #couchdb-meeting on
> irc.freenode.org at 19:00 UTC, Wednesday as usual.
>
> The meeting room:
>
> irc://irc.fre
On Sat, Jun 1, 2013 at 9:14 AM, Randall Leeds wrote:
> On Fri, May 31, 2013 at 4:30 PM, Jason Smith wrote:
> > Hi, Benoit.
> >
> > I did not put this in a branch since it was a single commit. I think I
> > missed that IRC meeting and did not realize the policy.
> &g
> in the query string.
> >>
> >> Updating _config/admins/* already requires admin privileges, so there is
> >> no change to the security.
> >>
> >>
> >> Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
> >> Commit: ht
Sorry, just catching up.
+1
On Fri, May 10, 2013 at 4:29 PM, Jan Lehnardt wrote:
> +1
>
> Jan
> --
>
> On May 7, 2013, at 21:34 , Robert Newson wrote:
>
>> Hi All,
>>
>> I propose to merge in the following work,
>> https://github.com/rnewson/couchdb/tree/nebraska-merge-candidate to
>> the offic
The couchjs npm package (a drop-in Node.js replacement for
SpiderMonkey) uses synchronous i/o. I had great success using Fibers
for this.
https://github.com/iriscouch/couchjs/blob/master/couchjs.js#L50-L68
readline() is synchronous. If there is no input in the queue, it
yields to Fibers (blocking
1 - 100 of 499 matches
Mail list logo