)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"b897409258ae08b8cd08996906fdf7ae864732b0","unresolved":false,"context_lines":[{"line_number":33,"context_line":""},{"line_number":34,"context_line":"- Possibility for arranging more focused discussions with stackholders"},{"line_number":35,"context_line":"  on hours that work best. The smaller the group, the easier it is to"},{"line_number":36,"context_line":"  pick a time."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- More open and transparent discussions as it\u0027ll force everyone to"},{"line_number":39,"context_line":"  discuss things using gerrit and the mailing list instead of waiting"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_586353b2","line":36,"updated":"2017-04-26 17:06:09.000000000","message":"While this is true for known stakeholders, a moving time will almost certainly exclude interested parties that weren\u0027t identified early","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"b897409258ae08b8cd08996906fdf7ae864732b0","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- More open and transparent discussions as it\u0027ll force everyone to"},{"line_number":39,"context_line":"  discuss things using gerrit and the mailing list instead of waiting"},{"line_number":40,"context_line":"  for meetings to happen."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_b8f017cb","line":40,"updated":"2017-04-26 17:06:09.000000000","message":"While this may simplify things for the TC, it puts greater work for non-TC members that wish to track the direction of the technical committee without reviewing each and every CR to gerrit. The agenda for the TC meeting is one of the best summaries of current state there is. Without the meeting, there may be an exercise to summarize, but that has been attempted and then ceased in the recent past.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"99da8230d945bd40bba9d6f8070327f16856ccfc","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- More open and transparent discussions as it\u0027ll force everyone to"},{"line_number":39,"context_line":"  discuss things using gerrit and the mailing list instead of waiting"},{"line_number":40,"context_line":"  for meetings to happen."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_dad15625","line":40,"in_reply_to":"5ff73747_b8f017cb","updated":"2017-04-27 14:23:36.000000000","message":"This is a good point. I think we can solve some of this issues by sending constant updates to the mailing with the list of \"hot topics\" or something like that.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"b897409258ae08b8cd08996906fdf7ae864732b0","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"},{"line_number":44,"context_line":"  focus on the other 2 we\u0027re already using."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_98c43b61","line":44,"updated":"2017-04-26 17:06:09.000000000","message":"I disagree, you are removing the most concise form and only leaving the longer forms.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"99da8230d945bd40bba9d6f8070327f16856ccfc","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"},{"line_number":44,"context_line":"  focus on the other 2 we\u0027re already using."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_1a3fbe87","line":44,"in_reply_to":"5ff73747_98c43b61","updated":"2017-04-27 14:23:36.000000000","message":"The TC meetings don\u0027t represent all the views of everyone that has been involved in a specific discussion. More often than not, things are skipped during the TC meeting and folks can\u0027t attend making the content of the meeting not enough to actually know what\u0027s going on.\n\nLet alone discussions that are split into several meetings","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"9c1810e58575b0822f105fd5f726feb76a2e4d0c","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"},{"line_number":48,"context_line":"  to do it."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Change-Id: If70bb95da3216aad7632983f1955d06de1c50521"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_e8047f4c","line":48,"updated":"2017-04-26 08:43:54.000000000","message":"I think we need to also add in something about timzones here, but I see thats covered in the main body of the doc.\n\nIn the past poor PTLs in some continents had to attend the meeting at 4 am to make their case for their project to be added into the project.yaml. To me thats totally unacceptable. We can go on about they didn\u0027t have to, but thats not the point.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":5623,"name":"David Lyle","email":"dklyle0@gmail.com","username":"david-lyle"},"change_message_id":"b897409258ae08b8cd08996906fdf7ae864732b0","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"},{"line_number":48,"context_line":"  to do it."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Change-Id: If70bb95da3216aad7632983f1955d06de1c50521"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_3884070c","line":48,"updated":"2017-04-26 17:06:09.000000000","message":"This bullet is certainly true.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"99da8230d945bd40bba9d6f8070327f16856ccfc","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"},{"line_number":48,"context_line":"  to do it."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"Change-Id: If70bb95da3216aad7632983f1955d06de1c50521"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"5ff73747_ba932a5b","line":48,"in_reply_to":"5ff73747_e8047f4c","updated":"2017-04-27 14:23:36.000000000","message":"I can add it as a bullet too :)","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- More open and transparent discussions as it\u0027ll force everyone to"},{"line_number":39,"context_line":"  discuss things using gerrit and the mailing list instead of waiting"},{"line_number":40,"context_line":"  for meetings to happen."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5ff73747_71bfdba9","line":40,"updated":"2017-04-28 16:46:27.000000000","message":"I don\u0027t know that this is accurate cause and effect. What could happen instead is that more conversations will happen in #openstack-dev, on the fly, meaning even less involvement by people who don\u0027t happen to be there (at that unpredictable time).\n\nSo the thing that needs to happen is not that we only dissuade the regular meeting but that we very explicitly require asynch communication for most things.\n\n(Assuming maximum participation is the primary goal)","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"- More open and transparent discussions as it\u0027ll force everyone to"},{"line_number":39,"context_line":"  discuss things using gerrit and the mailing list instead of waiting"},{"line_number":40,"context_line":"  for meetings to happen."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5ff73747_3225ba09","line":40,"in_reply_to":"5ff73747_71bfdba9","updated":"2017-05-01 11:25:33.000000000","message":"Yes! What I tried to express here is the expected actions/behavior and not necessarily the \"natural\" effect of this change.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"},{"line_number":44,"context_line":"  focus on the other 2 we\u0027re already using."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5ff73747_b1f7a38b","line":44,"updated":"2017-04-28 16:46:27.000000000","message":"That\u0027s not really true. We\u0027ll going from three predictable (the meeting, gerrit, email) and one unpredictable channel (random irc chats) to two predictable and one potentially very increased unpredictable.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":41,"context_line":""},{"line_number":42,"context_line":"- It\u0027ll be easier for folks to stay up-to-date with the on-going"},{"line_number":43,"context_line":"  discussions as we\u0027ll be reducing one channel of communication and"},{"line_number":44,"context_line":"  focus on the other 2 we\u0027re already using."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"- It\u0027ll be easier for folks (especially non-native English speakers) to"},{"line_number":47,"context_line":"  participate in the discussions as it\u0027ll allow them to take their time"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5ff73747_326a5a19","line":44,"in_reply_to":"5ff73747_b1f7a38b","updated":"2017-05-01 11:25:33.000000000","message":"Again, this all depends on how the TC members will act after this change. There are 13 of us driving this change. What I mean is that if members of the TC drive this change correctly by having IRC conversations when really needed, by encouraging asynchronous communications over synchronous, by logging and reporting everything to gerrit/email when these IRC chats happen, then we should be reducing the channels.\n\nWe\u0027re not expecting the entire community to drive this change but us. It\u0027s entirely our responsibility.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"}],"resolutions/20170425-drop-tc-weekly-meetings.rst":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8159897c7ff2faef7900f9af65cddd2c0374d2c5","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"2017-04-25 Drop Technical Committee meetings "},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The Technical Committee meetings have become a barrier for some folks in the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ff73747_bbb915ea","line":2,"updated":"2017-04-26 15:17:25.000000000","message":"nit","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8159897c7ff2faef7900f9af65cddd2c0374d2c5","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Ad-Hoc meetings with the stakeholders for specific topics can happen but the"},{"line_number":20,"context_line":"results of these discussions should be published on gerrit (assuming there\u0027s a"},{"line_number":21,"context_line":"review in progress) and/or the mailing list."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ff73747_5b78d128","line":21,"updated":"2017-04-26 15:17:25.000000000","message":"Do we need to make sure that these ad hoc meetings are not just logged, but referenced in a concrete way so they can be discovered.\n\nOtherwise we could end up with results but no background.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"99da8230d945bd40bba9d6f8070327f16856ccfc","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Ad-Hoc meetings with the stakeholders for specific topics can happen but the"},{"line_number":20,"context_line":"results of these discussions should be published on gerrit (assuming there\u0027s a"},{"line_number":21,"context_line":"review in progress) and/or the mailing list."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ff73747_7a72424b","line":21,"in_reply_to":"5ff73747_5b78d128","updated":"2017-04-27 14:23:36.000000000","message":"Yes, I\u0027ll be more explicit about it.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"f9600464d19c90fd5e57c37f1bd0723385b10e4d","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Ad-Hoc meetings with the stakeholders for specific topics can happen but the"},{"line_number":20,"context_line":"results of these discussions should be published on gerrit (assuming there\u0027s a"},{"line_number":21,"context_line":"review in progress) and/or the mailing list."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ff73747_a07ad0ed","line":21,"in_reply_to":"5ff73747_7a72424b","updated":"2017-04-27 18:26:28.000000000","message":"i imagine ad-hoc needs to include some defined notice time so that people can actually figure out if they are interested? i guess the argument for having a set time is that you know exactly when something of importance will be discussed (even if it\u0027s at 3am in the morning).","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"9c1810e58575b0822f105fd5f726feb76a2e4d0c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5ff73747_283ca7e0","line":22,"updated":"2017-04-26 08:43:54.000000000","message":"I think we need some sort of sprint cadence in here to replace the weekly meeting.\n\nA weekly status email with some sort of list of reviews that are about to be approved / seem close, similar to the meeting agenda.\n\nWe could make it the chair\u0027s job to ensure the weekly email is sent, and the status is collected together somehow (I know ttx is looking at a wiki page for the swg).","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"077aae93b4735a10b38adcac882b435c7e47d168","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5ff73747_eacc69bd","line":22,"in_reply_to":"5ff73747_283ca7e0","updated":"2017-04-26 14:01:57.000000000","message":"+1","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"99da8230d945bd40bba9d6f8070327f16856ccfc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5ff73747_fa9bf262","line":22,"in_reply_to":"5ff73747_283ca7e0","updated":"2017-04-27 14:23:36.000000000","message":"This used to be part of the communications working group and I think we can revive that with help from other folks too. A weekly summary will be necessary, yes.","commit_id":"a4b1e0df5a895422a3680a957150e9733f05e069"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"2017-04-25 Replace Technical Committee meetings "},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The Technical Committee meetings have become a barrier for some folks in the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_110d378f","line":2,"updated":"2017-04-28 16:46:27.000000000","message":"nit whitespace","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"2017-04-25 Replace Technical Committee meetings "},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The Technical Committee meetings have become a barrier for some folks in the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_f26f5225","line":2,"in_reply_to":"5ff73747_110d378f","updated":"2017-05-01 11:25:33.000000000","message":"Done","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Negative aspects of the current format:"},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_71491bb5","line":19,"updated":"2017-04-28 16:46:27.000000000","message":"It\u0027s also a known moment in time when the community can show up and be a part of things.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Negative aspects of the current format:"},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_b2678a4d","line":19,"in_reply_to":"5ff73747_71491bb5","updated":"2017-05-01 11:25:33.000000000","message":"Done","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2dd348cbb1df889abfbf0c1c60db4912f1fb792b","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Negative aspects of the current format:"},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_d900e436","line":19,"in_reply_to":"5ff73747_b2678a4d","updated":"2017-05-02 08:34:30.000000000","message":"I would elaborate on \"the meeting keeps efforts progressing\", and say instead:\n\nThe meeting provides a weekly rhythm that forces TC members to regularly pay attention to TC initiatives, and therefore keeps efforts progressing","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"c8bb4c8afd17346a9e8636dbf1d1f07a4f3cf4fa","unresolved":false,"context_lines":[{"line_number":45,"context_line":"----------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The weekly meeting gives us a good regular cadence to keep progress moving"},{"line_number":48,"context_line":"forward. When we loose the regular meeting, we really need to keep this"},{"line_number":49,"context_line":"cadence. This should not be merely be a summary of what has happened, but"},{"line_number":50,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":51,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_a633c3aa","line":48,"updated":"2017-05-01 18:49:57.000000000","message":"/loose/lose/","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2dd348cbb1df889abfbf0c1c60db4912f1fb792b","unresolved":false,"context_lines":[{"line_number":50,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":51,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":54,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_59f5f455","line":53,"range":{"start_line":53,"start_character":4,"end_line":53,"end_character":32},"updated":"2017-05-02 08:34:30.000000000","message":"The stuff mentioned below feels a lot like what the TC chair currently needs to track anyway (priority reviews, blocked reviews, application of house rules shortcuts, etc...). \n\nRather than duplicating this work, it sounds simpler if the TC chair would directly produce that weekly content as part of that tracking work. The chair would delegate that role in case of absence, in the same way we currently delegate chairing of the meeting.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":57,"context_line":"* Gerrit patches and email threads that need attention over the coming week"},{"line_number":58,"context_line":"* List of reviews that have enough support to be merged. They will be merged"},{"line_number":59,"context_line":"  after a 24 hour period of waiting for any final objections. This can be"},{"line_number":60,"context_line":"  accelerated, as normal, using the existing house rules."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"It is likely the above will be built in a collaborative way using tools such"},{"line_number":63,"context_line":"as gerrit, wiki pages and etherpads that track the TC\u0027s work."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_71f7db5a","line":60,"updated":"2017-04-28 16:46:27.000000000","message":"This is a great of way for the TC to keep the community informed, but it does not fully accomplish the reverse: the community keeping the TC informed.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":57,"context_line":"* Gerrit patches and email threads that need attention over the coming week"},{"line_number":58,"context_line":"* List of reviews that have enough support to be merged. They will be merged"},{"line_number":59,"context_line":"  after a 24 hour period of waiting for any final objections. This can be"},{"line_number":60,"context_line":"  accelerated, as normal, using the existing house rules."},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"It is likely the above will be built in a collaborative way using tools such"},{"line_number":63,"context_line":"as gerrit, wiki pages and etherpads that track the TC\u0027s work."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_124e3ec0","line":60,"in_reply_to":"5ff73747_71f7db5a","updated":"2017-05-01 11:25:33.000000000","message":"We need to encourage the community to use email or gerrit to keep the TC informed. If IRC is better, then the TC members involved in those conversations should keep the rest of the team informed.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4361b07f172a7b92ab2fffd0ff991af5ccdfc73","unresolved":false,"context_lines":[{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The weekly meeting is a good time for non-TC members to interact with TC"},{"line_number":73,"context_line":"members. However the timing is very poor for many members of the community."},{"line_number":74,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":77,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_51c17fe4","line":74,"updated":"2017-04-28 16:46:27.000000000","message":"This will help with that, but we\u0027ll need to be good about it.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b4b5568dcd96b6f732e77952cf1534ad4affa987","unresolved":false,"context_lines":[{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The weekly meeting is a good time for non-TC members to interact with TC"},{"line_number":73,"context_line":"members. However the timing is very poor for many members of the community."},{"line_number":74,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":77,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_92cfee27","line":74,"in_reply_to":"5ff73747_51c17fe4","updated":"2017-05-01 11:25:33.000000000","message":"+1","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2dd348cbb1df889abfbf0c1c60db4912f1fb792b","unresolved":false,"context_lines":[{"line_number":84,"context_line":"in review and possibly close to getting merged. Doing this in the meeting"},{"line_number":85,"context_line":"makes it clear when something will be debated so people can join in that"},{"line_number":86,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":87,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":90,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_140a931e","line":87,"updated":"2017-05-02 08:34:30.000000000","message":"My suggestion would be that in case of stuck reviews (due to standing disagreements), the chair could call for a live meeting to discuss that specific problem. It should be exceptional: in most cases the disagreement should be solved in the review using async communications and/or office hours group discussions.\n\nIf a meeting is necessary, it would be organized/chaired by a facilitator (someone mostly neutral on the issue ideally) who would be tasked with posting a summary to the review and/or ML at the end of the meeting. If the issue takes less than an hour to discuss, the meeting can end early. If it takes more than an hour, a second meeting could be organized a few days later. Scheduling the meeting could be done using framadate on a number of pre-designated worldwide time slots, asking for interested parties to vote on time and picking the less worse option.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"719960537fb47983bd850772d1736efe77dd6e98","unresolved":false,"context_lines":[{"line_number":86,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":87,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":90,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"},{"line_number":91,"context_line":"allow for much higher bandwidth, if we are successful."},{"line_number":92,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_ee4a9daa","line":89,"range":{"start_line":89,"start_character":37,"end_line":89,"end_character":39},"updated":"2017-05-02 20:00:56.000000000","message":"redundant word","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"719960537fb47983bd850772d1736efe77dd6e98","unresolved":false,"context_lines":[{"line_number":87,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":90,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"},{"line_number":91,"context_line":"allow for much higher bandwidth, if we are successful."},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"While email and gerrit conversations provide a good asynchronous mechanism to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_aeca5517","line":90,"range":{"start_line":90,"start_character":46,"end_line":90,"end_character":53},"updated":"2017-05-02 20:00:56.000000000","message":"Loosening?","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"719960537fb47983bd850772d1736efe77dd6e98","unresolved":false,"context_lines":[{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":90,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"},{"line_number":91,"context_line":"allow for much higher bandwidth, if we are successful."},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"While email and gerrit conversations provide a good asynchronous mechanism to"},{"line_number":94,"context_line":"debate, sometimes it is more efficient to have a synchronous conversation to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5ff73747_aec135e7","line":91,"updated":"2017-05-02 20:00:56.000000000","message":"I don\u0027t agree with this assertion. We have a policy in place today that says we will review topics during meetings before final approval. We have no policy stating how many topics anyone can review. If we had more topics with enough votes to pass, I think we would have them on the agenda already. So, I don\u0027t think removing the need to discuss them during a meeting is going to automatically mean they will be discussed more rapidly in other places.","commit_id":"a06b0d82ee0c1d5a9ee301e395a7f0d41f22e99c"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"47bdbd3a825716c3ece5b5ef049c74e20adb76ad","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f013ff3_ef2df246","line":19,"updated":"2017-05-15 10:25:22.000000000","message":"I would elaborate on \"the meeting keeps efforts progressing\", and say instead:\n\nThe meeting provides a weekly rhythm that forces TC members to regularly pay attention to TC initiatives, and therefore keeps efforts progressing","commit_id":"a237780a409ea3fd7fdf413865badedc1d2127fa"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"47bdbd3a825716c3ece5b5ef049c74e20adb76ad","unresolved":false,"context_lines":[{"line_number":51,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":52,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":55,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f013ff3_af27ea64","line":54,"updated":"2017-05-15 10:25:22.000000000","message":"The stuff mentioned below feels a lot like what the TC chair currently needs to track anyway (priority reviews, blocked reviews, application of house rules shortcuts, etc...). \n\nRather than duplicating this work, it sounds simpler if the TC chair would directly produce that weekly content as part of that tracking work. The chair would delegate that role in case of absence, in the same way we currently delegate chairing of the meeting.","commit_id":"a237780a409ea3fd7fdf413865badedc1d2127fa"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"47bdbd3a825716c3ece5b5ef049c74e20adb76ad","unresolved":false,"context_lines":[{"line_number":85,"context_line":"in review and possibly close to getting merged. Doing this in the meeting"},{"line_number":86,"context_line":"makes it clear when something will be debated so people can join in that"},{"line_number":87,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":88,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":91,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f013ff3_efd29234","line":88,"updated":"2017-05-15 10:25:22.000000000","message":"My suggestion would be that in case of stuck reviews (due to standing disagreements), the chair could call for a live meeting to discuss that specific problem. It should be exceptional: in most cases the disagreement should be solved in the review using async communications and/or office hours group discussions.\n\nIf a meeting is necessary, it would be organized/chaired by a facilitator (someone mostly neutral on the issue ideally) who would be tasked with posting a summary to the review and/or ML at the end of the meeting. If the issue takes less than an hour to discuss, the meeting can end early. If it takes more than an hour, a second meeting could be organized a few days later. Scheduling the meeting could be done using framadate on a number of pre-designated worldwide time slots, asking for interested parties to vote on time and picking the less worse option.","commit_id":"a237780a409ea3fd7fdf413865badedc1d2127fa"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d245d06bb7cfaf8fe7d0ed609f7830c3bdf721a1","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_56f69afb","line":19,"updated":"2017-05-16 13:12:03.000000000","message":"I would elaborate on \"the meeting keeps efforts progressing\", and say instead:\n\nThe meeting provides a weekly rhythm that forces TC members to regularly pay attention to TC initiatives, and therefore keeps efforts progressing.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_7c173053","line":19,"in_reply_to":"1f013ff3_56f69afb","updated":"2017-05-16 16:35:06.000000000","message":"++ for the word \"rhythm\" going in here, thats the thing we need to keep after the meeting, from a process point of view.\n\nI am not just saying that because I play the Tuba, its widely used in describing process ;)","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"db8891b1969d1a34766ba2b9e0d98384bdd81dfa","unresolved":false,"context_lines":[{"line_number":16,"context_line":"  how to move a particular proposal or idea forward."},{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f436f4f_a4256aad","line":19,"in_reply_to":"1f013ff3_56f69afb","updated":"2017-08-11 11:33:30.000000000","message":"Done","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_9f09ce2d","line":20,"range":{"start_line":20,"start_character":20,"end_line":20,"end_character":38},"updated":"2017-05-16 16:35:06.000000000","message":"Nit: when parts of the community can show up","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"db8891b1969d1a34766ba2b9e0d98384bdd81dfa","unresolved":false,"context_lines":[{"line_number":17,"context_line":"* The meeting is used to make time to resolve disagreements and build"},{"line_number":18,"context_line":"  consensus around the particular topics that need progressing."},{"line_number":19,"context_line":"* The meeting keeps efforts progressing"},{"line_number":20,"context_line":"* It\u0027s a known time when the community can show up and interact with the TC"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Negative aspects of the current format:"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f436f4f_643782e5","line":20,"range":{"start_line":20,"start_character":20,"end_line":20,"end_character":38},"in_reply_to":"1f013ff3_9f09ce2d","updated":"2017-08-11 11:33:30.000000000","message":"Done","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"905b4c0182d8b5e57e40175a0671fc6094e411e7","unresolved":false,"context_lines":[{"line_number":28,"context_line":"  conversation and get their point across. It is even worse for non-native"},{"line_number":29,"context_line":"  English speakers."},{"line_number":30,"context_line":"* Feels like many conversations happen outside the meeting in non-open ways,"},{"line_number":31,"context_line":"  we should make it easy to have more open conversations."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"All of this is fighting the goals laid out in the TC 2019 vision around"},{"line_number":34,"context_line":"diversity of OpenStack leadership and in particular in the TC. We must"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_88463b7c","line":31,"updated":"2017-05-16 16:10:09.000000000","message":"While I don\u0027t disagree with this sentiment, I do not see how it really affects the rest of this resolution.  Stepping up efforts to move discussion away from meetings to ML/IRC/etc does not really change the motivation for side-channel conversations.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":28,"context_line":"  conversation and get their point across. It is even worse for non-native"},{"line_number":29,"context_line":"  English speakers."},{"line_number":30,"context_line":"* Feels like many conversations happen outside the meeting in non-open ways,"},{"line_number":31,"context_line":"  we should make it easy to have more open conversations."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"All of this is fighting the goals laid out in the TC 2019 vision around"},{"line_number":34,"context_line":"diversity of OpenStack leadership and in particular in the TC. We must"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_3f375ae6","line":31,"in_reply_to":"1f013ff3_88463b7c","updated":"2017-05-16 16:35:06.000000000","message":"I would strongly argue its very related to the meeting time. Its way too common to PM folks on IRC to make things happen before the meeting, because there is no other established way to make things happen.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d245d06bb7cfaf8fe7d0ed609f7830c3bdf721a1","unresolved":false,"context_lines":[{"line_number":51,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":52,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":55,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_16d8127d","line":54,"updated":"2017-05-16 13:12:03.000000000","message":"The stuff mentioned below feels a lot like what the TC chair currently needs to track anyway (priority reviews, blocked reviews, application of house rules shortcuts, etc...). \n\nRather than duplicating this work, it sounds simpler if the TC chair would directly produce that weekly content as part of that tracking work. The chair would delegate that role in case of absence, in the same way we currently delegate chairing of the meeting.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"905b4c0182d8b5e57e40175a0671fc6094e411e7","unresolved":false,"context_lines":[{"line_number":51,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":52,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":55,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_dcff64ff","line":54,"in_reply_to":"1f013ff3_16d8127d","updated":"2017-05-16 16:10:09.000000000","message":"++","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"db8891b1969d1a34766ba2b9e0d98384bdd81dfa","unresolved":false,"context_lines":[{"line_number":51,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":52,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":55,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f436f4f_24461a51","line":54,"in_reply_to":"1f013ff3_9f70aea7","updated":"2017-08-11 11:33:30.000000000","message":"Done","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":51,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":52,"context_line":"existing meeting agenda that is sent 24 hours before the current meeting."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The communications working group will be responsible for getting a weekly"},{"line_number":55,"context_line":"checkpoint email sent that includes items such as:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Highlights of what the TC has got done over the last week"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_9f70aea7","line":54,"in_reply_to":"1f013ff3_dcff64ff","updated":"2017-05-16 16:35:06.000000000","message":"I prefer making it the chair\u0027s role, to make sure it happens. Some sub committee could end up doing it.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"2e78d1bac492cbcb4a1c1c570bbe049b81b128a5","unresolved":false,"context_lines":[{"line_number":74,"context_line":"members. However the timing is very poor for many members of the community."},{"line_number":75,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":78,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"},{"line_number":79,"context_line":"timezone to drop in and ask questions."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_4b238806","line":77,"updated":"2017-05-16 19:24:23.000000000","message":"I have no idea what \"ring fence a group of slots\" means. It sounds like it has something to do with sheep, though.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"db8891b1969d1a34766ba2b9e0d98384bdd81dfa","unresolved":false,"context_lines":[{"line_number":74,"context_line":"members. However the timing is very poor for many members of the community."},{"line_number":75,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":78,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"},{"line_number":79,"context_line":"timezone to drop in and ask questions."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f436f4f_049c36be","line":77,"in_reply_to":"1f013ff3_4b238806","updated":"2017-08-11 11:33:30.000000000","message":"reworded","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"905b4c0182d8b5e57e40175a0671fc6094e411e7","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":78,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"},{"line_number":79,"context_line":"timezone to drop in and ask questions."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"Debating"},{"line_number":82,"context_line":"--------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_3cf408cf","line":79,"updated":"2017-05-16 16:10:09.000000000","message":"I think one of the keys to making this work is to have regular published times.  That sets expectations in the community and assists in keeping the rhythm mentioned above going.  I find it very helpful to block time in my calendar to focus on TC activities, more so if it is a regular time each week.  The accountability to others is a motivating factor here, maybe more than I want to admit.\n\nFrankly, today most of the TC _is_ available on IRC much of the time, even outside local work hours.  Part of what we are trying to do is modify the culture a bit and establish new expectations i the community that extend beyond the current membership.\n\nAlso, I am sure there is more than a little feeling of \"not wanting to interrupt\" other work so the conversations are not started by those who may not be long-time contributors.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Ring fence a group of slots so there are current members of the TC present in"},{"line_number":78,"context_line":"the #openstack-dev IRC channel and there is a good time for folks from any"},{"line_number":79,"context_line":"timezone to drop in and ask questions."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"Debating"},{"line_number":82,"context_line":"--------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_5f98e6be","line":79,"in_reply_to":"1f013ff3_3cf408cf","updated":"2017-05-16 16:35:06.000000000","message":"I think regular published times was probably the intent of \"a group of slots\", I guess the wording could be tightened up here.\n\nI want to move away from the assumption that we only spend some small amount of scheudled time on TC work, when others are also available. That will not help us grown a more global level of participation. We can and should all come up with our own preferences for how we manage our time.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d245d06bb7cfaf8fe7d0ed609f7830c3bdf721a1","unresolved":false,"context_lines":[{"line_number":85,"context_line":"in review and possibly close to getting merged. Doing this in the meeting"},{"line_number":86,"context_line":"makes it clear when something will be debated so people can join in that"},{"line_number":87,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":88,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":91,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_36c66e9c","line":88,"updated":"2017-05-16 13:12:03.000000000","message":"My suggestion would be that in case of stuck reviews (due to standing disagreements), the chair could call for a live meeting to discuss that specific problem. It should be exceptional: in most cases the disagreement should be solved in the review using async communications and/or office hours group discussions.\n\nIf a meeting is necessary, it would be organized/chaired by a facilitator (someone mostly neutral on the issue ideally) who would be tasked with posting a summary to the review and/or ML at the end of the meeting. If the issue takes less than an hour to discuss, the meeting can end early. If it takes more than an hour, a second meeting could be organized a few days later. Scheduling the meeting could be done using framadate on a number of pre-designated worldwide time slots, asking for interested parties to vote on time and picking the less worse option.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"3bc8a0a66d63b063c18e7d6fdc09b487b28a8992","unresolved":false,"context_lines":[{"line_number":85,"context_line":"in review and possibly close to getting merged. Doing this in the meeting"},{"line_number":86,"context_line":"makes it clear when something will be debated so people can join in that"},{"line_number":87,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":88,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":91,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f013ff3_5fdd866e","line":88,"in_reply_to":"1f013ff3_36c66e9c","updated":"2017-05-16 16:35:06.000000000","message":"++ ttx describes my preference well. Using the office hour slots may be a good starting point.","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"db8891b1969d1a34766ba2b9e0d98384bdd81dfa","unresolved":false,"context_lines":[{"line_number":85,"context_line":"in review and possibly close to getting merged. Doing this in the meeting"},{"line_number":86,"context_line":"makes it clear when something will be debated so people can join in that"},{"line_number":87,"context_line":"debate, and the debate is clearly recorded in the meeting logs. We need to"},{"line_number":88,"context_line":"find a similar forum of debate outside the weekly meeting."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"Using the current meeting for debate is artificially limits the bandwidth"},{"line_number":91,"context_line":"to what can be agreed within one hour a week. Loosing this restriction should"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f436f4f_04de7610","line":88,"in_reply_to":"1f013ff3_5fdd866e","updated":"2017-08-11 11:33:30.000000000","message":"Done","commit_id":"0270a0533e043baf7242e32b3dde710e63c12af0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"ad678deb62316c73e4d31c7cf0292ccd17a61bb5","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Highlights of what the TC has got done over the last week"},{"line_number":60,"context_line":"* Gerrit patches and email threads that need attention over the coming week"},{"line_number":61,"context_line":"* List of reviews that have enough support to be merged. They will be merged"},{"line_number":62,"context_line":"  after a 24 hour period of waiting for any final objections. This can be"},{"line_number":63,"context_line":"  accelerated, as normal, using the existing house rules."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"It is likely the above will be built in a collaborative way using tools such"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9f436f4f_25cecf81","line":62,"updated":"2017-08-15 09:03:33.000000000","message":"I ended up doing ~48 hours to give everyone on the planet a good chance to voice last-minute objections.","commit_id":"0e07dff5eaef556204242489a500d0ae8c930afb"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"4bc015cf7078d885f02d0feac63921e857d22eda","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Highlights of what the TC has got done over the last week"},{"line_number":60,"context_line":"* Gerrit patches and email threads that need attention over the coming week"},{"line_number":61,"context_line":"* List of reviews that have enough support to be merged. They will be merged"},{"line_number":62,"context_line":"  after a 24 hour period of waiting for any final objections. This can be"},{"line_number":63,"context_line":"  accelerated, as normal, using the existing house rules."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"It is likely the above will be built in a collaborative way using tools such"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9f436f4f_f5acb0ef","line":62,"in_reply_to":"9f436f4f_25cecf81","updated":"2017-08-17 13:39:31.000000000","message":"Done","commit_id":"0e07dff5eaef556204242489a500d0ae8c930afb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"ad678deb62316c73e4d31c7cf0292ccd17a61bb5","unresolved":false,"context_lines":[{"line_number":77,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Schedule a set of slots so there are current members of the TC present in the"},{"line_number":80,"context_line":"#openstack-dev IRC channel and there is a good time for folks from any timezone"},{"line_number":81,"context_line":"to drop in and ask questions."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Debating"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9f436f4f_e5ea07d6","line":80,"updated":"2017-08-15 09:03:33.000000000","message":"We ended up using #openstack-tc for office hours.","commit_id":"0e07dff5eaef556204242489a500d0ae8c930afb"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"4bc015cf7078d885f02d0feac63921e857d22eda","unresolved":false,"context_lines":[{"line_number":77,"context_line":"We can replace this part of the weekly meeting with office hours."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"Schedule a set of slots so there are current members of the TC present in the"},{"line_number":80,"context_line":"#openstack-dev IRC channel and there is a good time for folks from any timezone"},{"line_number":81,"context_line":"to drop in and ask questions."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Debating"}],"source_content_type":"text/x-rst","patch_set":8,"id":"9f436f4f_75820055","line":80,"in_reply_to":"9f436f4f_e5ea07d6","updated":"2017-08-17 13:39:31.000000000","message":"Done","commit_id":"0e07dff5eaef556204242489a500d0ae8c930afb"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"ab66b84bd45d4d34bdb901efcc891255783264ac","unresolved":false,"context_lines":[{"line_number":51,"context_line":"forward. When we loose the regular meeting, we really need to keep this"},{"line_number":52,"context_line":"cadence. This should not be merely be a summary of what has happened, but"},{"line_number":53,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":54,"context_line":"existing meeting agenda that is sent 48 hours before the current meeting."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The TC chair will be responsible for sending a weekly status update to the"},{"line_number":57,"context_line":"development mailing list, which includes:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f436f4f_7f2a922c","line":54,"updated":"2017-08-21 10:57:07.000000000","message":"This was the wrong 24 - 48 change. I think you wanted line 62?","commit_id":"f528a9f0c77f02d53dc1504e5191415aa0dd9115"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"861770efd3e9e3688c024fe34571d85efd754ecc","unresolved":false,"context_lines":[{"line_number":51,"context_line":"forward. When we loose the regular meeting, we really need to keep this"},{"line_number":52,"context_line":"cadence. This should not be merely be a summary of what has happened, but"},{"line_number":53,"context_line":"rather should include a call to action and priority setting, much like the"},{"line_number":54,"context_line":"existing meeting agenda that is sent 48 hours before the current meeting."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"The TC chair will be responsible for sending a weekly status update to the"},{"line_number":57,"context_line":"development mailing list, which includes:"}],"source_content_type":"text/x-rst","patch_set":9,"id":"7f287b81_8eb92ccd","line":54,"in_reply_to":"9f436f4f_7f2a922c","updated":"2017-08-29 04:54:17.000000000","message":"arrrggggggg","commit_id":"f528a9f0c77f02d53dc1504e5191415aa0dd9115"}]}
