Open Stack

Excerpts from Fox, Kevin M's message of 2016-05-04 16:49:42 +0000:
> Ok. Sure. More generically then. There are OpenStack compatible API implementations existing in the world, deployed by a not insignificant number of production clouds, that are currently outside the big tent that may have not considered proposing joining the community because of the past history of Python onlyness in the community. If we're considering Go, should we also be considering C++? Go currently has no production level OpenStack code finished. C++ does.

Independent of the implementation language question, we also have a
policy against "gratuitous" competition:

  Where it makes sense, the project cooperates with existing projects
  rather than gratuitously competing or reinventing the wheel [1]

So, a project that re-implements an existing official project is unlikely
to be a good candidate for official status, no matter what language it
was written in (especially if it was produced following processes that
don't follow the other 4 Open tenets that make up the foundation of our
policy). Although, we haven't had a real case of this, and there are
bound to be case-specific issues that could negate my generalization,
and I'm only one member of the TC.

The policy has, AIUI, always been that if someone wants to use something
other than one of our existing languages, they need to establish both
a really good reason why that is true (to overcome the objections based
on the amount of duplication that might be needed to do things currently
handled by libraries being shared between projects) *and* to step up to
establish the patterns and interfaces to be used to work within our CI
system for all appropriate testing. So, objections to the contrary, I'm
not sure it's useful to continue talking about this in the abstract. If
there's a project that wants to join, we should talk about that project
and whether it meets *all* of our criteria, not just what language it's
in. Hypothetical proposals about projects that aren't actually interested
in joining OpenStack aren't going to lead to useful discussion.

Doug

[1] http://governance.openstack.org/reference/new-projects-requirements.html



> 
> Thanks,
> Kevin
> ________________________________________
> From: Shinobu Kinjo [shinobu.kj at gmail.com]
> Sent: Wednesday, May 04, 2016 3:32 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [tc] supporting Go
> 
> - Could we kindly stop discussing radosgw at this moment?
> + Could we kindly stop discussing any particular application at this moment?
> 
> On Wed, May 4, 2016 at 7:02 PM, Shinobu Kinjo <shinobu.kj at gmail.com> wrote:
> > Could we kindly stop discussing radosgw at this moment?
> >
> > On Wed, May 4, 2016 at 6:47 PM, Thierry Carrez <thierry at openstack.org> wrote:
> >> Fox, Kevin M wrote:
> >>>
> >>> RadosGW has been excluded from joining the OpenStack community in part due
> >>> to its use of c++.
> >>
> >>
> >> I'm not sure I'd use the word "excluded" since RadosGW was never actually
> >> proposed. Maybe our past Python-centricity discouraged them to apply, but
> >> that's conjecture.
> >>
> >>> Now that we're talking about alternate languages, that may be on the table
> >>> now?
> >>
> >>
> >> It's been a possibility for the last 8 months.
> >>
> >> That said, my personal view is that we should accept additional languages
> >> when the current set of accepted languages is suboptimal for something we
> >> want to write or create. A technical benefit to outweigh the community
> >> fragmentation and increase in infrastructure tasks that result from adding
> >> that language.
> >>
> >> I'm less convinced that we should add a language for the sole benefit of
> >> being able to absorb an existing project into OpenStack which happens to be
> >> written in a specific language. Especially if the then-supported set of
> >> languages could provide the same technical benefits.
> >>
> >> --
> >> Thierry Carrez (ttx)
> >>
> >>
> >> __________________________________________________________________________
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> >
> > --
> > Email:
> > shinobu at linux.com
> > shinobu at redhat.com
>