Re: [VOTE] acceptance of CouchBase-provided API documentation (ref COUCHDB-1523)
On 23 August 2012 14:27, Dave Cottlehuber wrote: > Hi everybody, > > Due to the size of this welcome contribution, we need a bit more > paperwork than usual, which Jan is handling, and also a vote accepting > the contribution which can be done prior. > > I would like call a vote for including the CouchBase API documentation > into the CouchDB project: > > Source repo: https://github.com/janl/couchdb-docs > commit SHA: 9fc95b422060d020ba25f559e893fc7fb98c9a15 > > NB only the required XML* files to complete the export to RST format > will actually added to the CouchDB git repo. > > Voters gonna vote! > > A+ > Dave I'm pretty sure the reqd 72 hours have passed now, quorum unlocked. Total votes: 9. This exceeds the required minimum three +1 votes and the proposal passes. Dirkjan Ochtman http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3ccakmkyactjj0stbr5nopcwpkabkkpendicladvgw9q3_nzxc...@mail.gmail.com%3e Adam Kocoloski http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3cfc4a7628-f963-4c86-961d-d1ab44608...@apache.org%3e Octavian Damiean http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3ccagt9u8h9xwezmcbwhnh573dwddgd13cu+k6iar4+jwgyfma...@mail.gmail.com%3e Bob Dionne http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3c5d62cf34-f595-4b3e-89c4-b08273559...@dionne-associates.com%3e Robert Newson http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3c202f0e26-924e-45d0-8e13-ba459c0dd...@apache.org%3e Benoit Chesneau http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3cCAJNb-9rF=wbykao2vq0wimva-xp_njt+-uny7gaysakbknn...@mail.gmail.com%3e Paul Davis http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3ccaj_m3ydnfsbnfnm2fpxkcjzcizeqkozizuruz8_kepehuoq...@mail.gmail.com%3e Wendell Cada http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3c5036.8070...@83864.com%3e Dave Cottlehuber http://mail-archives.apache.org/mod_mbox/couchdb-dev/201208.mbox/%3CCAHZBNKbpzbwAyh3xEs5_XnL=nv8phpjhpcv9y34wovq5wtq...@mail.gmail.com%3E A+ Dave
[jira] [Updated] (COUCHDB-1523) Import CouchBase documentation
[ https://issues.apache.org/jira/browse/COUCHDB-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Cottlehuber updated COUCHDB-1523: -- Description: Some of the activities reqd to import the documentation must be done by a PMC member with incubator karma. 4 main tasks: 1. get Couchbase signed in PDF or email, http://www.apache.org/licenses/software-grant.txt - jan@ agreed to do this 2. prepare codebase template http://incubator.apache.org/ip-clearance/ip-clearance-template.html - dch@ doing this 3. file paperwork (PMC+incubator karma reqd) - nslater@ are you able to do this? I'll fill you in on details. 4. git stuff - dch@ working on this with kxepal & djc. Content is ready https://github.com/dch/couchdb/commits/merge_docs/asf but makefiles are not. was: Some of the activities reqd to import the documentation must be done by a PMC member with incubator karma. 4 main tasks: 1. get Couchbase signed in PDF or email, http://www.apache.org/licenses/software-grant.txt - jan@ agreed to do this 2. prepare codebase template http://incubator.apache.org/ip-clearance/ip-clearance-template.html - dch@ doing this 3. file paperwork (PMC+incubator karma reqd) - nslater@ are you able to do this? I'll fill you in on details. 4. git stuff - dch@ working on this with kxepal & djc I'll file a separate jira for #4 when the above is complete. > Import CouchBase documentation > -- > > Key: COUCHDB-1523 > URL: https://issues.apache.org/jira/browse/COUCHDB-1523 > Project: CouchDB > Issue Type: New Feature > Components: Documentation >Reporter: Dave Cottlehuber > Fix For: 1.3 > > Attachments: couchdb-docs-0.1.xml > > > Some of the activities reqd to import the documentation must be done by a PMC > member with incubator karma. > 4 main tasks: > 1. get Couchbase signed in PDF or email, > http://www.apache.org/licenses/software-grant.txt - jan@ agreed to do this > 2. prepare codebase template > http://incubator.apache.org/ip-clearance/ip-clearance-template.html - dch@ > doing this > 3. file paperwork (PMC+incubator karma reqd) - nslater@ are you able to do > this? I'll fill you in on details. > 4. git stuff - dch@ working on this with kxepal & djc. Content is ready > https://github.com/dch/couchdb/commits/merge_docs/asf but makefiles are not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1529) Add API to find the deleted branches of a doc's rev tree
Jens Alfke created COUCHDB-1529: --- Summary: Add API to find the deleted branches of a doc's rev tree Key: COUCHDB-1529 URL: https://issues.apache.org/jira/browse/COUCHDB-1529 Project: CouchDB Issue Type: Improvement Affects Versions: 1.2 Reporter: Jens Alfke Priority: Minor There's no efficient way to discover the complete revision tree of a document. API options like ?open_revs=all or ?conflicts will only return active/undeleted revisions; it won't discover deleted branches resulting from already-resolved conflicts. There should be an extra option, like "?include_deleted=true", to use along with open_revs to tell it to return even deleted leaf revisions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1529) Add API to find the deleted branches of a doc's rev tree
[ https://issues.apache.org/jira/browse/COUCHDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448249#comment-13448249 ] Jens Alfke commented on COUCHDB-1529: - Note: It's possible to do this currently by iterating through the database's entire _changes feed, since it includes deletions. That's expensive, though. > Add API to find the deleted branches of a doc's rev tree > > > Key: COUCHDB-1529 > URL: https://issues.apache.org/jira/browse/COUCHDB-1529 > Project: CouchDB > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Jens Alfke >Priority: Minor > > There's no efficient way to discover the complete revision tree of a > document. API options like ?open_revs=all or ?conflicts will only return > active/undeleted revisions; it won't discover deleted branches resulting from > already-resolved conflicts. > There should be an extra option, like "?include_deleted=true", to use along > with open_revs to tell it to return even deleted leaf revisions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1530) Add a mode to _all_docs to include deleted docs
Jens Alfke created COUCHDB-1530: --- Summary: Add a mode to _all_docs to include deleted docs Key: COUCHDB-1530 URL: https://issues.apache.org/jira/browse/COUCHDB-1530 Project: CouchDB Issue Type: Improvement Affects Versions: 1.2 Reporter: Jens Alfke Priority: Minor There's currently no efficient way to discover the deleted documents in a database, since _all_docs only returns active documents. It can be useful to show all documents, even deleted ones, for troubleshooting or forensic purposes. I propose adding an option like "?include_deleted=true" to _all_docs that will cause it to return deleted documents as well. To provide a way to tell deleted docs apart from active ones (if the include_docs option isn't on), the "value" object should include a "deleted":true property for those docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1530) Add a mode to _all_docs to include deleted docs
[ https://issues.apache.org/jira/browse/COUCHDB-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448271#comment-13448271 ] Jens Alfke commented on COUCHDB-1530: - Note: It's possible to find the deleted documents by iterating over the database's entire _changes feed, but it's expensive. > Add a mode to _all_docs to include deleted docs > --- > > Key: COUCHDB-1530 > URL: https://issues.apache.org/jira/browse/COUCHDB-1530 > Project: CouchDB > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Jens Alfke >Priority: Minor > > There's currently no efficient way to discover the deleted documents in a > database, since _all_docs only returns active documents. It can be useful to > show all documents, even deleted ones, for troubleshooting or forensic > purposes. > I propose adding an option like "?include_deleted=true" to _all_docs that > will cause it to return deleted documents as well. To provide a way to tell > deleted docs apart from active ones (if the include_docs option isn't on), > the "value" object should include a "deleted":true property for those docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1529) Add API to find the deleted branches of a doc's rev tree
[ https://issues.apache.org/jira/browse/COUCHDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448394#comment-13448394 ] Paul Joseph Davis commented on COUCHDB-1529: Perhaps simpler we might just want to add a ?include_tree=true or ?revs_as_tree=true and maybe remove a couple of the other weirder options to simplify this API further. > Add API to find the deleted branches of a doc's rev tree > > > Key: COUCHDB-1529 > URL: https://issues.apache.org/jira/browse/COUCHDB-1529 > Project: CouchDB > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Jens Alfke >Priority: Minor > > There's no efficient way to discover the complete revision tree of a > document. API options like ?open_revs=all or ?conflicts will only return > active/undeleted revisions; it won't discover deleted branches resulting from > already-resolved conflicts. > There should be an extra option, like "?include_deleted=true", to use along > with open_revs to tell it to return even deleted leaf revisions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1530) Add a mode to _all_docs to include deleted docs
[ https://issues.apache.org/jira/browse/COUCHDB-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448395#comment-13448395 ] Paul Joseph Davis commented on COUCHDB-1530: +1 for include_deleted. Though I'll note that this won't allow for an efficient view of *only* deleted docs. Perhaps a view option like local seqs or including design docs that allows users to create views would be a good addition as well. > Add a mode to _all_docs to include deleted docs > --- > > Key: COUCHDB-1530 > URL: https://issues.apache.org/jira/browse/COUCHDB-1530 > Project: CouchDB > Issue Type: Improvement >Affects Versions: 1.2 >Reporter: Jens Alfke >Priority: Minor > > There's currently no efficient way to discover the deleted documents in a > database, since _all_docs only returns active documents. It can be useful to > show all documents, even deleted ones, for troubleshooting or forensic > purposes. > I propose adding an option like "?include_deleted=true" to _all_docs that > will cause it to return deleted documents as well. To provide a way to tell > deleted docs apart from active ones (if the include_docs option isn't on), > the "value" object should include a "deleted":true property for those docs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
