2015-09-01 OpenStack Programming Languages¶
Because we recognize these considerations, the OpenStack Technical Committee will allow additional language support in OpenStack projects on a case-by-case basis, carefully weighing the technical benefits of supporting the new language against the community costs of supporting it.
We already recognize a number of standing exceptions to this rule:
- short-term experimentations in feature branches
- temporary legacy code, as long as the medium-term plan is to completely remove it
- downstream packaging, which uses the specific language of that particular trade (like Ruby Puppet recipes)
- project infrastructure configuration files, plug-ins or extensions, where the language is dictated by the tool being used or integrated
- downstream language SDKs, which obviously are implemented in the local idiom
The general idea is that this resolution applies to upstream OpenStack services and libraries which are our main deliverables, not to downstream integration projects or development infrastructure. The Technical Committee will use common sense when considering those requests on a case-by-case basis.