openstack/governance
Code Issues Proposed changes

Merge "Handling the OpenStack name in external services"

Browse Source
This commit is contained in:
Zuul 2020-04-01 07:53:51 +00:00 committed by Gerrit Code Review
commit 6c91b455c5
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
reference/OpenStack-name-in-external-services.rst Normal file
View File

@ -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

1
reference/index.rst
View File

@ -32,3 +32,4 @@ Reference documents which need to be revised over time.
house-rules
comparison-of-official-group-structures
joining-tc
OpenStack-name-in-external-services