Fox, Kevin M wrote:
[...]
Part of the disconnect to me has been that these questions have been left up to
the projects by and large. But, users don't use the projects. Users use
OpenStack. Or, moving forward, they at least use a Constellation. But
Constellation is still just a documentation co
On 5/11/2018 2:00 PM, Fox, Kevin M wrote:
Currently the isolation between the Projects and the thing that the users use, the
Constellation allows for user needs to easily slip through the cracks. Cause
"Project X: we agree that is a problem, but its Y projects problem. Project Y: we
agree that
; though. And we can't even really define what a user is. This is a big problem.
>
> Anyway, more Leadership please! Ready. GO! :)
>
> Thanks,
> Kevin
>
>
> From: Jay Pipes [jaypi...@gmail.com]
> Sent: Friday, May 11, 2018
From: Jay Pipes [jaypi...@gmail.com]
Sent: Friday, May 11, 2018 9:31 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in
Vancouver
On 05/11/2018 12:21 PM, Zane Bitter wrote:
On 11/05/18 11:46, Jay Pipes w
t even really define what a user is. This is a big problem.
Anyway, more Leadership please! Ready. GO! :)
Thanks,
Kevin
From: Jay Pipes [jaypi...@gmail.com]
Sent: Friday, May 11, 2018 9:31 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [all] Topics for the Board+TC+UC meet
On 05/11/2018 12:21 PM, Zane Bitter wrote:
On 11/05/18 11:46, Jay Pipes wrote:
On 05/10/2018 08:12 PM, Zane Bitter wrote:
On 10/05/18 16:45, Matt Riedemann wrote:
On 5/10/2018 3:38 PM, Zane Bitter wrote:
How can we avoid (or get out of) the local maximum trap and ensure
that OpenStack will me
On 11/05/18 11:46, Jay Pipes wrote:
On 05/10/2018 08:12 PM, Zane Bitter wrote:
On 10/05/18 16:45, Matt Riedemann wrote:
On 5/10/2018 3:38 PM, Zane Bitter wrote:
How can we avoid (or get out of) the local maximum trap and ensure
that OpenStack will meet the needs of all the users we want to
se
On 05/10/2018 08:12 PM, Zane Bitter wrote:
On 10/05/18 16:45, Matt Riedemann wrote:
On 5/10/2018 3:38 PM, Zane Bitter wrote:
How can we avoid (or get out of) the local maximum trap and ensure
that OpenStack will meet the needs of all the users we want to serve,
not just those whose needs are s
Zane Bitter wrote:
> [...]
> How can we avoid (or get out of) the local maximum trap and ensure that
> OpenStack will meet the needs of all the users we want to serve, not
> just those whose needs are similar to those of the users we already have?
It'a a good question, and a topic I raised a coupl
On 10/05/18 16:52, Doug Hellmann wrote:
Excerpts from Zane Bitter's message of 2018-05-10 16:38:37 -0400:
On 17/04/18 05:24, Thierry Carrez wrote:
Hi everyone,
As you know the Technical Committee (the governance body representing
contributors producing OpenStack software) meets with other Open
On 10/05/18 16:45, Matt Riedemann wrote:
On 5/10/2018 3:38 PM, Zane Bitter wrote:
How can we avoid (or get out of) the local maximum trap and ensure
that OpenStack will meet the needs of all the users we want to serve,
not just those whose needs are similar to those of the users we
already hav
Excerpts from Zane Bitter's message of 2018-05-10 16:38:37 -0400:
> On 17/04/18 05:24, Thierry Carrez wrote:
> > Hi everyone,
> >
> > As you know the Technical Committee (the governance body representing
> > contributors producing OpenStack software) meets with other OpenStack
> > governance bodie
On 5/10/2018 3:38 PM, Zane Bitter wrote:
How can we avoid (or get out of) the local maximum trap and ensure that
OpenStack will meet the needs of all the users we want to serve, not
just those whose needs are similar to those of the users we already have?
The phrase "jack of all trades, master
On 17/04/18 05:24, Thierry Carrez wrote:
Hi everyone,
As you know the Technical Committee (the governance body representing
contributors producing OpenStack software) meets with other OpenStack
governance bodies (Board of Directors and User Committee) on the Sunday
before every Summit, and Vanco
Doug Hellmann wrote:
> Excerpts from Graham Hayes's message of 2018-04-23 15:36:32 +0100:
>> I think as an add on to this, would to ask the board to talk to members
>> and see what contributions they have made to the technical side of
>> OpenStack.
>>
>> This should not just be Number of commits /
On 2018-04-23 15:36:32 +0100 (+0100), Graham Hayes wrote:
> I think as an add on to this, would to ask the board to talk to members
> and see what contributions they have made to the technical side of
> OpenStack.
>
> This should not just be Number of commits / reviews / bugs etc but
> also the mo
Excerpts from Graham Hayes's message of 2018-04-23 15:36:32 +0100:
> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. What are we to do, a
big +1 to Graham's suggestion
On Mon, Apr 23, 2018 at 10:36 PM, Graham Hayes wrote:
> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. Wha
On 18/04/18 11:38, Chris Dent wrote:
> On Tue, 17 Apr 2018, Thierry Carrez wrote:
>
>> So... Is there any specific topic you think we should cover in that
>> meeting ?
>
> The topics:
>
> 1. What are we to do, as a community, when external pressures for
> results are not matched by contribution
On Tue, 17 Apr 2018, Thierry Carrez wrote:
So... Is there any specific topic you think we should cover in that
meeting ?
I'll bite. I've got two topics that I think are pretty critical to
address with the various segments of the community that are the
source of code commits and reviews. Neithe
Hi everyone,
As you know the Technical Committee (the governance body representing
contributors producing OpenStack software) meets with other OpenStack
governance bodies (Board of Directors and User Committee) on the Sunday
before every Summit, and Vancouver will be no exception.
At the TC retro
21 matches
Mail list logo
