openstack-poc team mailing list archive
-
openstack-poc team
-
Mailing list archive
-
Message #00004
Re: Discussion Item - Core Dev process
> -----Original Message-----
> From: openstack-poc-bounces+ewan.mellor=citrix.com@xxxxxxxxxxxxxxxxxxx
> [mailto:openstack-poc-
> bounces+ewan.mellor=citrix.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Jonathan Bryce
> Sent: 17 January 2011 17:50
> To: openstack-poc@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Openstack-poc] Discussion Item - Core Dev process
>
> On Jan 17, 2011, at 11:33 AM, Ewan Mellor wrote:
>
> > The problem I have is really something else, rather than with this
> process itself, but it manifests itself here, so here we go:
> >
> > The proposal says "In OpenStack a core developer is a developer who
> has submitted enough high quality code and done enough code reviews
> that we trust their code reviews for merging into the base source
> tree."
> >
> > This is all very well and good, but we've got lots of other things
> tangled up with core-developerness, other than just writing good code
> and doing good code reviews. For example, I don't see any of the
> questions that are filed on Launchpad, or notifications of new
> blueprints. I presume that these kind of things are going to
> openstack-core (and if they aren't, where are they going?)
>
> You can receive bug notifications, merge proposals, questions, etc. by
> subscribing to them even if you aren't a member of a -core group. It's
> kind of a manual one-time process that you have to do in a number of
> different places. At the very least we should document the steps to get
> all the relevant notifications.
Bug notifications I can get. I don't see any way to get blueprint notifications.
Ewan.
Follow ups
References