)]}'
{"resolutions/20141202-project-structure-reform-spec.rst":[{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"8aac23bc500969d5257b29d9763e08b3da69d154","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"OpenStack project structure reform specification"},{"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Problem description"},{"line_number":6,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_8b5b1b53","line":3,"updated":"2014-12-02 20:17:21.000000000","message":"Jenkins is upset with the title expanding beyond the \u003d\u003d\u003d\u003d\u0027s.","commit_id":"69d704834ffa3dcdd762ae7f727bc379795699f4"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":24,"context_line":"components they feel are useful. New users, however, are presented with a"},{"line_number":25,"context_line":"complex and scary \"integrated release\" as the thing they have to deploy and"},{"line_number":26,"context_line":"manage: this inhibits adoption, and this inhibits the adoption of a slice of"},{"line_number":27,"context_line":"OpenStack that could serve their need."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Second, the integrated release being the only and ultimate goal for projects,"},{"line_number":30,"context_line":"there is no lack of candidates, and the list is always-growing. Why reject"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_209c705d","line":27,"updated":"2014-12-05 23:44:44.000000000","message":"well said.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":35,"context_line":"release components, etc. The resources working on those integrated horizontal"},{"line_number":36,"context_line":"tasks are very finite, and complexity grows non-linearly as we add more"},{"line_number":37,"context_line":"projects. So there is outside pressure to add more projects, and internal"},{"line_number":38,"context_line":"pressure to resist further additions."},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"Third, the binary nature of the integrated release results in projects"},{"line_number":41,"context_line":"outside the integrated release failing to get the recognition they deserve."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_a0a780a6","line":38,"updated":"2014-12-05 23:44:44.000000000","message":"Or to re-define what it means to be part of the \u0027integrated gate.\u0027 it could be a \u0027not so tightly integrated release\u0027 instead.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":43,"context_line":"development resources. Alternative solutions can\u0027t emerge in the shadow of"},{"line_number":44,"context_line":"the blessed approach. Becoming part of the integrated release, which was"},{"line_number":45,"context_line":"originally designed to be a technical decision, quickly became a"},{"line_number":46,"context_line":"life-or-death question for new projects, and a political/community minefield."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"In summary, the \"integrated release\" is paradoxically too large to be"},{"line_number":49,"context_line":"effectively integrated, installed or upgraded in one piece, and too small to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_80f9a450","line":46,"updated":"2014-12-05 23:44:44.000000000","message":"Agreed, but this may be simplifying the issue.\n\n* Incubated projects do get some attention\n* Yes non official projects in say stackforge that compete with an official project are second or third class citizens. But so are ecosystem projects that compete with official openstack projects. Say a competitor to Savanna that deploys Hadoop on any cloud that provides Compute and volume storage.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":48,"context_line":"In summary, the \"integrated release\" is paradoxically too large to be"},{"line_number":49,"context_line":"effectively integrated, installed or upgraded in one piece, and too small to"},{"line_number":50,"context_line":"express the diversity of our rich ecosystem. Its slow-moving, binary nature"},{"line_number":51,"context_line":"is too granular to represent the complexity of what our community produces,"},{"line_number":52,"context_line":"and therefore we need to reform it."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The challenge is to fix those three issues at the same time. Embrace the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_c092ccfb","line":51,"updated":"2014-12-05 23:44:44.000000000","message":"yes","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":51,"context_line":"is too granular to represent the complexity of what our community produces,"},{"line_number":52,"context_line":"and therefore we need to reform it."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The challenge is to fix those three issues at the same time. Embrace the"},{"line_number":55,"context_line":"diversity of our ecosystem while making sure that what we produce is easily"},{"line_number":56,"context_line":"understandable and consumable by our downstream users (distributions,"},{"line_number":57,"context_line":"deployers, end users), all that without putting more stress on the already"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_8090c4ee","line":54,"updated":"2014-12-05 23:44:44.000000000","message":"I see another issue, although this overlaps with the 3 you list.\n\nMainlining the horizontal teams even with the current scale of OpenStack. For example it is very hard for a single person to be able to have a deep understanding and ability to help debug all of the OpenStack today.\n\nI am also not convinced we must fix all 3 issues at the same time. It may be easier to fix one and then the other two. Smaller incremental changes are usually easier to implement then a single large one.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5418680594740c669e94ebc8542078a88d140f37","unresolved":false,"context_lines":[{"line_number":51,"context_line":"is too granular to represent the complexity of what our community produces,"},{"line_number":52,"context_line":"and therefore we need to reform it."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"The challenge is to fix those three issues at the same time. Embrace the"},{"line_number":55,"context_line":"diversity of our ecosystem while making sure that what we produce is easily"},{"line_number":56,"context_line":"understandable and consumable by our downstream users (distributions,"},{"line_number":57,"context_line":"deployers, end users), all that without putting more stress on the already"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_641672a9","line":54,"in_reply_to":"5a890539_8090c4ee","updated":"2014-12-09 11:02:12.000000000","message":"Agreed -- what I actually meant is \"find a solution that allows to address those 3 issues\", not necessarily in one step. Will fix.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"3141d874fcc7fd333ea083c6d52e7be20454558b","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Provide a precise taxonomy to help navigating the ecosystem"},{"line_number":66,"context_line":"-----------------------------------------------------------"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"We can\u0027t add any more \"OpenStack\" projects without dramatically revisiting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_a5ff20aa","line":65,"updated":"2014-12-02 22:42:52.000000000","message":"I don\u0027t think \u0027taxonomy\u0027 is the word you were looking for here. Taxonomies are inherently hierarchical - they\u0027re not the solution, they\u0027re actually the problem. The suggestion here IIUC (assuming this is based on Jay\u0027s proposal) is to explicitly move away from that towards a more free-form tagging system.\n\n(All the weird stuff we used to have with Official projects, Integrated projects, Library projects, Catch-all projects and the like was an example of a taxonomy.)","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Provide a precise taxonomy to help navigating the ecosystem"},{"line_number":66,"context_line":"-----------------------------------------------------------"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"We can\u0027t add any more \"OpenStack\" projects without dramatically revisiting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_416fb992","line":65,"in_reply_to":"3a961159_1ec7e046","updated":"2014-12-08 22:33:20.000000000","message":"Although a taxonomy *can* include hierarchical components (as in a biological context), it doesn\u0027t have to do so and the word taxonomy doesn\u0027t necessarily imply that it would. In this context, saying \"taxonomy\" is much more focused on creating the \"controlled vocabulary\" that will make the tags useful.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Provide a precise taxonomy to help navigating the ecosystem"},{"line_number":66,"context_line":"-----------------------------------------------------------"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"We can\u0027t add any more \"OpenStack\" projects without dramatically revisiting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_cc194225","line":65,"in_reply_to":"5a890539_a5ff20aa","updated":"2014-12-05 09:56:45.000000000","message":"Would \"classification framework\" work better ?","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"2408dec18f1a4fc63ac5fec9a930ba7505512f67","unresolved":false,"context_lines":[{"line_number":62,"context_line":"Proposed change"},{"line_number":63,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Provide a precise taxonomy to help navigating the ecosystem"},{"line_number":66,"context_line":"-----------------------------------------------------------"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"We can\u0027t add any more \"OpenStack\" projects without dramatically revisiting"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_1ec7e046","line":65,"in_reply_to":"5a890539_cc194225","updated":"2014-12-08 13:43:43.000000000","message":"Yeah I think that\u0027s better, although \"classification\" still implies mutually exclusive categories to my ear. Maybe \"characterisation framework\"?","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":68,"context_line":"We can\u0027t add any more \"OpenStack\" projects without dramatically revisiting"},{"line_number":69,"context_line":"the information we provide. It is the duty of the Technical Committee to"},{"line_number":70,"context_line":"help downstream consumers of OpenStack understand what each project means"},{"line_number":71,"context_line":"to them, and provide them with accurate statuses for those projects."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Currently the landscape is very simple: you\u0027re in the integrated release, or"},{"line_number":74,"context_line":"you\u0027re not. But since there was only one category (or badge of honor), it"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_80552420","line":71,"updated":"2014-12-05 23:44:44.000000000","message":"yes","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a7121c4f0c97ea7e093c9f53e9e315c9181f8456","unresolved":false,"context_lines":[{"line_number":91,"context_line":"Directors questions about which set of projects may make sense for a given"},{"line_number":92,"context_line":"trademark license program. It will allow our downstream users to know which"},{"line_number":93,"context_line":"projects are mature, which are security-supported, which are used in more"},{"line_number":94,"context_line":"than one public cloud, or which are really massively scalable."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"Recognize all our community is a part of OpenStack"},{"line_number":97,"context_line":"--------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_2e7f9518","line":94,"updated":"2014-12-02 20:39:22.000000000","message":"This cuts to the heart of the essential tension I\u0027ve seen in most articulations of this proposal: the TC seems to be expressing discomfort with its existing badge-granting powers, while lining up new (more fine-grained) badge-granting powers.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":91,"context_line":"Directors questions about which set of projects may make sense for a given"},{"line_number":92,"context_line":"trademark license program. It will allow our downstream users to know which"},{"line_number":93,"context_line":"projects are mature, which are security-supported, which are used in more"},{"line_number":94,"context_line":"than one public cloud, or which are really massively scalable."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"Recognize all our community is a part of OpenStack"},{"line_number":97,"context_line":"--------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_ac9f9650","line":94,"in_reply_to":"5a890539_2e7f9518","updated":"2014-12-05 09:56:45.000000000","message":"I won\u0027t talk for all TC members, but my impression is that the TC is more uncomfortable with its life-or-death power on OpenStack community projects, which is linked to the binary nature of the \"integrated release\" badge. It\u0027s fine with defining how to precisely describe our ecosystem (and taking its part in describing). I would even argue it\u0027s part of its role.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":91,"context_line":"Directors questions about which set of projects may make sense for a given"},{"line_number":92,"context_line":"trademark license program. It will allow our downstream users to know which"},{"line_number":93,"context_line":"projects are mature, which are security-supported, which are used in more"},{"line_number":94,"context_line":"than one public cloud, or which are really massively scalable."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"Recognize all our community is a part of OpenStack"},{"line_number":97,"context_line":"--------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_a1121db2","line":94,"in_reply_to":"5a890539_ac9f9650","updated":"2014-12-08 22:33:20.000000000","message":"I somewhat agree with Thierry. I\u0027m not uncomfortable with the \"powers\". I\u0027m uncomfortable with the way we have (or have not) been fulfilling the responsibilities associated with those powers.\n\nAs I have pointed out in some of the face-to-face discussions, the OpenStack foundation bylaws give the TC the responsibility for making decisions about which projects are part of or not part of OpenStack:\n\n\"4.13(b) The Technical Committee shall have the authority to determine the modules for addition, combination, split or deletion from the OpenStack Project except for modules of the Core OpenStack Project (as defined in Section 4.1(b) above) which shall be managed as provided below.\"\n\nsee http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/\n\nWe are the only body of representatives fully elected directly by the individuals who contribute to the project. If we abdicate this responsibility, there is no other group made up of members similarly close to that constituency to take up the duty.\n\nWe cannot simply stop evaluating projects, and the way we are evaluating them is not working. So, we must change how we do that evaluation.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development discussions on the openstack-dev mailing-list and use"},{"line_number":104,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":105,"context_line":"the OpenStack community as well, and we propose that those should be hosted"},{"line_number":106,"context_line":"under the \"openstack\" GitHub organization, as long as:"},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"* They align with the OpenStack Mission: the project should help further the"},{"line_number":109,"context_line":"  OpenStack mission, by providing a cloud infrastructure service, or"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_0b079519","line":106,"updated":"2014-12-05 23:44:44.000000000","message":"So the OpenStack code base (GitHub organization) consists of things that follow the \u0027OpenStack way\u0027 and support the \u0027OpenStack mission\u0027? Makes sense, but I don\u0027t think that is equivalent to recognizing all our community is part of \u0027OpenStack.\u0027 That doesn\u0027t recognize an OpenStack operator as part of \u0027OpenStack\u0027 etc.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5418680594740c669e94ebc8542078a88d140f37","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development discussions on the openstack-dev mailing-list and use"},{"line_number":104,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":105,"context_line":"the OpenStack community as well, and we propose that those should be hosted"},{"line_number":106,"context_line":"under the \"openstack\" GitHub organization, as long as:"},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"* They align with the OpenStack Mission: the project should help further the"},{"line_number":109,"context_line":"  OpenStack mission, by providing a cloud infrastructure service, or"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_4496d6f1","line":106,"in_reply_to":"3a961159_e1d185ce","updated":"2014-12-09 11:02:12.000000000","message":"Agreed, will fix to more clearly say \"openstack projects\" and only mention the github org as a consequence.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":103,"context_line":"development discussions on the openstack-dev mailing-list and use"},{"line_number":104,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":105,"context_line":"the OpenStack community as well, and we propose that those should be hosted"},{"line_number":106,"context_line":"under the \"openstack\" GitHub organization, as long as:"},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"* They align with the OpenStack Mission: the project should help further the"},{"line_number":109,"context_line":"  OpenStack mission, by providing a cloud infrastructure service, or"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_e1d185ce","line":106,"in_reply_to":"5a890539_0b079519","updated":"2014-12-08 22:33:20.000000000","message":"Yes, I think the more important thing here is to say that we would recognize the projects as \"OpenStack projects\" rather than say where we would host them. The hosting is a \"benefit\" (or side-effect), and I don\u0027t think we want to say that \"openstack-dev\" or \"openstack-infra\" are less a part of OpenStack than the \"openstack\" is. We might want \"openstack-ops\" and \"openstack-something-else\" as a way of organizing projects, for example. The issue with using the \"stackforge\" namespace now is that it is so different that projects there are clearly not part of OpenStack, to the extent that the rules for projects in that namespace are different.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":107,"context_line":""},{"line_number":108,"context_line":"* They align with the OpenStack Mission: the project should help further the"},{"line_number":109,"context_line":"  OpenStack mission, by providing a cloud infrastructure service, or"},{"line_number":110,"context_line":"  directly building on an existing one"},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"* They follow the OpenStack way: open source (licensing), open community"},{"line_number":113,"context_line":"  (leadership chosen by the contributors to the project), open development"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_2a30a19d","line":110,"updated":"2014-12-09 19:59:50.000000000","message":"\"directly building on an existing one\" is not precise enough. \"or directly building on an existing OpenStack infrastructure service\" may be what you mean here but I\u0027m not sure.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":112,"context_line":"* They follow the OpenStack way: open source (licensing), open community"},{"line_number":113,"context_line":"  (leadership chosen by the contributors to the project), open development"},{"line_number":114,"context_line":"  (public reviews on Gerrit, core reviewers, gate), and open design"},{"line_number":115,"context_line":"  (direction discussed at Design Summit and on public MLs)"},{"line_number":116,"context_line":""},{"line_number":117,"context_line":"* They ensure basic interoperability (API services should support at least"},{"line_number":118,"context_line":"  Keystone)"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_aae2d1fe","line":115,"updated":"2014-12-09 19:59:50.000000000","message":"Requiring discussion at a Design Summit may not be viable if we add dozens of projects at once, so perhaps only require discussion in public forums.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"3141d874fcc7fd333ea083c6d52e7be20454558b","unresolved":false,"context_lines":[{"line_number":118,"context_line":"  Keystone)"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"* They submit to the OpenStack Technical Committee oversight"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_45b2fce5","line":121,"updated":"2014-12-02 22:42:52.000000000","message":"It\u0027s implicit from the non-inclusion in this list of any scope overlap limits and the language below about \u0027similar\u0027 projects that this means competing projects will be allowed too, but I think it\u0027s worth making it very explicit for the benefit of those who haven\u0027t been following closely.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":118,"context_line":"  Keystone)"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"* They submit to the OpenStack Technical Committee oversight"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_41d899ef","line":121,"in_reply_to":"5a890539_45b2fce5","updated":"2014-12-08 22:33:20.000000000","message":"+1, however, I think we do want *some* limits on that. Creating a new puppet module to deploy nova because you want to use _ in your variables instead of camelCase (or the reverse, as the case may be) is not something we want to encourage.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":118,"context_line":"  Keystone)"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"* They submit to the OpenStack Technical Committee oversight"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_ecc0be2d","line":121,"in_reply_to":"5a890539_45b2fce5","updated":"2014-12-05 09:56:45.000000000","message":"Agreed, will add in next version of draft.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":120,"context_line":"* They submit to the OpenStack Technical Committee oversight"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"},{"line_number":125,"context_line":"collaboration between similar projects, or to remove dead projects."},{"line_number":126,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_a1bcdd6d","line":123,"updated":"2014-12-08 22:33:20.000000000","message":"I would prefer if this was strengthened to say that the TC will vote to approve or reject applications itself, based on the recommendations and input of any delegates, but without being bound to that advice. It has been proposed, for example, that we let the core reviewers on the project-config repository approve projects. That goes too far in the direction of removing the elected representatives from the process.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"e7c700bff098589db5bd4c5d9354842f70b2fa00","unresolved":false,"context_lines":[{"line_number":120,"context_line":"* They submit to the OpenStack Technical Committee oversight"},{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"},{"line_number":125,"context_line":"collaboration between similar projects, or to remove dead projects."},{"line_number":126,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_1956efd2","line":123,"in_reply_to":"3a961159_a1bcdd6d","updated":"2014-12-09 14:27:59.000000000","message":"I\u0027m fine with making the TC the voting body, as mentioned in some of the face to face meetings.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a7121c4f0c97ea7e093c9f53e9e315c9181f8456","unresolved":false,"context_lines":[{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"},{"line_number":125,"context_line":"collaboration between similar projects, or to remove dead projects."},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_aeff05aa","line":124,"updated":"2014-12-02 20:39:22.000000000","message":"IMO the concepts of \"authority\" and \"encourage\" don\u0027t really sit well together in this context.\n\nAnyone can encourage a good outcome, but surely authority is only required to *mandate* a particular approach?","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":121,"context_line":""},{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"},{"line_number":125,"context_line":"collaboration between similar projects, or to remove dead projects."},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_2c76460d","line":124,"in_reply_to":"5a890539_aeff05aa","updated":"2014-12-05 09:56:45.000000000","message":"I meant, TC retains authority as to which projects are in OpenStack and which aren\u0027t. For example it may unilaterally decide to remove a stillborn project. Will clarify in next version.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":122,"context_line":"These criteria are objective, and therefore the Technical Committee may"},{"line_number":123,"context_line":"delegate processing applications to another team. However, it retains full"},{"line_number":124,"context_line":"authority over the approved projects, and may decide to encourage"},{"line_number":125,"context_line":"collaboration between similar projects, or to remove dead projects."},{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":128,"context_line":"Contributors to those projects will all be considered ATCs and participate"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_6a862915","line":125,"updated":"2014-12-09 19:59:50.000000000","message":"\"encourage collaboration\" is certainly addressed in this proposal, but you had another point about \"avoiding duplication of effort\" that didn\u0027t make it in this proposal that I can see, can you point it out? \n\nAlso do we want to state that we encourage competing solutions with the new governance model?","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":128,"context_line":"Contributors to those projects will all be considered ATCs and participate"},{"line_number":129,"context_line":"in electing the Technical Committee."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Transition"},{"line_number":132,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_6b62d9da","line":129,"updated":"2014-12-05 23:44:44.000000000","message":"huh? I am not sure what this means? So we drop the \u0027Compute Program\u0027?  I also don\u0027t think this needs to be explicitly called out. This sounds like it may be an implementation detail, and the important part is the ATC and right to vote.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"e7c700bff098589db5bd4c5d9354842f70b2fa00","unresolved":false,"context_lines":[{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":128,"context_line":"Contributors to those projects will all be considered ATCs and participate"},{"line_number":129,"context_line":"in electing the Technical Committee."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Transition"},{"line_number":132,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_d972a77b","line":129,"in_reply_to":"3a961159_21770dd6","updated":"2014-12-09 14:27:59.000000000","message":"++, that is exactly correct, Doug.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"5660451f5b878487bbabebffb6c205f39fe32d05","unresolved":false,"context_lines":[{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":128,"context_line":"Contributors to those projects will all be considered ATCs and participate"},{"line_number":129,"context_line":"in electing the Technical Committee."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Transition"},{"line_number":132,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_563cbae2","line":129,"in_reply_to":"3a961159_21770dd6","updated":"2014-12-09 18:13:32.000000000","message":"Thanks for the clarification. Presumably whatever the Compute Program becomes can contain multiple git repos. Maybe it makes sense to explicitly something along the lines of what Doug said instead of the current phrasing.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":126,"context_line":""},{"line_number":127,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":128,"context_line":"Contributors to those projects will all be considered ATCs and participate"},{"line_number":129,"context_line":"in electing the Technical Committee."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"Transition"},{"line_number":132,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_21770dd6","line":129,"in_reply_to":"5a890539_6b62d9da","updated":"2014-12-08 22:33:20.000000000","message":"If we are going to support competing projects, we will need to drop the program structure. We created that structure to encourage collaboration, and now we want to loosen it up to allow competition. So instead of a \"Compute Program\" we can go back to calling it simply \"Nova\".","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"c0fde81d0332cb81881b0a37dfa194632fa2b806","unresolved":false,"context_lines":[{"line_number":150,"context_line":"The work on this transition is assigned to the Technical Committee members,"},{"line_number":151,"context_line":"under the coordination of the Chair of the Technical Committee."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Work Items"},{"line_number":154,"context_line":"----------"},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"* Create project taxonomy base structure"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_10007200","line":153,"range":{"start_line":153,"start_character":5,"end_line":153,"end_character":10},"updated":"2014-12-09 20:35:20.000000000","message":"Would be good to have point person listed for each work item.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"c4cc0394a01de3422eb56198e96c83950eb52518","unresolved":false,"context_lines":[{"line_number":151,"context_line":"under the coordination of the Chair of the Technical Committee."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Work Items"},{"line_number":154,"context_line":"----------"},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"* Create project taxonomy base structure"},{"line_number":157,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_e51b2ac8","line":154,"updated":"2014-12-09 20:25:14.000000000","message":"to make this clearer, we should have a rough timeline associated with these items. It will both give us at the TC some deadlines to work towards, and also make it clear about the kinds of time frames we expect these bits to emerge in the community.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":153,"context_line":"Work Items"},{"line_number":154,"context_line":"----------"},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"* Create project taxonomy base structure"},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"* Replace incubation-integration-requirements.rst by rules definition for"},{"line_number":159,"context_line":"  the \"integrated-release\" transitional tag"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_6ab469d1","line":156,"updated":"2014-12-09 19:59:50.000000000","message":"Create a list of tags that can be applied to each project so that users have an indicator of the project\u0027s current classification","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":159,"context_line":"  the \"integrated-release\" transitional tag"},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"* Create taxonomy navigation website, to make the taxonomy easily"},{"line_number":162,"context_line":"  discoverable, searchable and browseable"},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"* Define new objective OpenStack project requirements (to replace old"},{"line_number":165,"context_line":"  new-programs-requirements.rst)"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_4affad67","line":162,"updated":"2014-12-09 19:59:50.000000000","message":"If you don\u0027t use the word taxonomy above you\u0027ll need to change this to controlled list of tags or some such.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1849,"name":"Joe Gordon","email":"joe.gordon0@gmail.com","username":"jogo"},"change_message_id":"0e1cb7ab09e9c655b3f507ca2c9ffca96df2d570","unresolved":false,"context_lines":[{"line_number":179,"context_line":"number of expectations toward the projects in the \"integrated release\"."},{"line_number":180,"context_line":"This is what created tension as the Technical Committee added more projects"},{"line_number":181,"context_line":"which those horizontal teams had to support. Those expectations have to be"},{"line_number":182,"context_line":"revisited as we replace the \"integrated release\" with a richer landscape."},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"With this proposed change, the work of horizontal teams shall gradually move"},{"line_number":185,"context_line":"away from centrally handling work for all projects, to a more decentralized"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_0b8075f6","line":182,"updated":"2014-12-05 23:44:44.000000000","message":"I would argue we should do this even if we maintain the current scope of OpenStack as well.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"2408dec18f1a4fc63ac5fec9a930ba7505512f67","unresolved":false,"context_lines":[{"line_number":179,"context_line":"number of expectations toward the projects in the \"integrated release\"."},{"line_number":180,"context_line":"This is what created tension as the Technical Committee added more projects"},{"line_number":181,"context_line":"which those horizontal teams had to support. Those expectations have to be"},{"line_number":182,"context_line":"revisited as we replace the \"integrated release\" with a richer landscape."},{"line_number":183,"context_line":""},{"line_number":184,"context_line":"With this proposed change, the work of horizontal teams shall gradually move"},{"line_number":185,"context_line":"away from centrally handling work for all projects, to a more decentralized"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_3ef2dc9a","line":182,"in_reply_to":"5a890539_0b8075f6","updated":"2014-12-08 13:43:43.000000000","message":"+1, for me this is just the next sensible step at the current maturity level of the project, independent of scope.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"fbfa16a9ef7df31bc2cdb528c7d74ea85495d499","unresolved":false,"context_lines":[{"line_number":184,"context_line":"With this proposed change, the work of horizontal teams shall gradually move"},{"line_number":185,"context_line":"away from centrally handling work for all projects, to a more decentralized"},{"line_number":186,"context_line":"model where they provide processes and tools to empower projects to do the"},{"line_number":187,"context_line":"work themselves."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":190,"context_line":"under the new project structure, and which (if any) projects they still"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_6068c6ba","line":187,"updated":"2014-12-02 22:51:51.000000000","message":"Do we want to call out that the horizontal teams should also be responsible for passing along the knowledge/tools/processes to the projects in order to produce quality artifacts?\n\ne.g. The docs team would write a guide for creating quality documentation that the projects can follow.\n\ne.g. The release management team would write a checklist for all of the artifacts that the projects need to produce.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":184,"context_line":"With this proposed change, the work of horizontal teams shall gradually move"},{"line_number":185,"context_line":"away from centrally handling work for all projects, to a more decentralized"},{"line_number":186,"context_line":"model where they provide processes and tools to empower projects to do the"},{"line_number":187,"context_line":"work themselves."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":190,"context_line":"under the new project structure, and which (if any) projects they still"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_0f2edc8c","line":187,"in_reply_to":"5a890539_6068c6ba","updated":"2014-12-05 09:56:45.000000000","message":"+1. Will add to next version","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0dca0f902f75342d44706c7afa42bc5b74d887ac","unresolved":false,"context_lines":[{"line_number":184,"context_line":"With this proposed change, the work of horizontal teams shall gradually move"},{"line_number":185,"context_line":"away from centrally handling work for all projects, to a more decentralized"},{"line_number":186,"context_line":"model where they provide processes and tools to empower projects to do the"},{"line_number":187,"context_line":"work themselves."},{"line_number":188,"context_line":""},{"line_number":189,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":190,"context_line":"under the new project structure, and which (if any) projects they still"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_2a2fc1f7","line":187,"in_reply_to":"5a890539_6068c6ba","updated":"2014-12-09 19:59:50.000000000","message":"Yep, I think that\u0027s fine to require.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"96fb22b7b8ca890025ba8f4a1d80b2a5a65b5686","unresolved":false,"context_lines":[{"line_number":189,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":190,"context_line":"under the new project structure, and which (if any) projects they still"},{"line_number":191,"context_line":"directly handle. They will be able to define tags (like"},{"line_number":192,"context_line":"\"security-supported\") to communicate that new organization. Note that most"},{"line_number":193,"context_line":"teams already started that transition as more projects were being added to"},{"line_number":194,"context_line":"the integrated release, so this will help them to more explicitly describe"},{"line_number":195,"context_line":"the service they provide."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_1c13565d","line":192,"updated":"2014-12-08 22:33:20.000000000","message":"A tag like \"security-supported\" implies that some projects may not be supported by the security team at all. The cross-project teams need to be willing to \"support\" all of the projects, even if that support is minimal advice. A tag like \"security-reviewed\" more directly indicates a useful characteristic of the project and how it relates to the cross-project team.\n\nSimilarly, for docs we might have tags like \"install-guide\" or \"operators-guide\" indicating that those guides include details about the project. I would hate to see a \"documentation: no\" tag on any project, though.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5418680594740c669e94ebc8542078a88d140f37","unresolved":false,"context_lines":[{"line_number":189,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":190,"context_line":"under the new project structure, and which (if any) projects they still"},{"line_number":191,"context_line":"directly handle. They will be able to define tags (like"},{"line_number":192,"context_line":"\"security-supported\") to communicate that new organization. Note that most"},{"line_number":193,"context_line":"teams already started that transition as more projects were being added to"},{"line_number":194,"context_line":"the integrated release, so this will help them to more explicitly describe"},{"line_number":195,"context_line":"the service they provide."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a961159_c47726d3","line":192,"in_reply_to":"3a961159_1c13565d","updated":"2014-12-09 11:02:12.000000000","message":"OK, \"security-supported\" might not be the right term, I\u0027ll fix it in next revision.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a7121c4f0c97ea7e093c9f53e9e315c9181f8456","unresolved":false,"context_lines":[{"line_number":192,"context_line":"\"security-supported\") to communicate that new organization. Note that most"},{"line_number":193,"context_line":"teams already started that transition as more projects were being added to"},{"line_number":194,"context_line":"the integrated release, so this will help them to more explicitly describe"},{"line_number":195,"context_line":"the service they provide."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":198,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_ee12edb2","line":195,"updated":"2014-12-02 20:39:22.000000000","message":"Presumably these tags could be rescinded some time after being granted?\n\nOnly on release boundaries, or at any time, I wonder?","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":192,"context_line":"\"security-supported\") to communicate that new organization. Note that most"},{"line_number":193,"context_line":"teams already started that transition as more projects were being added to"},{"line_number":194,"context_line":"the integrated release, so this will help them to more explicitly describe"},{"line_number":195,"context_line":"the service they provide."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":198,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_2f2398ab","line":195,"in_reply_to":"5a890539_ee12edb2","updated":"2014-12-05 09:56:45.000000000","message":"That should be part of the tag definition. Some would be very volatile, and some would have a deprecation period.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"0bc7dca5d994503801a543b2205beb7305ac4e4e","unresolved":false,"context_lines":[{"line_number":207,"context_line":"framework that will allow us to do that, but doesn\u0027t actually do anything"},{"line_number":208,"context_line":"yet. In particular, the \"integrated release\" as a concept will still very"},{"line_number":209,"context_line":"much exist at least until the end of the Kilo development cycle."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Trademark checks"},{"line_number":212,"context_line":"----------------"},{"line_number":213,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_5c86f765","line":210,"updated":"2014-12-04 21:11:39.000000000","message":"I would like to see a section here for \"Impact for existing incubated projects\"","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c78d93de5081d2d682aa3dbe49cbd23aabcd200","unresolved":false,"context_lines":[{"line_number":207,"context_line":"framework that will allow us to do that, but doesn\u0027t actually do anything"},{"line_number":208,"context_line":"yet. In particular, the \"integrated release\" as a concept will still very"},{"line_number":209,"context_line":"much exist at least until the end of the Kilo development cycle."},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Trademark checks"},{"line_number":212,"context_line":"----------------"},{"line_number":213,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"5a890539_ef47d04a","line":210,"in_reply_to":"5a890539_5c86f765","updated":"2014-12-05 09:56:45.000000000","message":"Agreed, will add to next version.","commit_id":"ab3d16d6121ed7be3d0a82b346cbe1f40ef94bdb"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"4fc7b49cbfc879faf43639c6a4a86c63cc97e00d","unresolved":false,"context_lines":[{"line_number":104,"context_line":"development discussions on the openstack-dev mailing-list and use"},{"line_number":105,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":106,"context_line":"the OpenStack community as well, and we propose that those should considered"},{"line_number":107,"context_line":"\"OpenStack projects\" (and be hosted under \"openstack\" GitHub organizations),"},{"line_number":108,"context_line":"as long as:"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"* They align with the OpenStack Mission: the project should help further the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_74c15c53","line":107,"updated":"2014-12-11 17:49:27.000000000","message":"Maybe we shouldn\u0027t be mentioning github, since it\u0027s not the primary host of our code (git.openstack.org is).  Perhaps talking about the \"openstack namespace\" is sufficient?\n\nThe same comment applies to the \"Trademark checks\" section later in the document.","commit_id":"00e6870ddecbbd312797090742ca71580133c1ef"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5aefc005bfce392d49ef708b9950e70f7cfc74a0","unresolved":false,"context_lines":[{"line_number":104,"context_line":"development discussions on the openstack-dev mailing-list and use"},{"line_number":105,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":106,"context_line":"the OpenStack community as well, and we propose that those should considered"},{"line_number":107,"context_line":"\"OpenStack projects\" (and be hosted under \"openstack\" GitHub organizations),"},{"line_number":108,"context_line":"as long as:"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"* They align with the OpenStack Mission: the project should help further the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_5c6714b7","line":107,"in_reply_to":"3a961159_74c15c53","updated":"2014-12-12 08:44:38.000000000","message":"Good point, let me fix that real quick.","commit_id":"00e6870ddecbbd312797090742ca71580133c1ef"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"4fc7b49cbfc879faf43639c6a4a86c63cc97e00d","unresolved":false,"context_lines":[{"line_number":213,"context_line":""},{"line_number":214,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":215,"context_line":"under the new project structure, and which (if any) projects they still"},{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_b4ae6496","line":216,"updated":"2014-12-11 17:49:27.000000000","message":"This is probably just an implementation detail, but this makes me think that we may want a hierarchy for tags.  For example, all release management related tags could be in their own namespace to keep things well organized.","commit_id":"00e6870ddecbbd312797090742ca71580133c1ef"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5aefc005bfce392d49ef708b9950e70f7cfc74a0","unresolved":false,"context_lines":[{"line_number":213,"context_line":""},{"line_number":214,"context_line":"Each horizontal team will have to redefine how they organize their work"},{"line_number":215,"context_line":"under the new project structure, and which (if any) projects they still"},{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_9c333caa","line":216,"in_reply_to":"3a961159_b4ae6496","updated":"2014-12-12 08:44:38.000000000","message":"Right, that\u0027s implementation detail for the taxonomy. Good one though.","commit_id":"00e6870ddecbbd312797090742ca71580133c1ef"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f138db28fe90af14e81a55a7b70ef8e9c6b17656","unresolved":false,"context_lines":[{"line_number":105,"context_line":"#openstack-meeting channels for their team meetings. Those are part of"},{"line_number":106,"context_line":"the OpenStack community as well, and we propose that those should considered"},{"line_number":107,"context_line":"\"OpenStack projects\" (and be hosted under openstack git namespaces), as"},{"line_number":108,"context_line":"long as:"},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"* They align with the OpenStack Mission: the project should help further the"},{"line_number":111,"context_line":"  OpenStack mission, by providing a cloud infrastructure service, or"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_214aad27","line":108,"updated":"2014-12-16 20:16:13.000000000","message":"These are good base requirements, but I think we can do a little more to ensure that we\u0027re only concerned with reviewing active, somewhat mature, projects. Our current incubation requirements include things like \"Project should have an active team of contributors\" which are pretty easy to meet, but allow us to push projects into the attic or back to stackforge when they fall idle.\n\nThe list below provides a good set of principles for building a list of criteria for inclusion, but I don\u0027t think it is a good list by itself. As worded, this proposal implies that the list below is *the* list. Can we change the end of the paragraph to read:\n\n  as long as they meet an objective criteria for inclusion\n  (to be developed as one of the work items below).\n  This might include items such as:","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"f94293dce0677336755fe5fbbe1a54b45553133f","unresolved":false,"context_lines":[{"line_number":132,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":133,"context_line":"We\u0027ll still track which team owns which git repository, but this will let"},{"line_number":134,"context_line":"multiple different \"OpenStack\" teams potentially address the same problem"},{"line_number":135,"context_line":"space. Contributors to those projects will all be considered ATCs and"},{"line_number":136,"context_line":"participate in electing the Technical Committee."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Transition"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_3722f301","line":135,"updated":"2014-12-16 17:47:58.000000000","message":"Can we expand \"those projects\" for the purposes of electoral clarity? I am reading \"Contributors to those projects hosted under openstack git namespaces\". If I am wrong in my interpretation, please do correct me.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":2271,"name":"Michael Still","email":"mikal@stillhq.com","username":"mikalstill"},"change_message_id":"c12374aed0c726c9a1e150b38bde6fe577d35b65","unresolved":false,"context_lines":[{"line_number":132,"context_line":"This proposed structure will replace the current program-driven structure."},{"line_number":133,"context_line":"We\u0027ll still track which team owns which git repository, but this will let"},{"line_number":134,"context_line":"multiple different \"OpenStack\" teams potentially address the same problem"},{"line_number":135,"context_line":"space. Contributors to those projects will all be considered ATCs and"},{"line_number":136,"context_line":"participate in electing the Technical Committee."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Transition"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_a19a1dc3","line":135,"in_reply_to":"3a961159_3722f301","updated":"2014-12-16 20:13:47.000000000","message":"Agreed, I read this as former program projects, but I think its intended to be \"projects in the OpenStack git namespace\".","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"f94293dce0677336755fe5fbbe1a54b45553133f","unresolved":false,"context_lines":[{"line_number":133,"context_line":"We\u0027ll still track which team owns which git repository, but this will let"},{"line_number":134,"context_line":"multiple different \"OpenStack\" teams potentially address the same problem"},{"line_number":135,"context_line":"space. Contributors to those projects will all be considered ATCs and"},{"line_number":136,"context_line":"participate in electing the Technical Committee."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Transition"},{"line_number":139,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_774abbad","line":136,"updated":"2014-12-16 17:47:58.000000000","message":"I would add here, \"as defined in the Technical Committee charter\", as I believe this is just pointing to the definitions in the charter not over writing them in this document.\n\nPlus addressing the charter is a work item in this spec so I think we should be clear that the charter is the governing document for electoral process.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6fca4ba732a148cac2bada05ab876dfcf3584117","unresolved":false,"context_lines":[{"line_number":133,"context_line":"We\u0027ll still track which team owns which git repository, but this will let"},{"line_number":134,"context_line":"multiple different \"OpenStack\" teams potentially address the same problem"},{"line_number":135,"context_line":"space. Contributors to those projects will all be considered ATCs and"},{"line_number":136,"context_line":"participate in electing the Technical Committee."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Transition"},{"line_number":139,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_7a9b8272","line":136,"in_reply_to":"3a961159_774abbad","updated":"2014-12-16 17:57:45.000000000","message":"Note that this is just a TC resolution on a plan, not a reference document or a change to the election process.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"aa8e09fbedd59684579d0f201cf4d92b719b9cc9","unresolved":false,"context_lines":[{"line_number":133,"context_line":"We\u0027ll still track which team owns which git repository, but this will let"},{"line_number":134,"context_line":"multiple different \"OpenStack\" teams potentially address the same problem"},{"line_number":135,"context_line":"space. Contributors to those projects will all be considered ATCs and"},{"line_number":136,"context_line":"participate in electing the Technical Committee."},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"Transition"},{"line_number":139,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_dafd5670","line":136,"in_reply_to":"3a961159_7a9b8272","updated":"2014-12-16 18:00:33.000000000","message":"Well your comment to that effect will suffice for me. Thanks Thierry.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"8acca113cfa33f4a51b16babcef61c1e7331573a","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_9d1c0f6c","line":219,"updated":"2014-12-12 14:08:08.000000000","message":"Is there also an implicit loss of exclusivity-of-mandate here, in terms of the existing horizontal teams?\n\ni.e. for the projects not included in some proposed \"${horizontal-concern}-supported\" tag, to pool their resources and spin up their own alternative ${horizontal-concern}?","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"63a02ed904ff3babf48841b5858ff9be0651767b","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_d7560f06","line":219,"in_reply_to":"3a961159_1287ec13","updated":"2014-12-16 17:20:53.000000000","message":"I agree this is fine as a foundational direction, and then the implementation is where we\u0027ll determine sensible tags.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"1fda49b7d0dbe06947c6812f6c38edce3d6a8179","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_6f3ec2db","line":219,"in_reply_to":"3a961159_5e445a1a","updated":"2014-12-12 18:05:25.000000000","message":"Hm, yeah, calling things out as supported could indeed have bad side effects.  Taking docs as an example again, saying officially that project foo\u0027s docs are handled by the docs team makes it easier for project foo to not really worry or think about docs.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"0472690868e871f27c3fb64feb9a2115e072c43e","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_ea4380ac","line":219,"in_reply_to":"3a961159_6f3ec2db","updated":"2014-12-12 18:34:24.000000000","message":"Let\u0027s face it, docs are especially squirrelly to put metrics on and determine support levels. I can: codify current state, meet with other cross-project PTLs to see how they manage, and get back on this. Definitely needs discussion.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"7fe5c5f7950429091d23167daaf46cc0a270c307","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_aec35336","line":219,"in_reply_to":"3a961159_9d1c0f6c","updated":"2014-12-12 15:40:27.000000000","message":"I\u0027m not sure I totally understand the concern ... for example, do you mean that if not directly supported by docs, projects may not feel a requirement to build up their own docs?\n\nSay, for docs, I think we need a way to say that a project is meeting a set of expectations around docs (perhaps that\u0027s yet another tag).  A project may or may not have \"docs:supported\", but either way docs must be in place before you get \"docs:mature\" or something.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"acd2ec0cda7330d4dc2cb55e944989d486776395","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_fe8b461c","line":219,"in_reply_to":"3a961159_ae051315","updated":"2014-12-12 16:55:46.000000000","message":"(Of course, this isn\u0027t docs specific, but just using it as an example ...)\n\nI think regarding \"docs:supported\" and \"docs:mature\", IMO it\u0027s all of the above.\n\nEven if you\u0027re not \"docs:supported\", all projects would be expected to work within the framework set up by the docs team to empower projects to make docs happen and eventually get \"docs:mature\".\n\nIf some team of documentation writers wanted to work together on docs for several projects, that seems fine.  They could be a team that owns some repos.  I would just expect that team to work with the official docs horizontal team to utilize and improve as required the tools and processes needed to accomplish the task.\n\nPerhaps we should specify that the TC will still recognize some horizontal teams as the \"official\" team for that function.  I don\u0027t want another release management team that is seen as an \"alternative\" to the one Thierry leads, for example.  There should be one release management team that is blessed and expected to guide and empower release management across all of OpenStack.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"0ca485bf7bfd1189a568e0bead9bb84a5a73364d","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_5e445a1a","line":219,"in_reply_to":"3a961159_ae051315","updated":"2014-12-12 16:57:49.000000000","message":"Having duplication in the cross-project teams will lead to fragmentation. We should not encourage the cross-project teams to consider some projects \"more supported\" than others. For example, individual Oslo team members may decide to help manage sync patches in project foo, but as a team we consider that task the responsibility of the liaison from project foo. We help with advice about transitions and debugging, but we do not as a rule do the work for any project. The release, documentation, and QA teams could work in a similar way.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"fc017001214545e3fe8805df675f945b3c55e64d","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_ae051315","line":219,"in_reply_to":"3a961159_aec35336","updated":"2014-12-12 16:04:45.000000000","message":"@russellb: yeah, so I guess the confusion is partially around whether the tags will tend to be:\n\n* a declaration that a horizontal team is doing work on behalf of a particular project - e.g. \"docs:supported\" meaning the docs team is directly providing support to this project\n* or, more like a value-judgement on the state of a particular project - e.g. \"docs:mature\" meaning that docs provided for and by a particular project are considered mature, for some definition of mature\n* or, indeed, all of the above\n\nIIRC the first iteration of this patch used a specific example that leaned towards the first interpretation (\"security-supported\" or some-such), and if I\u0027m reading the latest text correctly it seem to lean that way also in less specific terms:\n\n  \"... which (if any) projects they still directly handle\"\n\nIn any case, the question relates to whether the projects that a horizontal team declines to tag with \"foo-supported\" are free to club together to build their own alternative foo?\n\ni.e. there\u0027ll potentially no longer be *the* release-mgmt program (or *the* docs program or whatever), rather *a* release-mgmt program that chooses to handle certain projects directly, maybe some projects managing themselves individually, and indeed other projects aligning themselves into an alternative release-mgmt structure.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"3b07d3ee4882b1369fd2a15c60094363a2fd0787","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_1287ec13","line":219,"in_reply_to":"3a961159_c937924b","updated":"2014-12-15 18:07:58.000000000","message":"+1000 Doug\n\nI think following the processes and conventions put in place by the various horizontal teams is part of the \u0027one-of-us\u0027 test. It would be up to the TC to decide how far a project could stray from that (recognising that *every* project will likely stray to some extent) while remaining one-of-us, and that\u0027s part and parcel of projects submitting to TC oversight in exchange for ATC status for their developers.\n\nThe tagging, as I understand it, is aimed at communicating to interested parties outside of the OpenStack development community, so it would be things like docs:mature-install-guide, not things like docs:someone-elses-problem.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"ccbc2ef06acdcd20f21ee4bb92624ef5526a4151","unresolved":false,"context_lines":[{"line_number":216,"context_line":"directly handle. They will be able to define tags to communicate that new"},{"line_number":217,"context_line":"organization. Note that most teams already started that transition as more"},{"line_number":218,"context_line":"projects were being added to the integrated release, so this will help them"},{"line_number":219,"context_line":"to more explicitly describe the service they provide."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Impact for existing integrated projects and the Kilo cycle"},{"line_number":222,"context_line":"----------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_c937924b","line":219,"in_reply_to":"3a961159_ea4380ac","updated":"2014-12-15 08:57:26.000000000","message":"I think the \"exclusivity\" of horizontal teams is more a side-effect of the minimal collaboration that the TC enforces on \"OpenStack\" projects. We encourage collaboration and consider it part of the \"open development\", therefore it\u0027s unlikely that we would include an hypothetical alternate horizontal team with the exact same scope (because it would fragment that collaboration).\n\nIt\u0027s unlikely, but not impossible -- I\u0027d therefore rather not carve the \"exclusivity\" in stone and prevent us from having multiple teams if it ever makes sense.\n\nAs far as tags go, there will obviously be more discussion about which precise ones we create to support (for example) Documentation. But let\u0027s cross that bridge when we get there, and approve this foundational direction document first.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":7973,"name":"Douglas Mendizábal","email":"dmendiza@redhat.com","username":"dougmendizabal"},"change_message_id":"2ed25f4b144e3a1f579c08511f77af8e85b2fee5","unresolved":false,"context_lines":[{"line_number":238,"context_line":"Currently-incubated projects would directly become \"OpenStack projects\""},{"line_number":239,"context_line":"under the new structure, without needing another formal application. Future"},{"line_number":240,"context_line":"tags will be defined and applied to them to further describe their nature"},{"line_number":241,"context_line":"and maturity status."},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"Trademark checks"},{"line_number":244,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_1278ccf7","line":241,"updated":"2014-12-15 17:50:39.000000000","message":"Thanks for adding this section.  One thing that is still not clear to me is whether the \"integrated-release\" tag will continue to be a goal for currently incubated projects?\n\nLike many other incubated projects, our team is spending a considerable amount of effort working towards meeting the requirements specified in incubation-integration-requirements.rst with the expectation that there would be a graduation review at the end of the Kilo cycle.\n\nSince of the work items is to change the incubation-integration-requriements.rst, I\u0027m concerned that the changes will result in wasted effort on our part.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"3b07d3ee4882b1369fd2a15c60094363a2fd0787","unresolved":false,"context_lines":[{"line_number":238,"context_line":"Currently-incubated projects would directly become \"OpenStack projects\""},{"line_number":239,"context_line":"under the new structure, without needing another formal application. Future"},{"line_number":240,"context_line":"tags will be defined and applied to them to further describe their nature"},{"line_number":241,"context_line":"and maturity status."},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"Trademark checks"},{"line_number":244,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_15b996ec","line":241,"in_reply_to":"3a961159_1278ccf7","updated":"2014-12-15 18:07:58.000000000","message":"I think it\u0027s a valid concern that incubated projects are in a sort of feedback vacuum with respect to the TC until this process is bedded in.\n\nI don\u0027t think it\u0027s reasonable to be concerned about \u0027wasted effort\u0027 though. Those requirements aren\u0027t valuable because they\u0027re in the Integration Requirements, they\u0027re in the Integration Requirements because they\u0027re valuable. The only change here is that they\u0027ll be assessed in a more fine-grained way, one tag per requirement, not in a monolithic all-or-nothing review.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5a665c229620c84ab43f52519740fc99c55695a4","unresolved":false,"context_lines":[{"line_number":238,"context_line":"Currently-incubated projects would directly become \"OpenStack projects\""},{"line_number":239,"context_line":"under the new structure, without needing another formal application. Future"},{"line_number":240,"context_line":"tags will be defined and applied to them to further describe their nature"},{"line_number":241,"context_line":"and maturity status."},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"Trademark checks"},{"line_number":244,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_c81f625a","line":241,"in_reply_to":"3a961159_15b996ec","updated":"2014-12-16 09:50:21.000000000","message":"Agree with Zane: while the \"integrated release\" will fade out as a monolithic goal, most of the integration-requirements should translate into valuable tags like \"ci-tested\", \"end-user-docs\" or \"diverse-contributors\" (I just made those up, but you get the idea). So that is certainly not wasted effort.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"f94293dce0677336755fe5fbbe1a54b45553133f","unresolved":false,"context_lines":[{"line_number":250,"context_line":"projects under the openstack git namespaces are considered projects from the"},{"line_number":251,"context_line":"OpenStack Community, and won\u0027t all be preventively checked for potential"},{"line_number":252,"context_line":"trademark conflicts. To communicate that, a note will be posted on the"},{"line_number":253,"context_line":"relevant git organization pages stating that the OpenStack Foundation is not"},{"line_number":254,"context_line":"responsible for the project names or content below, which are posted by"},{"line_number":255,"context_line":"independent developers."},{"line_number":256,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_9a258eb0","line":253,"updated":"2014-12-16 17:47:58.000000000","message":"What you mean by git organization pages? Would that be a Readme file in their repo?","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":6316,"name":"Anita Kuno","email":"anteaya@anteaya.info","username":"anteaya"},"change_message_id":"aa8e09fbedd59684579d0f201cf4d92b719b9cc9","unresolved":false,"context_lines":[{"line_number":250,"context_line":"projects under the openstack git namespaces are considered projects from the"},{"line_number":251,"context_line":"OpenStack Community, and won\u0027t all be preventively checked for potential"},{"line_number":252,"context_line":"trademark conflicts. To communicate that, a note will be posted on the"},{"line_number":253,"context_line":"relevant git organization pages stating that the OpenStack Foundation is not"},{"line_number":254,"context_line":"responsible for the project names or content below, which are posted by"},{"line_number":255,"context_line":"independent developers."},{"line_number":256,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_5ada4618","line":253,"in_reply_to":"3a961159_1acd1e87","updated":"2014-12-16 18:00:33.000000000","message":"Ah.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"6fca4ba732a148cac2bada05ab876dfcf3584117","unresolved":false,"context_lines":[{"line_number":250,"context_line":"projects under the openstack git namespaces are considered projects from the"},{"line_number":251,"context_line":"OpenStack Community, and won\u0027t all be preventively checked for potential"},{"line_number":252,"context_line":"trademark conflicts. To communicate that, a note will be posted on the"},{"line_number":253,"context_line":"relevant git organization pages stating that the OpenStack Foundation is not"},{"line_number":254,"context_line":"responsible for the project names or content below, which are posted by"},{"line_number":255,"context_line":"independent developers."},{"line_number":256,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"3a961159_1acd1e87","line":253,"in_reply_to":"3a961159_9a258eb0","updated":"2014-12-16 17:57:45.000000000","message":"I\u0027m meaning mostly posting a warning on GitHub organization descriptions, but didn\u0027t want to single out GitHub here.","commit_id":"e9c7f252e861c16cd43ab8d5011dd7b47050a86e"}]}