Re: [openstack-dev] [ptl] code churn and questionable changes

On 23/09/16 11:19, Lana Brindley wrote: On 23/09/16 02:19, Amrith Kumar wrote: Joshua, I think Steve and you may be missing the point of my email. It *IS* because I want to be open and inviting that I even asked the question, and what I'm asking for is how to deal with it. All Steve says

Re: [openstack-dev] [ptl] code churn and questionable changes

On 23/09/16 02:19, Amrith Kumar wrote: > Joshua, > > I think Steve and you may be missing the point of my email. It *IS* because I > want to be open and inviting that I even asked the question, and what I'm > asking for is how to deal with it. > > All Steve says is " The fact that a

Re: [openstack-dev] [ptl] code churn and questionable changes

FWIW, No, this is *not* just an problem for OpenStack https://youtu.be/wf-BqAjZb8M?t=531 ^ Raymond Hettinger Ultimately the problem is mis-aligned goals between the individual and the project maintainers. They want to "do stuff" and get a change landed; we want to maximize the positive results

Re: [openstack-dev] [ptl] code churn and questionable changes

Sean Dague wrote: > If this is the bug that triggered this discussion, yes, please never do > anything like that - > https://bugs.launchpad.net/python-openstacksdk/+bug/1475722 > Here was another fun one. https://bugs.launchpad.net/python-cinderclient/+bug/1586268 I commented as such that we

Re: [openstack-dev] [ptl] code churn and questionable changes

On 2016-09-22 08:55:04 -0700 (-0700), Joshua Harlow wrote: [...] > And yes I understand it's not always easy, and some of it can be a PITA > based on (new) contributors experience (or lack of) and so on and so forth > but that's the way the world works folks (and everyone was likely >

Re: [openstack-dev] [ptl] code churn and questionable changes

openstack.org> Subject: Re: [openstack-dev] [ptl] code churn and questionable changes Steven Dake (stdake) wrote: Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contri

Re: [openstack-dev] [ptl] code churn and questionable changes

On Wed, Sep 21, 2016 at 12:43:06PM +, Dolph Mathews wrote: > > > > And as a general rule, there is zero benefit to filing bugs in Launchpad if > there is no end-user impact (especially against 20+ projects). Close the > bug as Opinion (if Launchpad hasn't already broken) and focus on the >

Re: [openstack-dev] [ptl] code churn and questionable changes

project(s). -amrith > -Original Message- > From: Joshua Harlow [mailto:harlo...@fastmail.com] > Sent: Thursday, September 22, 2016 11:55 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re

Re: [openstack-dev] [ptl] code churn and questionable changes

Steven Dake (stdake) wrote: Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it

Re: [openstack-dev] [ptl] code churn and questionable changes

On 22/09/2016 11:18 AM, Amrith Kumar wrote: > [amrith] Actually, not true. Some of the changes I'm seeing are from people > who have a track record of these kinds of changes. And if there is a knob in > Launchpad somewhere, I sure as hell can't find it. no way to block actions but as a

Re: [openstack-dev] [ptl] code churn and questionable changes

estions) > > <openstack-dev@lists.openstack.org> > > Subject: Re: [openstack-dev] [ptl] code churn and questionable changes > > > > Hello, > > > > > in addition to this, please, PLEASE stop creating 'all project bugs'. i > > > don't want to get email

Re: [openstack-dev] [ptl] code churn and questionable changes

> -Original Message- > From: Boris Bobrov [mailto:bbob...@mirantis.com] > Sent: Wednesday, September 21, 2016 10:35 AM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [ptl] cod

Re: [openstack-dev] [ptl] code churn and questionable changes

I agree. I am not saying new contributors are not welcome. They are. But there are also things that we are not comfortable with. But our leadership cannot prevent them from making such error. There should be a way to lure them to mentors before doing things that we consider bad. On 09/22/2016

Re: [openstack-dev] [ptl] code churn and questionable changes

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [ptl] code churn and questionable changes > Folks, > > We want to be inviting to new contributors even if they are green. New > contributors reflect > on OpenStack’s growth in a positive way. The fact that

Re: [openstack-dev] [ptl] code churn and questionable changes

On Thu, Sep 22, 2016 at 8:26 AM, Steven Dake (stdake) wrote: > Folks, > > We want to be inviting to new contributors even if they are green. New > contributors reflect on OpenStack’s growth in a positive way. The fact > that a new-to-openstack contributor would make such and

Re: [openstack-dev] [ptl] code churn and questionable changes

Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it a hassle for the various PTLs

Re: [openstack-dev] [ptl] code churn and questionable changes

On 9/21/2016 6:56 AM, Amrith Kumar wrote: Of late I've been seeing a lot of rather questionable changes that appear to be getting blasted out across multiple projects; changes that cause considerable code churn, and don't (IMHO) materially improve the quality of OpenStack. I’d love to provide a

Re: [openstack-dev] [ptl] code churn and questionable changes

Hello, in addition to this, please, PLEASE stop creating 'all project bugs'. i don't want to get emails on updates to projects unrelated to the ones i care about. also, it makes updating the bug impossible because it times out. i'm too lazy to search ML but this has been raise before, please

Re: [openstack-dev] [ptl] code churn and questionable changes

On Wed, Sep 21 2016, Amrith Kumar wrote: > Over time, the result generally is that these developers' changes get ignored. > And that's not a good thing for the community as a whole. We want to be a > welcoming community and one which values all contributions so I'm looking for > some suggestions

Re: [openstack-dev] [ptl] code churn and questionable changes

On Wed, Sep 21, 2016 at 8:15 AM, gordon chung wrote: > i feel like this gets brought up every year. we block these patches in > Telemetry projects unless they can be justified beyond the copy/paste > description. > > in addition to this, please, PLEASE stop creating 'all project

Re: [openstack-dev] [ptl] code churn and questionable changes

This is a topic that appears periodically; I think it's important that we consider the patches objectively, just like any other patch. If these patches result in substantial and unproductive load on infra that can be deemed abusive, then that's another matter. And as a general rule, there is

Re: [openstack-dev] [ptl] code churn and questionable changes

If this is the bug that triggered this discussion, yes, please never do anything like that - https://bugs.launchpad.net/python-openstacksdk/+bug/1475722 The bug now has too many projects to take any actions on it. I think a basic rule of thumb that before creating a bug that has > 4 projects on

Re: [openstack-dev] [ptl] code churn and questionable changes

i feel like this gets brought up every year. we block these patches in Telemetry projects unless they can be justified beyond the copy/paste description. in addition to this, please, PLEASE stop creating 'all project bugs'. i don't want to get emails on updates to projects unrelated to the

[openstack-dev] [ptl] code churn and questionable changes

Of late I've been seeing a lot of rather questionable changes that appear to be getting blasted out across multiple projects; changes that cause considerable code churn, and don't (IMHO) materially improve the quality of OpenStack. I'd love to provide a list of the changes that triggered this