From a729d8a58643fb494be705bf108180b7ae86dbdf Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Wed, 26 Feb 2020 15:48:01 +0100 Subject: [PATCH] Handling the OpenStack name in external services Without this patch, one might wonder which team owns the "OpenStack" name in an external service. This should clarify the current ownership for a few known services. Change-Id: I88996e3302f9bee7c3ab81bd0f5017f300590616 --- .../OpenStack-name-in-external-services.rst | 24 +++++++++++++++++++ reference/index.rst | 1 + 2 files changed, 25 insertions(+) create mode 100644 reference/OpenStack-name-in-external-services.rst diff --git a/reference/OpenStack-name-in-external-services.rst b/reference/OpenStack-name-in-external-services.rst new file mode 100644 index 000000000..5e4d717fc --- /dev/null +++ b/reference/OpenStack-name-in-external-services.rst @@ -0,0 +1,24 @@ +================================================== + Handling the OpenStack name in external services +================================================== + +The OpenStack projects are building and producing artifacts outside its own +infrastructure, like python packaging on PyPI, container images on docker hub, +etc. + +When an external service can hold an official "OpenStack" namespace or user, +we should clarify which teams are responsible for it. Please note that +the team can delegate the credentials management to a different team, like +the OpenStack-infra team for example. + +.. list-table:: + :header-rows: 1 + + * - Service name + - Team + * - supermarket.chef.io + - openstack-chef team + * - jaas.ai + - OpenStack Charms team + * - galaxy.ansible.com + - Ansible SIG diff --git a/reference/index.rst b/reference/index.rst index 69c9cb244..c3d0bdf69 100644 --- a/reference/index.rst +++ b/reference/index.rst @@ -31,3 +31,4 @@ Reference documents which need to be revised over time. house-rules comparison-of-official-group-structures joining-tc + OpenStack-name-in-external-services