)]}'
{"reference/technical-committee-vision-2019.rst":[{"author":{"_account_id":113,"name":"Jonathan Bryce","email":"jbryce@jbryce.com","username":"jbryce"},"change_message_id":"ceb6691d7e1d98ad88097c84d93be4f8d502a4a6","unresolved":false,"context_lines":[{"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"It\u0027s March of 2019 and we are getting ready for the upcoming Forum at"},{"line_number":6,"context_line":"the OpenStack summit in Beijing. The OpenStack community has evolved"},{"line_number":7,"context_line":"quite a bit over the last couple of years. Where do we even begin?"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"We have finally released our 4th Constellation for OpenStack,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dfeb2761_2e4ec596","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":31},"updated":"2017-04-04 21:21:22.000000000","message":"I might pick a different location (or something clearly fictional like Mars). I know this probably seems nitpicky for a vision doc, but you\u0027d be surprised how much speculation we get around these locations--and Beijing specifically--and 2019 is close enough that I\u0027m afraid people might think this is an actual announcement.","commit_id":"c1c69bb70e0a687acb7f6e3ce427f9fb23f57255"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"b9d3270f0aab0d20066da0db0d51a30d8e6200a9","unresolved":false,"context_lines":[{"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"It\u0027s March of 2019 and we are getting ready for the upcoming Forum at"},{"line_number":6,"context_line":"the OpenStack summit in Beijing. The OpenStack community has evolved"},{"line_number":7,"context_line":"quite a bit over the last couple of years. Where do we even begin?"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"We have finally released our 4th Constellation for OpenStack,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dfeb2761_e24580b5","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":31},"in_reply_to":"dfeb2761_2e4ec596","updated":"2017-04-05 09:24:10.000000000","message":"That is a good point. We wanted to acknowledge the growing importance of China in the OpenStack universe, but I see how that could be seen as a commitment :)","commit_id":"c1c69bb70e0a687acb7f6e3ce427f9fb23f57255"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"10b931e38c19fe77599aa082328eb23e7174ddcf","unresolved":false,"context_lines":[{"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"It\u0027s March of 2019 and we are getting ready for the upcoming Forum at"},{"line_number":6,"context_line":"the OpenStack summit in Beijing. The OpenStack community has evolved"},{"line_number":7,"context_line":"quite a bit over the last couple of years. Where do we even begin?"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"We have finally released our 4th Constellation for OpenStack,"}],"source_content_type":"text/x-rst","patch_set":2,"id":"dfeb2761_a58bfd65","line":6,"range":{"start_line":6,"start_character":4,"end_line":6,"end_character":31},"in_reply_to":"dfeb2761_e24580b5","updated":"2017-04-05 11:12:54.000000000","message":"I think we cover APAC representation generally later, so I am good dropping this to stop any confusion.","commit_id":"c1c69bb70e0a687acb7f6e3ce427f9fb23f57255"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e0029333cc7795a3b4b0222a5174041b3bb0c986","unresolved":false,"context_lines":[{"line_number":7,"context_line":"over the last couple of years. Where do we even begin?"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"We have finally released our 4th Constellation for OpenStack,"},{"line_number":10,"context_line":"available at https://orion.openstack.org. This new way of looking at"},{"line_number":11,"context_line":"OpenStack reference architectures has successfully given people"},{"line_number":12,"context_line":"concrete approaches to get started with OpenStack. Users have been"},{"line_number":13,"context_line":"excited that not only do these constellations come with a dedicated"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_78eaa975","line":10,"updated":"2017-04-06 18:30:00.000000000","message":"This doesn\u0027t currently resolve, which is good, but we now probably need to make sure that we reserve the name for future use, otherwise it could eventually resolve to the wrong thing. Some where some thing is going to harvest this URL.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":9,"context_line":"We have finally released our 4th Constellation for OpenStack,"},{"line_number":10,"context_line":"available at https://orion.openstack.org. This new way of looking at"},{"line_number":11,"context_line":"OpenStack reference architectures has successfully given people"},{"line_number":12,"context_line":"concrete approaches to get started with OpenStack. Users have been"},{"line_number":13,"context_line":"excited that not only do these constellations come with a dedicated"},{"line_number":14,"context_line":"website explaining which set of projects make up this constellation,"},{"line_number":15,"context_line":"but they have dedicated documentation for each one as well. A custom"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_6c5b392e","line":12,"range":{"start_line":12,"start_character":57,"end_line":12,"end_character":66},"updated":"2017-04-05 21:17:02.000000000","message":"are","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"83e903548e112c3006144aed715fccee9094427d","unresolved":false,"context_lines":[{"line_number":13,"context_line":"excited that not only do these constellations come with a dedicated"},{"line_number":14,"context_line":"website explaining which set of projects make up this constellation,"},{"line_number":15,"context_line":"but they have dedicated documentation for each one as well. A custom"},{"line_number":16,"context_line":"install guide, an operators guide for the constellation in question, a"},{"line_number":17,"context_line":"consolidated API reference for the environment, as well as a"},{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_9f7ce91f","line":16,"range":{"start_line":16,"start_character":18,"end_line":16,"end_character":27},"updated":"2017-04-20 01:06:30.000000000","message":"operator\u0027s","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":16,"context_line":"install guide, an operators guide for the constellation in question, a"},{"line_number":17,"context_line":"consolidated API reference for the environment, as well as a"},{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"},{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_ec462950","line":19,"range":{"start_line":19,"start_character":21,"end_line":19,"end_character":45},"updated":"2017-04-05 21:17:02.000000000","message":"configured to be interoperable","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"344c1b805e095e2f0fcf4adcf6070056bd985753","unresolved":false,"context_lines":[{"line_number":16,"context_line":"install guide, an operators guide for the constellation in question, a"},{"line_number":17,"context_line":"consolidated API reference for the environment, as well as a"},{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"},{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_61821a52","line":19,"range":{"start_line":19,"start_character":21,"end_line":19,"end_character":45},"in_reply_to":"bff0334d_ec462950","updated":"2017-04-14 17:50:41.000000000","message":"or just s/fully configured interoperable/interoperable/","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":12,"context_line":"concrete approaches to get started with OpenStack. Users have been"},{"line_number":13,"context_line":"excited that not only do these constellations come with a dedicated"},{"line_number":14,"context_line":"website explaining which set of projects make up this constellation,"},{"line_number":15,"context_line":"but they have dedicated documentation for each one as well. A custom"},{"line_number":16,"context_line":"install guide, an operators guide for the constellation in question, a"},{"line_number":17,"context_line":"consolidated API reference for the environment, as well as a"},{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"},{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_ae8ed52b","line":20,"range":{"start_line":15,"start_character":60,"end_line":20,"end_character":47},"updated":"2017-04-24 07:33:53.000000000","message":"These things are all great, but I think before worrying about constellation interoperability we should be concerned with constellation validation, i.e., ensuring all components work together at the specified versions for the constellation and can be easily operated, scaled and upgraded together. It\u0027s abundantly clear from deployment survey data that OpenStack has a problem with adoption of new releases in production deployments.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"},{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_6ca9f9dd","line":21,"range":{"start_line":21,"start_character":64,"end_line":21,"end_character":65},"updated":"2017-04-05 21:17:02.000000000","message":"strike the \"a\" to make the verb and object forms match","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":11819,"name":"Chaoyi Huang","email":"joehuang@huawei.com","username":"joehuang"},"change_message_id":"c9737afb4ba28ef3d4894728865cea82a34cd6b1","unresolved":false,"context_lines":[{"line_number":18,"context_line":"validation script based on tempest that helps determine if the"},{"line_number":19,"context_line":"environment is fully configured interoperable with other similar"},{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_50d01551","line":22,"range":{"start_line":21,"start_character":25,"end_line":22,"end_character":23},"updated":"2017-04-24 00:49:48.000000000","message":"Use high level macros to install a specific constellations means abstract, on the other hand the abstraction will also limit the flexibility of services included in the constellation. What we defined in constellation may not be able to include exactly all services that the user expects.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":10787,"name":"Michal Jastrzebski (inc0)","email":"michal.jastrzebski@intel.com","username":"inc0"},"change_message_id":"d75d0f479311f5d744a8449f2a89996e6be26ed1","unresolved":false,"context_lines":[{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_ace6d6e7","line":23,"updated":"2017-04-14 23:27:19.000000000","message":"Isn\u0027t constellation a reference implementation? Do we want to create new term for that? Every deployment tool effectively have their own reference implementation (or set of thereof) and they will always differ from each other.\n\nI think definition of constellation is important here. Is it just set of services (nova, neutron)? Or also configuration files? Base operating system? Infra service configuration (like rabbitmq)? Reference implementations are hard because of amount of moving parts, where do we draw a line for constellation?\n\nDepending on answer of above, certain deployment tools might not be able to meet \"constellation\" requirements. For example one deployment tool is focused on ubuntu and another on red hat.\n\nWhat are requirements for constellation? Is it just set of packages or also upgrade procedures and things like that? Again, varies per deployment tool.\n\nBottom line, I think we need clear definition of what constellation is or could be.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_41d55de4","line":23,"in_reply_to":"5ff73747_51037643","updated":"2017-06-02 02:36:12.000000000","message":"Without designing and implementation a system in a vision document, I do wonder what this means for end-user applications and capability discovery and interoperability between clouds. Does it basically boil down to, you get a token (is keystone required btw?) which gets you the service catalog and you can see if compute (is that nova or something else?) is available in this cloud, and if it is, you expect it to be interoperable with any other cloud that has compute in the service catalog. Something else might implement the compute API but we\u0027d still expect it to be interoperable right?\n\nI\u0027ve been told that constellations aren\u0027t reference architectures or best practices, but then I have a hard time understanding what they are, or who they are helping - is it deployers? Is it users - do I as a user ask cloud X which constellations it has available and I somehow know what that means, in addition to the service catalog and what the various endpoints provide?\n\nJust random thoughts, going into details on any of this is probably counter-productive to the vision document, but it\u0027s kind of hard to know what we\u0027re envisioning without some concrete examples maybe. It also feels like we\u0027re tip-toeing around k8s without saying it, but I think this would be more clear if we used that as an example, i.e. \"You\u0027ve got your keystone + cinder + neutron + k8s constellation for multi-tenant containers with persistent storage and SDN, super!\". Someone trying to use said container for VMs can\u0027t use it, which that\u0027s fine, they find another provider that has a constellation deployed which has a compute endpoint which provides VMs. Is that the idea?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_51037643","line":23,"in_reply_to":"7ffa3b31_ace6d6e7","updated":"2017-04-24 07:33:53.000000000","message":"Agreed - I started writing a comment about how I didn\u0027t see the need for another bit of jargon which really just means reference architecture. Then I considered how worthless many reference architectures are in the industry, often just marketing toilet paper, so I can understand a desire to differentiate. But it begs the question, what exactly do we think an OpenStack reference architecture (Constellation) that is valuable to different community profiles looks like? Some ideas are found in the following paragraph, but this certainly deserves a whole new document covering finer points and dependencies.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"d6d9407c0fe3f0c264d73cd16211b6e510a741ce","unresolved":false,"context_lines":[{"line_number":20,"context_line":"constellation deployments completes the picture. Many of the"},{"line_number":21,"context_line":"deployment tools are now providing high level macros to install a"},{"line_number":22,"context_line":"specific constellations, which gives users a great way to see"},{"line_number":23,"context_line":"different configurations of OpenStack without getting lost."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f1d235d_2ad5c443","line":23,"in_reply_to":"df140735_41d55de4","updated":"2017-07-11 20:16:12.000000000","message":"I don\u0027t think that\u0027s what capability discovery and interoperability between clouds means. Or, at least, that is a necessary but not sufficient definition.\n\nIf the catalog says compute, there should be a compute service there. Yes.\n\nIf there are ways in which different installations of the compute service can reasonably be expected to behave differently because of plugins/config/whatever, those differences should be discovable. that\u0027s \"capabilities discovery\" For instance, on some clouds a server snapshot is live. In others it takes down the VM. That\u0027s a behavior difference of the same API. The user should be able to find that out.\n\nWe don\u0027t need the clouds to all be indentical. We just need the differences to be reasonably knowable.\n\nThis isn\u0027t theoretical and has nothing to do with k8s or containers. This is a problem right now - the only way our clouds are interoperable is via a shim layer that has, as one of it\u0027s features a collection of pre-discovered per-cloud differences recorded in files.\n\nObviously as we add more integration with k8s or mesos or docker or openwhisk, providing such things becomes even more important. ... but it is and has been important already.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"},{"line_number":27,"context_line":"connect the dots from constellations into which projects to"},{"line_number":28,"context_line":"contribute. The old confusion about git namespaces is a thing of the"},{"line_number":29,"context_line":"past, given how convenient and user friendly these new views"},{"line_number":30,"context_line":"are. Users have definitely reported via the user survey a higher ease"},{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_8b830b05","line":28,"range":{"start_line":27,"start_character":17,"end_line":28,"end_character":10},"updated":"2017-04-24 07:33:53.000000000","message":"is the \"to\" superfluous or is there something missing here about what the advanced users are / want to contribute to?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"02445800bdf2861e0b811bcb10ebd4c04ded2585","unresolved":false,"context_lines":[{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Constellations have become the new standard way to start exploring"},{"line_number":26,"context_line":"OpenStack. For more advanced users, the project navigator helps"},{"line_number":27,"context_line":"connect the dots from constellations into which projects to"},{"line_number":28,"context_line":"contribute. The old confusion about git namespaces is a thing of the"},{"line_number":29,"context_line":"past, given how convenient and user friendly these new views"},{"line_number":30,"context_line":"are. Users have definitely reported via the user survey a higher ease"},{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1f013ff3_7c7050dd","line":28,"range":{"start_line":27,"start_character":17,"end_line":28,"end_character":10},"in_reply_to":"5ff73747_8b830b05","updated":"2017-05-16 18:51:45.000000000","message":"I think this wants to say \"from constellations to projects, making it easier to focus their contributions\".","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_2284fc0b","line":34,"range":{"start_line":34,"start_character":23,"end_line":34,"end_character":44},"updated":"2017-04-06 14:30:33.000000000","message":"I\u0027m not sure about the \"removing\" part, it comes with a strong negative nuance to me. Does this mean they are not allowed to leave in the openstack namespace anymore and they cannot use OpenStack infra?\n\nI would phrase it in a more positive way, i.e. that we will focus our energies and resources on projects included in constellations. Which means new projects or existing projects can start the discussion about whether a new constellation would fit or not.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"72721902d7598bc2cebe3a85d1c753f49fd5dff1","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_3c51d5d9","line":34,"updated":"2017-04-06 04:07:49.000000000","message":"This is a little vague. Is there a list of components that are candidates for ejection from OpenStack due to competition with other projects? Are we going to drop Swift and adopt Ceph\u0027s object storage (RGW), for example?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e0029333cc7795a3b4b0222a5174041b3bb0c986","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_b8bef162","line":34,"in_reply_to":"bff0334d_2284fc0b","updated":"2017-04-06 18:30:00.000000000","message":"Another way to perhaps change the tone would be to change the subject from \"We\" to \"Components\" and then the implication is that the components chose themselves to have an elegant retirement rather than being kicked out.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_abe127d3","line":34,"range":{"start_line":34,"start_character":23,"end_line":34,"end_character":44},"in_reply_to":"bff0334d_2284fc0b","updated":"2017-04-24 07:33:53.000000000","message":"For what it\u0027s worth, I simply took this to mean that the composition of the constellation/s has changed since the first iterations, which is to be expected and does not necessarily have any impact on whether a project is OpenStack-official or not.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":10787,"name":"Michal Jastrzebski (inc0)","email":"michal.jastrzebski@intel.com","username":"inc0"},"change_message_id":"d75d0f479311f5d744a8449f2a89996e6be26ed1","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_4ccd125c","line":34,"in_reply_to":"bff0334d_2dcbbd72","updated":"2017-04-14 23:27:19.000000000","message":"Soo...deployment tools...","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":31,"context_line":"of initial understanding of OpenStack. This Constellation based view"},{"line_number":32,"context_line":"has helped shape the overall project map. As we have been going"},{"line_number":33,"context_line":"through and building these constellations we found several components"},{"line_number":34,"context_line":"that did not fit well. We removed components that either overlapped"},{"line_number":35,"context_line":"with work in adjacent communities or were not consistent with the"},{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_2dcbbd72","line":34,"in_reply_to":"bff0334d_b8bef162","updated":"2017-04-06 21:42:59.000000000","message":"Perhaps. Though in this case I think we are actually talking about reviewing our scope, and looking for situations where we may be giving the impression of suffering from not-invented-here syndrome as a way to foster better collaboration and more adoption of the other projects that are unique. The recent App Catalog discussion is an example of this.\n\nMaybe we should add a sentence or two explaining that background.\n\nFWIW, I don\u0027t think Swift has come up in that context.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":36,"context_line":"OpenStack mission. Other projects were refactored to clarify their"},{"line_number":37,"context_line":"scope as they were placed on the map."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"While the Constellation view has helped understand some prebuilt"},{"line_number":40,"context_line":"patterns with OpenStack that are successful, it has also demonstrated"},{"line_number":41,"context_line":"that there is more than one way to remix these components into"},{"line_number":42,"context_line":"interesting architectures. Having multiple deeply worked examples has"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_eea85d78","line":39,"range":{"start_line":39,"start_character":33,"end_line":39,"end_character":40},"updated":"2017-04-24 07:33:53.000000000","message":"helped us","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":14091,"name":"Yih Leong Sun","email":"yihleong@gmail.com","username":"yihleongsun"},"change_message_id":"870007a59248201ce9b12f34bbca77310ebf9274","unresolved":false,"context_lines":[{"line_number":39,"context_line":"While the Constellation view has helped understand some prebuilt"},{"line_number":40,"context_line":"patterns with OpenStack that are successful, it has also demonstrated"},{"line_number":41,"context_line":"that there is more than one way to remix these components into"},{"line_number":42,"context_line":"interesting architectures. Having multiple deeply worked examples has"},{"line_number":43,"context_line":"helped clarify that OpenStack components can work well in many"},{"line_number":44,"context_line":"configurations and use cases. As a result, new use cases are now"},{"line_number":45,"context_line":"easier to envision and has led to the use of individual OpenStack"},{"line_number":46,"context_line":"components in other deployments."},{"line_number":47,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_ed2cbc48","line":44,"range":{"start_line":42,"start_character":27,"end_line":44,"end_character":28},"updated":"2017-04-17 16:54:30.000000000","message":"Wondering if the effort \"workload reference architecture\" that kicked off by Enterprise WG can be useful or connected here? Three reference architectures (web app, big data, ecommerce) were produced and published at Sample Config (eg. https://www.openstack.org/software/sample-configs/#ecommerce), which illustrate the required underlying OpenStack services in order to support the users\u0027 workloads.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":42,"context_line":"interesting architectures. Having multiple deeply worked examples has"},{"line_number":43,"context_line":"helped clarify that OpenStack components can work well in many"},{"line_number":44,"context_line":"configurations and use cases. As a result, new use cases are now"},{"line_number":45,"context_line":"easier to envision and has led to the use of individual OpenStack"},{"line_number":46,"context_line":"components in other deployments."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"At the most recent OpenStack summit, three users gave presentations"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_ce192189","line":45,"range":{"start_line":45,"start_character":19,"end_line":45,"end_character":26},"updated":"2017-04-24 07:33:53.000000000","message":"and this has","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"344c1b805e095e2f0fcf4adcf6070056bd985753","unresolved":false,"context_lines":[{"line_number":43,"context_line":"helped clarify that OpenStack components can work well in many"},{"line_number":44,"context_line":"configurations and use cases. As a result, new use cases are now"},{"line_number":45,"context_line":"easier to envision and has led to the use of individual OpenStack"},{"line_number":46,"context_line":"components in other deployments."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"At the most recent OpenStack summit, three users gave presentations"},{"line_number":49,"context_line":"about using single or minimal components of OpenStack, including using"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_81cbe6a3","line":46,"updated":"2017-04-14 17:50:41.000000000","message":"w00t. :)","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":45,"context_line":"easier to envision and has led to the use of individual OpenStack"},{"line_number":46,"context_line":"components in other deployments."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"At the most recent OpenStack summit, three users gave presentations"},{"line_number":49,"context_line":"about using single or minimal components of OpenStack, including using"},{"line_number":50,"context_line":"Keystone for authenticating services not related to OpenStack at"},{"line_number":51,"context_line":"all. Everyone was really thrilled by that as the landscape of"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_e63ec789","line":48,"range":{"start_line":48,"start_character":0,"end_line":48,"end_character":35},"updated":"2017-06-02 02:36:12.000000000","message":"Is talking about a theoretical future summit, or the Pike summit in Boston? The tense is hard to follow. If it\u0027s the latter, \"most recent\" won\u0027t make sense 2 years from now if this is a thing that gets merged.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":48,"context_line":"At the most recent OpenStack summit, three users gave presentations"},{"line_number":49,"context_line":"about using single or minimal components of OpenStack, including using"},{"line_number":50,"context_line":"Keystone for authenticating services not related to OpenStack at"},{"line_number":51,"context_line":"all. Everyone was really thrilled by that as the landscape of"},{"line_number":52,"context_line":"technology does not begin and end with OpenStack. This happened"},{"line_number":53,"context_line":"because we started thinking differently about adjacent"},{"line_number":54,"context_line":"Communities. The TC identified OpenStack services that would be of"},{"line_number":55,"context_line":"value in new use cases and scenarios in conjunction with other"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_c2cd505e","line":52,"range":{"start_line":51,"start_character":5,"end_line":52,"end_character":49},"updated":"2017-04-06 14:30:33.000000000","message":"This feels a bit redundant to me, I think the message is pretty clear already in the vision.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":51,"context_line":"all. Everyone was really thrilled by that as the landscape of"},{"line_number":52,"context_line":"technology does not begin and end with OpenStack. This happened"},{"line_number":53,"context_line":"because we started thinking differently about adjacent"},{"line_number":54,"context_line":"Communities. The TC identified OpenStack services that would be of"},{"line_number":55,"context_line":"value in new use cases and scenarios in conjunction with other"},{"line_number":56,"context_line":"communities and ensured that they can be run as projects independent"},{"line_number":57,"context_line":"of others. We have done the heavy lifting that makes it easy to"},{"line_number":58,"context_line":"integrate Keystone into projects written in Go, Nodejs, or Java, so"},{"line_number":59,"context_line":"that new projects starting off can easily start with a multi-tenancy"},{"line_number":60,"context_line":"user/project story. It also makes it seamless for users to combine"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_82a8681f","line":57,"range":{"start_line":54,"start_character":13,"end_line":57,"end_character":10},"updated":"2017-04-06 14:30:33.000000000","message":"I don\u0027t think this should be exclusive of the TC. Anyone in OpenStack or even adjacent communities may identify / propose new use cases. \n\nThe role of the TC on this should be to facilitate, mediate relationships with other communities when needed and help driving the changes required to make OpenStack projects useful / usable outside of OpenStack.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":51,"context_line":"all. Everyone was really thrilled by that as the landscape of"},{"line_number":52,"context_line":"technology does not begin and end with OpenStack. This happened"},{"line_number":53,"context_line":"because we started thinking differently about adjacent"},{"line_number":54,"context_line":"Communities. The TC identified OpenStack services that would be of"},{"line_number":55,"context_line":"value in new use cases and scenarios in conjunction with other"},{"line_number":56,"context_line":"communities and ensured that they can be run as projects independent"},{"line_number":57,"context_line":"of others. We have done the heavy lifting that makes it easy to"},{"line_number":58,"context_line":"integrate Keystone into projects written in Go, Nodejs, or Java, so"},{"line_number":59,"context_line":"that new projects starting off can easily start with a multi-tenancy"},{"line_number":60,"context_line":"user/project story. It also makes it seamless for users to combine"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_ad3a2d95","line":57,"range":{"start_line":54,"start_character":13,"end_line":57,"end_character":10},"in_reply_to":"bff0334d_82a8681f","updated":"2017-04-06 21:42:59.000000000","message":"Do you read this as meaning that the TC wouldn\u0027t want anyone else to do those things? I think it\u0027s meant to show the TC being active in this area, not blocking others from being active.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":51,"context_line":"all. Everyone was really thrilled by that as the landscape of"},{"line_number":52,"context_line":"technology does not begin and end with OpenStack. This happened"},{"line_number":53,"context_line":"because we started thinking differently about adjacent"},{"line_number":54,"context_line":"Communities. The TC identified OpenStack services that would be of"},{"line_number":55,"context_line":"value in new use cases and scenarios in conjunction with other"},{"line_number":56,"context_line":"communities and ensured that they can be run as projects independent"},{"line_number":57,"context_line":"of others. We have done the heavy lifting that makes it easy to"},{"line_number":58,"context_line":"integrate Keystone into projects written in Go, Nodejs, or Java, so"},{"line_number":59,"context_line":"that new projects starting off can easily start with a multi-tenancy"},{"line_number":60,"context_line":"user/project story. It also makes it seamless for users to combine"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_b19f5ab3","line":57,"range":{"start_line":54,"start_character":13,"end_line":57,"end_character":10},"in_reply_to":"bff0334d_ad3a2d95","updated":"2017-04-24 07:33:53.000000000","message":"I agree with Andrea that this comes across as unclear. Maybe the envisioned role of the TC in these matters should be explicitly spelt out in a separate paragraph.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":59,"context_line":"that new projects starting off can easily start with a multi-tenancy"},{"line_number":60,"context_line":"user/project story. It also makes it seamless for users to combine"},{"line_number":61,"context_line":"services from OpenStack, and all these other communities in their"},{"line_number":62,"context_line":"composite applications. The users love not having to hard code"},{"line_number":63,"context_line":"credentials from different services throughout their environment."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"We have learned a lot from adjacent communities in the process, and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_513b76d0","line":62,"range":{"start_line":62,"start_character":24,"end_line":62,"end_character":33},"updated":"2017-04-24 07:33:53.000000000","message":"Just \"Users\" is fine","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"83e903548e112c3006144aed715fccee9094427d","unresolved":false,"context_lines":[{"line_number":68,"context_line":"communities with overlapping interests including consumers of"},{"line_number":69,"context_line":"OpenStack as well as components which play a critical role in"},{"line_number":70,"context_line":"deployment of a OpenStack Solution. In addition, we have also been"},{"line_number":71,"context_line":"able been able to share some of our hard learned lessons and success"},{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_9fcaa94b","line":71,"range":{"start_line":71,"start_character":5,"end_line":71,"end_character":14},"updated":"2017-04-20 01:06:30.000000000","message":"Duplicate, remove these words.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":68,"context_line":"communities with overlapping interests including consumers of"},{"line_number":69,"context_line":"OpenStack as well as components which play a critical role in"},{"line_number":70,"context_line":"deployment of a OpenStack Solution. In addition, we have also been"},{"line_number":71,"context_line":"able been able to share some of our hard learned lessons and success"},{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_26d5df1c","line":71,"range":{"start_line":71,"start_character":36,"end_line":71,"end_character":56},"updated":"2017-06-02 02:36:12.000000000","message":"Let\u0027s not tell k8s about the pci whitelist config option, let them learn about it on their own...","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":69,"context_line":"OpenStack as well as components which play a critical role in"},{"line_number":70,"context_line":"deployment of a OpenStack Solution. In addition, we have also been"},{"line_number":71,"context_line":"able been able to share some of our hard learned lessons and success"},{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"},{"line_number":75,"context_line":"every community has their own culture and needs as they grow. The 5-10"},{"line_number":76,"context_line":"groups we have formed close partnerships with are continuously asked"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_223bdceb","line":73,"range":{"start_line":72,"start_character":53,"end_line":73,"end_character":7},"updated":"2017-04-06 14:30:33.000000000","message":"I would argue that every community is different, so it may be hard to have a repeatable system. But we can have a lot of good practices and lessons learnt.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"},{"line_number":75,"context_line":"every community has their own culture and needs as they grow. The 5-10"},{"line_number":76,"context_line":"groups we have formed close partnerships with are continuously asked"},{"line_number":77,"context_line":"for feedback to ensure their satisfaction with our partnership. Our"},{"line_number":78,"context_line":"partnerships focus on this quality of partnership, rather than"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_2c91b153","line":75,"range":{"start_line":75,"start_character":66,"end_line":75,"end_character":70},"updated":"2017-04-05 21:17:02.000000000","message":"In the future, we will know exactly how many groups we have partnered with. We should pick a single number here.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"ff04cd958049bcceec1837553249d12362bd9fcc","unresolved":false,"context_lines":[{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"},{"line_number":75,"context_line":"every community has their own culture and needs as they grow. The 5-10"},{"line_number":76,"context_line":"groups we have formed close partnerships with are continuously asked"},{"line_number":77,"context_line":"for feedback to ensure their satisfaction with our partnership. Our"},{"line_number":78,"context_line":"partnerships focus on this quality of partnership, rather than"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_c3ab12d4","line":75,"range":{"start_line":75,"start_character":66,"end_line":75,"end_character":70},"in_reply_to":"bff0334d_2c91b153","updated":"2017-04-06 14:29:13.000000000","message":"The recommendation from the Zingermanns folks was to use ranges for things like this. Because it is talking about the future, and we\u0027re painting the range of success. Without it is 4 bad when you said 6?\n\nIt does sit in a balance space, but this is about painting a picture with the error bars in there I think.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"72721902d7598bc2cebe3a85d1c753f49fd5dff1","unresolved":false,"context_lines":[{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"},{"line_number":75,"context_line":"every community has their own culture and needs as they grow. The 5-10"},{"line_number":76,"context_line":"groups we have formed close partnerships with are continuously asked"},{"line_number":77,"context_line":"for feedback to ensure their satisfaction with our partnership. Our"},{"line_number":78,"context_line":"partnerships focus on this quality of partnership, rather than"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_3c6af57f","line":75,"range":{"start_line":75,"start_character":66,"end_line":75,"end_character":70},"in_reply_to":"bff0334d_2c91b153","updated":"2017-04-06 04:07:49.000000000","message":"This is why IMHO the \"future blog post\" format is a mistake overall: it leaves no room for ambiguity.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":72,"context_line":"stories to help them on their journey. We now have a very repeatable"},{"line_number":73,"context_line":"system for engaging with new communities, sharing some of our past"},{"line_number":74,"context_line":"insights, and helping where we can, while being respectful of how"},{"line_number":75,"context_line":"every community has their own culture and needs as they grow. The 5-10"},{"line_number":76,"context_line":"groups we have formed close partnerships with are continuously asked"},{"line_number":77,"context_line":"for feedback to ensure their satisfaction with our partnership. Our"},{"line_number":78,"context_line":"partnerships focus on this quality of partnership, rather than"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_cd2e9142","line":75,"range":{"start_line":75,"start_character":66,"end_line":75,"end_character":70},"in_reply_to":"bff0334d_c3ab12d4","updated":"2017-04-06 21:42:59.000000000","message":"@sdague - OK. It jumped out at me as different from the other numbers we\u0027ve given elsewhere, but it\u0027s not a big deal.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":80,"context_line":"resources can be focused on success. It is a regular occurrence that"},{"line_number":81,"context_line":"TC members are or have been committers within these other communities."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"The outreach included both technical and non-technical aspects. Since"},{"line_number":84,"context_line":"the OpenStack ecosystem is mature and has excellent systems and"},{"line_number":85,"context_line":"processes in place for dealing with governance, vulnerabilities,"},{"line_number":86,"context_line":"continuous integration infrastructure, leadership development, etc.,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_3d2d3d95","line":83,"range":{"start_line":83,"start_character":13,"end_line":83,"end_character":21},"updated":"2017-04-06 14:30:33.000000000","message":"(still) includes?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":87,"context_line":"the TC shares the best practices with other newly forming communities"},{"line_number":88,"context_line":"to help bootstrap them. On the technical side, the TC worked closely"},{"line_number":89,"context_line":"with leadership teams of the other communities to find opportunities"},{"line_number":90,"context_line":"to share code as services, libraries, reduce scope and complexity of"},{"line_number":91,"context_line":"some projects to remove duplicated effort. This has empowered"},{"line_number":92,"context_line":"contributors to easily move between OpenStack and other communities"},{"line_number":93,"context_line":"and develop synergies to benefit everyone. The TC worked with the"},{"line_number":94,"context_line":"OpenStack Infrastructure, Quality Assurance, and similar teams to make"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_2c9f7151","line":91,"range":{"start_line":90,"start_character":0,"end_line":91,"end_character":42},"updated":"2017-04-05 21:17:02.000000000","message":"The phrasing of this section is not clear to me. Does this rewrite reflect the intent?\n\n  to share code as services and libraries, in order to reduce the scope and\n  complexity of some projects by removing duplicated effort.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"ff04cd958049bcceec1837553249d12362bd9fcc","unresolved":false,"context_lines":[{"line_number":87,"context_line":"the TC shares the best practices with other newly forming communities"},{"line_number":88,"context_line":"to help bootstrap them. On the technical side, the TC worked closely"},{"line_number":89,"context_line":"with leadership teams of the other communities to find opportunities"},{"line_number":90,"context_line":"to share code as services, libraries, reduce scope and complexity of"},{"line_number":91,"context_line":"some projects to remove duplicated effort. This has empowered"},{"line_number":92,"context_line":"contributors to easily move between OpenStack and other communities"},{"line_number":93,"context_line":"and develop synergies to benefit everyone. The TC worked with the"},{"line_number":94,"context_line":"OpenStack Infrastructure, Quality Assurance, and similar teams to make"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_43eee222","line":91,"range":{"start_line":90,"start_character":0,"end_line":91,"end_character":42},"in_reply_to":"bff0334d_2c9f7151","updated":"2017-04-06 14:29:13.000000000","message":"Agree, probably helps to get out of generalities and come up with a good hypothetical example.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":91,"context_line":"some projects to remove duplicated effort. This has empowered"},{"line_number":92,"context_line":"contributors to easily move between OpenStack and other communities"},{"line_number":93,"context_line":"and develop synergies to benefit everyone. The TC worked with the"},{"line_number":94,"context_line":"OpenStack Infrastructure, Quality Assurance, and similar teams to make"},{"line_number":95,"context_line":"sure there is a common understanding of how to deal with new language"},{"line_number":96,"context_line":"ecosystems, new projects that will need continuous integration,"},{"line_number":97,"context_line":"mirroring needs, and works to expand available resources as well as"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_fd74759b","line":94,"range":{"start_line":94,"start_character":43,"end_line":94,"end_character":62},"updated":"2017-04-06 14:30:33.000000000","message":"and other horizontal teams? I think we should mention documentation and i18n as well?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":91,"context_line":"some projects to remove duplicated effort. This has empowered"},{"line_number":92,"context_line":"contributors to easily move between OpenStack and other communities"},{"line_number":93,"context_line":"and develop synergies to benefit everyone. The TC worked with the"},{"line_number":94,"context_line":"OpenStack Infrastructure, Quality Assurance, and similar teams to make"},{"line_number":95,"context_line":"sure there is a common understanding of how to deal with new language"},{"line_number":96,"context_line":"ecosystems, new projects that will need continuous integration,"},{"line_number":97,"context_line":"mirroring needs, and works to expand available resources as well as"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_c6ad039c","line":94,"range":{"start_line":94,"start_character":43,"end_line":94,"end_character":62},"in_reply_to":"bff0334d_fd74759b","updated":"2017-06-02 02:36:12.000000000","message":"Docs team is dissolving a bit as of the Boston summit, right? Similar with i18n - they have pulled back on translations in recent releases I thought.\n\nI guess that\u0027s what \"similar teams\" means though - horizontal teams.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":98,"context_line":"ensure that there is no undue impact on limited resources."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"Reaching out to so many other communities, and sharing lessons between"},{"line_number":101,"context_line":"us, really confirmed for all of us how critical diversity is to the"},{"line_number":102,"context_line":"future of OpenStack. There are so many good ideas out there, and so"},{"line_number":103,"context_line":"many people that are motivated to help move the conversation"},{"line_number":104,"context_line":"forward. The diverse community also drives a lot of empathy in our"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_514a5627","line":101,"range":{"start_line":101,"start_character":4,"end_line":101,"end_character":10},"updated":"2017-04-24 07:33:53.000000000","message":"superfluous","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"30204b76196936e375b724e41436cad5d86a313e","unresolved":false,"context_lines":[{"line_number":107,"context_line":"with OpenStack when we have so many different perspectives in our"},{"line_number":108,"context_line":"community. Diversity, on many axes, is now a key value in OpenStack"},{"line_number":109,"context_line":"itself, and we have seen our contributor base get measurably more"},{"line_number":110,"context_line":"diverse in each of the last three releases."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"More than 50% of the contributors to the most recent OpenStack release"},{"line_number":113,"context_line":"identified strongly as an OpenStack user or operator. This has helped"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ff0f0b1f_50e3cdd9","line":110,"updated":"2017-05-23 11:36:45.000000000","message":"Do we currently measure this multi-axis diversity in any meaningful way, beyond say the self-declared gender of summit attendees?\n\nIf we\u0027re aiming to be increasingly diverse along many axes, obviously we have to (a) all agree on what axes of diversity actually matter[1], and (b) actively measure in an ongoing and accurate way.\n\n[1] IIRC the diversity WG made some kind of abortive attempt back in the day to survey contributors on IMO irrelevant diversity factors such as educational attainment, religious affiliation, etc.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"9ba03dedd1af2cd10871e16ee04d23a4bbb2aa19","unresolved":false,"context_lines":[{"line_number":107,"context_line":"with OpenStack when we have so many different perspectives in our"},{"line_number":108,"context_line":"community. Diversity, on many axes, is now a key value in OpenStack"},{"line_number":109,"context_line":"itself, and we have seen our contributor base get measurably more"},{"line_number":110,"context_line":"diverse in each of the last three releases."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"More than 50% of the contributors to the most recent OpenStack release"},{"line_number":113,"context_line":"identified strongly as an OpenStack user or operator. This has helped"}],"source_content_type":"text/x-rst","patch_set":3,"id":"ff0f0b1f_b04c69c8","line":110,"in_reply_to":"ff0f0b1f_50e3cdd9","updated":"2017-05-23 11:43:23.000000000","message":"a) good question\n\nb) happy to see you are keeping your asking questions medal polished\n\nc) I agree that any goals that get set need to be measurable, but in the context of this vision, since it is a squishy vision thing, I don\u0027t think we need to worry too much about the details of the goal, rather that there is a goal at all. It sets a pole by which to guide our compasses. Once we have that we can define the specifics of the goals that are revealed by the process, somewhere else.\n\nI completely agree that the if diversity is going to be measured, the choice of axes is a political one and care should be taken.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":107,"context_line":"with OpenStack when we have so many different perspectives in our"},{"line_number":108,"context_line":"community. Diversity, on many axes, is now a key value in OpenStack"},{"line_number":109,"context_line":"itself, and we have seen our contributor base get measurably more"},{"line_number":110,"context_line":"diverse in each of the last three releases."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"More than 50% of the contributors to the most recent OpenStack release"},{"line_number":113,"context_line":"identified strongly as an OpenStack user or operator. This has helped"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_a6cd6f67","line":110,"in_reply_to":"ff0f0b1f_b04c69c8","updated":"2017-06-02 02:36:12.000000000","message":"Harking back to Eoghan\u0027s comment which isn\u0027t inline, I guess this is the vision part, but diversity has really gone down I\u0027d say in recent releases because of vendors/large companies with large contributor bases have pulled out. Others are stepping up, but there is a thinning out in areas, e.g. core maintainers/reviewers. On the other hand, China is building up lately but mostly around newer projects that aren\u0027t part of what has historically been considered part of the base/core/key projects (you know, what\u0027s tested in the integrated-gate jobs). Maybe the vision here is if we\u0027re cross-pollinating with other communities so much, people from those communities will be showing up in OpenStack and working here, while we\u0027re working in their community. Anyway, it\u0027s a bit fuzzy.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":109,"context_line":"itself, and we have seen our contributor base get measurably more"},{"line_number":110,"context_line":"diverse in each of the last three releases."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"More than 50% of the contributors to the most recent OpenStack release"},{"line_number":113,"context_line":"identified strongly as an OpenStack user or operator. This has helped"},{"line_number":114,"context_line":"grow different patterns and culture of contributions, that are more"},{"line_number":115,"context_line":"focused on near term needs of the operators in the field. It has also"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_46d573e4","line":112,"range":{"start_line":112,"start_character":41,"end_line":112,"end_character":52},"updated":"2017-06-02 02:36:12.000000000","message":"Again, is this vision / future speak or from April 2017? Because in 2 years this is going to be confusing.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"2877f9ff94fdaeb3903cff25ef0a1a9f93ed289d","unresolved":false,"context_lines":[{"line_number":113,"context_line":"identified strongly as an OpenStack user or operator. This has helped"},{"line_number":114,"context_line":"grow different patterns and culture of contributions, that are more"},{"line_number":115,"context_line":"focused on near term needs of the operators in the field. It has also"},{"line_number":116,"context_line":"brought much more sympathy to the needs of part time contributors who"},{"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"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_0fb50eee","line":117,"range":{"start_line":116,"start_character":43,"end_line":117,"end_character":49},"updated":"2017-04-11 17:26:34.000000000","message":"Flow wise whole paragraph, and in particular this sentence, feels disconnected from the section about retaining contributors over the longer term down near line 187.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"2877f9ff94fdaeb3903cff25ef0a1a9f93ed289d","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":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_8f1b5e71","line":120,"range":{"start_line":120,"start_character":27,"end_line":120,"end_character":39},"updated":"2017-04-11 17:26:34.000000000","message":"I think we should add more about the why here, something like:\n\nWe have worked hard to \"lower the bar to entry\" with efforts such at the new bot that...","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"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":3,"id":"df140735_464333b0","line":122,"range":{"start_line":121,"start_character":60,"end_line":122,"end_character":49},"updated":"2017-06-02 02:36:12.000000000","message":"Is the new bot future-speak again? Or is this something that\u0027s actually happening?\n\nBTW, more patches, yay! What happens when the core reviewer teams are flooded with low quality patch sets by people that can\u0027t work on them, but there isn\u0027t a matched growth in people actually doing reviews? Anywho, not a very helpful point/question, but just came to mind.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":597,"name":"Pete Zaitcev","email":"zaitcev@kotori.zaitcev.us","username":"zaitcev"},"change_message_id":"72721902d7598bc2cebe3a85d1c753f49fd5dff1","unresolved":false,"context_lines":[{"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"},{"line_number":126,"context_line":"assisting with many of the TC initiated efforts. The TC now looks much"},{"line_number":127,"context_line":"more like our contributor base. The TC membership now includes several"},{"line_number":128,"context_line":"women and representatives from APAC and European countries. These"},{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_5cc93976","line":128,"range":{"start_line":127,"start_character":31,"end_line":128,"end_character":59},"updated":"2017-04-06 04:07:49.000000000","message":"And this helps OpenStack to fulfill the needs of its users how exactly","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":125,"context_line":"from the operator community and user committee both on the TC and"},{"line_number":126,"context_line":"assisting with many of the TC initiated efforts. The TC now looks much"},{"line_number":127,"context_line":"more like our contributor base. The TC membership now includes several"},{"line_number":128,"context_line":"women and representatives from APAC and European countries. These"},{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_0ddb591b","line":128,"in_reply_to":"bff0334d_386d4132","updated":"2017-04-06 21:42:59.000000000","message":"ttx +1","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"dae4f0d1283a99d1b836a4e6beb51185d9637ace","unresolved":false,"context_lines":[{"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"},{"line_number":126,"context_line":"assisting with many of the TC initiated efforts. The TC now looks much"},{"line_number":127,"context_line":"more like our contributor base. The TC membership now includes several"},{"line_number":128,"context_line":"women and representatives from APAC and European countries. These"},{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_e95b942b","line":128,"range":{"start_line":127,"start_character":31,"end_line":128,"end_character":59},"in_reply_to":"bff0334d_5cc93976","updated":"2017-04-06 16:14:15.000000000","message":"As an elected governance body, the TC should ideally reflect the diversity of its constituency. We have ~11% of women in our community representing ~9% of the activity, and yet there are currently 0% of women on the Technical Committee. To be representative, we should have between one and two women in the TC. Same for APAC which represent a fair share of contributors and yet we still have no member from Asian countries on the TC. I think it\u0027s good to paint a desirable future where this is no longer the case.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e0029333cc7795a3b4b0222a5174041b3bb0c986","unresolved":false,"context_lines":[{"line_number":125,"context_line":"from the operator community and user committee both on the TC and"},{"line_number":126,"context_line":"assisting with many of the TC initiated efforts. The TC now looks much"},{"line_number":127,"context_line":"more like our contributor base. The TC membership now includes several"},{"line_number":128,"context_line":"women and representatives from APAC and European countries. These"},{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_386d4132","line":128,"in_reply_to":"bff0334d_e95b942b","updated":"2017-04-06 18:30:00.000000000","message":"ttx++","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"},{"line_number":132,"context_line":"by the Drupal Ladder program, has aimed to bring more traditional"},{"line_number":133,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":134,"context_line":"don’t feel overwhelmed getting their first patch in."},{"line_number":135,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_6c1219b4","line":132,"range":{"start_line":132,"start_character":30,"end_line":132,"end_character":33},"updated":"2017-04-05 21:17:02.000000000","message":"which has","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":10787,"name":"Michal Jastrzebski (inc0)","email":"michal.jastrzebski@intel.com","username":"inc0"},"change_message_id":"d75d0f479311f5d744a8449f2a89996e6be26ed1","unresolved":false,"context_lines":[{"line_number":129,"context_line":"changes did not happen overnight, or by accident. We now have very"},{"line_number":130,"context_line":"heavy emphasis on mentoring in the community, with multiple different"},{"line_number":131,"context_line":"efforts underway. There is the new OpenStack Ladder program, inspired"},{"line_number":132,"context_line":"by the Drupal Ladder program, has aimed to bring more traditional"},{"line_number":133,"context_line":"users and operators into the contributor space and ensure that they"},{"line_number":134,"context_line":"don’t feel overwhelmed getting their first patch in."},{"line_number":135,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_cc1802d5","line":132,"range":{"start_line":132,"start_character":30,"end_line":132,"end_character":33},"in_reply_to":"bff0334d_6c1219b4","updated":"2017-04-14 23:27:19.000000000","message":"We had this discussion in Kolla. Various mentoring of reviewers and contributors seems to be common request. I\u0027d be happy to help with this and volunteer Kolla to be mentoring guinea pig:) (sorry guys!)","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":12356,"name":"Vladyslav Drok","email":"vdrok@mirantis.com","username":"vdrok"},"change_message_id":"3e9c4b7a35bc81cee0dfdb98270dd59d163dae5a","unresolved":false,"context_lines":[{"line_number":146,"context_line":""},{"line_number":147,"context_line":"With more community members having successes in inter-project work, it"},{"line_number":148,"context_line":"is now commonplace for popup teams to form around these kind of"},{"line_number":149,"context_line":"efforts, often lead by members of the mentoring program. They will"},{"line_number":150,"context_line":"engage with key members from different project teams within OpenStack,"},{"line_number":151,"context_line":"or projects in other communities, or both. Members of the user and and"},{"line_number":152,"context_line":"operators communities are often a part of these popup teams. People"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_4cf99d7e","line":149,"range":{"start_line":149,"start_character":15,"end_line":149,"end_character":19},"updated":"2017-04-14 10:46:38.000000000","message":"led","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4b725368ae46dedc16009717d8693ee44c9016a1","unresolved":false,"context_lines":[{"line_number":148,"context_line":"is now commonplace for popup teams to form around these kind of"},{"line_number":149,"context_line":"efforts, often lead by members of the mentoring program. They will"},{"line_number":150,"context_line":"engage with key members from different project teams within OpenStack,"},{"line_number":151,"context_line":"or projects in other communities, or both. Members of the user and and"},{"line_number":152,"context_line":"operators communities are often a part of these popup teams. People"},{"line_number":153,"context_line":"find it exciting and energizing to dive into such crucial work early"},{"line_number":154,"context_line":"in their OpenStack engagement. Success breeds success, and as the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_6c87b9d9","line":151,"range":{"start_line":151,"start_character":63,"end_line":151,"end_character":70},"updated":"2017-04-05 21:17:02.000000000","message":"repeated \"and\"","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"83e903548e112c3006144aed715fccee9094427d","unresolved":false,"context_lines":[{"line_number":156,"context_line":"from member companies to keep accelerating this work."},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"Much of the work done by these inter-project teams has come from the"},{"line_number":159,"context_line":"improved feedback loop between user, operators and developers. Indeed"},{"line_number":160,"context_line":"this feedback, coupled with the increase in diversity of"},{"line_number":161,"context_line":"contributions, makes it hard to distinguish between users, operators"},{"line_number":162,"context_line":"and developers. One visible success story has been the TC curated Top"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_3f083590","line":159,"range":{"start_line":159,"start_character":31,"end_line":159,"end_character":35},"updated":"2017-04-20 01:06:30.000000000","message":"users","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":14091,"name":"Yih Leong Sun","email":"yihleong@gmail.com","username":"yihleongsun"},"change_message_id":"870007a59248201ce9b12f34bbca77310ebf9274","unresolved":false,"context_lines":[{"line_number":155,"context_line":"velocity of this work has increased we have seen a renewed investment"},{"line_number":156,"context_line":"from member companies to keep accelerating this work."},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"Much of the work done by these inter-project teams has come from the"},{"line_number":159,"context_line":"improved feedback loop between user, operators and developers. Indeed"},{"line_number":160,"context_line":"this feedback, coupled with the increase in diversity of"},{"line_number":161,"context_line":"contributions, makes it hard to distinguish between users, operators"},{"line_number":162,"context_line":"and developers. One visible success story has been the TC curated Top"},{"line_number":163,"context_line":"10 hit list. It has brought renewed focus on some of the hard problems"},{"line_number":164,"context_line":"we need to go after in the near term. It is now commonplace that key"},{"line_number":165,"context_line":"features that identified in the Top 10 hit list get completed in a"},{"line_number":166,"context_line":"single cycle. Not only does it easily express some of the most"},{"line_number":167,"context_line":"important work that we need to get done as a community, but the"},{"line_number":168,"context_line":"process of creating it made us all understand OpenStack that much"},{"line_number":169,"context_line":"more."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"When TC members and other community leaders started taking deep dives"},{"line_number":172,"context_line":"into projects they normally don’t contribute to, there was a ton of"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_8dabf81b","line":169,"range":{"start_line":158,"start_character":0,"end_line":169,"end_character":5},"updated":"2017-04-17 16:54:30.000000000","message":"I often hear from operators/users that it is a challenge to express their needs/requirements and seems to me that the existing feedback loop is kind of disconnected. \n\nCan the Development Proposal workflow (from Product WG) be utilized here so that OpenStack can have a well-defined channel for users/operators to express their needs, and then TC + UC can curate the list based on the Development Proposal and prioritize the top 10 list that should be completed in a single cycle, supported by all related-projects as a common community goal. \n\nhttps://wiki.openstack.org/wiki/ProductTeam/Development_Proposals\n\nhttps://github.com/openstack/openstack-user-stories/tree/master/development-proposals/proposed","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":172,"context_line":"into projects they normally don’t contribute to, there was a ton of"},{"line_number":173,"context_line":"enlightenment. Old prejudices took a backseat as we walked a mile in"},{"line_number":174,"context_line":"each other’s shoes. This new understanding is part of why hierarchical"},{"line_number":175,"context_line":"quotas are now implemented and working in many services, and are now"},{"line_number":176,"context_line":"getting tested in the field. We expect most of the OpenStack projects,"},{"line_number":177,"context_line":"as well as a number of non OpenStack projects in adjacent communities"},{"line_number":178,"context_line":"to have this supported over the next year."}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_f1a84278","line":175,"range":{"start_line":175,"start_character":42,"end_line":175,"end_character":55},"updated":"2017-04-24 07:33:53.000000000","message":"can we say, \"including all core services\"?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":172,"context_line":"into projects they normally don’t contribute to, there was a ton of"},{"line_number":173,"context_line":"enlightenment. Old prejudices took a backseat as we walked a mile in"},{"line_number":174,"context_line":"each other’s shoes. This new understanding is part of why hierarchical"},{"line_number":175,"context_line":"quotas are now implemented and working in many services, and are now"},{"line_number":176,"context_line":"getting tested in the field. We expect most of the OpenStack projects,"},{"line_number":177,"context_line":"as well as a number of non OpenStack projects in adjacent communities"},{"line_number":178,"context_line":"to have this supported over the next year."}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_e106b11c","line":175,"range":{"start_line":175,"start_character":42,"end_line":175,"end_character":55},"in_reply_to":"5ff73747_f1a84278","updated":"2017-06-02 02:36:12.000000000","message":"There are no \"core\" services, remember? You can be OpenStack without Nova so...","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b007e361ec20509d076e03532252304085e5905d","unresolved":false,"context_lines":[{"line_number":174,"context_line":"each other’s shoes. This new understanding is part of why hierarchical"},{"line_number":175,"context_line":"quotas are now implemented and working in many services, and are now"},{"line_number":176,"context_line":"getting tested in the field. We expect most of the OpenStack projects,"},{"line_number":177,"context_line":"as well as a number of non OpenStack projects in adjacent communities"},{"line_number":178,"context_line":"to have this supported over the next year."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"Over the past year, the TC has proudly celebrated the good work done"}],"source_content_type":"text/x-rst","patch_set":3,"id":"df140735_41179d46","line":177,"range":{"start_line":177,"start_character":23,"end_line":177,"end_character":27},"updated":"2017-06-02 02:36:12.000000000","message":"non-","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":1921,"name":"Andrea Frittoli","email":"andrea.frittoli@gmail.com","username":"andrea-frittoli"},"change_message_id":"6f35fd9ebbfa096920f2f66c1b8950cf301ed126","unresolved":false,"context_lines":[{"line_number":181,"context_line":"by those who stepped up to lead and work on crucial work in the"},{"line_number":182,"context_line":"community. It has been particularly satisfying to see the breadth of"},{"line_number":183,"context_line":"talent now involved in the technical leadership of the OpenStack"},{"line_number":184,"context_line":"community. More companies are investing longer term contributors to"},{"line_number":185,"context_line":"the OpenStack project, because they can see a clearer path for value"},{"line_number":186,"context_line":"delivery to their products and services delivered using OpenStack. We"},{"line_number":187,"context_line":"now have between 50 and 100 contributors with significant commits to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_a3bfeef9","line":184,"range":{"start_line":184,"start_character":11,"end_line":184,"end_character":64},"updated":"2017-04-06 14:30:33.000000000","message":"This looks fine, but I think on top of retaining contributors, developing new ones is also very important. The vision includes programs to attract, mentor and help new contributors. We should also help existing contributors grow within the OpenStack community and become the future leaders (we do, but I think we should do it more and it should be in the vision).","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":181,"context_line":"by those who stepped up to lead and work on crucial work in the"},{"line_number":182,"context_line":"community. It has been particularly satisfying to see the breadth of"},{"line_number":183,"context_line":"talent now involved in the technical leadership of the OpenStack"},{"line_number":184,"context_line":"community. More companies are investing longer term contributors to"},{"line_number":185,"context_line":"the OpenStack project, because they can see a clearer path for value"},{"line_number":186,"context_line":"delivery to their products and services delivered using OpenStack. We"},{"line_number":187,"context_line":"now have between 50 and 100 contributors with significant commits to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_2d6f3d93","line":184,"range":{"start_line":184,"start_character":11,"end_line":184,"end_character":64},"in_reply_to":"bff0334d_a3bfeef9","updated":"2017-04-06 21:42:59.000000000","message":"I agree. I think lines 136-156 cover this to some degree?","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":23186,"name":"Felipe Monteiro","email":"felipe.carneiro.monteiro@gmail.com","username":"felipe.monteiro"},"change_message_id":"83e903548e112c3006144aed715fccee9094427d","unresolved":false,"context_lines":[{"line_number":185,"context_line":"the OpenStack project, because they can see a clearer path for value"},{"line_number":186,"context_line":"delivery to their products and services delivered using OpenStack. We"},{"line_number":187,"context_line":"now have between 50 and 100 contributors with significant commits to"},{"line_number":188,"context_line":"two or more Projects every release cycle. Importantly, we have"},{"line_number":189,"context_line":"retained 75% of those contributors over the last three"},{"line_number":190,"context_line":"releases. Moreover, 50% of these contributors are part time, yet still"},{"line_number":191,"context_line":"able to get actively involved in critical inter-project work. And we"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7ffa3b31_7ff11d95","line":188,"range":{"start_line":188,"start_character":42,"end_line":188,"end_character":53},"updated":"2017-04-20 01:06:30.000000000","message":"\"More importantly\" sounds better.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":7546,"name":"Blair Bethwaite","email":"blair.bethwaite@gmail.com","username":"blairo"},"change_message_id":"0b4aa72574235e7a3c65a86b0bc96102cfca5f07","unresolved":false,"context_lines":[{"line_number":185,"context_line":"the OpenStack project, because they can see a clearer path for value"},{"line_number":186,"context_line":"delivery to their products and services delivered using OpenStack. We"},{"line_number":187,"context_line":"now have between 50 and 100 contributors with significant commits to"},{"line_number":188,"context_line":"two or more Projects every release cycle. Importantly, we have"},{"line_number":189,"context_line":"retained 75% of those contributors over the last three"},{"line_number":190,"context_line":"releases. Moreover, 50% of these contributors are part time, yet still"},{"line_number":191,"context_line":"able to get actively involved in critical inter-project work. And we"}],"source_content_type":"text/x-rst","patch_set":3,"id":"5ff73747_f1c16230","line":188,"range":{"start_line":188,"start_character":12,"end_line":188,"end_character":20},"updated":"2017-04-24 07:33:53.000000000","message":"projects (lower case for consistency)","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"e0029333cc7795a3b4b0222a5174041b3bb0c986","unresolved":false,"context_lines":[{"line_number":190,"context_line":"releases. Moreover, 50% of these contributors are part time, yet still"},{"line_number":191,"context_line":"able to get actively involved in critical inter-project work. And we"},{"line_number":192,"context_line":"regularly see those folks that leave our community become leaders and"},{"line_number":193,"context_line":"mentors in other Open Source projects in the ecosystem. We have grown"},{"line_number":194,"context_line":"not just OpenStack, but Open Source as a whole, and that is something"},{"line_number":195,"context_line":"we can all be proud of."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_f880f98d","line":193,"updated":"2017-04-06 18:30:00.000000000","message":"If there is one bit of modern English I could choose to see die in a fire, it is this particular use of \"grown\", but meh.","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1b6a82a81b8c183de5dcb3c3e5d4df6debb2a05d","unresolved":false,"context_lines":[{"line_number":190,"context_line":"releases. Moreover, 50% of these contributors are part time, yet still"},{"line_number":191,"context_line":"able to get actively involved in critical inter-project work. And we"},{"line_number":192,"context_line":"regularly see those folks that leave our community become leaders and"},{"line_number":193,"context_line":"mentors in other Open Source projects in the ecosystem. We have grown"},{"line_number":194,"context_line":"not just OpenStack, but Open Source as a whole, and that is something"},{"line_number":195,"context_line":"we can all be proud of."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bff0334d_ad08edd8","line":193,"in_reply_to":"bff0334d_f880f98d","updated":"2017-04-06 21:42:59.000000000","message":"+1","commit_id":"c32b3761a55ab58bdfe8f6730d63c29ea71c86d0"}]}