Limit the locales that can be requested for projects
This issue was created automatically by a script.
Bug 1636505
Bug Reporter: @flodolo CC: @guerojeff, @mathjazz, @peiying2
Currently, there are at least two problematic scenarios.
Exclude locales from a project
We enabled a generic locale, and we don't want to enable region specific locales. This typically happens with es and es-*, but also other locales (bn, pt).
Periodically people request the unsupported version (e.g. es-ES when es is used), and if the PM in charge forgets, we end up with a locale that will need to be dropped. If they remember, they still need to answer the request and explain why it can't be satisfied. This is error prone and wastes everybody's time.
It would be really useful to be able to exclude some locales from a project, so that they cannot be requested at all.
Given that a locale can only be in one state at a time (can be requested, active, read-only, cannot be requested) it could be a fourth column in the admin panel.
Flag a locale as cannot be requested
We create locales only for one project, and don't want to use them anywhere else. This is happening more and more for Common Voice.
It would be great to flag the locale so that it cannot be requested at all. Admins would still be able to add it in project admin, because it would show up in the list of available locales, but the button to request project would be disabled in the teams page, and the locale would not show up when requesting locales for a project.