[jira] [Created] (COUCHDB-2662) Saving view multiple times causes conflict
Garren Smith created COUCHDB-2662: - Summary: Saving view multiple times causes conflict Key: COUCHDB-2662 URL: https://issues.apache.org/jira/browse/COUCHDB-2662 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Garren Smith Saving view multiple times causes a conflict as the revision is not being updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request: Active tasks in React
Github user garrensmith commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/317#discussion_r28320921
--- Diff: app/addons/activetasks/routes.js ---
@@ -14,60 +14,40 @@ define([
'app',
'api',
'addons/activetasks/resources',
- 'addons/activetasks/views'
+ 'addons/activetasks/components.react',
+ 'addons/activetasks/actions'
],
-function (app, FauxtonAPI, Activetasks, Views) {
+function (app, FauxtonAPI, ActiveTasksResources, ActiveTasksComponents,
Actions) {
var ActiveTasksRouteObject = FauxtonAPI.RouteObject.extend({
-layout: 'with_tabs_sidebar',
-
+selectedHeader: 'Active Tasks',
+layout: 'one_pane',
routes: {
- 'activetasks/:id': 'defaultView',
- 'activetasks': 'defaultView'
-},
-
-events: {
- 'route:changeFilter': 'changeFilter'
+ 'activetasks/:id': 'showActiveTasks',
+ 'activetasks': 'showActiveTasks'
},
-
-selectedHeader: 'Active Tasks',
-
crumbs: [
{'name': 'Active tasks', 'link': 'activetasks'}
],
-
apiUrl: function () {
- return [this.allTasks.url('apiurl'), this.allTasks.documentation];
+ var apiurl = window.location.origin + '/_active_tasks';
+ return [ apiurl, FauxtonAPI.constants.DOC_URLS.ACTIVE_TASKS];
},
-
roles: ['_admin'],
-
initialize: function () {
- this.allTasks = new Activetasks.AllTasks();
- this.search = new Activetasks.Search();
-},
-
-defaultView: function () {
- this.setView('#dashboard-lower-content', new Views.View({
-collection: this.allTasks,
-currentView: 'all',
-searchModel: this.search
- }));
-
- this.setView('#sidebar-content', new Views.TabMenu({}));
-
- this.headerView = this.setView('#dashboard-upper-content', new
Views.TabHeader({
-searchModel: this.search
- }));
+ this.allTasks = new ActiveTasksResources.AllTasks();
},
+showActiveTasks: function () {
+ Actions.fetchAndSetActiveTasks(this.allTasks);
+ Actions.changePollingInterval(5);
-changeFilter: function (filterType) {
- this.search.set('filterType', filterType);
+ this.activeTasksSection = this.setComponent('#dashboard-content',
ActiveTasksComponents.ActiveTasksController);
--- End diff --
This looks great. I don't think you need `this.pollingwidget` or
`this.activeTasksSection`. The RouteObject will call `removeComponent` so you
don't need to manually remove them.
---
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 feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-chttpd pull request: Remove /_sleep endpoint
Github user janl commented on the pull request: https://github.com/apache/couchdb-chttpd/pull/32#issuecomment-92763845 FINALLY \o/ --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user kxepal commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92764010 @janl why not to fix them before? since they are pretty trivial. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user mar-ia commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92767820 And already fixed :) I did some more fixes and some rewrites too, in a try to make things more clear. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Active tasks in React
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/317#issuecomment-92786240 This is looking good. +1 for merging. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user janl commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92763742 Great work @mar-ia! Letâs get this merged and file issues for the line-comments to fix soon after. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user kxepal commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92777684 @mar-ia great! Could you only squash your commits please. If you think it's ready, I'll merge it. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user mar-ia commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92842306 Squashed. @kxepal Please do :) --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user kxepal commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92850783 Thank you! (: --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-documentation/pull/19 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Changes auto-update option added
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/368#issuecomment-92853950 @benkeen this looks great. I'm getting a strange behaviour if I view changes. Then make a few changes to the db and then click on the filter and check auto update. It then does a lot of updating. If I view the changes page, then check auto update and then make a few changes to the db I don't get as many updates. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Changes auto-update option added
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/368#issuecomment-92996212 Ah, drat. Good catch. What's happening is that the first time you check the auto update feature it'll show all changes that have occurred since the page was originally loaded, rather than from that moment on which is what you'd expect. I'll fix it. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: GSOC 2015 [Visualize document revision tree and navigate betweenthese revisions]
Hi Robert, As you suggested here is the link for my react component testing development branch. At the moment I am completing the react lessons and one left to go. :) https://github.com/nadeeshaan/couchdb-fauxton/tree/InitialTestingBranch Cheers. On Sat, Apr 4, 2015 at 5:08 PM, Nadeeshaan Gunasinghe nadeeshaangunasin...@gmail.com wrote: Hi Robert, I followed the resources you shared previously and I could successfully create a react component to display some content on the view. For the reference of other newbies like me who try to create react components I would like to suggest taking a look at on app/addons/cors app/addons/config as well as https://github.com/nadeeshaan/couchdb-fauxton/blob/master/writing_addons.md Going through those we can successfully create a react component. :) Cheers On Wed, Mar 25, 2015 at 2:37 AM, Nadeeshaan Gunasinghe nadeeshaangunasin...@gmail.com wrote: Hi Robert, As you suggested yesterday I started generating the UIs in the fauxton Code base. I followed the sample addon writing tutorial in github and went through the already written addons. As a first step I could get an idea about how the data is flowing through fauxton and how content is managed. So as my next step I am going to try writing a bit more complex UI adding bits of components there. Cheers On Mon, Mar 23, 2015 at 6:13 PM, Alexander Shorin kxe...@gmail.com wrote: Very good! Such layout indeed have better potential to handle upcoming feature requests. I wouldn't concentrate here on the details (like action menu - it's uncommon for Fauxton interface to have a dropdown list of actions since buttons are preferred instead) - the idea and the base layout are more important at the start. Robert, what do you think? -- ,,,^..^,,, On Mon, Mar 23, 2015 at 3:15 PM, Nadeeshaan Gunasinghe nadeeshaangunasin...@gmail.com wrote: Hi Robert, According to the suggestions of Alex I re designed the Interface. It will be great if you can give some feedback regarding the current UI. I will point to each suggestion as follows, *1. Tree could be wide. Very wide and tall. Proposed interface has a quite small limit for amount of conflicts which could be showed without having horizontal scrolling. How this is suppose to be handled? * Tree is being shown inside a scrollable (Horizontal and vertical only if the tree does not fit in side the pane) pane in which we can click on the nodes and traverse the tree allowing much wider as well as taller trees *2. Tree is used to only to look it at and browse document for each selected revision, but also to apply some kind of operation: revert to, delete, merge, etc. Proposed interface doesn't assumes to have any bar for such operations.* Above the tree's display pane there is a drop down select in order to select the desired operation to be done. As an example merge, revert to, etc. Ex: If you select the merge option then you are allowed to select two tree nodes. If you select delete option or explore (Default Option) then you are allowed to select one node. When you select such option, as an example merge, two nodes' document content will be shown in the two document view panes. Relevant revision id is shown above the corresponding pane. *3. Document content for some revisions may not be available. What will be showed on the right pane in this case?* If the content of a revision is not available then the pane will be left blank (No more right side pane in the available pane) *4. During the conflict resolution, or merge, you'll need to see both conflict documents and the result of their merge. How proposed interface could help with that?* At the top right corner above the display panes there is an icon of eye. Clicking on it, a modal opens and shows the result of the operation *5. Will navigation to revision tree page be available from document view page?* Yes. This issue had addressed in the previous version. In which we are adding a link to each document (A tree icon left to the pencil icon) which redirect to the revision tree page. *Features for operations.* Options: Explore Revert to Merge Delete In the operation selection drop down there is a default option *Explore *when this is selected eye icon, Apply Button will be disabled. Also only one pane will be shown for loading the document content Delete works as same and only the Apply Button won't be disabled At the moment I focused on the above options only depending on the options we can to alterations for the UI based on the current View. During the implementation there may be slight changes of the designed, but the basic structure will remain same. Links to the UIs, Documents view: https://www.dropbox.com/s/oezvfztq9abqtv5/alldocs_added_tree_icon.png?dl=0 Revision Tree View:
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1, I think thats a great idea. On 14 Apr 2015, at 4:09 PM, Jan Lehnardt j...@apache.org wrote: Thanks for all your feedback! How about this: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@. There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) What do you think? Best Jan -- On 18 Feb 2015, at 15:41, Robert Kowalski r...@kowalski.gd wrote: I like the cross-pollunation between the dev-topics, e.g. when we announced / suggested coding style guidelines, I would like to keep that at the main dev-list I also think the amount of git-commit-mails and Jira stuff is floody. Can we just move the Jira and git-commit stuff to an own mailing list? On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk andyw...@apache.org wrote: On 18 February 2015 at 15:15, Jan Lehnardt j...@apache.org wrote: On 18 Feb 2015, at 15:12, Andy Wenk a...@nms.de wrote: Hi Jan, I am +0. Recently, there is not that much traffic at dev@. So I am wondering what the intention is to split technical discussions further. We saw in the last year, that the main list is dev@ for developing on CouchDB. The only list with much traffic is marketing@ because it is a complete different topic. This is mostly about the git notifications, they are significant :) ok fair point ... I just have the fear, that the participation will decrease because of yet another ML a developer has to subscribe to. But we can inform every one appropriately ... so let's go for it ... Unless I am missing something essential like to much different topics in one list, I would leave it at dev@. Cheers Andy On 18 February 2015 at 14:38, Garren Smith gar...@apache.org wrote: +1 that is a good idea. On 18 Feb 2015, at 3:34 PM, Jan Lehnardt j...@apache.org wrote: Hey all, I’m wondering how you would feel to give the Fauxton team their own mailing list for discussions and GitHub notifications? In my view, the Fauxton project is generating enough traffic to warrant it’s own space :) I’d propose fauxton-...@couchdb.apache.org Best Jan -- -- 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 -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
[GitHub] couchdb-fauxton pull request: http-proxy@1.10.1
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb-fauxton/pull/379 http-proxy@1.10.1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb-fauxton go Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/379.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #379 commit 7b475ba7f1ad0d5ed0f528b9dc4b3c4835da52a9 Author: Robert Kowalski robertkowal...@apache.org Date: 2015-04-14T15:23:34Z http-proxy@1.10.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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1 to Jan's idea -- I love seeing all the dev discussion but my inbox is exploding due to our wonderful fauxton work. On Tue, Apr 14, 2015 at 10:58 AM, Garren Smith gar...@apache.org wrote: +1, I think thats a great idea. On 14 Apr 2015, at 4:09 PM, Jan Lehnardt j...@apache.org wrote: Thanks for all your feedback! How about this: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) What do you think? Best Jan -- On 18 Feb 2015, at 15:41, Robert Kowalski r...@kowalski.gd wrote: I like the cross-pollunation between the dev-topics, e.g. when we announced / suggested coding style guidelines, I would like to keep that at the main dev-list I also think the amount of git-commit-mails and Jira stuff is floody. Can we just move the Jira and git-commit stuff to an own mailing list? On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk andyw...@apache.org wrote: On 18 February 2015 at 15:15, Jan Lehnardt j...@apache.org wrote: On 18 Feb 2015, at 15:12, Andy Wenk a...@nms.de wrote: Hi Jan, I am +0. Recently, there is not that much traffic at dev@. So I am wondering what the intention is to split technical discussions further. We saw in the last year, that the main list is dev@ for developing on CouchDB. The only list with much traffic is marketing@ because it is a complete different topic. This is mostly about the git notifications, they are significant :) ok fair point ... I just have the fear, that the participation will decrease because of yet another ML a developer has to subscribe to. But we can inform every one appropriately ... so let's go for it ... Unless I am missing something essential like to much different topics in one list, I would leave it at dev@. Cheers Andy On 18 February 2015 at 14:38, Garren Smith gar...@apache.org wrote: +1 that is a good idea. On 18 Feb 2015, at 3:34 PM, Jan Lehnardt j...@apache.org wrote: Hey all, I’m wondering how you would feel to give the Fauxton team their own mailing list for discussions and GitHub notifications? In my view, the Fauxton project is generating enough traffic to warrant it’s own space :) I’d propose fauxton-...@couchdb.apache.org Best Jan -- -- 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 -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1 On Tue, Apr 14, 2015 at 2:24 PM, Paul J Davis paul.joseph.da...@gmail.com wrote: +1 On Apr 14, 2015, at 3:50 PM, Andy Wenk andyw...@apache.org wrote: +1 On 14 April 2015 at 21:02, Alexander Shorin kxe...@gmail.com wrote: On Tue, Apr 14, 2015 at 5:09 PM, Jan Lehnardt j...@apache.org wrote: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) +1 -- ,,,^..^,,, -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
[GitHub] couchdb-fauxton pull request: Doc Workflow improvements
GitHub user benkeen opened a pull request: https://github.com/apache/couchdb-fauxton/pull/382 Doc Workflow improvements *** This is just an IDEA. This is not a finished PR. I think the improvements it makes to the UX is very worthwhile but the implementation is questionable in places. Intended for discussion only. *** ___ This PR is part of Doc Workflow to improve the overall UX of navigating around the UI with respect to the documents. Changes: 1. Clicking back/cancel from a full page doc editor no longer limits the results to 20 on the doc list page. 2. Clicking back to a list of documents from the full page doc editor now returns you to the last PAGE you were on, and the SCROLL offset of wherever you were on the page as well. 3. Introduces fauxton/memory.js as a way to store information across multiple page loads. Notes: - Perhaps the functionality in memory.js should be moved to utils? so app.utils.memory.set(), etc. It could also replace localStorageGet and localStorageSet: memory.set() and get() would just take an extra param to specify whether it's getting/setting local storage or transient JS data. - itâs missing better tests - thereâs an existing bug where when you click from one page to the next it doesnât update the scrollTop to 0 on the scrollable. Thatâs unrelated to this ticket. Big flaws: - The cloudant.pagingcollection.js file change. Why is that a separate external lib? I ran into serious problem trying to persuade it to re-initialize on a non-first page and couldnât get around it, hence the modification to the file. There is a solution around it by circumventing it in the store, but that felt like an even worse solution. - I really donât like having to reference the .scrollable region (to get + set the scrollTop) within ResultsScreen /, but I donât see any other place to do it now we're dropping Backbone views (i.e. I need a before/afterRender on the routeobject to know when that element is available in the page) - generally I find the whole thing a bit hacky, but I love the UX improvement. You can merge this pull request into a Git repository by running: $ git pull https://github.com/benkeen/couchdb-fauxton doc-workflow Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/382.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #382 commit ba491edc91d4ac345cf6e0c52cb13b67896db471 Author: Ben Keen ben.k...@gmail.com Date: 2015-04-15T04:56:48Z Doc Workflow improvements *** This is just an IDEA. This is not a finished PR. I think the improvements it makes to the UX is very worthwhile but the implementation is questionable in places. Intended for discussion only. *** ___ This PR is part of Doc Workflow to improve the overall UX of navigating around the UI with respect to the documents. Changes: 1. Clicking back/cancel from a full page doc editor no longer limits the results to 20 on the doc list page. 2. Clicking back to a list of documents from the full page doc editor now returns you to the last PAGE you were on, and the SCROLL offset of wherever you were on the page as well. 3. Introduces fauxton/memory.js as a way to store information across multiple page loads. Notes: - Perhaps the functionality in memory.js should be moved to utils? so app.utils.memory.set(), etc. It could also replace localStorageGet and localStorageSet: memory.set() and get() would just take an extra param to specify whether it's getting/setting local storage or transient JS data. - itâs missing better tests - thereâs an existing bug where when you click from one page to the next it doesnât update the scrollTop to 0 on the scrollable. Thatâs unrelated to this ticket. Big flaws: - The cloudant.pagingcollection.js file change. Why is that a separate external lib? I ran into serious problem trying to persuade it to re-initialize on a non-first page and couldnât get around it, hence the modification to the file. There is a solution around it by circumventing it in the store, but that felt like an even worse solution. - I really donât like having to reference the .scrollable region (to get + set the scrollTop) within ResultsScreen /, but I donât see any other place to do it now we're dropping Backbone views (i.e. I need a before/afterRender on the routeobject to know when that element is available in the page) - generally I find the whole thing a bit hacky, but I love the UX improvement.
Re: [DISCUSSION] Move Fauxton to its own mailing list?
Thanks for all your feedback! How about this: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@. There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) What do you think? Best Jan -- On 18 Feb 2015, at 15:41, Robert Kowalski r...@kowalski.gd wrote: I like the cross-pollunation between the dev-topics, e.g. when we announced / suggested coding style guidelines, I would like to keep that at the main dev-list I also think the amount of git-commit-mails and Jira stuff is floody. Can we just move the Jira and git-commit stuff to an own mailing list? On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk andyw...@apache.org wrote: On 18 February 2015 at 15:15, Jan Lehnardt j...@apache.org wrote: On 18 Feb 2015, at 15:12, Andy Wenk a...@nms.de wrote: Hi Jan, I am +0. Recently, there is not that much traffic at dev@. So I am wondering what the intention is to split technical discussions further. We saw in the last year, that the main list is dev@ for developing on CouchDB. The only list with much traffic is marketing@ because it is a complete different topic. This is mostly about the git notifications, they are significant :) ok fair point ... I just have the fear, that the participation will decrease because of yet another ML a developer has to subscribe to. But we can inform every one appropriately ... so let's go for it ... Unless I am missing something essential like to much different topics in one list, I would leave it at dev@. Cheers Andy On 18 February 2015 at 14:38, Garren Smith gar...@apache.org wrote: +1 that is a good idea. On 18 Feb 2015, at 3:34 PM, Jan Lehnardt j...@apache.org wrote: Hey all, I’m wondering how you would feel to give the Fauxton team their own mailing list for discussions and GitHub notifications? In my view, the Fauxton project is generating enough traffic to warrant it’s own space :) I’d propose fauxton-...@couchdb.apache.org Best Jan -- -- 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 -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
[jira] [Resolved] (COUCHDB-2548) Collapse should reduce docs to single line
[ https://issues.apache.org/jira/browse/COUCHDB-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Keen resolved COUCHDB-2548. --- Resolution: Fixed Collapse should reduce docs to single line Key: COUCHDB-2548 URL: https://issues.apache.org/jira/browse/COUCHDB-2548 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: Fauxton Reporter: Ben Keen Assignee: Ben Keen Right now when you're on All Docs or anywhere that shows a list of documents, the Collapse option doesn't fully collapse the list - but shows a redundant, second _id row + _rev. This should be changed to just show a more concise list of single rows with the IDs. This has been requested in the past, just never gotten to. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (COUCHDB-2548) Collapse should reduce docs to single line
[ https://issues.apache.org/jira/browse/COUCHDB-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Keen closed COUCHDB-2548. - Collapse should reduce docs to single line Key: COUCHDB-2548 URL: https://issues.apache.org/jira/browse/COUCHDB-2548 Project: CouchDB Issue Type: Improvement Security Level: public(Regular issues) Components: Fauxton Reporter: Ben Keen Assignee: Ben Keen Right now when you're on All Docs or anywhere that shows a list of documents, the Collapse option doesn't fully collapse the list - but shows a redundant, second _id row + _rev. This should be changed to just show a more concise list of single rows with the IDs. This has been requested in the past, just never gotten to. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] couchdb-fauxton pull request: Active tasks in React
Github user michellephung closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/317 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1 On Tue, Apr 14, 2015 at 5:11 PM, Kyle Snavely kjsnav...@gmail.com wrote: +1 to Jan's idea -- I love seeing all the dev discussion but my inbox is exploding due to our wonderful fauxton work. On Tue, Apr 14, 2015 at 10:58 AM, Garren Smith gar...@apache.org wrote: +1, I think thats a great idea. On 14 Apr 2015, at 4:09 PM, Jan Lehnardt j...@apache.org wrote: Thanks for all your feedback! How about this: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) What do you think? Best Jan -- On 18 Feb 2015, at 15:41, Robert Kowalski r...@kowalski.gd wrote: I like the cross-pollunation between the dev-topics, e.g. when we announced / suggested coding style guidelines, I would like to keep that at the main dev-list I also think the amount of git-commit-mails and Jira stuff is floody. Can we just move the Jira and git-commit stuff to an own mailing list? On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk andyw...@apache.org wrote: On 18 February 2015 at 15:15, Jan Lehnardt j...@apache.org wrote: On 18 Feb 2015, at 15:12, Andy Wenk a...@nms.de wrote: Hi Jan, I am +0. Recently, there is not that much traffic at dev@. So I am wondering what the intention is to split technical discussions further. We saw in the last year, that the main list is dev@ for developing on CouchDB. The only list with much traffic is marketing@ because it is a complete different topic. This is mostly about the git notifications, they are significant :) ok fair point ... I just have the fear, that the participation will decrease because of yet another ML a developer has to subscribe to. But we can inform every one appropriately ... so let's go for it ... Unless I am missing something essential like to much different topics in one list, I would leave it at dev@. Cheers Andy On 18 February 2015 at 14:38, Garren Smith gar...@apache.org wrote: +1 that is a good idea. On 18 Feb 2015, at 3:34 PM, Jan Lehnardt j...@apache.org wrote: Hey all, I’m wondering how you would feel to give the Fauxton team their own mailing list for discussions and GitHub notifications? In my view, the Fauxton project is generating enough traffic to warrant it’s own space :) I’d propose fauxton-...@couchdb.apache.org Best Jan -- -- 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 -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/
Re: [DISCUSSION] Move Fauxton to its own mailing list?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 +1 On 14.04.2015 20:59, Robert Kowalski wrote: +1 On Tue, Apr 14, 2015 at 5:11 PM, Kyle Snavely kjsnav...@gmail.com wrote: +1 to Jan's idea -- I love seeing all the dev discussion but my inbox is exploding due to our wonderful fauxton work. On Tue, Apr 14, 2015 at 10:58 AM, Garren Smith gar...@apache.org wrote: +1, I think thats a great idea. On 14 Apr 2015, at 4:09 PM, Jan Lehnardt j...@apache.org wrote: Thanks for all your feedback! How about this: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) What do you think? Best Jan -- On 18 Feb 2015, at 15:41, Robert Kowalski r...@kowalski.gd wrote: I like the cross-pollunation between the dev-topics, e.g. when we announced / suggested coding style guidelines, I would like to keep that at the main dev-list I also think the amount of git-commit-mails and Jira stuff is floody. Can we just move the Jira and git-commit stuff to an own mailing list? On Wed, Feb 18, 2015 at 3:23 PM, Andy Wenk andyw...@apache.org wrote: On 18 February 2015 at 15:15, Jan Lehnardt j...@apache.org wrote: On 18 Feb 2015, at 15:12, Andy Wenk a...@nms.de wrote: Hi Jan, I am +0. Recently, there is not that much traffic at dev@. So I am wondering what the intention is to split technical discussions further. We saw in the last year, that the main list is dev@ for developing on CouchDB. The only list with much traffic is marketing@ because it is a complete different topic. This is mostly about the git notifications, they are significant :) ok fair point ... I just have the fear, that the participation will decrease because of yet another ML a developer has to subscribe to. But we can inform every one appropriately ... so let's go for it ... Unless I am missing something essential like to much different topics in one list, I would leave it at dev@. Cheers Andy On 18 February 2015 at 14:38, Garren Smith gar...@apache.org wrote: +1 that is a good idea. On 18 Feb 2015, at 3:34 PM, Jan Lehnardt j...@apache.org wrote: Hey all, I’m wondering how you would feel to give the Fauxton team their own mailing list for discussions and GitHub notifications? In my view, the Fauxton project is generating enough traffic to warrant it’s own space :) I’d propose fauxton-...@couchdb.apache.org Best Jan -- -- 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 - -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc -- Professional Support for Apache CouchDB: http://www.neighbourhood.ie/couchdb-support/ -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVLWTwAAoJED+W7gN+c0gcElkH/RrIWSH6B4/wv91Ua+3JI0r6 bT8huNhb5+K4SoTMMM0Pw3xW1A1gePu8/VCzTZTcRoSjTKN0KODKVg1TZb2pFfVO Yge/hyCJuRuwtSr0/8xLMLl0pX3M6hYBI4Acmfb5S4jMaxFRHSWW39ZsADDc04xN vJv623nqhx2WL1ttP3wy5LkDhOb5fpyoJEh5/UMeAGn3kyN20v5+iE6Y8fY4dZ+J PWn5D/olcs4tymv0yiXp3xVn7+H73P6+MsCmPoJdbLGwgmumIptHPEzpcuNwLvSC jGbOD/LQ/w43ur93ji9E+R0JIzLtMZc2/0n6ef1BJbBE3Hkemyrjt1k3za3ldyE= =U9ih -END PGP SIGNATURE-
Re: [DISCUSSION] Move Fauxton to its own mailing list?
On Tue, Apr 14, 2015 at 5:09 PM, Jan Lehnardt j...@apache.org wrote: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@. There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) +1 -- ,,,^..^,,,
[GitHub] couchdb-fauxton pull request: error handling for active tasks
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/380#issuecomment-93029438 Shouldn't be spaced around ( and ), but +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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: error handling for active tasks
GitHub user michellephung opened a pull request: https://github.com/apache/couchdb-fauxton/pull/380 error handling for active tasks You can merge this pull request into a Git repository by running: $ git pull https://github.com/michellephung/couchdb-fauxton Active-Tasks-in-REACT Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/380.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #380 commit c253092dd64be6fcfe59626eb78339f63b408c37 Author: michelleph...@gmail.com michelleph...@gmail.com Date: 2015-04-14T19:05:55Z error handling --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Changes auto-update option added
Github user benkeen commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/368#issuecomment-93045162 Squashed merged. --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: Changes auto-update option added
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/368 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request: hasDataSize() method added to Databa...
GitHub user benkeen opened a pull request: https://github.com/apache/couchdb-fauxton/pull/381 hasDataSize() method added to Databases.Status Just a helper function because dataSize() didn't provide enough info. You can merge this pull request into a Git repository by running: $ git pull https://github.com/benkeen/couchdb-fauxton db-status-method Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/381.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #381 commit 90f3e9777f6370fc16196745aea586548449f70a Author: Ben Keen ben.k...@gmail.com Date: 2015-04-14T22:43:12Z hasDataSize() method added to Databases.Status --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Github user janl commented on the pull request: https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92795169 @kxepal all I meant: I donât think these are blockers. We can always fix them before, too. Sorry for being unclear :) --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Database ranking
I am also planning to target AdvocateHub activities at improving this score. On Sat, 11 Apr 2015 at 15:44 Alexander Shorin kxe...@gmail.com wrote: 2.0 roll is good, but not enough. We extremely need more activity around the project to keep rating high enough. -- ,,,^..^,,, On Sat, Apr 11, 2015 at 1:47 PM, Andy Wenk andyw...@apache.org wrote: Hi all, here is a little info about the databases out there in the wild. http://db-engines.com/en/ranking The CouchDB ranking will most likely change when we roll out 2.0 ;-) Cheers Andy -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
[GitHub] couchdb-fauxton pull request: error handling for active tasks
Github user michellephung closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/380 --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1 On 14 April 2015 at 21:02, Alexander Shorin kxe...@gmail.com wrote: On Tue, Apr 14, 2015 at 5:09 PM, Jan Lehnardt j...@apache.org wrote: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) +1 -- ,,,^..^,,, -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
[GitHub] couchdb-fauxton pull request: error handling for active tasks
Github user michellephung commented on the pull request: https://github.com/apache/couchdb-fauxton/pull/380#issuecomment-93061585 merged : 9d8be3bb26fde37637f9555aa4361f207fb5d96a --- 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 feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [DISCUSSION] Move Fauxton to its own mailing list?
+1 On Apr 14, 2015, at 3:50 PM, Andy Wenk andyw...@apache.org wrote: +1 On 14 April 2015 at 21:02, Alexander Shorin kxe...@gmail.com wrote: On Tue, Apr 14, 2015 at 5:09 PM, Jan Lehnardt j...@apache.org wrote: We create new mailing list c...@couchdb.apache.org (or your favourite bike shed) that gets all JIRA and GitHub traffic. dev@ then is for discussion and decisions for all code projects (including Fauxton). If you want to keep track of tickets and pull requests, sign up for code@ . There is a bit of a discrepancy between discussions in JIRA and dev@, but I’m willing to take that risk, as most people probably bulk-delete all JIRA mails anyway :) +1 -- ,,,^..^,,, -- Andy Wenk Hamburg - Germany RockIt! GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc
