)]}'
{"reference/house-rules.rst":[{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"cd658aa506a4541383f586df75b418b405fde219","unresolved":false,"context_lines":[{"line_number":54,"context_line":"by providing links to artifacts for tracking the work, or an"},{"line_number":55,"context_line":"explanation of why work is not going to be done. They will also"},{"line_number":56,"context_line":"provide references to completion artifacts at the end of each cycle"},{"line_number":57,"context_line":"for goals where work was needed. These patches should be reviewed for"},{"line_number":58,"context_line":"completeness and clarity (is enough information provided for"},{"line_number":59,"context_line":"interested parties to track the work, or is the justification for not"},{"line_number":60,"context_line":"doing work clear enough)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_9a32f60e","line":57,"updated":"2016-08-29 22:03:15.000000000","message":"reviewed by the TC\n\n(best to set expectations and ensure ownership/understand responsiblity)","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"ee1e6fd7d95cadb5135e2f92ab7a95e3bc8046c5","unresolved":false,"context_lines":[{"line_number":54,"context_line":"by providing links to artifacts for tracking the work, or an"},{"line_number":55,"context_line":"explanation of why work is not going to be done. They will also"},{"line_number":56,"context_line":"provide references to completion artifacts at the end of each cycle"},{"line_number":57,"context_line":"for goals where work was needed. These patches should be reviewed for"},{"line_number":58,"context_line":"completeness and clarity (is enough information provided for"},{"line_number":59,"context_line":"interested parties to track the work, or is the justification for not"},{"line_number":60,"context_line":"doing work clear enough)."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_627104a8","line":57,"in_reply_to":"fa7ab95a_9a32f60e","updated":"2016-08-29 22:58:23.000000000","message":"Done","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"cd658aa506a4541383f586df75b418b405fde219","unresolved":false,"context_lines":[{"line_number":59,"context_line":"interested parties to track the work, or is the justification for not"},{"line_number":60,"context_line":"doing work clear enough)."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"They do not need to go through the formal vote process, and so the"},{"line_number":63,"context_line":"lazy consensus rules will be used. If there is no objection posted one"},{"line_number":64,"context_line":"week after the change is proposed (or a significant new revision of"},{"line_number":65,"context_line":"the change is posted), then the change can be approved by the chair."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_7c3c4fc8","line":62,"updated":"2016-08-29 22:03:15.000000000","message":"They here means either: PTLs? or the team\u0027s change artifacts? Can you clarify? \n\nAlso do we document our lazy consensus rules somewhere here? I can\u0027t find it with a simple scan. I only see \"fast-track\" referred to in this document.","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"ee1e6fd7d95cadb5135e2f92ab7a95e3bc8046c5","unresolved":false,"context_lines":[{"line_number":59,"context_line":"interested parties to track the work, or is the justification for not"},{"line_number":60,"context_line":"doing work clear enough)."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"They do not need to go through the formal vote process, and so the"},{"line_number":63,"context_line":"lazy consensus rules will be used. If there is no objection posted one"},{"line_number":64,"context_line":"week after the change is proposed (or a significant new revision of"},{"line_number":65,"context_line":"the change is posted), then the change can be approved by the chair."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_826a88b1","line":62,"in_reply_to":"fa7ab95a_7c3c4fc8","updated":"2016-08-29 22:58:23.000000000","message":"I\u0027ve clarified that I mean we\u0027re reviewing the patches.","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"cd658aa506a4541383f586df75b418b405fde219","unresolved":false,"context_lines":[{"line_number":63,"context_line":"lazy consensus rules will be used. If there is no objection posted one"},{"line_number":64,"context_line":"week after the change is proposed (or a significant new revision of"},{"line_number":65,"context_line":"the change is posted), then the change can be approved by the chair."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"If a TC member feels that one of these responses needs to be discussed"},{"line_number":68,"context_line":"by the entire TC, they should place it on the agenda for an upcoming"},{"line_number":69,"context_line":"meeting and the change should not be approved until after the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_1cf0a3fd","line":66,"updated":"2016-08-29 22:03:15.000000000","message":"Oh maybe you\u0027re defining lazy consensus rules with the last sentence? \n\nI think this is what the para means, please check my understanding and see if this revision could work:\n\nThese artifacts for tracking purposes do not need to go through the formal vote process. Instead, lazy consensus rules are used, meaning, if there is no objection posted one week after the artifact changes are proposed, then the change can be approved by the chair. If a significant new revision of the change is posted, and there\u0027s no objection within a week, that change can also be approved by the chair, using lazy consensus rules.","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"ee1e6fd7d95cadb5135e2f92ab7a95e3bc8046c5","unresolved":false,"context_lines":[{"line_number":63,"context_line":"lazy consensus rules will be used. If there is no objection posted one"},{"line_number":64,"context_line":"week after the change is proposed (or a significant new revision of"},{"line_number":65,"context_line":"the change is posted), then the change can be approved by the chair."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"If a TC member feels that one of these responses needs to be discussed"},{"line_number":68,"context_line":"by the entire TC, they should place it on the agenda for an upcoming"},{"line_number":69,"context_line":"meeting and the change should not be approved until after the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa7ab95a_42a32000","line":66,"in_reply_to":"fa7ab95a_1cf0a3fd","updated":"2016-08-29 22:58:23.000000000","message":"The phrase lazy consensus is used elsewhere in this document, and I mean roughly the same definition though I do clarify that I think significant changes to a patch should reset the clock.","commit_id":"6172505c2709eada4c372354f87e8f55713b6072"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"aa2bef2391019607a7508d65fab7266381f092b5","unresolved":false,"context_lines":[{"line_number":63,"context_line":"completion artifacts to the goal document do not need to go through"},{"line_number":64,"context_line":"the formal vote process, and so lazy consensus rules will be used. If"},{"line_number":65,"context_line":"there is no objection posted one week after the change is proposed (or"},{"line_number":66,"context_line":"a significant new revision of the change is posted), then the change"},{"line_number":67,"context_line":"can be approved by the chair."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"If a TC member feels that one of these responses needs to be discussed"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa7ab95a_384d489a","line":66,"updated":"2016-08-30 13:37:05.000000000","message":"I\u0027m still not able to parse the parenthetical.\n\nIf there\u0027s a significant new revision the chair approves anyway? Because of lazy consensus? I\u0027m confused.","commit_id":"d7fd6c9433433010accdd45f96523acf028082f4"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"fd3de964c5845f3be5f6c9ceac3c81fbb372afee","unresolved":false,"context_lines":[{"line_number":63,"context_line":"completion artifacts to the goal document do not need to go through"},{"line_number":64,"context_line":"the formal vote process, and so lazy consensus rules will be used. If"},{"line_number":65,"context_line":"there is no objection posted one week after the change is proposed (or"},{"line_number":66,"context_line":"a significant new revision of the change is posted), then the change"},{"line_number":67,"context_line":"can be approved by the chair."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"If a TC member feels that one of these responses needs to be discussed"}],"source_content_type":"text/x-rst","patch_set":3,"id":"fa7ab95a_08281932","line":66,"in_reply_to":"fa7ab95a_384d489a","updated":"2016-08-30 18:56:55.000000000","message":"I was trying to say \"if no object is posted after a significant revision is posted\" but I can see how that\u0027s confusing. I\u0027ve reworded.","commit_id":"d7fd6c9433433010accdd45f96523acf028082f4"}]}