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 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 and core reviewer teams to deal with".
I'm not proposing a negative response, I'm asking how to deal with it.
What, for example, does one do if a patch is proposed virtually identically in
a half dozen (or two dozen) projects by someone and is totally bat-shit crazy?
Merely -1'ing it and offering to help in a private email is not really the
answer. I've tried it.
Having a file in the projects repo that talks about guidelines for
contributions isn't it either. We have one of those. It is up to the
contributor to read it; yes, I can keep pointing contributors to that but this
is a systemic problem which I'm hoping to address.
What does one do when a contributor continually proposes one line changes that
fix typos in comments (yes, really). At some point, these changes (while
absolutely, and unarguably valid) begin to be a drag on the community.
What I'm asking for is something, something that may cross project boundaries,
that will help bring contributors onto openstack, and rapidly bring them to the
point where they are contributing at a level that materially benefits the
> -----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)
> 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 contributor would make such and error doesn’t
> warrant such a negative response even if it a hassle for the various PTLs
> and core reviewer teams to deal with. This is one of the many aspects of
> OpenStack projects a PTL is elected to manage (mentorship). If mentorship
> isn’t in a leader’s personal mission, I’m not sure they should be leading
> > Regards
> > -steve
> Well said and +100 from me :)
> 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
> inexperienced at some time in their life...)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
OpenStack Development Mailing List (not for usage questions)