Open Stack

Morgan Fainberg wrote:
> [...]  If we are accepting golang, I want it to be clearly
> documented that the expectation is it is used exclusively where there is
> a demonstrable case (such as with swift) and not a carte blanche to use
> it wherever-you-please.
>
> I want this to be a social contract looked at and enforced by the
> community, not special permissions that are granted by the TC (I don't
> want the TC to need to step in an approve every single use case of
> golang, or javascript ...). It's bottlenecking back to the TC for
> special permissions or inclusion (see reasons for the dissolution of the
> "integrated release").
>
> This isn't strictly an all or nothing case, this is a "how would we
> enforce this?" type deal. Lean on infra to enforce that only projects
> with the golang-is-ok-here tag are allowed to use it? I don't want
> people to write their APIs in javascript (and node.js) nor in golang. I
> would like to see most of the work continue with python as the primary
> language. I just think it's unreasonable to lock tools behind a gate
> that is stronger than the social / community contract (and outlined in
> the resolution including X language).

+1

I'd prefer if we didn't have to special-case anyone, and we could come 
up with general rules that every OpenStack project follows. Any other 
solution is an administrative nightmare and a source of tension between 
projects (why are they special and not me).

-- 
Thierry Carrez (ttx)