Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-19 Thread ChangBo Guo
There is no objection in past 7 days, so I added Stephen Finucane as
pbr-core group,  welecom Stephen !


2017-04-19 0:01 GMT+08:00 Jeremy Stanley :

> On 2017-04-12 08:14:31 -0500 (-0500), Monty Taylor wrote:
> [...]
> > Recently Stephen Finucane (sfinucan) has stepped up to the plate
> > to help sort out issues we've been having. He's shown a lack of
> > fear of the codebase and an understanding of what's going on. He's
> > also following through on patches to projects themselves when
> > needed, which is a huge part of the game. And most importantly he
> > knows when to suggest we _not_ do something.
> [...]
>
> As an occasional pbr author and transitive core, I'm in favor. The
> more help the better!
> --
> Jeremy Stanley
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-18 Thread Jeremy Stanley
On 2017-04-12 08:14:31 -0500 (-0500), Monty Taylor wrote:
[...]
> Recently Stephen Finucane (sfinucan) has stepped up to the plate
> to help sort out issues we've been having. He's shown a lack of
> fear of the codebase and an understanding of what's going on. He's
> also following through on patches to projects themselves when
> needed, which is a huge part of the game. And most importantly he
> knows when to suggest we _not_ do something.
[...]

As an occasional pbr author and transitive core, I'm in favor. The
more help the better!
-- 
Jeremy Stanley


signature.asc
Description: Digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-13 Thread Julien Danjou
On Wed, Apr 12 2017, Monty Taylor wrote:

> Recently Stephen Finucane (sfinucan) has stepped up to the plate to help sort
> out issues we've been having. He's shown a lack of fear of the codebase and an
> understanding of what's going on. He's also following through on patches to
> projects themselves when needed, which is a huge part of the game. And most
> importantly he knows when to suggest we _not_ do something.

+1, he's done a good job. :)

-- 
Julien Danjou
# Free Software hacker
# https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-12 Thread Joshua Hesketh
+1, yay! :-)

On Thu, Apr 13, 2017 at 2:46 AM, Doug Hellmann 
wrote:

> Excerpts from Monty Taylor's message of 2017-04-12 08:14:31 -0500:
> > Hey all,
> >
> > As I'm sure you all know, pbr is both our most pervasively used
> > dependency and our least well understood. Nobody ever wants to look at
> > the code (sorry, I can write ugly code sometimes - but also wow
> > setuptools) or dig in to figure out what happened when things break.
> >
> > Recently Stephen Finucane (sfinucan) has stepped up to the plate to help
> > sort out issues we've been having. He's shown a lack of fear of the
> > codebase and an understanding of what's going on. He's also following
> > through on patches to projects themselves when needed, which is a huge
> > part of the game. And most importantly he knows when to suggest we _not_
> > do something.
> >
> > It's not a HUGE corpus of work we have to go on - but that's a good
> > thing - pbr shouldn't chance much - but it's in keeping with the other
> > active pbr maintainers:
> >
> > http://stackalytics.com/report/contribution/pbr/90
> >
> > Monty
> >
>
> +1 -- Stephen has been doing good work elsewhere, too.
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-12 Thread Doug Hellmann
Excerpts from Monty Taylor's message of 2017-04-12 08:14:31 -0500:
> Hey all,
> 
> As I'm sure you all know, pbr is both our most pervasively used 
> dependency and our least well understood. Nobody ever wants to look at 
> the code (sorry, I can write ugly code sometimes - but also wow 
> setuptools) or dig in to figure out what happened when things break.
> 
> Recently Stephen Finucane (sfinucan) has stepped up to the plate to help 
> sort out issues we've been having. He's shown a lack of fear of the 
> codebase and an understanding of what's going on. He's also following 
> through on patches to projects themselves when needed, which is a huge 
> part of the game. And most importantly he knows when to suggest we _not_ 
> do something.
> 
> It's not a HUGE corpus of work we have to go on - but that's a good 
> thing - pbr shouldn't chance much - but it's in keeping with the other 
> active pbr maintainers:
> 
> http://stackalytics.com/report/contribution/pbr/90
> 
> Monty
> 

+1 -- Stephen has been doing good work elsewhere, too.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-12 Thread Ben Nemec

+1

On 04/12/2017 08:14 AM, Monty Taylor wrote:

Hey all,

As I'm sure you all know, pbr is both our most pervasively used
dependency and our least well understood. Nobody ever wants to look at
the code (sorry, I can write ugly code sometimes - but also wow
setuptools) or dig in to figure out what happened when things break.

Recently Stephen Finucane (sfinucan) has stepped up to the plate to help
sort out issues we've been having. He's shown a lack of fear of the
codebase and an understanding of what's going on. He's also following
through on patches to projects themselves when needed, which is a huge
part of the game. And most importantly he knows when to suggest we _not_
do something.

It's not a HUGE corpus of work we have to go on - but that's a good
thing - pbr shouldn't chance much - but it's in keeping with the other
active pbr maintainers:

http://stackalytics.com/report/contribution/pbr/90

Monty

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-12 Thread ChangBo Guo
+1, we really need more people who know pbr well :-)

2017-04-12 21:14 GMT+08:00 Monty Taylor :

> Hey all,
>
> As I'm sure you all know, pbr is both our most pervasively used dependency
> and our least well understood. Nobody ever wants to look at the code
> (sorry, I can write ugly code sometimes - but also wow setuptools) or dig
> in to figure out what happened when things break.
>
> Recently Stephen Finucane (sfinucan) has stepped up to the plate to help
> sort out issues we've been having. He's shown a lack of fear of the
> codebase and an understanding of what's going on. He's also following
> through on patches to projects themselves when needed, which is a huge part
> of the game. And most importantly he knows when to suggest we _not_ do
> something.
>
> It's not a HUGE corpus of work we have to go on - but that's a good thing
> - pbr shouldn't chance much - but it's in keeping with the other active pbr
> maintainers:
>
> http://stackalytics.com/report/contribution/pbr/90
>
> Monty
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [oslo][infra][pbr] Nominating Stephen Finucane for pbr-core

2017-04-12 Thread Monty Taylor

Hey all,

As I'm sure you all know, pbr is both our most pervasively used 
dependency and our least well understood. Nobody ever wants to look at 
the code (sorry, I can write ugly code sometimes - but also wow 
setuptools) or dig in to figure out what happened when things break.


Recently Stephen Finucane (sfinucan) has stepped up to the plate to help 
sort out issues we've been having. He's shown a lack of fear of the 
codebase and an understanding of what's going on. He's also following 
through on patches to projects themselves when needed, which is a huge 
part of the game. And most importantly he knows when to suggest we _not_ 
do something.


It's not a HUGE corpus of work we have to go on - but that's a good 
thing - pbr shouldn't chance much - but it's in keeping with the other 
active pbr maintainers:


http://stackalytics.com/report/contribution/pbr/90

Monty

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev