Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On Mon, Dec 19, 2016 at 2:09 PM, Doug Hellmann wrote: > Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > >> 3) Choose Goals for Pike. >> Some of us already did, but we might want to start looking at what >> Goals we would like to achieve during Pike

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > 3) Choose Goals for Pike. > Some of us already did, but we might want to start looking at what > Goals we would like to achieve during Pike cycle. > I was thinking at giving a score to the Goals, that could be > calculated by

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On Thu, Dec 15, 2016 at 10:58 AM, Sean Dague wrote: > One of the big things to consider is which of these items directly > support one of the key PWG issues: "painless upgrades" > > The following items: movinging paste.ini out of config, new style > olso.policy (in code), and

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Sean Dague's message of 2016-12-15 11:58:42 -0500: > One of the big things to consider is which of these items directly > support one of the key PWG issues: "painless upgrades" > > The following items: movinging paste.ini out of config, new style > olso.policy (in code), and

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

One of the big things to consider is which of these items directly support one of the key PWG issues: "painless upgrades" The following items: movinging paste.ini out of config, new style olso.policy (in code), and rootwrap -> privsep all eliminate files in /etc that dramatically impact code

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

> On 15 Dec 2016, at 16:19, Doug Hellmann wrote: > > Excerpts from Jean-Philippe Evrard's message of 2016-12-15 09:11:12 +: >> Hello, >> >> Maybe this will sound dumb … >> >> I received this email on openstack-dev mailing list. I don’t know if it was >> sent to any

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Jean-Philippe Evrard's message of 2016-12-15 09:11:12 +: > Hello, > > Maybe this will sound dumb … > > I received this email on openstack-dev mailing list. I don’t know if it was > sent to any other place, because it’s basically agreeing on development to be > done, which

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Jean-Philippe Evrard wrote: > Maybe this will sound dumb … > > I received this email on openstack-dev mailing list. I don’t know if it was > sent to any other place, because it’s basically agreeing on development to be > done, which makes sense to me. > So openstack-dev people (called further

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Hello, Maybe this will sound dumb … I received this email on openstack-dev mailing list. I don’t know if it was sent to any other place, because it’s basically agreeing on development to be done, which makes sense to me. So openstack-dev people (called further “devs”) will push their company

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Emilien Macchi's message of 2016-11-29 19:39:03 -0500: > A few months ago, our community started to find and work on > OpenStack-wide goals to "achieve visible common changes, push for > basic levels of consistency and user experience, and efficiently > improve certain areas where

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On Tue, Nov 29, 2016 at 7:39 PM, Emilien Macchi wrote: > A few months ago, our community started to find and work on > OpenStack-wide goals to "achieve visible common changes, push for > basic levels of consistency and user experience, and efficiently > improve certain areas

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On 2016-11-29 19:39:03 -0500 (-0500), Emilien Macchi wrote: [...] > - we expected all teams to respond to all goals, even if they have no > work to do. Should we continue that way? [...] While it struck me as a possible source of "busy work" at first, I now see that otherwise it can be quite

[openstack-dev] [all][ptls][tc][goals] community goals for Pike

A few months ago, our community started to find and work on 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".