)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"5d906befa999e33017b28fbe6f7fb284c4142bea","unresolved":false,"context_lines":[{"line_number":21,"context_line":"around it, and keeps track of which project teams follow such case."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Drivers are second-order objects from main projects, limited to"},{"line_number":24,"context_line":"implementing a specific published interface. We can therefore use a"},{"line_number":25,"context_line":"different set of requirements for \"driver teams\" and allow them to have"},{"line_number":26,"context_line":"more flexibility in terms of level playing field or open collaboration."},{"line_number":27,"context_line":"We recognize it\u0027s a price to pay in order to make the main projects"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"1a6eadb0_724bcd87","line":24,"range":{"start_line":24,"start_character":15,"end_line":24,"end_character":43},"updated":"2016-12-14 14:00:44.000000000","message":"This is a critical distinction but I\u0027m not sure you meant it to be? For things like the Nova virt driver \"interface\", it\u0027s not published (public) and is not stable (some might say on purpose).\n\nI would argue in the case of Nova virt drivers that since the virt driver interface is neither public nor published that teams of folks working only on their company\u0027s virt driver code in Nova are not eligible to be \"driver teams\".","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"642cfa2bd5bca93cabf5906ff71192c7c4ffaed3","unresolved":false,"context_lines":[{"line_number":21,"context_line":"around it, and keeps track of which project teams follow such case."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Drivers are second-order objects from main projects, limited to"},{"line_number":24,"context_line":"implementing a specific published interface. We can therefore use a"},{"line_number":25,"context_line":"different set of requirements for \"driver teams\" and allow them to have"},{"line_number":26,"context_line":"more flexibility in terms of level playing field or open collaboration."},{"line_number":27,"context_line":"We recognize it\u0027s a price to pay in order to make the main projects"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"1a6eadb0_8750fad5","line":24,"range":{"start_line":24,"start_character":15,"end_line":24,"end_character":43},"in_reply_to":"1a6eadb0_724bcd87","updated":"2016-12-15 11:03:29.000000000","message":"I meant it :) I don\u0027t think it\u0027s reasonable to support driver teams plugging into an unstable / unpublished / internal interface.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"b187d1161e30f4ad1359d0e6b3a7f46a0c081481","unresolved":false,"context_lines":[{"line_number":37,"context_line":"specific webpage), they will be listed together with other teams. The"},{"line_number":38,"context_line":"YAML entry will use a \"type: driver\" property to allow machines to"},{"line_number":39,"context_line":"read that the team scope is limited to drivers, without having to"},{"line_number":40,"context_line":"parse their mission statement prose."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Co-Authored-By: Thierry Carrez \u003cthierry@openstack.org\u003e"},{"line_number":43,"context_line":"Signed-off-by: Doug Hellmann \u003cdoug@doughellmann.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"1a6eadb0_243bfb9d","line":40,"updated":"2016-12-13 20:17:52.000000000","message":"While technically an implementation detail, this is a very important aspect and one of the only reasons I feel comfortable with the proposed solution.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"6563be5bc6e196e8bdb1fc513edf063be2147e88","unresolved":false,"context_lines":[{"line_number":32,"context_line":"drivers to file as separate project teams. Drivers should really be"},{"line_number":33,"context_line":"listed in project documentation and the OpenStack Marketplace, not in"},{"line_number":34,"context_line":"governance documents. To reduce that risk, brand names should not be"},{"line_number":35,"context_line":"part of the team name itself. Furthermore, driver teams won\u0027t use a"},{"line_number":36,"context_line":"specific tag or a separate YAML file (which would end up generating a"},{"line_number":37,"context_line":"specific webpage), they will be listed together with other teams. The"},{"line_number":38,"context_line":"YAML entry will use a \"type: driver\" property to allow machines to"},{"line_number":39,"context_line":"read that the team scope is limited to drivers, without having to"},{"line_number":40,"context_line":"parse their mission statement prose."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Co-Authored-By: Thierry Carrez \u003cthierry@openstack.org\u003e"},{"line_number":43,"context_line":"Signed-off-by: Doug Hellmann \u003cdoug@doughellmann.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"ba5201f7_6ea57aa0","line":40,"range":{"start_line":35,"start_character":30,"end_line":40,"end_character":35},"updated":"2017-01-06 00:57:58.000000000","message":"can you describe with an example how you envision the a patch to project.yaml file to be? If a driver team can get its own PTL and its own extra repos, how does that look in practice?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"}],"reference/new-driver-team-requirements.rst":[{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"cd74a9d1be5d69ec20501efe8981b6b3d91b4cbf","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":" Requirements for new OpenStack Driver team applications"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Driver Teams in OpenStack can be created as-needed and grow"},{"line_number":6,"context_line":"organically.  By becoming an official OpenStack team, they place"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_70647eb8","line":3,"range":{"start_line":3,"start_character":52,"end_line":3,"end_character":53},"updated":"2016-12-11 03:54:24.000000000","message":"missing a few \u003d\u003d\u0027s here and the first line","commit_id":"368ae395a65d15b91d49ac3db40d4085fbacd082"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"cd74a9d1be5d69ec20501efe8981b6b3d91b4cbf","unresolved":false,"context_lines":[{"line_number":2,"context_line":" Requirements for new OpenStack Driver team applications"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Driver Teams in OpenStack can be created as-needed and grow"},{"line_number":6,"context_line":"organically.  By becoming an official OpenStack team, they place"},{"line_number":7,"context_line":"themselves under the authority of the OpenStack Technical"},{"line_number":8,"context_line":"Committee. In return, their contributors get to vote in the Technical"},{"line_number":9,"context_line":"Committee election."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"When considering new driver teams for addition, the TC will check"},{"line_number":12,"context_line":"several criteria:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_f0708e74","line":9,"range":{"start_line":5,"start_character":0,"end_line":9,"end_character":19},"updated":"2016-12-11 03:54:24.000000000","message":"this is almost a straight copy of https://governance.openstack.org/tc/_sources/reference/new-projects-requirements.txt\n\nshould we add a sentence or two about why a new driver team may be required or wanted?","commit_id":"368ae395a65d15b91d49ac3db40d4085fbacd082"},{"author":{"_account_id":3153,"name":"Emilien Macchi","email":"emilien@redhat.com","username":"emilienm"},"change_message_id":"3b9205f460612259263992c9efe878d355e70f0f","unresolved":false,"context_lines":[{"line_number":17,"context_line":"    plug-in points in OpenStack projects"},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":20,"context_line":"    services consuming them"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"* Community Engagement"},{"line_number":23,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_ea4353ad","line":20,"updated":"2016-12-09 20:43:16.000000000","message":"Yes! this thing is really important to mention, thanks.","commit_id":"368ae395a65d15b91d49ac3db40d4085fbacd082"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"b910edd32dda673e454bac9ee78304903941ab2b","unresolved":false,"context_lines":[{"line_number":38,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":39,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"* Openness"},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a71b18c_76be3366","line":41,"updated":"2016-12-05 14:46:56.000000000","message":"Should we point to 4 opens? https://governance.openstack.org/reference/opens.html","commit_id":"368ae395a65d15b91d49ac3db40d4085fbacd082"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"769df01dc5dc37828041a8296022f7ca5bd74549","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":" Requirements for new OpenStack Driver team applications"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":6,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."},{"line_number":7,"context_line":"By becoming an official OpenStack team, they place themselves under the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_6858a757","line":4,"updated":"2016-12-12 17:14:27.000000000","message":"I would also like to include some language about preferring that drivers be part of the consuming project. Maybe the preamble from the stand-alone resolution can be inserted here.\n\n  The OpenStack community wants to encourage collaboration by\n  emphasizing contributions to projects that abstract differences\n  between vendor-specific products, while still empowering vendors to\n  integrate their products with OpenStack through drivers that can be\n  consumed by the abstraction layers. We strongly prefer that drivers\n  are included in the consuming projects and managed by the same\n  contributors in a collaborative fashion, whether by including drivers\n  \"in tree\" or by placing them in separate repositories owned by the\n  same team. However, we don\u0027t want to require project teams to \"own\"\n  code they are not comfortable managing by forcing all drivers to be a\n  part of the consuming project team\u0027s deliverables.\n\n  Some teams for projects that use drivers may not want to manage some\n  or all of the drivers that can be consumed by their project because\n  they have little insight into testing or debugging the code, or do not\n  have the resources needed to manage centrally a large number of\n  separate drivers. Vendors are of course free to produce drivers to\n  integrate with OpenStack completely outside of the community, but\n  because the community values having the drivers as well as the more\n  general support of vendor companies, we want to encourage a higher\n  level of engagement by welcoming vendor-specific teams to be a part of\n  our community governance.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"705e9e44bca8f3fb0d881342e47525dc6cd5f6b6","unresolved":false,"context_lines":[{"line_number":1,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":" Requirements for new OpenStack Driver team applications"},{"line_number":3,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":6,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."},{"line_number":7,"context_line":"By becoming an official OpenStack team, they place themselves under the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_59263a69","line":4,"in_reply_to":"1a6eadb0_6858a757","updated":"2016-12-13 10:46:18.000000000","message":"Will add","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"78ae8d2be5a26dd23be91ffab32663ddb0a30778","unresolved":false,"context_lines":[{"line_number":6,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."},{"line_number":7,"context_line":"By becoming an official OpenStack team, they place themselves under the"},{"line_number":8,"context_line":"authority of the OpenStack Technical Committee. In return, their contributors"},{"line_number":9,"context_line":"get to vote in the Technical Committee election."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"When considering new driver teams for addition, the TC will check"},{"line_number":12,"context_line":"several criteria:"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_c199e77a","line":9,"updated":"2016-12-12 14:17:05.000000000","message":"Can we please add:\n\n\"and access to vertical team resources like documentation and localization/internationalization\"\n\nSince access to vertical teams is prohibited currently for stackforge-style projects.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"705e9e44bca8f3fb0d881342e47525dc6cd5f6b6","unresolved":false,"context_lines":[{"line_number":6,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."},{"line_number":7,"context_line":"By becoming an official OpenStack team, they place themselves under the"},{"line_number":8,"context_line":"authority of the OpenStack Technical Committee. In return, their contributors"},{"line_number":9,"context_line":"get to vote in the Technical Committee election."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"When considering new driver teams for addition, the TC will check"},{"line_number":12,"context_line":"several criteria:"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_9920d24b","line":9,"in_reply_to":"3a71b18c_c199e77a","updated":"2016-12-13 10:46:18.000000000","message":"Will add","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"5b8d27a317f8ffac5c8734b09c6a9e5d04b8297c","unresolved":false,"context_lines":[{"line_number":14,"context_line":"* Team Name"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":17,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* Team Scope"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_2f7fe717","line":17,"updated":"2016-12-12 13:48:50.000000000","message":"Is this going to be confusing to users looking for the driver to go with their branded gear?","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"705e9e44bca8f3fb0d881342e47525dc6cd5f6b6","unresolved":false,"context_lines":[{"line_number":14,"context_line":"* Team Name"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":17,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* Team Scope"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_793a1638","line":17,"in_reply_to":"1a6eadb0_a8171f53","updated":"2016-12-13 10:46:18.000000000","message":"We tell them to look at the governance site for the list of official OpenStack teams (development cycle in progress). If they use it for a list of official components they are in for disappointment (some of those are dead, some of those are newborn, some of those are not even released).\n\nThey should really look at the release.o.o website for what is in the last release, at the main openstack.org website for a list of services (last release), and at the marketplace for vendor drivers (last release).","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"4d72a11bc2abeff909f65bec983747083d6df3c2","unresolved":false,"context_lines":[{"line_number":14,"context_line":"* Team Name"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":17,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* Team Scope"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_a1e22b9e","line":17,"in_reply_to":"3a71b18c_2f7fe717","updated":"2016-12-12 14:13:07.000000000","message":"They should basically not be looking into the list of teams in the governance website to find a driver. Otherwise there is a strong incentive to file as separate teams (rather than stay in-tree): you give those extra brand visibility.\n\nWe need to ramp up the driver section of the marketplace (and project docs) so that it is the authoritative list of drivers (in-tree and out-tree).","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"769df01dc5dc37828041a8296022f7ca5bd74549","unresolved":false,"context_lines":[{"line_number":14,"context_line":"* Team Name"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":17,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"* Team Scope"},{"line_number":20,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_a8171f53","line":17,"in_reply_to":"3a71b18c_a1e22b9e","updated":"2016-12-12 17:14:27.000000000","message":"Haven\u0027t we been telling them to look at the governance site for the list of official OpenStack components, though?","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"769df01dc5dc37828041a8296022f7ca5bd74549","unresolved":false,"context_lines":[{"line_number":22,"context_line":"    plug-in points in OpenStack projects"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":25,"context_line":"    services consuming them"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"* Community Engagement"},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_3c41903a","line":25,"updated":"2016-12-12 17:14:27.000000000","message":"I wonder how many project drivers do this today.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"78ae8d2be5a26dd23be91ffab32663ddb0a30778","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":44,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Openness"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_4137974c","line":45,"updated":"2016-12-12 14:17:05.000000000","message":"We should mandate a third-party CI setup, so that folks who are *not* employed by the vendor can actually test and land patches. This was incredibly useful for VMware Nova driver for example.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"705e9e44bca8f3fb0d881342e47525dc6cd5f6b6","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":44,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Openness"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_996d3235","line":45,"in_reply_to":"1a6eadb0_bce84018","updated":"2016-12-13 10:46:18.000000000","message":"I think that\u0027s a great topic, but whether this belongs to requirements or tag is a bit orthogonal to this change. Maybe we can work on that after we solve the driver-team policy question.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"769df01dc5dc37828041a8296022f7ca5bd74549","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":44,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Openness"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a6eadb0_bce84018","line":45,"in_reply_to":"3a71b18c_04f4cd58","updated":"2016-12-12 17:14:27.000000000","message":"On the other hand, if a project team has a rule that drivers must have third-party CI and the only reason a new project is being proposed is that the driver team doesn\u0027t want to deal with that, I would not support creating a new team. Maybe we need to update the point on line 29 to say something about that.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"e3fe2a0693978b5c66d752bb9699a24a500c7c94","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":44,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Openness"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_e437d1ad","line":45,"in_reply_to":"3a71b18c_4137974c","updated":"2016-12-12 14:23:16.000000000","message":"I don\u0027t particularly want the TC to have to police that. Maybe we can use a tag instead of a mandate?","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":6482,"name":"Steve Martinelli","email":"s.martinelli@gmail.com","username":"stevemar"},"change_message_id":"652143573d1641275bbd4a5b8a9646ad9b5b6323","unresolved":false,"context_lines":[{"line_number":42,"context_line":""},{"line_number":43,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":44,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* Openness"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables meet the :doc:`licensing`"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_04f4cd58","line":45,"in_reply_to":"3a71b18c_e437d1ad","updated":"2016-12-12 14:32:21.000000000","message":"++ for a tag","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"78ae8d2be5a26dd23be91ffab32663ddb0a30778","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  * The team has core reviewers and adopts a test-driven gate in the"},{"line_number":55,"context_line":"    OpenStack infrastructure for changes"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"In order to do an evaluation against this criteria, the TC expects the"},{"line_number":58,"context_line":"team to be set up and have some history to evaluate.  A few weeks of"},{"line_number":59,"context_line":"operating and following these team requirements is a rough guideline"},{"line_number":60,"context_line":"for how long to wait before applying to be approved by the TC."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_610d733d","line":57,"updated":"2016-12-12 14:17:05.000000000","message":"How can we ensure that this Driver concept does not turn into a stand alone project that works without the \"parent project\"? Do we need to worry about that?","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"e3fe2a0693978b5c66d752bb9699a24a500c7c94","unresolved":false,"context_lines":[{"line_number":54,"context_line":"  * The team has core reviewers and adopts a test-driven gate in the"},{"line_number":55,"context_line":"    OpenStack infrastructure for changes"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"In order to do an evaluation against this criteria, the TC expects the"},{"line_number":58,"context_line":"team to be set up and have some history to evaluate.  A few weeks of"},{"line_number":59,"context_line":"operating and following these team requirements is a rough guideline"},{"line_number":60,"context_line":"for how long to wait before applying to be approved by the TC."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a71b18c_c46655ba","line":57,"in_reply_to":"3a71b18c_610d733d","updated":"2016-12-12 14:23:16.000000000","message":"Line 21 talks about using existing plug-in points.","commit_id":"d973a2974264aba749a7ff8487dd2c547a3125af"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"d0d3fa1c0cd3b07c0ee78a9f8099e702020a4d59","unresolved":false,"context_lines":[{"line_number":6,"context_line":"emphasizing contributions to projects that abstract differences"},{"line_number":7,"context_line":"between vendor-specific products, while still empowering vendors to"},{"line_number":8,"context_line":"integrate their products with OpenStack through drivers that can be"},{"line_number":9,"context_line":"consumed by the abstraction layers. We strongly prefer that drivers"},{"line_number":10,"context_line":"are included in the consuming projects and managed by the same"},{"line_number":11,"context_line":"contributors in a collaborative fashion, whether by including drivers"},{"line_number":12,"context_line":"\"in tree\" or by placing them in separate repositories owned by the"},{"line_number":13,"context_line":"same team. However, we don\u0027t want to require project teams to \"own\""},{"line_number":14,"context_line":"code they are not comfortable managing by forcing all drivers to be a"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_5a8e7a2e","line":11,"range":{"start_line":9,"start_character":36,"end_line":11,"end_character":39},"updated":"2016-12-16 12:23:46.000000000","message":"Can we explain the rationale behind this? I\u0027m not comfortable with the \"strongly prefer\" wording. In the neutron case at least, the task of having vendor drivers in tree became detrimental to the development velocity of neutron itself. I don\u0027t think you\u0027d find many neutron developers who would advocate for the proposed preference.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"a4ceb522dcbdf6e98d60b92c4002793bdbf387bb","unresolved":false,"context_lines":[{"line_number":8,"context_line":"integrate their products with OpenStack through drivers that can be"},{"line_number":9,"context_line":"consumed by the abstraction layers. We strongly prefer that drivers"},{"line_number":10,"context_line":"are included in the consuming projects and managed by the same"},{"line_number":11,"context_line":"contributors in a collaborative fashion, whether by including drivers"},{"line_number":12,"context_line":"\"in tree\" or by placing them in separate repositories owned by the"},{"line_number":13,"context_line":"same team. However, we don\u0027t want to require project teams to \"own\""},{"line_number":14,"context_line":"code they are not comfortable managing by forcing all drivers to be a"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_3515519b","line":11,"in_reply_to":"1a6eadb0_5a8e7a2e","updated":"2016-12-16 12:45:12.000000000","message":"I think in-tree is an anti-pattern for something with the name \"driver\". If something is in tree it should be there because it has to be for the tree to work. Having drivers outside the tree helps ensure strong contracts that don\u0027t change very often and keeps integration boundaries (for testing, documentation, etc) more clear. We should be encouraging more outside-of-tree behavior, not less. Good fences, good neighbors and all that.\n\nWhich is not to say that they should be outside a project, or outside OpenStack. That\u0027s a different decision.\n\nBut let\u0027s do what we can to shrink repos, not encourage their growth.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"4fcccc6e8860eac7d8510f47f5ee136cab6efb67","unresolved":false,"context_lines":[{"line_number":21,"context_line":"separate drivers. Vendors are of course free to produce drivers to"},{"line_number":22,"context_line":"integrate with OpenStack completely outside of the community, but"},{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_f4ece2f4","line":26,"range":{"start_line":24,"start_character":0,"end_line":26,"end_character":25},"updated":"2017-01-05 19:37:15.000000000","message":"I have mixed feelings on this between Jays view and Thierry\u0027s.  I\u0027m not as optimistic about things given the history of things in Cinder for example.  The fact is that I like the idea of having drives in a separate repository, although I would prefer that entire collection be a team in and of itself.  So we don\u0027t have \"company-foo and company-biz\" teams, but instead we have projet-x:driver-team.\nThere are a number of reasons I think this is important:\n1. It requires and promotes cooptition\n2. It keeps some level of congruency between the drivers (hopefully)\n3. It isolates the vendor specific work vs community-based work\n\nI don\u0027t think a contributor that ONLY contributes to the driver side of things should have the same influence or input that somebody that commits to things further up the stack when it comes to things like the TC, voting or even things like ATC status.\n\nThe fact is that I don\u0027t believe the \"on ramp\" argument works in all cases, some vendors will have policies that say \"you can submit to *this* repo, and no others\".  That\u0027s fine, I don\u0027t have a problem with that, but it should be fairly easy to identify IMO.\n\nIn the cases that the \"on ramp\" theory works, then, that\u0027s great.  Nobody is stopping anybody from contributing elsewhere in the project or community so the same mechanisms we have in place today just picks those contributions up and well, \"Good for everyone\".\nI like the idea of welcoming contributions of all types, and while drivers are EXTREMELY important they are a different level of contribution as far as I\u0027m concerned and should be treated as such. I\u0027m not sure what the \"elusive carrot\" that\u0027s being debated here is though?  Is it just a matter of things like ATC, Infra resources, branding or what?\n\nAnyway, what I really don\u0027t understand is the apparent feeling that these contributors \"aren\u0027t welcome\".  Feelings of being welcome as a new contributor in my experience have had very little to do with driver vs core work (or whatever we\u0027re calling it) and more about the project as a whole.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"5d906befa999e33017b28fbe6f7fb284c4142bea","unresolved":false,"context_lines":[{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_6d0690cf","line":26,"updated":"2016-12-14 14:00:44.000000000","message":"We want to *incentivize* contributors that ONLY work on their vendor-specific driver code to actively contribute to the *good of the broader community*. Having \"driver teams\" officially \"recognized\" as some thing that is \"part of OpenStack\" -- but yet those teams don\u0027t do anything for the good of the broad OpenStack community (only their own vendor\u0027s customers) -- removes incentives for those contributors to participate in the broader upstream project team.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"d0d3fa1c0cd3b07c0ee78a9f8099e702020a4d59","unresolved":false,"context_lines":[{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_da11aa53","line":26,"in_reply_to":"1a6eadb0_67759ef8","updated":"2016-12-16 12:23:46.000000000","message":"As someone who used to work for a hardware vendor, I can say that it\u0027s incredibly valuable to encourage as much work as possible to be done within the OpenStack ecosystem. By having driver development done in the community, you immerse the developers in the OpenStack way of doing things, which has many benefits. One is that those developers are more likely to start getting involved with the development of the projects their drivers support. Another is that they become advocates for the OpenStack Way to the management in their company, which can work wonders for the way that company contributes to OpenStack as a whole. It also helps to alleviate the feeling of \"us and them\" which seems to be fueling some of Jay\u0027s concerns (apologies if I\u0027m misrepresenting your position, Jay). Even if the team is *only* contributing vendor drivers, that team is still benefiting the broader OpenStack community. More hardware support leads to more operator adoption, which leads to more user feedback and more development resources. Anything we can do to bring that work into the community benefits us all.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"642cfa2bd5bca93cabf5906ff71192c7c4ffaed3","unresolved":false,"context_lines":[{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_67759ef8","line":26,"in_reply_to":"1a6eadb0_6d0690cf","updated":"2016-12-15 11:03:29.000000000","message":"I see where you are coming from. I can definitely see that half-empty glass, where vendors consider they are contributing enough to \"OpenStack\" by only working on driver teams.\n\nI can also see the glass half-full though -- where welcoming those *inside* our community increases the chances that some of them will contribute to \"the good of the broader community\".\n\nSo the question is: which option is likely to trigger the most \"core\" contributions ? Keeping them out or welcoming them in ?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_480da136","line":26,"in_reply_to":"1a6eadb0_da11aa53","updated":"2016-12-19 05:24:03.000000000","message":"Without repeating what has been echoed by Thierry and John, I totally agree with the points made by both of them. Even when driver folks are working on vendor specific code, they bring wealth of Industry experience to the table. Including them and making them part of the wider community is only beneficial. When they are included, they work hand-in-hand with the core developers to help in many implicit ways (even if they are not explicit upstream developers)","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":1561,"name":"Russell Bryant","email":"rbryant@redhat.com","username":"russellb"},"change_message_id":"6ef5b9021f57a07f8a4e379053fffe93fa97d0e8","unresolved":false,"context_lines":[{"line_number":21,"context_line":"separate drivers. Vendors are of course free to produce drivers to"},{"line_number":22,"context_line":"integrate with OpenStack completely outside of the community, but"},{"line_number":23,"context_line":"because the community values having the drivers as well as the more"},{"line_number":24,"context_line":"general support of vendor companies, we want to encourage a higher"},{"line_number":25,"context_line":"level of engagement by welcoming vendor-specific teams to be a part of"},{"line_number":26,"context_line":"our community governance."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Driver Teams in OpenStack can be created when, for one reason or another,"},{"line_number":29,"context_line":"drivers can\u0027t be directly included in the consuming project code itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_26afc795","line":26,"range":{"start_line":24,"start_character":0,"end_line":26,"end_character":25},"in_reply_to":"ba5201f7_f4ece2f4","updated":"2017-01-09 14:31:09.000000000","message":"My take: even if a contributor only works on a vendor driver, I still find that a valuable, real contribution, and should be treated as such.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"4fcccc6e8860eac7d8510f47f5ee136cab6efb67","unresolved":false,"context_lines":[{"line_number":37,"context_line":""},{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_d46a7e80","line":41,"range":{"start_line":40,"start_character":0,"end_line":41,"end_character":73},"updated":"2017-01-05 19:37:15.000000000","message":"Back to my earlier suggestion, single driver repo for the project named \"project-x:drivers\" then this problem goes away.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"b187d1161e30f4ad1359d0e6b3a7f46a0c081481","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_4442b711","line":41,"updated":"2016-12-13 20:17:52.000000000","message":"Thanks, this is one of the considerations which makes the solution more acceptable for me.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"642cfa2bd5bca93cabf5906ff71192c7c4ffaed3","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_67911ef1","line":41,"in_reply_to":"1a6eadb0_1a1d46bd","updated":"2016-12-15 11:03:29.000000000","message":"We have a precedent here. The \"Winstackers\" does not call itself the \"OpenStack Hyper-V team\".\n\nThe only goal here is that we don\u0027t turn the project team list into a billboard. I\u0027m pretty sure we can find a reasonable middle point.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"76465621c6045383464546f9e10f5d3d4825f8df","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_9fed36f2","line":41,"in_reply_to":"1a6eadb0_1c3f74d7","updated":"2016-12-18 15:52:52.000000000","message":"Correct, I do intend for it to be prohibitively hard for vendors to market their products through our governance documentation, and instead provide them with somewhere easier to do so in ways that don\u0027t encourage them to place additional burdens on the TC (if \"driver teams\" became a popular way to market products and services I would push to dissolve the concept entirely rather than have the TC handle reviewing a never-ending flood of \"me too\" driver team applications).\n\nI don\u0027t expect this to _ever_ provide anything close to a comprehensive list of supported drivers, so I think you\u0027re actually making a better case for ensuring that the marketplace site includes known bug reporting information for every supported driver instead. Making it too easy to look up _some_ driver-specific details on the governance site simply leads to additional confusion as to what operators (and anyone else) should be consulting for the correct driver support information.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"bde4f5ea492c756378edb03c0d97937a8db35394","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_216fc4fc","line":41,"in_reply_to":"1a6eadb0_1d9eaa06","updated":"2016-12-16 20:29:27.000000000","message":"I think you have it backwards. It\u0027s not that I don\u0027t want vendors to have visibility, rather I want vendors to have visibility somewhere else which isn\u0027t conflated with our project governance. Our project governance documents are not an appropriate place to advertise commercial products and services, and we need to take measures to make sure nobody mistakes them as such.\n\nI\u0027d much prefer to have an official place to list drivers without requiring their developers to apply for TC recognition, and let that be the way operators find out where to get their source code, where to report bugs, where to get support and so on. Needing to have an official \"driver team\" before the community can publish information on how users can get in touch with them seems backwards and puts the TC in charge of things it absolutely should not be.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_68dc1d75","line":41,"in_reply_to":"1a6eadb0_1d9eaa06","updated":"2016-12-19 05:24:03.000000000","message":"Right, in neutron we use networking-arista, networking-odl, networking-l2gw, etc. \nThere is nothing wrong if a vendor\u0027s or project\u0027s name is used. \nThis make it easier for the vendors/users rather than trying to figure out which drive maps to which driver/project. \nThis method has worked well in neutron, and, it can work well in a general fashion","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"e1383746c0e47ccfd222f1b5f1531e425928b851","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_798de4d1","line":41,"in_reply_to":"1a6eadb0_1e7f7615","updated":"2016-12-17 15:42:01.000000000","message":"You\u0027re right that my preference is to not have driver teams at all and just require all teams to meet the same sets of requirements instead (whether they produce drivers or anything else). That said, if we do end up with a separate concept of driver teams I want to make sure that we track and list them in ways which cripple the ability to use our governance documentation for marketing commercial products and services. We have other places to do that sort of thing, and having an \"official driver team\" already runs the risk of becoming an additional sales badge for various companies instead of simply reflecting how we allocate community resources.\n\nThe only way I can see to effectively prevent such misuse is to avoid publishing a list of drivers, products or the companies responsible for them (that is what the marketplace should be instead); first, by not listing driver teams somewhere separate from other non-driver teams, and second by making sure that the places where a summary list of teams is published remains free of the names of commercial products and their companies.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"9bf0cae0a6e3ec783487733ed4ba140c7e669956","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_1e7f7615","line":41,"in_reply_to":"1a6eadb0_216fc4fc","updated":"2016-12-17 12:25:07.000000000","message":"Ah, I think I\u0027ve misunderstood your position then. So you\u0027re advocating to reject all driver teams entirely? Not just prevent them from using their actual name in the team name. I don\u0027t think anybody is suggesting that a driver can\u0027t be listed on the marketplace without having an official driver team. Are they? This particular discussion is about what the driver teams that do become official teams should be called.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"5358a2dd1f8de6b3af5f56591c198e426328806b","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_1d9eaa06","line":41,"in_reply_to":"1a6eadb0_2ea17646","updated":"2016-12-16 19:53:01.000000000","message":"It\u0027s not just about finding the driver itself, but knowing where to report bugs, which irc channel to ask questions in, which mailing lists to sign up to, which meetings to join, etc, etc. Neutron alone currently lists 48 drivers, maintained by 29 different vendors. It would be much more straightforward if we could stick to networking-cisco, networking-arista, etc, rather than requiring each team to come up with a unique and vaguely relevant name. Is there any justification for this other than not wanting to provide vendors with visibility?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"911e8276389306a44eee1d93248b22bc4291446f","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_fb607103","line":41,"in_reply_to":"1a6eadb0_2ea17646","updated":"2017-01-05 05:57:55.000000000","message":"isn\u0027t it simpler to drop driver teams when rendering for the governance site, rather than having cryptic names?\ni don\u0027t think operators will look at yaml files to find drivers.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"5d906befa999e33017b28fbe6f7fb284c4142bea","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_cde16400","line":41,"in_reply_to":"1a6eadb0_4442b711","updated":"2016-12-14 14:00:44.000000000","message":"While this does sound appealing, how exactly would this work? How do you call the \"Cisco Networking driver team\" anything other than exactly what it is? It\u0027s a brand/trademark-specific team...\n\nWould you call that team \"networking-[san fran]-cisco\" to get around this requirement?\n\nAnd no, I\u0027m not just picking on Cisco... same goes for any of the proposed driver teams. How would one call the EMC Cinder driver team? block-storage-einstein-relativity?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":11307,"name":"Andreas Scheuring","email":"andreas.scheuring@de.ibm.com","username":"uniqueName"},"change_message_id":"d6cf8e5efd9ae992326f857dd307b4410e0dfad7","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_1a1d46bd","line":41,"in_reply_to":"1a6eadb0_454e0870","updated":"2016-12-14 16:34:19.000000000","message":"I\u0027m totally with Jay here! I wonder how this might work out in practice....","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"d0d3fa1c0cd3b07c0ee78a9f8099e702020a4d59","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_ff61f8d3","line":41,"in_reply_to":"1a6eadb0_67911ef1","updated":"2016-12-16 12:23:46.000000000","message":"Users/operators aren\u0027t going to want to dig out a lookup-table to figure out which project actually contains the driver they need for their hardware. Is including the company name in the project/team name really such a bad thing? The added complexity introduced by preventing it seems to be a bigger problem to me.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"ce3d0d462071755e981ca2cf310ff36a94fe03fe","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_0ca39d9f","line":41,"in_reply_to":"1a6eadb0_68dc1d75","updated":"2016-12-19 17:01:37.000000000","message":"Keep in mind those are the deliverable/repository names and nobody\u0027s suggesting avoiding trademarked terms in them. The only restriction on the table is rejecting trademarked terms in the _team_ names.\n\nWe\u0027d intentionally avoid listing the names of all driver deliverables/repositories across multiple teams in a special place in our governance documentation, instead intermixing them with traditional teams in the reference/projects.yaml file and only listing the names of their teams in the projects index on the governance site (leaving the deliverable/repository names to the team-specific subpages just like we already do for all teams today).","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"4ef83f31546874bcc6219d6b2c60ba747c8a4675","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_1c3f74d7","line":41,"in_reply_to":"1a6eadb0_798de4d1","updated":"2016-12-18 15:17:20.000000000","message":"What do you think about the additional layer of complexity that this will add for operators and users? Obfuscating the purpose of a driver team to this degree is going to cause a lot of headaches, so we have to be sure that the benefits outweigh the negatives.\n\nSo what are the benefits? That vendors will have a harder time marketing their products? Why do you see that as a benefit? It seems to me that anything which drives OpenStack adoption, including hardware support, is a positive thing for the entire community. Forcing a driver team to be called something other than what it really is won\u0027t stop vendors using it to attract customers, it will just make operators lives harder when reporting bugs, finding support, attending meetings etc.\n\nOf course this is mostly speculation on my part. It would be interesting to get an operators perspective on this.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"554624619be4055b805716d6bb43eeb0809d4caf","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_454e0870","line":41,"in_reply_to":"1a6eadb0_cde16400","updated":"2016-12-14 15:28:12.000000000","message":"OpenStack does have a tradition of team/project names that are obscure, e.g., a newcomer has no idea what the Glance Team works on (well, probably Glance, but you know what I mean) without looking it up.\n\nWe could make this requirement more actionable by saying that all driver teams must be named after a color.  Everyone would want to be the Black Driver Team, but first come, first served.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"dd881d27563e89d3f0f176c378354df91730fa28","unresolved":false,"context_lines":[{"line_number":38,"context_line":"* Team Name"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"  * The team name should not include any brand or trademarks -- creating"},{"line_number":41,"context_line":"    a driver team has nothing to do with giving any brand any visibility."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"* Team Scope"},{"line_number":44,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_2ea17646","line":41,"in_reply_to":"1a6eadb0_ff61f8d3","updated":"2016-12-16 17:29:04.000000000","message":"You\u0027ve hit on exactly the reason why this is desirable, in fact. I specifically don\u0027t want our governance documentation turning into the place operators go to find drivers. This is only documenting teams of people and what they do. There should be other, far superior places for the general public to look up information on how to get the right drivers for their hardware/systems. By intentionally making it hard to use our governance site and data as a lookup portal for finding software, we reduce the chances that teams apply for the wrong reasons (like, because they want to be on the same \"list\" as their competitors or peers rather than because they want to participate in our contributor community).","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":13426,"name":"Carol Bouchard","email":"cabthatsme@gmail.com","username":"caboucha"},"change_message_id":"ee6b1f470c954f22d46502c446840544da52d45a","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_d2b821e8","line":49,"range":{"start_line":49,"start_character":23,"end_line":49,"end_character":27},"updated":"2016-12-14 13:46:49.000000000","message":"As a developer of ML2 Cisco Nexus Driver, I plan to use REST APIs as it is much more efficient than current ncclient method.  This is an important change for Nexus driver.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"b187d1161e30f4ad1359d0e6b3a7f46a0c081481","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_6445f315","line":49,"updated":"2016-12-13 20:17:52.000000000","message":"As pointed out before, this may be challenging in places like Neutron where extending the API is expected (but maybe it\u0027s good for us to discourage it anyway?).","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"9689af6c9dafb39ffeaa46ddc09dde9429b51ade","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_202bba95","line":49,"in_reply_to":"1a6eadb0_0830099e","updated":"2016-12-20 20:48:00.000000000","message":"+1 ttx","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":782,"name":"John Garbutt","email":"john@johngarbutt.com","username":"johngarbutt"},"change_message_id":"f1a8a0340f5036c90db3df44d183ed71de905d68","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_0b917f99","line":49,"in_reply_to":"1a6eadb0_0830099e","updated":"2016-12-20 20:56:31.000000000","message":"FWIW, its the end user API changes that are the worst bits here. But I can live with this definition.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"911e8276389306a44eee1d93248b22bc4291446f","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_fb2871e4","line":49,"in_reply_to":"1a6eadb0_0b917f99","updated":"2017-01-05 05:57:55.000000000","message":"FYI in neutron vendor extensions are discouraged these days.\nwe\u0027re trying to consolidate rest api definitions into neutron-lib.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":2243,"name":"John Griffith","email":"john.griffith8@gmail.com","username":"john-griffith"},"change_message_id":"4fcccc6e8860eac7d8510f47f5ee136cab6efb67","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_54804ef7","line":49,"in_reply_to":"1a6eadb0_6445f315","updated":"2017-01-05 19:37:15.000000000","message":"IMO that\u0027s where you promote participation further up the chain, you have some special things in your driver you want to expose, then work on the core pieces to make them usable.\n\nIf you\u0027re going down the path of custom extensions for each driver then honestly I don\u0027t know how anybody can consider the project itself as being an \"integrated component\" let alone the drivers.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"dcb52c980d87e053fb74356382e47a034f831fad","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_a421cbb6","line":49,"in_reply_to":"1a6eadb0_6445f315","updated":"2016-12-13 20:40:59.000000000","message":"In Ironic, we have a vendor_passthru area of our API explicitly intended for extension by vendor drivers. I would prefer this be more weakly-worded.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"9e82ef8d8b57dd1bd64bf66b44531e69fa75f12b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_845f6f40","line":49,"in_reply_to":"1a6eadb0_6445f315","updated":"2016-12-13 20:40:15.000000000","message":"Yes, I would like to get some feedback from the neutron team and the Cisco folks about whether this is going to block their ability to create a useful driver.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":162,"name":"Bob Melander","email":"bob.melander@gmail.com","username":"bob-melander"},"change_message_id":"dd4c94fdbf9d0b746a97e6d15607e5a2743c1c49","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_80456e71","line":49,"in_reply_to":"1a6eadb0_845f6f40","updated":"2016-12-14 19:04:38.000000000","message":"Short answer: Yes it will because our implementations depend on them. We’d therefore prefer the second bullet to be more weakly-worded.\n\nLonger answer: For some of our neutron plugins and drivers we have created extensions.\nThis was basically done to handle gaps in how we could integrate our platforms while meeting customer requirements that were given to us.\n\nWe also care about inter-operability between Openstack clouds. We’ve therefore tried as much as possible to avoid extending Neutron APIs that are consumed by end-users of Neutron.\nHence, the absolute majority of our extensions are for APIs targeting admins of a neutron deployment that uses our platforms. We argue that is an acceptable trade-off that does little to hamper interoperability between Openstack clouds.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":162,"name":"Bob Melander","email":"bob.melander@gmail.com","username":"bob-melander"},"change_message_id":"be52f19774b6eaaa46675e33d19fd84b26c4ada1","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_f7e09898","line":49,"in_reply_to":"1a6eadb0_8dba0cbf","updated":"2016-12-14 20:41:05.000000000","message":"Just to add one more perspective on this.\n\nVendors have customers. They sometimes request that a feature of the underlying vendor platform is exposed in Neutron. Naturally the preferred way is to introduce that feature the community way (and speaking for Cisco, that’s what we normally do). But the feature may be vendor specific or not garner broader interest in the community while still being considered critical for the customer. Additionally, the customer’s Openstack deployment may be entirely internal so interoperability is not an issue. Situations like those are a good fit for vendor specific API extensions.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":13426,"name":"Carol Bouchard","email":"cabthatsme@gmail.com","username":"caboucha"},"change_message_id":"d15f482a0b09fa20a2e9e53b24da06d7d375bb7b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_b12482af","line":49,"in_reply_to":"1a6eadb0_8dba0cbf","updated":"2016-12-14 14:08:31.000000000","message":"What do you propose for a substitute for RESTAPIs to configure vendor devices?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"5d906befa999e33017b28fbe6f7fb284c4142bea","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_8dba0cbf","line":49,"in_reply_to":"1a6eadb0_a421cbb6","updated":"2016-12-14 14:00:44.000000000","message":"The vendor_passthru area in the Ironic API appropriately sandboxes vendor extensions. The problem with it is that it makes Ironic entirely non-interoperable between OpenStack clouds. This isn\u0027t a big deal for Ironic, which doesn\u0027t have a multi-tenant cloud REST API, but for Neutron, these kinds of vendor-specific API extensions totally neuter OpenStack\u0027s official goals of interoperability between OpenStack clouds.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_0830099e","line":49,"in_reply_to":"1a6eadb0_aa4e9b6c","updated":"2016-12-19 05:24:03.000000000","message":"@Thierry - I think your proposed suggestion is reasonable.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"927ec65e1dc1017ce892b5131050bed672f7df87","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_7162eaae","line":49,"in_reply_to":"1a6eadb0_b12482af","updated":"2016-12-14 14:11:48.000000000","message":"@cbouchard: Configure vendor devices via vendor-specific APIs and don\u0027t pollute the OpenStack REST APIs with vendor-device configuration specifics. Keep all that stuff abstracted behind stable driver interfaces.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"642cfa2bd5bca93cabf5906ff71192c7c4ffaed3","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_aa4e9b6c","line":49,"in_reply_to":"1a6eadb0_b21f0e07","updated":"2016-12-15 11:03:29.000000000","message":"How about: \"The proposed deliverables do not extend the REST APIs of the services consuming them (unless the main project plug-in point is specifically about providing such a controlled API extension point)\" ?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"99c1801d18765d4b98d11a63476a2fee4bfb1f7b","unresolved":false,"context_lines":[{"line_number":46,"context_line":"    plug-in points in OpenStack projects"},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"  * The proposed deliverables do not extend the REST APIs of the"},{"line_number":49,"context_line":"    services consuming them"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Community Engagement"},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_b21f0e07","line":49,"in_reply_to":"1a6eadb0_f7e09898","updated":"2016-12-14 20:54:36.000000000","message":"@bobmelander: No disagreement from me on that. still doesn\u0027t change my view regarding the \"OpenStack officialness\" of vendor/driver teams, though.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6635,"name":"John Davidge","email":"john.davidge@rackspace.com","username":"john-davidge"},"change_message_id":"d0d3fa1c0cd3b07c0ee78a9f8099e702020a4d59","unresolved":false,"context_lines":[{"line_number":62,"context_line":"  * The team provides liaisons that serve as contacts for the work of"},{"line_number":63,"context_line":"    cross-project teams in OpenStack, where needed"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_9f280435","line":65,"range":{"start_line":65,"start_character":25,"end_line":65,"end_character":28},"updated":"2016-12-16 12:23:46.000000000","message":"Should this be two? Or are we encouraging teams to merge patches with approval from a single core?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":62,"context_line":"  * The team provides liaisons that serve as contacts for the work of"},{"line_number":63,"context_line":"    cross-project teams in OpenStack, where needed"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_28dce545","line":65,"range":{"start_line":65,"start_character":25,"end_line":65,"end_character":28},"in_reply_to":"1a6eadb0_9f280435","updated":"2016-12-19 05:24:03.000000000","message":"Currently, one core is allowed to merge the patches in off-tree projects. It is usually \"recommended\" that two cores approve. \nSo, I would say the statement as-is fine","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"b187d1161e30f4ad1359d0e6b3a7f46a0c081481","unresolved":false,"context_lines":[{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Openness"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_844ccf43","line":68,"updated":"2016-12-13 20:17:52.000000000","message":"Not to be conflated with third-party testing which may or may not be required by the service projects with which these drivers integrate.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"554624619be4055b805716d6bb43eeb0809d4caf","unresolved":false,"context_lines":[{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Openness"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_e5f554cb","line":68,"in_reply_to":"1a6eadb0_0dcefc59","updated":"2016-12-14 15:28:12.000000000","message":"I have the same question.  It would be good to state explicitly whether the TC will periodically review Driver Teams for compliance, and if so, what frequency is proposed.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"5d906befa999e33017b28fbe6f7fb284c4142bea","unresolved":false,"context_lines":[{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Openness"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_0dcefc59","line":68,"in_reply_to":"1a6eadb0_844ccf43","updated":"2016-12-14 14:00:44.000000000","message":"All of the above requirements are great, but how will they be enforced? By the project team? By the TC? By the community at large complaining about things?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Openness"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_88ac1937","line":68,"in_reply_to":"1a6eadb0_e5f554cb","updated":"2016-12-19 05:24:03.000000000","message":"I think TC should put of general guidelines and leave the details/specifics to the sub-teams. There should be a list of conformance requirements. As long the sub-project meets the list, it is in compliance. \nFor example, one driver may require only one page worth of documentation vs the other may require 50 pages manual. The details should be left to the sub-team. As long there exists a bonafide documentation (in this example), the sub-project is in compliance - unless there is explicit objection is raise by any community member.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"642cfa2bd5bca93cabf5906ff71192c7c4ffaed3","unresolved":false,"context_lines":[{"line_number":65,"context_line":"  * The team should have one or more active contributors"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"  * The team meets any policies that the TC requires all deliverables"},{"line_number":68,"context_line":"    to meet. For instance, the :doc:`project-testing-interface`"},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Openness"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_4ac34789","line":68,"in_reply_to":"1a6eadb0_e5f554cb","updated":"2016-12-15 11:03:29.000000000","message":"There is nothing specific to driver teams here : all the teams have requirements. The TC used to \"review\" all teams periodically but that was not the best use of our time -- we now address complaints when they are raised (by TC members or anyone else in the community) and don\u0027t find resolution through simpler ways.\n\nFor example the Kolla video meeting discussion is a case of potential requirement violation. If the ML thread does not reach satisfactory resolution, I expect the TC to look into the case.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"b187d1161e30f4ad1359d0e6b3a7f46a0c081481","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  * The team uses public code reviews on the OpenStack infrastructure"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"  * The team has core reviewers and adopts a test-driven gate in the"},{"line_number":79,"context_line":"    OpenStack infrastructure for changes"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to do an evaluation against this criteria, the TC expects the"},{"line_number":82,"context_line":"team to be set up and have some history to evaluate.  A few weeks of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_a4470b1c","line":79,"updated":"2016-12-13 20:17:52.000000000","message":"In the case of drivers for proprietary devices/software, their upstream testing may end up limited to static analysis and unit tests.","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6558,"name":"Sukhdev Kapur","email":"sukhdevkapur@gmail.com","username":"sukhdev-8"},"change_message_id":"d7ab87d6a1004a932add289cce47b83a069820ca","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  * The team uses public code reviews on the OpenStack infrastructure"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"  * The team has core reviewers and adopts a test-driven gate in the"},{"line_number":79,"context_line":"    OpenStack infrastructure for changes"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to do an evaluation against this criteria, the TC expects the"},{"line_number":82,"context_line":"team to be set up and have some history to evaluate.  A few weeks of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a6eadb0_e8dbcd1f","line":79,"in_reply_to":"1a6eadb0_a4470b1c","updated":"2016-12-19 05:24:03.000000000","message":"Yes and No. For example in case Neutron, if we required that all in-tree drivers be configured in the neutron configuration, all of these will be tested for full API compatibility. For example, the scenario/functional test invoke neutron APIs, which will force invocations on all in-tree drivers. If any of the drivers fail, the core team for sub-project should be required to address it. Does it make sense?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"911e8276389306a44eee1d93248b22bc4291446f","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  * The team uses public code reviews on the OpenStack infrastructure"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"  * The team has core reviewers and adopts a test-driven gate in the"},{"line_number":79,"context_line":"    OpenStack infrastructure for changes"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"In order to do an evaluation against this criteria, the TC expects the"},{"line_number":82,"context_line":"team to be set up and have some history to evaluate.  A few weeks of"}],"source_content_type":"text/x-rst","patch_set":4,"id":"ba5201f7_e6437840","line":79,"in_reply_to":"1a6eadb0_e8dbcd1f","updated":"2017-01-05 05:57:55.000000000","message":"Sukhdev,\n\ni\u0027m not sure what you mean.\nhow drivers for proprietary stuff can work on the upstream CI environment?","commit_id":"1470060659cef638ef1f9f56bfa29b46d7d2846b"}]}
