)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"8755f9ad4b29f816c286e99723f7a861e21eed4d","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Use the opendev/python-builder opendev/python-base pair to make a"},{"line_number":15,"context_line":"minimal image that contains an install of python-openstackclient"},{"line_number":16,"context_line":"and publish it to the osclient org on dockerhub. There is an overall"},{"line_number":17,"context_line":"policy against having binary artifacts such as this appear to be"},{"line_number":18,"context_line":"official deliverables of the OpenStack project, which this is not."},{"line_number":19,"context_line":"It\u0027s also only publishing images based on master, so no warranties"},{"line_number":20,"context_line":"should be implied. But if this makes life easier for a user somewhere,"},{"line_number":21,"context_line":"cool."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"1fa4df85_32688085","line":18,"range":{"start_line":16,"start_character":49,"end_line":18,"end_character":66},"updated":"2020-03-05 13:43:21.000000000","message":"Can you cite this policy? If OpenStack has a policy against publishing binary artifacts, we should not do this. Maybe then it would better happen under the OpenDev tent?","commit_id":"a403c67038c47b30164718c5b74f65682bad7480"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"66b832c4719bd307b14debefd62d4daf08c47dfd","unresolved":false,"context_lines":[{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Use the opendev/python-builder opendev/python-base pair to make a"},{"line_number":15,"context_line":"minimal image that contains an install of python-openstackclient"},{"line_number":16,"context_line":"and publish it to the osclient org on dockerhub. There is an overall"},{"line_number":17,"context_line":"policy against having binary artifacts such as this appear to be"},{"line_number":18,"context_line":"official deliverables of the OpenStack project, which this is not."},{"line_number":19,"context_line":"It\u0027s also only publishing images based on master, so no warranties"},{"line_number":20,"context_line":"should be implied. But if this makes life easier for a user somewhere,"},{"line_number":21,"context_line":"cool."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"1fa4df85_de3d738f","line":18,"range":{"start_line":16,"start_character":49,"end_line":18,"end_character":66},"in_reply_to":"1fa4df85_32688085","updated":"2020-03-05 16:38:14.000000000","message":"The policy is here:\n\nhttps://governance.openstack.org/tc/resolutions/20170530-binary-artifacts.html#guidelines\n\nThe main crux is that we should not provide artifacts that make it seem like they are \"official output\" of the openstack project - which is why this is being published to osclient/ and not openstack/ ... this is a very common pattern - magnum, kolla and loci off the top of my head all publish images to non-openstack namespaces because they need to publish images somewhere but as a whole we don\u0027t want to centrally publish those to an openstack/ branded location and imply some sort of project warranty.","commit_id":"a403c67038c47b30164718c5b74f65682bad7480"}]}