)]}'
{"reference/licensing.rst":[{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"7331c1ad4fa2e6b4905885c15f7d5ff43d1219e5","unresolved":false,"context_lines":[{"line_number":32,"context_line":"**Projects run as part of the OpenStack Infrastructure** (in order to"},{"line_number":33,"context_line":"*produce* OpenStack software) may be licensed under any `OSI-approved license`_."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"This includes tools that are run with or on OpenStack projects only"},{"line_number":36,"context_line":"during validation or testing phases of development (e.g., a source"},{"line_number":37,"context_line":"code linter)."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dae33548_2be445df","line":35,"updated":"2016-02-17 06:09:47.000000000","message":"Doug, I do not believe this is a policy change.  The project under discussion is intended to be used in testing, just as other GPL software is currently used in testing.  This patch does not change policy, it only clarifies it.","commit_id":"17bc0415bc3d6a4049e9273f853a561ad6d0904e"},{"author":{"_account_id":5638,"name":"Davanum Srinivas","email":"davanum@gmail.com","username":"dims-v"},"change_message_id":"b4bb016ef087dcf8f1769ba1a8cd9ef09b059fb4","unresolved":false,"context_lines":[{"line_number":32,"context_line":"**Projects run as part of the OpenStack Infrastructure** (in order to"},{"line_number":33,"context_line":"*produce* OpenStack software) may be licensed under any `OSI-approved license`_."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"This includes tools that are run with or on OpenStack projects only"},{"line_number":36,"context_line":"during validation or testing phases of development (e.g., a source"},{"line_number":37,"context_line":"code linter)."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dae33548_a320f9f8","line":35,"updated":"2016-02-14 16:45:20.000000000","message":"Here\u0027s a catch - We currently cannot make sure things specified in g-r can occur only on test-requirements. Nor can we make sure that code that we ship are used only in tests and not in the main source code. Say neutron folks see scapy and add imports in the main line neutron code to \"import scapy\" and use it, we cannot prevent that from happening.\n\nSo at this point this means that we cannot add such code to global-requirements.txt, These can be baked into images or some other infrastructure components in the CI pipeline can install them for projects that require them.","commit_id":"17bc0415bc3d6a4049e9273f853a561ad6d0904e"},{"author":{"_account_id":1,"name":"James E. Blair","email":"jim@acmegating.com","username":"corvus"},"change_message_id":"3410afb01d74d42d0babebe4bb2de1619f5d61e5","unresolved":false,"context_lines":[{"line_number":32,"context_line":"**Projects run as part of the OpenStack Infrastructure** (in order to"},{"line_number":33,"context_line":"*produce* OpenStack software) may be licensed under any `OSI-approved license`_."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"This includes tools that are run with or on OpenStack projects only"},{"line_number":36,"context_line":"during validation or testing phases of development (e.g., a source"},{"line_number":37,"context_line":"code linter)."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dae33548_e1f57dcb","line":35,"updated":"2016-02-16 16:45:38.000000000","message":"These are implementation details about the global requirements project that I don\u0027t think impact our policy declaration here.  This is a document that describes what is permissible for OpenStack projects to do, and it is certainly permissible for them to use any FOSS software in their testing (they already do and have done so for years).\n\nEven so -- the purpose of the global requirements repo is to help converge on versions of software that projects use and to ensure that the deployment community is involved in the addition of new dependencies.  It defines a superset of components that projects can use both as direct dependencies and development dependencies.  We *used* to maintain a separate testing requirements file in the repo, but decided that was too complex.  Nonetheless it is still the intent for test-only dependencies to be listed in g-r to help projects and deployers converge on versions in use.","commit_id":"17bc0415bc3d6a4049e9273f853a561ad6d0904e"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b35de823a1ea0957a1330b694c3e46504195c7a3","unresolved":false,"context_lines":[{"line_number":32,"context_line":"**Projects run as part of the OpenStack Infrastructure** (in order to"},{"line_number":33,"context_line":"*produce* OpenStack software) may be licensed under any `OSI-approved license`_."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"This includes tools that are run with or on OpenStack projects only"},{"line_number":36,"context_line":"during validation or testing phases of development (e.g., a source"},{"line_number":37,"context_line":"code linter)."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dae33548_9c1e5db9","line":35,"in_reply_to":"dae33548_2be445df","updated":"2016-02-17 15:24:57.000000000","message":"Sorry, poor choice of words on my part. I just meant this patch, and didn\u0027t mean to imply that the policy itself was being modified beyond the clarification.\n\nWhat I want to avoid is having lots of folks try to add GPL things to the requirements file, without any way for reviewers of that file to know that it is safe to approve the additions and we won\u0027t end up introducing them as production dependencies. I do agree that we should clarify that it\u0027s fine to use GPL tools for testing.","commit_id":"17bc0415bc3d6a4049e9273f853a561ad6d0904e"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"56bdd16afb7ad839bc95780bb8c411dd380e6c5e","unresolved":false,"context_lines":[{"line_number":32,"context_line":"**Projects run as part of the OpenStack Infrastructure** (in order to"},{"line_number":33,"context_line":"*produce* OpenStack software) may be licensed under any `OSI-approved license`_."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"This includes tools that are run with or on OpenStack projects only"},{"line_number":36,"context_line":"during validation or testing phases of development (e.g., a source"},{"line_number":37,"context_line":"code linter)."},{"line_number":38,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"dae33548_9713130d","line":35,"in_reply_to":"dae33548_e1f57dcb","updated":"2016-02-16 17:18:02.000000000","message":"I would like to see something in the requirements project to support the split, to go along with the policy change here. Up until now most of the GPL tools have been clearly things one would not use at runtime, like a linter. The new case that triggered this update is a library that, IIUC, might be useful at runtime. I\u0027d at least like to see a plan for how we intend to ensure those dependencies are only in test-requirements.txt and never in requirements.txt.","commit_id":"17bc0415bc3d6a4049e9273f853a561ad6d0904e"}]}
