)]}'
{"reference/technical-committee-vision-2019.rst":[{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"4646c563d54ccad681c5f88be8175df7ce556e48","unresolved":false,"context_lines":[{"line_number":16,"context_line":"* `Guiding Principles \u003chttps://governance.openstack.org/tc/reference/principles.html\u003e`_"},{"line_number":17,"context_line":"* \u003cadd ref\u003e Some info on zingerman\u0027s process"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":".. TODO(cdent): Key points or TOC as noted on the etherpad."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"----"},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7f231b9d_11ec3f8d","line":19,"updated":"2017-06-15 15:10:04.000000000","message":"I am tempted to try sub-headings to aid people\u0027s (unavoidable) skim reading, rather enabling the skim readers to get more out of the document.","commit_id":"ca69f808ec0eafd473f2b301ab9e2b9ab76f215b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"7a4ee5557103245eb8f0789cc725408ae46a7306","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_98be12fd","line":21,"range":{"start_line":21,"start_character":4,"end_line":21,"end_character":10},"updated":"2017-06-16 13:22:29.000000000","message":"\"Spring\" doesn\u0027t mean the same thing in the southern hemisphere, which is why we originally settled for \"March of 2019\"","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d690bce9e294a218670067760e3a4447e12ef424","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_e8e990e2","line":21,"in_reply_to":"7f231b9d_4b02e20b","updated":"2017-06-19 08:54:46.000000000","message":"Ah! Too subtle for me. I\u0027ll leave the choice to you then.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"49eb65729089e8ddf5cf98abccc14d251c9718cb","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_4b02e20b","line":21,"in_reply_to":"7f231b9d_98be12fd","updated":"2017-06-16 13:44:06.000000000","message":"I pretty much did that on purpose as a bit of ambiguous (being fully aware of how the seasons work in the hemispheres) artistic flair: Spring as in new beginnings, sets a tone.\n\nBut if we think it is going to draw out people saying what you\u0027ve just said, I can correct it.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"7a4ee5557103245eb8f0789cc725408ae46a7306","unresolved":false,"context_lines":[{"line_number":52,"context_line":"clarified that OpenStack components can work well in many"},{"line_number":53,"context_line":"configurations and use cases. New use cases are easier to envision"},{"line_number":54,"context_line":"leading to individual OpenStack components being used in other"},{"line_number":55,"context_line":"deployments."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Working with Adjacent Communities"},{"line_number":58,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_981a9214","line":55,"updated":"2017-06-16 13:22:29.000000000","message":"I kinda liked the \"demonstrated that there is more than one way to remix these components into interesting architectures\", I fear that it\u0027s lost on this rewrite...","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d690bce9e294a218670067760e3a4447e12ef424","unresolved":false,"context_lines":[{"line_number":52,"context_line":"clarified that OpenStack components can work well in many"},{"line_number":53,"context_line":"configurations and use cases. New use cases are easier to envision"},{"line_number":54,"context_line":"leading to individual OpenStack components being used in other"},{"line_number":55,"context_line":"deployments."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Working with Adjacent Communities"},{"line_number":58,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_a8bdd8b7","line":55,"in_reply_to":"7f231b9d_8b491a61","updated":"2017-06-19 08:54:46.000000000","message":"I agree on the need to cut, I just feel like the creative aspect of the \"remix\" concept is no longer there at all (making it feel like you\u0027re supposed to follow one of several pre-defined configurations). Maybe replace \"can work well in many configurations and use cases\" by \"can be remixed in many configurations and use cases\" ?","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"49eb65729089e8ddf5cf98abccc14d251c9718cb","unresolved":false,"context_lines":[{"line_number":52,"context_line":"clarified that OpenStack components can work well in many"},{"line_number":53,"context_line":"configurations and use cases. New use cases are easier to envision"},{"line_number":54,"context_line":"leading to individual OpenStack components being used in other"},{"line_number":55,"context_line":"deployments."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Working with Adjacent Communities"},{"line_number":58,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_8b491a61","line":55,"in_reply_to":"7f231b9d_981a9214","updated":"2017-06-16 13:44:06.000000000","message":"I cut a lot of that stuff because otherwise this section was far too long. In terms of creating a vision the earlier verbosity was appropriate, but in terms of something people read it was way too much on this one relatively small detail.\n\nBut I may be in the minority on that thought, so happy to revise if there\u0027s a clear preference.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"f4f3ca4e4b93e4d46e732d520fb238afed0ffa20","unresolved":false,"context_lines":[{"line_number":52,"context_line":"clarified that OpenStack components can work well in many"},{"line_number":53,"context_line":"configurations and use cases. New use cases are easier to envision"},{"line_number":54,"context_line":"leading to individual OpenStack components being used in other"},{"line_number":55,"context_line":"deployments."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"Working with Adjacent Communities"},{"line_number":58,"context_line":"---------------------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_a38cd635","line":55,"in_reply_to":"7f231b9d_a8bdd8b7","updated":"2017-06-19 11:01:59.000000000","message":"good idea, done.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"7a4ee5557103245eb8f0789cc725408ae46a7306","unresolved":false,"context_lines":[{"line_number":75,"context_line":""},{"line_number":76,"context_line":".. TODO(cdent): We need an example going the other direction. A tech"},{"line_number":77,"context_line":"                from an adjacent community that OpenStack has chosen"},{"line_number":78,"context_line":"                to adopt (perhaps even replacing something)."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"We have learned a lot from adjacent communities and have made some"},{"line_number":81,"context_line":"substantial changes to the way we do things. The TC is proactive in"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_38a7febf","line":78,"updated":"2017-06-16 13:22:29.000000000","message":"etcd?","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"49eb65729089e8ddf5cf98abccc14d251c9718cb","unresolved":false,"context_lines":[{"line_number":75,"context_line":""},{"line_number":76,"context_line":".. TODO(cdent): We need an example going the other direction. A tech"},{"line_number":77,"context_line":"                from an adjacent community that OpenStack has chosen"},{"line_number":78,"context_line":"                to adopt (perhaps even replacing something)."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"We have learned a lot from adjacent communities and have made some"},{"line_number":81,"context_line":"substantial changes to the way we do things. The TC is proactive in"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_2b8a0669","line":78,"in_reply_to":"7f231b9d_38a7febf","updated":"2017-06-16 13:44:06.000000000","message":"I thought about that, but didn\u0027t choose it for two reasons:\n\n* etcd is already approved so it feels like cheating\n\n* etcd is a basic tool being integrated into openstack (like a database or a message queue) not a service being provided by openstack (like identity and auth mgt)\n\nSo I was thinking more along the lines of (just for the sake of example) something from an external community that provides an image service, which replaces glance.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"7a4ee5557103245eb8f0789cc725408ae46a7306","unresolved":false,"context_lines":[{"line_number":212,"context_line":"----"},{"line_number":213,"context_line":""},{"line_number":214,"context_line":".. TODO(cdent): Consider an epilogue that states some present day"},{"line_number":215,"context_line":"                next steps?"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7f231b9d_b8a0ae91","line":215,"updated":"2017-06-16 13:22:29.000000000","message":"I\u0027m fine with no epilogue. I like this ending.","commit_id":"36439f8b2e96e980f979cbc1e2574a37e65adcdd"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"bcd850d4d585a3c196183166b7be7b8bd7545053","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7f231b9d_dedf87d4","line":21,"range":{"start_line":21,"start_character":4,"end_line":21,"end_character":10},"updated":"2017-06-20 10:24:02.000000000","message":"You know I see arguments both ways like you and ttx have discussed.","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"bc0cbbfbd9fc530eff859b25a13d865618e74a56","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f201791_493ab1e7","line":21,"in_reply_to":"7f231b9d_cb3a2497","updated":"2017-06-20 15:34:33.000000000","message":"I like the descriptive \u0027spring\u0027 that cdent mentioned in an earlier comment, but tying it to a Summit makes it specific and that\u0027s where I think folks will interpret it like ttx did initially.  I think \u0027first\u0027 works, even if it loses the fresh flowery goodness.","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"fec13a59040ea5ec561896731986062068d36472","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The Spring OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7f231b9d_cb3a2497","line":21,"in_reply_to":"7f231b9d_dedf87d4","updated":"2017-06-20 10:26:42.000000000","message":"Another way to get the same flair of starting or newness would be \"first\"","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"bc0cbbfbd9fc530eff859b25a13d865618e74a56","unresolved":false,"context_lines":[{"line_number":75,"context_line":""},{"line_number":76,"context_line":".. TODO(cdent): We need an example going the other direction. A tech"},{"line_number":77,"context_line":"                from an adjacent community that OpenStack has chosen"},{"line_number":78,"context_line":"                to adopt (perhaps even replacing something)."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"We have learned a lot from adjacent communities and have made some"},{"line_number":81,"context_line":"substantial changes to the way we do things. The TC is proactive in"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f201791_646474ba","line":78,"updated":"2017-06-20 15:34:33.000000000","message":"We have a strong tendency to wrap up adopted tech and make it look like us (I am not counting oslo abstractions here).  I don\u0027t think making a new thing by wrapping an OpenStack-style REST API around an existing thing is what we want here.  The first thing that comes to my mind is Ceph, but it straddles the line between backend (not this) and service with the object API.  Arguably the only way another service will fit here natively is when it supports Keystone auth without wrapping it.","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"bcd850d4d585a3c196183166b7be7b8bd7545053","unresolved":false,"context_lines":[{"line_number":110,"context_line":"continuous integration, and works to expand available resources as"},{"line_number":111,"context_line":"well as ensure that there is no undue impact on limited resources."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Including a Wider Community"},{"line_number":114,"context_line":"---------------------------"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Reaching out to other communities has confirmed how critical diversity"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7f231b9d_fea92324","line":113,"updated":"2017-06-20 10:24:02.000000000","message":"I am not 100% on this title. But I am struggling to think of something better. Maybe \"Wider Participation\"?","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"bc0cbbfbd9fc530eff859b25a13d865618e74a56","unresolved":false,"context_lines":[{"line_number":110,"context_line":"continuous integration, and works to expand available resources as"},{"line_number":111,"context_line":"well as ensure that there is no undue impact on limited resources."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Including a Wider Community"},{"line_number":114,"context_line":"---------------------------"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Reaching out to other communities has confirmed how critical diversity"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f201791_8478b0f8","line":113,"in_reply_to":"7f231b9d_2b6cf89a","updated":"2017-06-20 15:34:33.000000000","message":"Expanding Our Community\n\nWidening the Community\n\nEmbracing Community Diversity","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"fec13a59040ea5ec561896731986062068d36472","unresolved":false,"context_lines":[{"line_number":110,"context_line":"continuous integration, and works to expand available resources as"},{"line_number":111,"context_line":"well as ensure that there is no undue impact on limited resources."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Including a Wider Community"},{"line_number":114,"context_line":"---------------------------"},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Reaching out to other communities has confirmed how critical diversity"}],"source_content_type":"text/x-rst","patch_set":4,"id":"7f231b9d_2b6cf89a","line":113,"in_reply_to":"7f231b9d_fea92324","updated":"2017-06-20 10:26:42.000000000","message":"Me neither. I struggled on this one, but wanted to have parallelism with the other headers, so a \"Foo-ing...\" of some kind.","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":970,"name":"Dean Troyer","email":"dtroyer@gmail.com","username":"dtroyer"},"change_message_id":"bc0cbbfbd9fc530eff859b25a13d865618e74a56","unresolved":false,"context_lines":[{"line_number":146,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":147,"context_line":"don’t feel overwhelmed."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Growing new Leaders"},{"line_number":150,"context_line":"-------------------"},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"For members of the community that are already engaged, we have built"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5f201791_448298ca","line":149,"updated":"2017-06-20 15:34:33.000000000","message":"New?","commit_id":"21a37551a6eb8301d20c71b056d3c73003310e7e"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"03545bbae053f54e44e0d12fa88f97bf8a034611","unresolved":false,"context_lines":[{"line_number":117,"context_line":"can\u0027t complete a perfect patch to get it accepted. A small organic"},{"line_number":118,"context_line":"team of shepherds have been taking the drive-by contributions and"},{"line_number":119,"context_line":"working them into the system, either by taking over the patches or by"},{"line_number":120,"context_line":"applying follow-up changes. The new bot that converts github pull"},{"line_number":121,"context_line":"requests to gerrit change-sets, instead of discarding them, imported"},{"line_number":122,"context_line":"several patches in each of the last three months."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"The TC itself has changed in the process. We now regularly have people"},{"line_number":125,"context_line":"from the operator community and user committee both on the TC and"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_abb82610","side":"PARENT","line":122,"range":{"start_line":120,"start_character":28,"end_line":122,"end_character":48},"updated":"2017-06-28 17:36:40.000000000","message":"I honestly don\u0027t like dropping this. It was one of the more concrete ways of explaining what it\u0027s like to make our software processes match with other communities.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"03545bbae053f54e44e0d12fa88f97bf8a034611","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"* `OpenStack Technical Committee Mission \u003chttps://governance.openstack.org/tc/reference/charter.html#mission\u003e`_"},{"line_number":16,"context_line":"* `Guiding Principles \u003chttps://governance.openstack.org/tc/reference/principles.html\u003e`_"},{"line_number":17,"context_line":"* \u003cadd ref\u003e Some info on zingerman\u0027s process"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_6bee8e22","line":17,"updated":"2017-06-28 17:36:40.000000000","message":"https://www.zingtrain.com/content/why-and-how-visioning-works for the reference, and honestly this should be the first link I think.","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"04f8e7d57ab0aa6048825b7059682b50fc913c7c","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"* `OpenStack Technical Committee Mission \u003chttps://governance.openstack.org/tc/reference/charter.html#mission\u003e`_"},{"line_number":16,"context_line":"* `Guiding Principles \u003chttps://governance.openstack.org/tc/reference/principles.html\u003e`_"},{"line_number":17,"context_line":"* \u003cadd ref\u003e Some info on zingerman\u0027s process"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_57e74aad","line":17,"in_reply_to":"3f1d235d_2846da50","updated":"2017-07-05 11:53:53.000000000","message":"Done","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b45fdce1ddc84e287f22fc44eb8b6b9da91f32ac","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"* `OpenStack Technical Committee Mission \u003chttps://governance.openstack.org/tc/reference/charter.html#mission\u003e`_"},{"line_number":16,"context_line":"* `Guiding Principles \u003chttps://governance.openstack.org/tc/reference/principles.html\u003e`_"},{"line_number":17,"context_line":"* \u003cadd ref\u003e Some info on zingerman\u0027s process"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_2846da50","line":17,"in_reply_to":"5f201791_6bee8e22","updated":"2017-07-04 08:40:43.000000000","message":"I like the idea of having this link being the first. We\u0027ll set the context under which this vision was written.","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"03545bbae053f54e44e0d12fa88f97bf8a034611","unresolved":false,"context_lines":[{"line_number":144,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"},{"line_number":145,"context_line":"by the Drupal Ladder program, which aims to bring more"},{"line_number":146,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":147,"context_line":"don’t feel overwhelmed."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Growing New Leaders"},{"line_number":150,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"5f201791_8b620aad","line":147,"range":{"start_line":147,"start_character":11,"end_line":147,"end_character":22},"updated":"2017-06-28 17:36:40.000000000","message":"doing what? I actually think dropping the specifics makes this less clear.","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"04f8e7d57ab0aa6048825b7059682b50fc913c7c","unresolved":false,"context_lines":[{"line_number":144,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"},{"line_number":145,"context_line":"by the Drupal Ladder program, which aims to bring more"},{"line_number":146,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":147,"context_line":"don’t feel overwhelmed."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Growing New Leaders"},{"line_number":150,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_b770de09","line":147,"in_reply_to":"3f1d235d_4850f65d","updated":"2017-07-05 11:53:53.000000000","message":"Presumably the goal is to have people not be overwhelmed by anything to do with openstack, not just getting their first patch in?\n\nI\u0027ll make Flavio\u0027s suggested change, and we\u0027ll see how it goes.","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b45fdce1ddc84e287f22fc44eb8b6b9da91f32ac","unresolved":false,"context_lines":[{"line_number":144,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"},{"line_number":145,"context_line":"by the Drupal Ladder program, which aims to bring more"},{"line_number":146,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":147,"context_line":"don’t feel overwhelmed."},{"line_number":148,"context_line":""},{"line_number":149,"context_line":"Growing New Leaders"},{"line_number":150,"context_line":"-------------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_4850f65d","line":147,"range":{"start_line":147,"start_character":11,"end_line":147,"end_character":22},"in_reply_to":"5f201791_8b620aad","updated":"2017-07-04 08:40:43.000000000","message":"Without getting too much into the specifics, we could end these paragraph with this (or something like this): \"overwhelmed by our contribution processes\"","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":6159,"name":"Flavio Percoco Premoli","display_name":"flaper87","email":"flavio.percoco@flyrlabs.com","username":"flaper87"},"change_message_id":"b45fdce1ddc84e287f22fc44eb8b6b9da91f32ac","unresolved":false,"context_lines":[{"line_number":173,"context_line":"Much of the work done by these inter-project teams has come from the"},{"line_number":174,"context_line":"improved feedback loop between users, operators and developers. Indeed"},{"line_number":175,"context_line":"this feedback, coupled with the increase in diversity of"},{"line_number":176,"context_line":"contributions, makes it hard to distinguish between users, operators"},{"line_number":177,"context_line":"and developers. One visible success story has been the TC curated Top"},{"line_number":178,"context_line":"10 hit list. It has brought renewed focus on some of the hard problems"},{"line_number":179,"context_line":"we need to address in the near term. It is now commonplace that key"},{"line_number":180,"context_line":"features that were identified in the Top 10 hit list get completed in a"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_e32b637f","line":177,"range":{"start_line":176,"start_character":15,"end_line":177,"end_character":15},"updated":"2017-07-04 08:40:43.000000000","message":"I understand where this is coming from but, asserting that these changes will make it hard to distinguish between these three groups is not necessarily good.\n\nI agree we want to provide a seamless experience to these groups but it\u0027s extremely important for us to know who our users, our operators and our developers are. \n\nAdmittedly, I might be taking this sentence literally when it\u0027s supposed to be figurative.\n\nDo you think we can rephrase this in a way that its literal interpretation doesn\u0027t mean it\u0027ll be hard for us to tell these groups apart when needed?\n\nHere\u0027s an idea:\n\n\"Indeed this feedback, coupled with the increase in diversity of contributions, makes the interactions - as well as the contributions - between users, operators and developers seamless\"","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"04f8e7d57ab0aa6048825b7059682b50fc913c7c","unresolved":false,"context_lines":[{"line_number":174,"context_line":"improved feedback loop between users, operators and developers. Indeed"},{"line_number":175,"context_line":"this feedback, coupled with the increase in diversity of"},{"line_number":176,"context_line":"contributions, makes it hard to distinguish between users, operators"},{"line_number":177,"context_line":"and developers. One visible success story has been the TC curated Top"},{"line_number":178,"context_line":"10 hit list. It has brought renewed focus on some of the hard problems"},{"line_number":179,"context_line":"we need to address in the near term. It is now commonplace that key"},{"line_number":180,"context_line":"features that were identified in the Top 10 hit list get completed in a"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3f1d235d_17fb1279","line":177,"in_reply_to":"3f1d235d_e32b637f","updated":"2017-07-05 11:53:53.000000000","message":"That\u0027s definitely better (to me). I\u0027ll make an adjustment along those lines.","commit_id":"0131199d3ef9cfb9bedd7802e084df1c87fa71e4"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"9b3f4333a46058b830e8f18692db8f8bbed1cf81","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The first OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f1d235d_974a26aa","line":21,"range":{"start_line":21,"start_character":35,"end_line":21,"end_character":43},"updated":"2017-07-07 14:05:52.000000000","message":"is a great","commit_id":"f3ba38f79143cbd86db7a7d01cf1cf594e0d99b2"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"4930453e78e004e34c4ef3eed8ea6c397125b0a2","unresolved":false,"context_lines":[{"line_number":18,"context_line":""},{"line_number":19,"context_line":"----"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The first OpenStack Summit of 2019 is great time to review how the"},{"line_number":22,"context_line":"OpenStack community has evolved over the last few years. We\u0027ve made"},{"line_number":23,"context_line":"progress on a new way to understand reference architectures, on using"},{"line_number":24,"context_line":"individual components of OpenStack on their own, on working with other"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f1d235d_537a3088","line":21,"in_reply_to":"3f1d235d_974a26aa","updated":"2017-07-10 13:50:17.000000000","message":"I\u0027ll do that in a follow up to not disrupt the voting.","commit_id":"f3ba38f79143cbd86db7a7d01cf1cf594e0d99b2"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"9b3f4333a46058b830e8f18692db8f8bbed1cf81","unresolved":false,"context_lines":[{"line_number":75,"context_line":""},{"line_number":76,"context_line":".. TODO(cdent): We need an example going the other direction. A tech"},{"line_number":77,"context_line":"                from an adjacent community that OpenStack has chosen"},{"line_number":78,"context_line":"                to adopt (perhaps even replacing something)."},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"We have learned a lot from adjacent communities and have made some"},{"line_number":81,"context_line":"substantial changes to the way we do things. The TC is proactive in"}],"source_content_type":"text/x-rst","patch_set":6,"id":"3f1d235d_77930a02","line":78,"updated":"2017-07-07 14:05:52.000000000","message":"etcd?","commit_id":"f3ba38f79143cbd86db7a7d01cf1cf594e0d99b2"}]}