)]}'
{"doc/source/process.rst":[{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"38f584d3e0ac84ccee5ead2660ae4a787b9e50e6","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"   In the guideline review, consensus means the changeset must be available"},{"line_number":28,"context_line":"   for review in its near final form for at least 2 working days. Minor"},{"line_number":29,"context_line":"   typo/formatting change updates do not reset the counter. There must be at"},{"line_number":30,"context_line":"   least four +1 votes and no -1\u0027s unless the concern by the -1 vote has been"},{"line_number":31,"context_line":"   discussed in an API WG meeting. Once the matter has been discussed there"},{"line_number":32,"context_line":"   should be no more than 20% (of votes cast) -1 votes."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_9136f8e5","line":29,"updated":"2015-06-16 04:01:45.000000000","message":"Here\n\n \"Minor typo/formatting change updates do not reset the counter.\"\n\nmeans\n\n Patch owner should not fix typos after getting many +1s\n\nor\n\n Even if resetting the counter by fixing typos, we need to count previous +1s\n\n?","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":6167,"name":"Ken\u0027ichi Ohmichi","email":"ken1ohmichi@gmail.com","username":"oomichi"},"change_message_id":"c76059f7775c4961672336f1fa9cb48881e24f4b","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"   In the guideline review, consensus means the changeset must be available"},{"line_number":28,"context_line":"   for review in its near final form for at least 2 working days. Minor"},{"line_number":29,"context_line":"   typo/formatting change updates do not reset the counter. There must be at"},{"line_number":30,"context_line":"   least four +1 votes and no -1\u0027s unless the concern by the -1 vote has been"},{"line_number":31,"context_line":"   discussed in an API WG meeting. Once the matter has been discussed there"},{"line_number":32,"context_line":"   should be no more than 20% (of votes cast) -1 votes."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_2aaf072b","line":29,"in_reply_to":"fa32b979_2ad067f5","updated":"2015-06-18 00:54:01.000000000","message":"Thanks for clarifying it, Everett\n\nThat is good for me:-)","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"227f41b763a05431943f305ca58af51d72ea2106","unresolved":false,"context_lines":[{"line_number":26,"context_line":""},{"line_number":27,"context_line":"   In the guideline review, consensus means the changeset must be available"},{"line_number":28,"context_line":"   for review in its near final form for at least 2 working days. Minor"},{"line_number":29,"context_line":"   typo/formatting change updates do not reset the counter. There must be at"},{"line_number":30,"context_line":"   least four +1 votes and no -1\u0027s unless the concern by the -1 vote has been"},{"line_number":31,"context_line":"   discussed in an API WG meeting. Once the matter has been discussed there"},{"line_number":32,"context_line":"   should be no more than 20% (of votes cast) -1 votes."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_2ad067f5","line":29,"in_reply_to":"fa32b979_9136f8e5","updated":"2015-06-18 00:49:52.000000000","message":"My current thinking is that it\u0027s the author\u0027s judgement call on whether or not to fix typos after getting many +1s. \n\nIf you choose to fix them, it\u0027s fine. We would just go with the +1s from the previous patch set and not reset the counter.","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":261,"name":"Salvatore Orlando","email":"salv.orlando@gmail.com","username":"salvatore-orlando"},"change_message_id":"e74f70e1bff10b2d6e87b3feb0e9682d47b1c0ab","unresolved":false,"context_lines":[{"line_number":37,"context_line":"   meetings. However we recognise that sometimes higher bandwidth, low"},{"line_number":38,"context_line":"   latency discussions can help break deadlocks."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"3. Once a changeset meets the requirements of #2, the `Cross Project Liaisons"},{"line_number":41,"context_line":"   \u003chttps://wiki.openstack.org/wiki/CrossProjectLiaisons#API_Working_Group\u003e`_"},{"line_number":42,"context_line":"   for the API WG should be engaged on various channels."},{"line_number":43,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_b150670c","line":40,"updated":"2015-06-18 07:07:05.000000000","message":"nit: [...] Cross Project Liaisons (CPL) [...]\n\n(introduce the acronym)","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":10215,"name":"Peter Stachowski","email":"peter@tesora.com","username":"peterstac"},"change_message_id":"3b4d1c34e91d91e4cc5b62964de72cb708dad9ea","unresolved":false,"context_lines":[{"line_number":42,"context_line":"   for the API WG should be engaged on various channels."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"   1. Review. The CPLs must be added as reviewers to any changeset that has"},{"line_number":45,"context_line":"   reached consensus."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"   2. The openstack-dev mailing list. An email must be sent to the"},{"line_number":48,"context_line":"   openstack-dev mailing list with the subject \"[all][api] New API"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5afe65bd_125e2444","line":45,"updated":"2015-06-04 16:10:29.000000000","message":"... reached consensus by the API WG.","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"227f41b763a05431943f305ca58af51d72ea2106","unresolved":false,"context_lines":[{"line_number":42,"context_line":"   for the API WG should be engaged on various channels."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"   1. Review. The CPLs must be added as reviewers to any changeset that has"},{"line_number":45,"context_line":"   reached consensus."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"   2. The openstack-dev mailing list. An email must be sent to the"},{"line_number":48,"context_line":"   openstack-dev mailing list with the subject \"[all][api] New API"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_8a073381","line":45,"in_reply_to":"5afe65bd_125e2444","updated":"2015-06-18 00:49:52.000000000","message":"Will fix in a subsequent patch.","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":10215,"name":"Peter Stachowski","email":"peter@tesora.com","username":"peterstac"},"change_message_id":"3b4d1c34e91d91e4cc5b62964de72cb708dad9ea","unresolved":false,"context_lines":[{"line_number":65,"context_line":"5. Once a changeset meets the requirements of #2, #3, and #4, the CPLs have"},{"line_number":66,"context_line":"   1 week to review it. If there is no review by a CPL, lazy consensus is"},{"line_number":67,"context_line":"   assumed. If there is a -1 review by a CPL that requires an update to the"},{"line_number":68,"context_line":"   changeset, it does not reset the 1 week the CPLs have to review it. Once"},{"line_number":69,"context_line":"   consensus it achieved, the changeset is mergable."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"6. Once a changeset meets the requirements of #5, it can be merged."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5afe65bd_7d6c09d0","line":69,"range":{"start_line":68,"start_character":71,"end_line":69,"end_character":52},"updated":"2015-06-04 16:10:29.000000000","message":"What is the criteria for CPL consensus?  Is it the same as for API WG consensus (i.e at least 4 votes, 80% approval) ?  (correct spelling is \u0027mergeable\u0027 ;) )","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"73d938be6654f0f89608ff79a340ed04d771c642","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   1 week to review it. If there is no review by a CPL, lazy consensus is"},{"line_number":67,"context_line":"   assumed. If there is a -1 review by a CPL that requires an update to the"},{"line_number":68,"context_line":"   changeset, it does not reset the 1 week the CPLs have to review it. Once"},{"line_number":69,"context_line":"   consensus it achieved, the changeset is mergable."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"6. Once a changeset meets the requirements of #5, it can be merged."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5afe65bd_62e92a80","line":69,"updated":"2015-06-03 20:44:38.000000000","message":"mergable? mergeable? this last sentence is redundant with #6 anyway","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"227f41b763a05431943f305ca58af51d72ea2106","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   1 week to review it. If there is no review by a CPL, lazy consensus is"},{"line_number":67,"context_line":"   assumed. If there is a -1 review by a CPL that requires an update to the"},{"line_number":68,"context_line":"   changeset, it does not reset the 1 week the CPLs have to review it. Once"},{"line_number":69,"context_line":"   consensus it achieved, the changeset is mergable."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"6. Once a changeset meets the requirements of #5, it can be merged."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_aa0a3788","line":69,"in_reply_to":"5afe65bd_62e92a80","updated":"2015-06-18 00:49:52.000000000","message":"Will fix in a subsequent patch.","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"},{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"227f41b763a05431943f305ca58af51d72ea2106","unresolved":false,"context_lines":[{"line_number":66,"context_line":"   1 week to review it. If there is no review by a CPL, lazy consensus is"},{"line_number":67,"context_line":"   assumed. If there is a -1 review by a CPL that requires an update to the"},{"line_number":68,"context_line":"   changeset, it does not reset the 1 week the CPLs have to review it. Once"},{"line_number":69,"context_line":"   consensus it achieved, the changeset is mergable."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"6. Once a changeset meets the requirements of #5, it can be merged."},{"line_number":72,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_ea1a7fc5","line":69,"in_reply_to":"5afe65bd_7d6c09d0","updated":"2015-06-18 00:49:52.000000000","message":"From #5. Consensus is lazy. Basically only a -1 by a CPL will matter.","commit_id":"b3e1874dcdc8ae20bf6a411bf6cced0c1c53149a"}]}