Open Stack

Excerpts from Davanum Srinivas (dims)'s message of 2016-01-29 06:17:39 -0600:
> Matt,
> 
> yes, that's a concern for sure. We work closely with all the new Oslo
> cores to defer to experts first and learn. This goes into the debate
> about the right mixture of Generalists and Specialists in the project
> as well.

Right. I trust everyone on the team to exercise judgment when
choosing which patches to review, and how to review them. I proposed
Alexis for oslo-core rather than oslo-config-core because his general
approach and collaboration on the config work he has already done
convinced me that my trust would not be misplaced. The fact that
we don't actually have a separate oslo-config-core group in gerrit
is an oversight, and didn't enter into it.

Doug

> 
> Thanks,
> Dims
> 
> On Fri, Jan 29, 2016 at 5:42 AM, Matt Riedemann
> <mriedem at linux.vnet.ibm.com> wrote:
> >
> >
> > On 1/29/2016 11:33 AM, Davanum Srinivas wrote:
> >>
> >> Matt,
> >>
> >> yes, Nomination is for oslo-core. We would like to expand the core
> >> group as well in addition to subject matter experts (example Dmitry
> >> Uklhov for Oslo.Messaging core yesterday). The hope and expectation is
> >> that Alexis would expand his reviews and expertise across all Oslo
> >> projects over a period of time.
> >>
> >> Thanks,
> >> Dims
> >>
> >> On Fri, Jan 29, 2016 at 5:24 AM, Matt Riedemann
> >> <mriedem at linux.vnet.ibm.com> wrote:
> >>>
> >>>
> >>>
> >>> On 1/28/2016 10:05 PM, Doug Hellmann wrote:
> >>>>
> >>>>
> >>>> I am nominating Alexis Lee (lxsli) for oslo-core.
> >>>>
> >>>> Alexis has been working on adding configuration file reloading to
> >>>> oslo.config this cycle. The work isn't complete, but at this point
> >>>> he probably knows as much or more about the internals of that library
> >>>> as any of us. :-) He has also shown, with some of his other recent
> >>>> proposals, that he has a ideas for the future of configuration
> >>>> management and an interest in contributing to Oslo.
> >>>>
> >>>> Please indicate yea or nay with the usual +1/-1 vote here.
> >>>>
> >>>> Doug
> >>>>
> >>>>
> >>>>
> >>>> http://stackalytics.com/?release=all&project_type=all&metric=commits&user_id=alexisl
> >>>>
> >>>>
> >>>> __________________________________________________________________________
> >>>> OpenStack Development Mailing List (not for usage questions)
> >>>> Unsubscribe:
> >>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>>>
> >>>
> >>> As an outsider, this is just a question, but I don't see an
> >>> oslo-config-core
> >>> group. I'm assuming that because of lxsli's work on oslo.config this
> >>> nomination is coming up, but is the nomination for oslo-core, as in all
> >>> of
> >>> the oslo projects? Including things like oslo.versionedobjects and
> >>> oslo.messaging?
> >>>
> >>> I'm just wondering how things get broken down because there are obviously
> >>> subject matter experts in certain projects in oslo, but I wouldn't
> >>> consider
> >>> them as being cores across all projects just because they are core on
> >>> one.
> >>> Or am I misunderstanding?
> >>>
> >>> --
> >>>
> >>> Thanks,
> >>>
> >>> Matt Riedemann
> >>>
> >>>
> >>>
> >>> __________________________________________________________________________
> >>> OpenStack Development Mailing List (not for usage questions)
> >>> Unsubscribe:
> >>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >>
> >>
> >
> > So people are made core and then expected to become experts on the other
> > projects? I get that is a carrot, but it seems like that could put the stick
> > on the consuming projects if non-expert cores are approving changes they
> > shouldn't be.
> >
> > Anyway, my two cents...
> >
> >
> > --
> >
> > Thanks,
> >
> > Matt Riedemann
> >
> >
> > __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>