settingsLogin | Registersettings

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

0 votes

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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 12, 2017 in openstack-dev by Monty_Taylor (22,780 points)   2 4 7

7 Responses

0 votes

+1, we really need more people who know pbr well :-)

2017-04-12 21:14 GMT+08:00 Monty Taylor mordred@inaugust.com:

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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by ChangBo_Guo (4,540 points)   3 5
0 votes

+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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by Ben_Nemec (19,660 points)   2 3 3
0 votes

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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 12, 2017 by Doug_Hellmann (87,520 points)   3 4 8
0 votes

+1, yay! :-)

On Thu, Apr 13, 2017 at 2:46 AM, Doug Hellmann doug@doughellmann.com
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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 13, 2017 by joshua.hesketh_at_gm (2,460 points)   1 2
0 votes

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


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

responded Apr 13, 2017 by Julien_Danjou (20,500 points)   2 4 6
0 votes

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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Apr 18, 2017 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

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 fungi@yuggoth.org:

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-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 19, 2017 by ChangBo_Guo (4,540 points)   3 5
...