aclfixer.py: Document standing exceptions
Deliverables under TC governance should have their release process handled by the Release Management team. However, there are a number of exceptions to the rule: deployment tools may have their artifacts released using an ecosystem-specific toolchain. Some teams might be in the process of leaving TC governance and adjusting their ACLS would be counter-productive. Change-Id: Ia304de2eea2364a990b17343879fe26b904706e1
This commit is contained in:
parent
d0cb7b9698
commit
8306df6759
@ -27,12 +27,17 @@ import yaml
|
||||
|
||||
|
||||
TEAM_EXCEPTIONS = [
|
||||
# Teams that are likely to be moved off TC governance
|
||||
'Infrastructure',
|
||||
'RefStack',
|
||||
|
||||
# Deployment tool teams with externally-released artifacts
|
||||
'OpenStack Charms',
|
||||
'Chef OpenStack',
|
||||
'OpenStack-Helm',
|
||||
|
||||
# Others
|
||||
'rally',
|
||||
'RefStack',
|
||||
]
|
||||
|
||||
WILDCARD_REPO_EXCEPTIONS = [
|
||||
|
Loading…
Reference in New Issue
Block a user