GitHub user michellephung opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/387
Add nightwatch custom function: replicate db
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michellephung/couchdb-fauxton
night
Github user robertkowalski commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#discussion_r28547303
--- Diff: app/addons/fauxton/components.react.jsx ---
@@ -84,9 +84,131 @@ function (app, FauxtonAPI, React, ZeroClipboard) {
});
+1 then
- Original Message -
> From: "Jan Lehnardt"
> To: dev@couchdb.apache.org
> Cc: "Joan Touzet"
> Sent: Thursday, April 16, 2015 12:42:04 PM
> Subject: Re: [DISCUSSION] Move Fauxton to its own mailing list?
>
>
> > On 16 Apr 2015, at 18:16, Noah Slater wrote:
> >
> > Here's my u
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-93818658
@michellephung the LoadLines are too cool to not use them, so I did that -
I still have to take care of your other comment though
---
If your projec
Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-93807018
theres a component for that ! :)
loadinglines:
https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/index-results/index-resu
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-93804502
thanks! - actually we lost the spinner when getting rid of views.js (was
tied to establish), I have to put it back in 2morrow...
---
If your project
Github user michellephung commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#discussion_r28533171
--- Diff: app/addons/fauxton/components.react.jsx ---
@@ -84,9 +84,131 @@ function (app, FauxtonAPI, React, ZeroClipboard) {
});
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/381#issuecomment-93800613
Thanks Michelle! Merged as 1847ef8
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your projec
Github user benkeen closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/381
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featu
Github user michellephung commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#discussion_r28532960
--- Diff: app/addons/fauxton/components.react.jsx ---
@@ -84,9 +84,129 @@ function (app, FauxtonAPI, React, ZeroClipboard) {
});
Github user sebastianrothbucher commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#discussion_r28532530
--- Diff: app/addons/fauxton/components.react.jsx ---
@@ -84,9 +84,129 @@ function (app, FauxtonAPI, React, ZeroClipboard) {
});
Github user michellephung commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/381#issuecomment-93795688
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
K, thanks Jan
On Thu, 16 Apr 2015 at 18:43 Jan Lehnardt wrote:
>
> > On 16 Apr 2015, at 13:40, Noah Slater wrote:
> >
> > I thought we'd already discussed moving this stuff to another list. See
> > "[PROPOSAL] Move transactional email out of dev@" sent around this time
> > last month.
> >
> > T
> On 16 Apr 2015, at 13:40, Noah Slater wrote:
>
> I thought we'd already discussed moving this stuff to another list. See
> "[PROPOSAL] Move transactional email out of dev@" sent around this time
> last month.
>
> The last email on that thread was me suggesting we kick off a DISCUSS
> thread.
Github user robertkowalski closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/384
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if th
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/384#issuecomment-93781491
merged as 730e856dcc6f8716e1a797d6bf0fabe27a62cbc9 and
123881d42ecc87565a9255fbec43ab5b1966447c
---
If your project is set up for it, you can reply to th
> On 16 Apr 2015, at 18:16, Noah Slater wrote:
>
> Here's my understanding:
>
> New mailing list:
>
> - notificati...@couchdb.apache.org
>
> (Changed from "code to "notifications", as "notifications" is more
> accurate, reflects the fact that not all JIRA tickets are about code, and
> leaves
Github user benkeen commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/384#issuecomment-93777675
LGTM +1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featur
I like this, I'm definitely keen to reduce the notification spam that comes
about, while remaining in the loop about decisions being made and so on.
On 16 April 2015 at 17:16, Noah Slater wrote:
> Here's my understanding:
>
> New mailing list:
>
> - notificati...@couchdb.apache.org
>
> (Changed
I like notifications@ name as more clean one.
--
,,,^..^,,,
On Thu, Apr 16, 2015 at 7:16 PM, Noah Slater wrote:
> Here's my understanding:
>
> New mailing list:
>
> - notificati...@couchdb.apache.org
>
> (Changed from "code to "notifications", as "notifications" is more
> accurate, reflects the
Here's my understanding:
New mailing list:
- notificati...@couchdb.apache.org
(Changed from "code to "notifications", as "notifications" is more
accurate, reflects the fact that not all JIRA tickets are about code, and
leaves it open to any other sorts of automatic notifications we want to
send
Ok, I'm confused now for what we voted for. In Jan second proposal,
there was nothing about moving Fauton out of dev@, but about to create
of code@ for JIRA and GitHub emails and I was sure that moving
automatically generated code-related emails to special ML in order to
make dev@ traffic more "hum
+1 to Noah's proposal, -1 to an additional separate Fauxton list.
All of the Fauxton traffic I see is GH related and if I really
wanted Fauxton traffic in a different folder, the filter rule is
trivial.
Once GH traffic is off of dev@ it will become readable again. And
the monthly reminder will hel
Github user iilyak commented on the pull request:
https://github.com/apache/couchdb-couch-mrview/pull/17#issuecomment-93760517
The problem is fixed by [following
commit](https://github.com/iilyak/couchdb-chttpd/commit/0b5e15e0ff9cd5ec13f5a332b0c3f1f2951ccfac)
Test case is added in
[
https://issues.apache.org/jira/browse/COUCHDB-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498140#comment-14498140
]
ASF GitHub Bot commented on COUCHDB-2656:
-
GitHub user iilyak opened a pull requ
GitHub user iilyak opened a pull request:
https://github.com/apache/couchdb-couch/pull/43
Add CORS test case for couch_mrview_show
COUCHDB-2656
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iilyak/couchdb-couch 2656-use-chttpd-f
I also think we need to start thinking carefully about the overhead we're
adding with all these mailing lists.
I think it's good that we've been in an expansionist phase. But there are
several downsides:
- Splitting mailing list traffic splits discussion and splits the
community, in a very real s
I thought we'd already discussed moving this stuff to another list. See
"[PROPOSAL] Move transactional email out of dev@" sent around this time
last month.
The last email on that thread was me suggesting we kick off a DISCUSS
thread.
My proposal was:
> I am +1 for GitHub PRs moving to something
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#issuecomment-93710083
one small comment - this is coming along very nicely!
also :heart: the testcoverage - this is awesome work!
---
If your project is set up for it
Github user robertkowalski commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/370#discussion_r28500914
--- Diff: app/addons/fauxton/components.react.jsx ---
@@ -84,9 +84,129 @@ function (app, FauxtonAPI, React, ZeroClipboard) {
});
30 matches
Mail list logo
