)]}'
{"reference/new-projects-requirements.rst":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"8f580c63baec56a636599af49fe933eb45b92036","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project already meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a41bdd9_16a618ae","line":58,"updated":"2015-07-14 20:45:24.000000000","message":"I\u0027d drop \"already\" to more closely match how the other requirements are introduced.","commit_id":"aadf07c986f3c4fe3f10071c470caaa0081d626f"},{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"3ba642f840974a3c4f59ab412bbac41da87f3542","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project already meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a41bdd9_7601a469","line":58,"in_reply_to":"9a41bdd9_16a618ae","updated":"2015-07-14 20:47:25.000000000","message":"Done","commit_id":"aadf07c986f3c4fe3f10071c470caaa0081d626f"},{"author":{"_account_id":8787,"name":"Dmitry Borodaenko","email":"angdraug@gmail.com","username":"angdraug"},"change_message_id":"b2515c04c39b07f6062995772e9e7d9b18f41404","unresolved":false,"context_lines":[{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Once a project has joined OpenStack, it may create additional source code"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9a41bdd9_ddb9f1ed","line":59,"updated":"2015-07-18 00:06:26.000000000","message":"Without an explicit reference to a document where *all* \"policies that the TC requires all projects to meet\" are enumerated, this requirement is vague enough to allow TC to impose arbitrary policy requirements on different projects from a potentially infinite set of \"any policy documented anywhere\". I suspect this was not the original intent of adding this requirement.\n\nA secondary but also important concern is that project-testing-interface does not make a consistent distinction between \"must\" and \"should\" requirements. If it becomes part of formal criteria for all new projects, it should be more straightforward about what is and isn\u0027t required.\n\nIn particular, the requirement to adopt a test-driven gate *in the OpenStack infrastructure\" should become part of project-testing-interface. Right now that document doesn\u0027t mention gate jobs at all.","commit_id":"127389fa43c7d35924a8ed7528084b1f9eff7b8a"},{"author":{"_account_id":8787,"name":"Dmitry Borodaenko","email":"angdraug@gmail.com","username":"angdraug"},"change_message_id":"ce92dcd53fec39c9517b0eb8153c57b5b069169c","unresolved":false,"context_lines":[{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Once a project has joined OpenStack, it may create additional source code"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_a5f38b9d","line":59,"in_reply_to":"3a50d1a3_6d1aba70","updated":"2015-07-21 20:06:36.000000000","message":"Making \"policies that the TC requires all projects to meet\" a hyperlink to governance.openstack.org would be enough to solve my primary concern.","commit_id":"127389fa43c7d35924a8ed7528084b1f9eff7b8a"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"5054d18c4412b66543da73625646790c7b5716b7","unresolved":false,"context_lines":[{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Once a project has joined OpenStack, it may create additional source code"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_b237bde2","line":59,"in_reply_to":"9a41bdd9_ddb9f1ed","updated":"2015-07-19 20:34:20.000000000","message":"I think \"policies\" means resolutions and reference documents as documented on the governance repository (and published in governance.openstack.org). \n\nAt least that\u0027s how I understand \"any policies the TC requires projects to meet\".\n\nNote that beyond \"policies\", the \"OpenStack way\" as mentioned at the top of this document is not a checklist, it\u0027s more a behavior and alignment on shared culture, and that is slightly more subjective. We\u0027ve been writing the project team guide to better document that.","commit_id":"127389fa43c7d35924a8ed7528084b1f9eff7b8a"},{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"91d1f090ba9d0878dec1eec1db83d1db6ba98166","unresolved":false,"context_lines":[{"line_number":56,"context_line":"* The project should have an active team of one or more contributors"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* The project meets any policies that the TC requires all projects to"},{"line_number":59,"context_line":"  meet. For instance, the :doc:`project-testing-interface`"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"Once a project has joined OpenStack, it may create additional source code"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_6d1aba70","line":59,"in_reply_to":"9a41bdd9_ddb9f1ed","updated":"2015-07-19 22:50:17.000000000","message":"The intent is to make clear that the list here \u0027new projects\u0027 is only a summary, that the full set set of policies applicable to all projects is also applicable to new projects. That wasn\u0027t previously called out, but it was the understanding of the TC. We uncovered this gap at the last TC meeting.\n\nAs written it does *not* allow arbitrary or inconsistent application because it says \u0027TC requires all projects\u0027, not \u0027TC requires some projects\u0027 :)\n\nI\u0027m not against further tweaking of our docs as a whole - please do push up a change proposal to make things clearer, but I don\u0027t see anything wrong or misleading about this particular change as-is.","commit_id":"127389fa43c7d35924a8ed7528084b1f9eff7b8a"}]}