Re: [openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-06 Thread Lance Bragstad 
For scheduling purposes, here is a link to the session [0].

[0]
https://www.openstack.org/summit/boston-2017/summit-schedule/events/18732/queens-goals

On Sat, May 6, 2017 at 5:36 PM, Matt Riedemann  wrote:

> On 5/5/2017 8:23 PM, Sean Dague wrote:
>
>> On 05/05/2017 05:09 PM, Matt Riedemann wrote:
>> 
>>
>>> This time is tough given how front-loaded the sessions are at the Forum
>>> on Monday. The Nova onboarding session overlaps with this, along with
>>> some other sessions that impact or are related to Nova. It would have
>>> been nice to do stuff like this toward the end of the week, but I
>>> realize scheduling is a nightmare and not everyone can be pleased, and
>>> that ship has sailed. So I don't think I can be there, but I assume
>>> anything that comes out of it will be proposed to the governance repo or
>>> recapped in the mailing list afterward so we can discuss there.
>>>
>>
>> Right, given that it's against Operating the VM/Baremetal Platform, and
>> Nova Onboarding, I'll just give feedback here.
>>
>> A migration path off of paste would be a huge win. Paste deploy is
>> unmaintained (as noted in the etherpad) and being in etc means it's
>> another piece of gratuitous state that makes upgrading harder than it
>> really should be.
>>
>> This is one of those that is going to require someone to commit to
>> working out that migration path up front. But it would be a pretty good
>> chunk of debt and upgrade ease.
>>
>> -Sean
>>
>>
> So, I don't know what I was thinking when I read thingee's original email,
> but I thought it was Monday but it's actually Thursday which makes it
> better. Sorry for any confusion I caused.
>
> --
>
> Thanks,
>
> Matt
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-06 Thread Matt Riedemann 

On 5/5/2017 8:23 PM, Sean Dague wrote:

On 05/05/2017 05:09 PM, Matt Riedemann wrote:


This time is tough given how front-loaded the sessions are at the Forum
on Monday. The Nova onboarding session overlaps with this, along with
some other sessions that impact or are related to Nova. It would have
been nice to do stuff like this toward the end of the week, but I
realize scheduling is a nightmare and not everyone can be pleased, and
that ship has sailed. So I don't think I can be there, but I assume
anything that comes out of it will be proposed to the governance repo or
recapped in the mailing list afterward so we can discuss there.


Right, given that it's against Operating the VM/Baremetal Platform, and
Nova Onboarding, I'll just give feedback here.

A migration path off of paste would be a huge win. Paste deploy is
unmaintained (as noted in the etherpad) and being in etc means it's
another piece of gratuitous state that makes upgrading harder than it
really should be.

This is one of those that is going to require someone to commit to
working out that migration path up front. But it would be a pretty good
chunk of debt and upgrade ease.

-Sean



So, I don't know what I was thinking when I read thingee's original 
email, but I thought it was Monday but it's actually Thursday which 
makes it better. Sorry for any confusion I caused.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-05 Thread Sean Dague 

On 05/05/2017 05:09 PM, Matt Riedemann wrote:


This time is tough given how front-loaded the sessions are at the Forum
on Monday. The Nova onboarding session overlaps with this, along with
some other sessions that impact or are related to Nova. It would have
been nice to do stuff like this toward the end of the week, but I
realize scheduling is a nightmare and not everyone can be pleased, and
that ship has sailed. So I don't think I can be there, but I assume
anything that comes out of it will be proposed to the governance repo or
recapped in the mailing list afterward so we can discuss there.


Right, given that it's against Operating the VM/Baremetal Platform, and 
Nova Onboarding, I'll just give feedback here.


A migration path off of paste would be a huge win. Paste deploy is 
unmaintained (as noted in the etherpad) and being in etc means it's 
another piece of gratuitous state that makes upgrading harder than it 
really should be.


This is one of those that is going to require someone to commit to 
working out that migration path up front. But it would be a pretty good 
chunk of debt and upgrade ease.


-Sean

--
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-05 Thread Matt Riedemann 

On 5/5/2017 10:47 AM, Mike Perez wrote:

Hello everyone,

May 11th at 11:00-12:30 at the forum we will be discussing our community wide
goals for the Queen release [1]!

We do OpenStack-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 OpenStack
projects" [2].

Our goals backlog: [3]

* New goals are highly welcome.
* Each goal would achieveable in one cycle, if not we need to break the goal
  into smaller connected goals.
* Some Goals already have a team (ex: Python 3) but some haven't.  Maybe could
  we dress a list of people able to step-up and volunteer to help on these
  ones.
* Some Goals might require some documentation for how to achieve it.

Thanks to Emilien for leading our community wide goals for Pike [4]

* There was an overwhelming amount of support for beginning Python 3.5 support
  [5] by having our unit tests voting.
* Unfortunately getting our API endpoints to support WSGI still has some work
  [6].

Lets start adding/updating what's in our backlog [3] to prepare for the forum
next week!

[1] - https://governance.openstack.org/tc/goals/pike/index.html
[2] - https://governance.openstack.org/tc/goals/pike/index.html
[3] - https://etherpad.openstack.org/p/community-goals
[4] - https://governance.openstack.org/tc/goals/pike/index.html



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



This time is tough given how front-loaded the sessions are at the Forum 
on Monday. The Nova onboarding session overlaps with this, along with 
some other sessions that impact or are related to Nova. It would have 
been nice to do stuff like this toward the end of the week, but I 
realize scheduling is a nightmare and not everyone can be pleased, and 
that ship has sailed. So I don't think I can be there, but I assume 
anything that comes out of it will be proposed to the governance repo or 
recapped in the mailing list afterward so we can discuss there.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-05 Thread Emilien Macchi 
On Fri, May 5, 2017 at 11:47 AM, Mike Perez  wrote:
> Hello everyone,
>
> May 11th at 11:00-12:30 at the forum we will be discussing our community wide
> goals for the Queen release [1]!
>
> We do OpenStack-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 
> OpenStack
> projects" [2].
>
> Our goals backlog: [3]
>
> * New goals are highly welcome.
> * Each goal would achieveable in one cycle, if not we need to break the goal
>   into smaller connected goals.
> * Some Goals already have a team (ex: Python 3) but some haven't.  Maybe could
>   we dress a list of people able to step-up and volunteer to help on these
>   ones.
> * Some Goals might require some documentation for how to achieve it.
>
> Thanks to Emilien for leading our community wide goals for Pike [4]

count on my to be at the session and continue to bring my little contribution.

> * There was an overwhelming amount of support for beginning Python 3.5 support
>   [5] by having our unit tests voting.
> * Unfortunately getting our API endpoints to support WSGI still has some work
>   [6].
>
> Lets start adding/updating what's in our backlog [3] to prepare for the forum
> next week!
>
> [1] - https://governance.openstack.org/tc/goals/pike/index.html
> [2] - https://governance.openstack.org/tc/goals/pike/index.html
> [3] - https://etherpad.openstack.org/p/community-goals
> [4] - https://governance.openstack.org/tc/goals/pike/index.html
>
> --
> Mike Perez
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][ptl][goals] Community goals for Queen

2017-05-05 Thread Mike Perez 
Hello everyone,

May 11th at 11:00-12:30 at the forum we will be discussing our community wide
goals for the Queen release [1]!

We do OpenStack-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 OpenStack
projects" [2].

Our goals backlog: [3]

* New goals are highly welcome.
* Each goal would achieveable in one cycle, if not we need to break the goal
  into smaller connected goals.
* Some Goals already have a team (ex: Python 3) but some haven't.  Maybe could
  we dress a list of people able to step-up and volunteer to help on these
  ones.
* Some Goals might require some documentation for how to achieve it.

Thanks to Emilien for leading our community wide goals for Pike [4]

* There was an overwhelming amount of support for beginning Python 3.5 support
  [5] by having our unit tests voting.
* Unfortunately getting our API endpoints to support WSGI still has some work
  [6].

Lets start adding/updating what's in our backlog [3] to prepare for the forum
next week!

[1] - https://governance.openstack.org/tc/goals/pike/index.html
[2] - https://governance.openstack.org/tc/goals/pike/index.html
[3] - https://etherpad.openstack.org/p/community-goals
[4] - https://governance.openstack.org/tc/goals/pike/index.html

-- 
Mike Perez


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev