om: *Lance Bragstad
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)"
> *Date: *Thursday, 27 September 2018 at 15:30
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
>
o: openstack-dev
mailto:openstack-dev@lists.openstack.org>>,
openstack-operators
mailto:openstack-operat...@lists.openstack.org>>,
openstack-sigs
mailto:openstack-s...@lists.openstack.org>>
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
ev@lists.openstack.org>
> Date: Wednesday, 26 September 2018 at 18:00
> To: openstack-dev ,
> openstack-operators ,
> openstack-sigs
> Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for
> T series
>
> It's time to start thinking about community
On 09/26/2018 04:12 PM, Dean Troyer wrote:
On Wed, Sep 26, 2018 at 3:01 PM, Doug Hellmann wrote:
Would it be useful to have the SDK work in OSC as a prerequisite to the
goal work? I would hate to have folks have to write a bunch of things
twice.
I don't think this is necessary, once we have
On Wed, Sep 26, 2018 at 3:01 PM, Doug Hellmann wrote:
> Would it be useful to have the SDK work in OSC as a prerequisite to the
> goal work? I would hate to have folks have to write a bunch of things
> twice.
I don't think this is necessary, once we have the auth and service
discovery/version
On 9/26/2018 3:01 PM, Doug Hellmann wrote:
Monty Taylor writes:
On 09/26/2018 01:55 PM, Tim Bell wrote:
Doug,
Thanks for raising this. I'd like to highlight the goal "Finish moving legacy
python-*client CLIs to python-openstackclient" from the etherpad and propose this
for a T/U series
--Original Message-----
>> From: Doug Hellmann
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>>
>> Date: Wednesday, 26 September 2018 at 18:00
>> To: openstack-dev , openstack-operators
>> , openstack-sigs
>>
tack-dev , openstack-operators
, openstack-sigs
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push fo
"OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, 26 September 2018 at 18:00
To: openstack-dev , openstack-operators
, openstack-sigs
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
It's time to start thinking
tember 2018 at 18:00
To: openstack-dev , openstack-operators
, openstack-sigs
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible
openstack-operators
, openstack-sigs
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push for
basic l
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push for
basic levels of consistency and user experience, and efficiently improve
certain areas where technical debt payments have become too high -
across all
12 matches
Mail list logo
