)]}'
{"goals/index.rst":[{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"1563feb8fc166414ef1ce54fbd5e82f1d6e58511","unresolved":false,"context_lines":[{"line_number":69,"context_line":"setup starting S release and members of the community could propose specific"},{"line_number":70,"context_line":"goals in separate patches. The goal should have identification from the UC story"},{"line_number":71,"context_line":"board tracking. The goal should be also divided into sub-goals which is targeted"},{"line_number":72,"context_line":"to be resolved for each cycle."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"The actual goals shouldn\u0027t be completely new proposals (things no one"},{"line_number":75,"context_line":"else in the community has seen before) because there will have been"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_2c07f583","line":72,"updated":"2018-09-15 03:30:41.000000000","message":"++ I like this idea. We kind of took a similar approach with improving RBAC across OpenStack by breaking it into \"smaller\" pieces of work (but we didn\u0027t propose them as multiple goals, just documented the overall idea [0][1]).\n\nI agree that an overall document describing the order dependency of the goals is invaluable, especially when readers are groking the big picture.\n\nI will say that it\u0027s hard to get goals done, and queuing goals for multiple cycles is likely going to change. What if we relaxed this a bit to say that we have:\n\n* an overall conceptual document describing the big picture\n* a series of goals (possibly with a linear dependency) with that linear dependency laid out clearly in the overall conceptual document\n* one goal that is targeted to the release\n* all other goals are on-deck\n\nI\u0027m just thinking this might help reduce reshuffling goals when/if a required goal is missed for a release. Whenever a goal is completed, we can pop the next goal off the stack and propose it to the current release.\n\n[0] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-goals.html\n[1] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/policy-security-roadmap.html","commit_id":"c09131430a45df13be4ba2f04287b66de42fe27c"},{"author":{"_account_id":13629,"name":"Zhipeng","email":"huangzhipeng@huawei.com","username":"zhipengh"},"change_message_id":"0c2ccfbb87cbf5684ac116cb9f4533eef643aa61","unresolved":false,"context_lines":[{"line_number":69,"context_line":"setup starting S release and members of the community could propose specific"},{"line_number":70,"context_line":"goals in separate patches. The goal should have identification from the UC story"},{"line_number":71,"context_line":"board tracking. The goal should be also divided into sub-goals which is targeted"},{"line_number":72,"context_line":"to be resolved for each cycle."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"The actual goals shouldn\u0027t be completely new proposals (things no one"},{"line_number":75,"context_line":"else in the community has seen before) because there will have been"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_07e77248","line":72,"in_reply_to":"3f79a3b5_2c07f583","updated":"2018-09-15 04:59:51.000000000","message":"I think if I understand what you propose here is the sub-goals has to be formed in an order with monotonic dependency ? If so I really like the idea :)","commit_id":"c09131430a45df13be4ba2f04287b66de42fe27c"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"0b6b05cb462f4d0cab585fae67a7c6f002775382","unresolved":false,"context_lines":[{"line_number":72,"context_line":"to be carried out at certain percentage for each cycle. The goal/sub-goals"},{"line_number":73,"context_line":"structure could be designed as follows:"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"- an overall conceptual document describing the big picture (The Goal)"},{"line_number":76,"context_line":"- a series of (sub) goals (possibly with a linear dependency) with that linear"},{"line_number":77,"context_line":"dependency laid out clearly in the overall conceptual document"},{"line_number":78,"context_line":"- one (sub) goal that is targeted to the release"},{"line_number":79,"context_line":"- all other (sub) goals are on-deck"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The actual goals shouldn\u0027t be completely new proposals (things no one"},{"line_number":82,"context_line":"else in the community has seen before) because there will have been"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_640e5a33","line":79,"range":{"start_line":75,"start_character":0,"end_line":79,"end_character":35},"updated":"2018-09-16 08:11:25.000000000","message":"use \"*\" for RST and indent correctly","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":13629,"name":"Zhipeng","email":"huangzhipeng@huawei.com","username":"zhipengh"},"change_message_id":"24a2260dbc5fa2f5016f90b3a5d0f349867c1fa0","unresolved":false,"context_lines":[{"line_number":72,"context_line":"to be carried out at certain percentage for each cycle. The goal/sub-goals"},{"line_number":73,"context_line":"structure could be designed as follows:"},{"line_number":74,"context_line":""},{"line_number":75,"context_line":"- an overall conceptual document describing the big picture (The Goal)"},{"line_number":76,"context_line":"- a series of (sub) goals (possibly with a linear dependency) with that linear"},{"line_number":77,"context_line":"dependency laid out clearly in the overall conceptual document"},{"line_number":78,"context_line":"- one (sub) goal that is targeted to the release"},{"line_number":79,"context_line":"- all other (sub) goals are on-deck"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"The actual goals shouldn\u0027t be completely new proposals (things no one"},{"line_number":82,"context_line":"else in the community has seen before) because there will have been"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_2c758e98","line":79,"range":{"start_line":75,"start_character":0,"end_line":79,"end_character":35},"in_reply_to":"3f79a3b5_640e5a33","updated":"2018-09-18 02:41:18.000000000","message":"Done","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"0b6b05cb462f4d0cab585fae67a7c6f002775382","unresolved":false,"context_lines":[{"line_number":82,"context_line":"else in the community has seen before) because there will have been"},{"line_number":83,"context_line":"discussion in the course of reaching consensus."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"UC/SIG/WG is welcomed to submit multi-cycle long term goal for community wide"},{"line_number":86,"context_line":"solution of user/operator/customer requirements."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Tracking Goal Progress"},{"line_number":89,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_e42b4a7f","line":86,"range":{"start_line":85,"start_character":0,"end_line":86,"end_character":33},"updated":"2018-09-16 08:11:25.000000000","message":"this sentence is very confusing, it implies to me that SIG\u003doperator, WG\u003dcustomer, let\u0027s remove the \"/\" and formulate properly.","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":13629,"name":"Zhipeng","email":"huangzhipeng@huawei.com","username":"zhipengh"},"change_message_id":"24a2260dbc5fa2f5016f90b3a5d0f349867c1fa0","unresolved":false,"context_lines":[{"line_number":82,"context_line":"else in the community has seen before) because there will have been"},{"line_number":83,"context_line":"discussion in the course of reaching consensus."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"UC/SIG/WG is welcomed to submit multi-cycle long term goal for community wide"},{"line_number":86,"context_line":"solution of user/operator/customer requirements."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"Tracking Goal Progress"},{"line_number":89,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_ec6a36b3","line":86,"range":{"start_line":85,"start_character":0,"end_line":86,"end_character":33},"in_reply_to":"3f79a3b5_e42b4a7f","updated":"2018-09-18 02:41:18.000000000","message":"Done","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"0b6b05cb462f4d0cab585fae67a7c6f002775382","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":"For long term goals, the members who proposed the goals could choose either to"},{"line_number":96,"context_line":"recruit separate goal champions for each cycle or serve as the champion"},{"line_number":97,"context_line":"themselves if they were UC/WG/SIG members. The tracking will utilize the UC"},{"line_number":98,"context_line":"storyboard facility."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_64373ae5","line":97,"updated":"2018-09-16 08:11:25.000000000","message":"were? -\u003e are. Why UC/WG/SIG are special.","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":13629,"name":"Zhipeng","email":"huangzhipeng@huawei.com","username":"zhipengh"},"change_message_id":"24a2260dbc5fa2f5016f90b3a5d0f349867c1fa0","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":"For long term goals, the members who proposed the goals could choose either to"},{"line_number":96,"context_line":"recruit separate goal champions for each cycle or serve as the champion"},{"line_number":97,"context_line":"themselves if they were UC/WG/SIG members. The tracking will utilize the UC"},{"line_number":98,"context_line":"storyboard facility."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":".. note::"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_0c70d2a3","line":97,"in_reply_to":"3f79a3b5_64373ae5","updated":"2018-09-18 02:41:18.000000000","message":"Done","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":11589,"name":"Harry Rybacki","email":"hrybacki@redhat.com","username":"hrybacki"},"change_message_id":"f5e82b828f24e383dc8fc33f0c442867ecbf2377","unresolved":false,"context_lines":[{"line_number":92,"context_line":"goal and one task per project per goal to track progress on"},{"line_number":93,"context_line":"completion."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"For long term goals, the members who proposed the goals could choose either to"},{"line_number":96,"context_line":"recruit separate goal champions for each cycle or serve as the champion"},{"line_number":97,"context_line":"themselves if they were UC/WG/SIG members. The tracking will utilize the UC"},{"line_number":98,"context_line":"storyboard facility."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":".. note::"},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_564f4234","line":98,"range":{"start_line":95,"start_character":0,"end_line":98,"end_character":20},"updated":"2018-09-17 14:49:01.000000000","message":"In another field I spend a lot of time in we rely heavily on community resources to accomplish our \u0027long term community goals.\u0027 \n\nWe have found that pairing up one of our board members with a community member as co-chairs (co-champions here) provides a succinct way to ensure the board is up-to-speed (can provide updates at meetings easily) and the community has an active leader (co-champion) that is not inundated with board (TC) responsibilities. \n\nWe should consider this concept when talking about multi-release goals. At a minimum it helps provide more continuity between the TC and group(s) working the issues.","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":13629,"name":"Zhipeng","email":"huangzhipeng@huawei.com","username":"zhipengh"},"change_message_id":"24a2260dbc5fa2f5016f90b3a5d0f349867c1fa0","unresolved":false,"context_lines":[{"line_number":92,"context_line":"goal and one task per project per goal to track progress on"},{"line_number":93,"context_line":"completion."},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"For long term goals, the members who proposed the goals could choose either to"},{"line_number":96,"context_line":"recruit separate goal champions for each cycle or serve as the champion"},{"line_number":97,"context_line":"themselves if they were UC/WG/SIG members. The tracking will utilize the UC"},{"line_number":98,"context_line":"storyboard facility."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":".. note::"},{"line_number":101,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_0c7e9269","line":98,"range":{"start_line":95,"start_character":0,"end_line":98,"end_character":20},"in_reply_to":"3f79a3b5_564f4234","updated":"2018-09-18 02:41:18.000000000","message":"This is an excellent point :) One extra thing we need to address is that TC composition changes from time to time, so maybe if we illustrate a little bit better that there is a co-championship bounding of 2 -3 people here, and unless the people sign off, no matter what the official status changes, the co team stays the same. TC or the Board at the mean time could point new liaison to help.","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"0b6b05cb462f4d0cab585fae67a7c6f002775382","unresolved":false,"context_lines":[{"line_number":140,"context_line":""},{"line_number":141,"context_line":"For long term goals project teams do not have to prioritize the sub-goals in"},{"line_number":142,"context_line":"certain cycle, but simply acknowledge the goals. In this way there is no mandate"},{"line_number":143,"context_line":"on development/release cadence, no overlap/conflict with the cycle-only goals,"},{"line_number":144,"context_line":"and give the project team its freedom to plan things themselves out."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"However the release team will need to use a newly added section called"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_841cd666","line":143,"range":{"start_line":143,"start_character":42,"end_line":143,"end_character":43},"updated":"2018-09-16 08:11:25.000000000","message":"reword and avoid \"/\", they only cause confusion on whether you mean \"and\" or \"or\".","commit_id":"316418e643ccdd4fdf061729cc255604e625e22b"}]}