Open Stack

Tom Fifield wrote:
>> Translations is another "horizontal effort", something that applies to
>> all projects, like release management or vulnerability handling, but
>> where contributions actually end up being applied as patches to other
>> projects, rather than having their own repos. Another example of that
>> would be the "Python 3" effort.
>>
>> We have yet to decide if those should be considered programs, or if they
>> should be recognized in some other way that is not a "program". That
>> shouldn't block the setup of the first programs though.
>>
>> Regards,
> 
> """
> 'OpenStack Programs' are efforts which are essential to the completion
> of our mission, but which do not produce deliverables included in the
> common release of OpenStack 'integrated' projects every 6 months, like
> Projects do.
> """
> 
> How is this not true of Translation?

It's not as clear of a slam dunk as the other (initial) programs due to
the nature of their "deliverable", which is consumed by the projects
themselves, so it's a bit of a corner case. Additionally, the reach of
the Technical Committee is supposedly limited to "technical" matters, so
we would have to rule that a message translation is a technical
contribution, and therefore under the oversight of the TC (rather than,
say, user committee or marketing team). Not saying it's not the case,
just saying we would need to discuss that in detail.

Mind you, I'm not closing the door or anything: translations can
certainly apply to become a program (once/when we establish them). The
goal of the "initial batch" is to catch up with the current state of
"official projects", not to come up with a definitive or closed list.

-- 
Thierry Carrez (ttx)