Excerpts from Jeremy Stanley's message of 2018-06-06 20:09:36 +:
> On 2018-06-06 14:52:04 -0400 (-0400), Zane Bitter wrote:
> > On 29/05/18 13:37, Jeremy Stanley wrote:
> > > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
> [...]
> > > > * If the repo is a fork of another project, the
Excerpts from Anne Bertucio's message of 2018-06-06 12:28:25 -0700:
> > Either way, I would like to ensure that someone from
> > Kata is communicating with qemu upstream.
>
> Since probably not too many Kata folks are on the OpenStack dev list
> (something to tackle in another thread or OSF all-p
On 2018-06-06 15:16:59 -0400 (-0400), Doug Hellmann wrote:
[...]
> Kata also has a qemu fork, but that is under the kata-containers
> github org and not our infrastructure. I'm not sure someone outside
> of our community would differentiate between the two, but maybe
> they would.
[...]
The Kata c
On 2018-06-06 14:52:04 -0400 (-0400), Zane Bitter wrote:
> On 29/05/18 13:37, Jeremy Stanley wrote:
> > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
[...]
> > > * If the repo is a fork of another project, there must be (public)
> > > evidence of an attempt to co-ordinate with the upstre
> Either way, I would like to ensure that someone from
> Kata is communicating with qemu upstream.
Since probably not too many Kata folks are on the OpenStack dev list (something
to tackle in another thread or OSF all-project meeting), chiming in to say
yup!, we’ve got QEMU upstream folks in the
Excerpts from Zane Bitter's message of 2018-06-06 14:52:04 -0400:
> On 29/05/18 13:37, Jeremy Stanley wrote:
> > On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
> >> We allow various open source projects that are not an official
> >> part of OpenStack or necessarily used by OpenStack to be
On 29/05/18 13:37, Jeremy Stanley wrote:
On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
We allow various open source projects that are not an official
part of OpenStack or necessarily used by OpenStack to be hosted on
OpenStack infrastructure - previously under the 'StackForge'
brandin
Jeremy Stanley wrote:
On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
It is my understanding that the infra team will enforce the
following conditions when a repo import request is received:
* The repo must be licensed under an OSI-approved open source
license.
That has been our cust
On 2018-05-29 10:53:03 -0400 (-0400), Zane Bitter wrote:
> We allow various open source projects that are not an official
> part of OpenStack or necessarily used by OpenStack to be hosted on
> OpenStack infrastructure - previously under the 'StackForge'
> branding, but now without separate branding
