[openstack-dev] [tc] StarlingX project status update

Emilien Macchi emilien at redhat.com
Tue Jun 12 14:54:59 UTC 2018


On Tue, Jun 12, 2018 at 7:46 AM, Doug Hellmann <doug at doughellmann.com>
wrote:

> Excerpts from Dean Troyer's message of 2018-06-12 09:28:48 -0500:
> > On Mon, Jun 11, 2018 at 5:02 PM, Emilien Macchi <emilien at redhat.com>
> wrote:
> > > While I agree with Doug that we assume good faith and hope for the
> best, I
> > > personally think we should help them (what we're doing now) but also
> make
> > > sure we DO NOT set a precedent. We could probably learn from this
> situation
> > > and document in our governance what the TC expects when companies have
> a
> > > fork and need to contribute back at some point. We all know StarlingX
> isn't
> > > alone and I'm pretty sure there are a lot of deployments out there who
> are
> > > in the same situation.
> >
> > /me pus on ex-TC hat for a minute
> >
> > Emilien, I totally agree with you here but would word it differently:
> > we should absolutely set a precedent, but one that exhibits how we
> > want to handle what ttx calls 'convergent' forks.  These already
> > exist, like it or not.  What I hope can be established is some
> > guidelines and boundaries on how to deal with these rather than just
> > reject them out-of-hand.
>
> Yes, well said.


Indeed, thanks Dean.
-- 
Emilien Macchi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180612/ff7f7a29/attachment.html>


More information about the OpenStack-dev mailing list