Re: [openstack-dev] [ptl][requirements] nomination period started

[Tony Breeds]

On Wed, Jul 27, 2016 at 11:13:03AM -0500, Tony Breeds wrote:

> I'd like to nominate for PTL of the, to be formed, requirements project.

I'd just like to clarify something as I've been asked by several people
privately.  The gist of the question is:
You're the Stable PTL if elected to requirements PTL what happens to Stable?

Frankly unless the community has a major objection to doing so I'm quite
willing to do the PTL roll for both projects.  There is considerable overlap
between the skills and (pun intended) requirements in both projects/rolls.

Yours Tony.


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] [ptl][requirements] nomination period started

[Anita Kuno]

On 16-07-27 09:41 AM, Matthew Thode wrote:

We've started a period of self nomination in preparation for the
requirements project fully moving into project (as it's still under Doug
Hellmann).

We are gathering the self nominations here before we vote next week.
https://etherpad.openstack.org/p/requirements-ptl-newton

Nominees should also send an email to the openstack-dev list.



__
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


The candidates for the OpenStack Requirements PTL election are as follows:

* Matthew Thode - prometheanfire

* Tony Breeds - tonyb

* Swapnil Kulkarni - coolsvap

Ballots are forthcoming.


Thank you,

Anita and 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] [ptl][requirements] nomination period started

[Tony Breeds]

On Thu, Jul 28, 2016 at 12:42:32PM -0400, Doug Hellmann wrote:

> As part of our discussion, we realized that over time we'll be
> automating more and more of the submissions to the requirements
> repo so the core review team (and everyone else) will likely end
> up submitting fewer manual patches. This points out a difference
> in the nature of this team from others that we'll need to address
> to avoid arriving at the unlikely situation where no human is
> actually able to vote for PTL. It's more likely that none of the
> core review team would be on the voter list using our usual "who
> has landed a patch" rule, and that would be bad as well, IMO.
> 
> So, the new team will need to add an item to their bootstrapping
> todo list to specify how their electorate is identified to ensure
> we can continue to have healthy, representative, elections.  Based
> on my interpretation of the TC charter [1], we don't need a rules
> change. Adding some team documentation and (as Jeremy pointed out)
> active maintenance of the "extra-atcs" list for the team in the
> governance repository should be sufficient.
> 
> I propose that we defer any real discussion of what the policy
> should be until after the current election, but try to work it out
> before the team applies for big tent membership.

Sounds like a good plan.

Tony.


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] [ptl][requirements] nomination period started

[Tony Breeds]

On Thu, Jul 28, 2016 at 12:21:26PM -0400, Anita Kuno wrote:

> So Doug and I had a chat and we propose the following workflow for
> deciding the requirements ptl:
> 1) Nominations open, done:
> http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
> 2) Nominations close: August 5th, 11:59 utc
> 3) List of Nominees posted to mailing list, a post appened to the
> parent:
> http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
> 4) Election officials start civs poll after 13:00 utc August 5, 2016
> 5) Election poll closes after 13:00 utc  August 11, 2016
> 6) Winning candidate will be announced to the mailing list
> (openstack-dev@lists.openstack.org)

Perfect!

Thanks Anita and Doug.

Tony.


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] [ptl][requirements] nomination period started

[Doug Hellmann]

Excerpts from Anita Kuno's message of 2016-07-28 12:21:26 -0400:
> On 07/27/2016 06:06 PM, Jeremy Stanley wrote:
> > On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote:
> > [...]
> >> However, we may have some folks on the core team who have not
> >> contributed a patch, since it is far more common to do reviews than
> >> to submit changes there (more and more of the changes are being
> >> automated). So, we probably need to expand the traditional definition
> >> to also include the existing core review team (members of
> >> requirements-core [1]), just to be safe.
> > [...]
> > 
> > Easy enough to do for a one-off, but might want to consider
> > officially adding them as extra-ATCs in governance down the road to
> > make that more explicit. Our existing tooling is already adapted to
> > that solution as well (for example, the current i18n voters are
> > _all_ recorded as extra-ATCs because we haven't implemented API
> > calls to Zanata for integrating it into the normal roll generation
> > process yet).
> > 
> > However, implicitly adding core reviewers seems a little weird as
> > they're officially appointed by the PTL and so allowing the
> > incumbent PTL to appoint (or remove) specific voters before their
> > pending reelection... well anyway, I guess it's balanced out by
> > there being a lot more committers to that repo than core reviewers
> > on it.
> > 
> 
> So Doug and I had a chat and we propose the following workflow for
> deciding the requirements ptl:
> 1) Nominations open, done:
> http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
> 2) Nominations close: August 5th, 11:59 utc
> 3) List of Nominees posted to mailing list, a post appened to the
> parent:
> http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
> 4) Election officials start civs poll after 13:00 utc August 5, 2016
> 5) Election poll closes after 13:00 utc  August 11, 2016
> 6) Winning candidate will be announced to the mailing list
> (openstack-dev@lists.openstack.org)
> 
> Electorate:
> requirements core reviewers and those who have merged at least one
> patch to the requirements repo between 1 Aug 2015 and July 31 2016

As part of our discussion, we realized that over time we'll be
automating more and more of the submissions to the requirements
repo so the core review team (and everyone else) will likely end
up submitting fewer manual patches. This points out a difference
in the nature of this team from others that we'll need to address
to avoid arriving at the unlikely situation where no human is
actually able to vote for PTL. It's more likely that none of the
core review team would be on the voter list using our usual "who
has landed a patch" rule, and that would be bad as well, IMO.

So, the new team will need to add an item to their bootstrapping
todo list to specify how their electorate is identified to ensure
we can continue to have healthy, representative, elections.  Based
on my interpretation of the TC charter [1], we don't need a rules
change. Adding some team documentation and (as Jeremy pointed out)
active maintenance of the "extra-atcs" list for the team in the
governance repository should be sufficient.

I propose that we defer any real discussion of what the policy
should be until after the current election, but try to work it out
before the team applies for big tent membership.

Doug

[1] 
http://governance.openstack.org/reference/charter.html#voters-for-ptl-seats-apc

> can I vote?
> 
> 
> https://review.openstack.org/#/q/project:openstack/requirements+is:owner+is:merged+after:2015-07-31+before:2016-08-01
> 
> how do I vote?
> 
> eligible voters will receive a ballot sent to their gerrit preferred
> email, if you are an eligible voter and don't receive an email providing
> you a link to the poll by August 6, 2016 please email the election
> officials with a gerrit url for your patch confirming your eligibility
> 
> 
> Please ask any questions you need to ask to clarify this process so you
> understand it.
> 
> If you have a question of a personal nature, please don't hesitate to
> email both election officials: Doug Hellmann  and
> Anita Kuno  as soon as you can so we can
> ensure you have the answers you need.
> 
> Thank you to Jeremy Stanley for his assistance and support as well as
> his offer to help us generate the electoral rolls, which include a wip
> patch to governance to generate an electoral roll separate from the
> Release Management team electorate. After the election, we will abandon
> that patch and let the new team propose its own change, including a
> mission statement and other metadata, when they seek to become a big
> tent project. Gerrit patch: https://review.openstack.org/#/c/348462
> 
> Thanks for your participation in the electoral process,
> 
> Anita and Doug
> 

__
OpenStack Development Mailing List (not 

Re: [openstack-dev] [ptl][requirements] nomination period started

[Anita Kuno]

On 07/27/2016 06:06 PM, Jeremy Stanley wrote:
> On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> However, we may have some folks on the core team who have not
>> contributed a patch, since it is far more common to do reviews than
>> to submit changes there (more and more of the changes are being
>> automated). So, we probably need to expand the traditional definition
>> to also include the existing core review team (members of
>> requirements-core [1]), just to be safe.
> [...]
> 
> Easy enough to do for a one-off, but might want to consider
> officially adding them as extra-ATCs in governance down the road to
> make that more explicit. Our existing tooling is already adapted to
> that solution as well (for example, the current i18n voters are
> _all_ recorded as extra-ATCs because we haven't implemented API
> calls to Zanata for integrating it into the normal roll generation
> process yet).
> 
> However, implicitly adding core reviewers seems a little weird as
> they're officially appointed by the PTL and so allowing the
> incumbent PTL to appoint (or remove) specific voters before their
> pending reelection... well anyway, I guess it's balanced out by
> there being a lot more committers to that repo than core reviewers
> on it.
> 

So Doug and I had a chat and we propose the following workflow for
deciding the requirements ptl:
1) Nominations open, done:
http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
2) Nominations close: August 5th, 11:59 utc
3) List of Nominees posted to mailing list, a post appened to the
parent:
http://lists.openstack.org/pipermail/openstack-dev/2016-July/100173.html
4) Election officials start civs poll after 13:00 utc August 5, 2016
5) Election poll closes after 13:00 utc  August 11, 2016
6) Winning candidate will be announced to the mailing list
(openstack-dev@lists.openstack.org)

Electorate:
requirements core reviewers and those who have merged at least one
patch to the requirements repo between 1 Aug 2015 and July 31 2016
can I vote?


https://review.openstack.org/#/q/project:openstack/requirements+is:owner+is:merged+after:2015-07-31+before:2016-08-01

how do I vote?

eligible voters will receive a ballot sent to their gerrit preferred
email, if you are an eligible voter and don't receive an email providing
you a link to the poll by August 6, 2016 please email the election
officials with a gerrit url for your patch confirming your eligibility


Please ask any questions you need to ask to clarify this process so you
understand it.

If you have a question of a personal nature, please don't hesitate to
email both election officials: Doug Hellmann  and
Anita Kuno  as soon as you can so we can
ensure you have the answers you need.

Thank you to Jeremy Stanley for his assistance and support as well as
his offer to help us generate the electoral rolls, which include a wip
patch to governance to generate an electoral roll separate from the
Release Management team electorate. After the election, we will abandon
that patch and let the new team propose its own change, including a
mission statement and other metadata, when they seek to become a big
tent project. Gerrit patch: https://review.openstack.org/#/c/348462

Thanks for your participation in the electoral process,

Anita and 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] [ptl][requirements] nomination period started

[Swapnil Kulkarni (coolsvap)]

On Wed, Jul 27, 2016 at 7:11 PM, Matthew Thode
 wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
>
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
>
> Nominees should also send an email to the openstack-dev list.
>
> --
> -- Matthew Thode (prometheanfire)
>
>
> __
> 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
>

I would like to nominate for the PTL of newly formed requirements team.

I joined release engineering discussion during Austin Summit as an
enthusiast to see and volunteer for contribution. From the bootstrap
meeting of the requirement group [1] I have contributed with both code
and reviews[2]. I constantly review the requirements queue and always
help people to accelerate the merge of failing/required libraries. I
would like to do better management of requirements project. I have
started with the formulating team meeting agenda on wiki.

I wish to work on the requirements in the same intent going forward.

Thank you,
coolsvap

[1] 
http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-05-18-12.00.html
[2] http://stackalytics.com/report/contribution/requirements/75

__
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] [ptl][requirements] nomination period started

[Matthew Thode]

On 07/27/2016 04:08 PM, Jeremy Stanley wrote:
> On 2016-07-27 08:41:17 -0500 (-0500), Matthew Thode wrote:
>> We've started a period of self nomination in preparation for the
>> requirements project fully moving into project (as it's still under Doug
>> Hellmann).
>>
>> We are gathering the self nominations here before we vote next week.
>> https://etherpad.openstack.org/p/requirements-ptl-newton
>>
>> Nominees should also send an email to the openstack-dev list.
> 
> Have you determined whether your electorate are traditional project
> technical contributors (Gerrit owners of changes merged to the
> openstack/requirements repo over the past year) like most teams use,
> or is there a different focus and constituency for this team?
> 

We have talked about it somewhat, but just assumed it'd be those that
have submitted (and had merge) changes.  Doug's suggestion to include
the current 'wip' core team might be good, I know at least Tony and I
didn't know for sure if we'd be disqualified or not.

The term 'interim' for ptl I think is just because elections are coming
up soon.

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP 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] [ptl][requirements] nomination period started

[Doug Hellmann]

Excerpts from Jeremy Stanley's message of 2016-07-27 22:06:43 +:
> On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > However, we may have some folks on the core team who have not
> > contributed a patch, since it is far more common to do reviews than
> > to submit changes there (more and more of the changes are being
> > automated). So, we probably need to expand the traditional definition
> > to also include the existing core review team (members of
> > requirements-core [1]), just to be safe.
> [...]
> 
> Easy enough to do for a one-off, but might want to consider
> officially adding them as extra-ATCs in governance down the road to
> make that more explicit. Our existing tooling is already adapted to
> that solution as well (for example, the current i18n voters are
> _all_ recorded as extra-ATCs because we haven't implemented API
> calls to Zanata for integrating it into the normal roll generation
> process yet).

Sure, adding them to the extra-atcs list rather than adding custom rules
to the tools makes great sense.

> 
> However, implicitly adding core reviewers seems a little weird as
> they're officially appointed by the PTL and so allowing the
> incumbent PTL to appoint (or remove) specific voters before their
> pending reelection... well anyway, I guess it's balanced out by
> there being a lot more committers to that repo than core reviewers
> on it.

Yes, it is a bit unusual. I'd hate to have the core reviewers *not*
have a vote, though, since they're the ones doing the work in that
repo.

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] [ptl][requirements] nomination period started

[Jeremy Stanley]

On 2016-07-27 17:56:39 -0400 (-0400), Doug Hellmann wrote:
[...]
> However, we may have some folks on the core team who have not
> contributed a patch, since it is far more common to do reviews than
> to submit changes there (more and more of the changes are being
> automated). So, we probably need to expand the traditional definition
> to also include the existing core review team (members of
> requirements-core [1]), just to be safe.
[...]

Easy enough to do for a one-off, but might want to consider
officially adding them as extra-ATCs in governance down the road to
make that more explicit. Our existing tooling is already adapted to
that solution as well (for example, the current i18n voters are
_all_ recorded as extra-ATCs because we haven't implemented API
calls to Zanata for integrating it into the normal roll generation
process yet).

However, implicitly adding core reviewers seems a little weird as
they're officially appointed by the PTL and so allowing the
incumbent PTL to appoint (or remove) specific voters before their
pending reelection... well anyway, I guess it's balanced out by
there being a lot more committers to that repo than core reviewers
on it.
-- 
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

Re: [openstack-dev] [ptl][requirements] nomination period started

[Doug Hellmann]

Excerpts from Jeremy Stanley's message of 2016-07-27 21:08:12 +:
> On 2016-07-27 08:41:17 -0500 (-0500), Matthew Thode wrote:
> > We've started a period of self nomination in preparation for the
> > requirements project fully moving into project (as it's still under Doug
> > Hellmann).
> > 
> > We are gathering the self nominations here before we vote next week.
> > https://etherpad.openstack.org/p/requirements-ptl-newton
> > 
> > Nominees should also send an email to the openstack-dev list.
> 
> Have you determined whether your electorate are traditional project
> technical contributors (Gerrit owners of changes merged to the
> openstack/requirements repo over the past year) like most teams use,
> or is there a different focus and constituency for this team?

Excellent question.

I assumed that we would use the list of contributors to the
repositories managed by the team. At the moment I think that means
only the openstack/requirements repository.

However, we may have some folks on the core team who have not
contributed a patch, since it is far more common to do reviews than
to submit changes there (more and more of the changes are being
automated). So, we probably need to expand the traditional definition
to also include the existing core review team (members of
requirements-core [1]), just to be safe.

Does that include everyone we should?

Once we have consensus, I can document the decision in the wiki
under [2].

[1] https://review.openstack.org/#/admin/groups/131,members
[2] https://wiki.openstack.org/wiki/Requirements#Requirements_Team

__
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] [ptl][requirements] nomination period started

[Anita Kuno]

On 07/27/2016 05:44 PM, Jeremy Stanley wrote:
> On 2016-07-27 17:38:49 -0400 (-0400), Anita Kuno wrote:
> [...]
>> /me assumes Jeremy's follow up suggestion/offer is to help compose the
>> rolls, for which Anita is grateful
> 
> Good guess, and yes I'm happy to if desired but if the means of
> identifying Requirements team voters differs from the norm then that
> may take some additional coding to automate.
> 
Wonderful, as usual, thanks for the constant support. Once the direction
the group wants to take in regards to computing the electorate becomes
clear we can move forward hopefully with details in hand.

Thanks Jeremy,
Anita.

__
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] [ptl][requirements] nomination period started

[Jeremy Stanley]

On 2016-07-27 17:38:49 -0400 (-0400), Anita Kuno wrote:
[...]
> /me assumes Jeremy's follow up suggestion/offer is to help compose the
> rolls, for which Anita is grateful

Good guess, and yes I'm happy to if desired but if the means of
identifying Requirements team voters differs from the norm then that
may take some additional coding to automate.
-- 
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

Re: [openstack-dev] [ptl][requirements] nomination period started

[Anita Kuno]

On 07/27/2016 05:08 PM, Jeremy Stanley wrote:
> On 2016-07-27 08:41:17 -0500 (-0500), Matthew Thode wrote:
>> We've started a period of self nomination in preparation for the
>> requirements project fully moving into project (as it's still under Doug
>> Hellmann).
>>
>> We are gathering the self nominations here before we vote next week.
>> https://etherpad.openstack.org/p/requirements-ptl-newton
>>
>> Nominees should also send an email to the openstack-dev list.
> 
> Have you determined whether your electorate are traditional project
> technical contributors (Gerrit owners of changes merged to the
> openstack/requirements repo over the past year) like most teams use,
> or is there a different focus and constituency for this team?
> 

It is a good question. Since they haven't yet determined if they will do
a civs poll or just do a show of hands at a meeting, I was going to give
them a bit and see which direction they wanted to go.

I have an outstanding question to Doug actually on the nature of the
word 'interm' in play currently, because they way I see it a ptl is a
plt and has the same responsibilities as every other ptl adjectives
notwithstanding.

/me assumes Jeremy's follow up suggestion/offer is to help compose the
rolls, for which Anita is grateful

Thanks,
Anita.

__
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] [ptl][requirements] nomination period started

[Jeremy Stanley]

On 2016-07-27 08:41:17 -0500 (-0500), Matthew Thode wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
> 
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
> 
> Nominees should also send an email to the openstack-dev list.

Have you determined whether your electorate are traditional project
technical contributors (Gerrit owners of changes merged to the
openstack/requirements repo over the past year) like most teams use,
or is there a different focus and constituency for this team?
-- 
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

Re: [openstack-dev] [ptl][requirements] nomination period started

[Tony Breeds]

On Wed, Jul 27, 2016 at 08:41:17AM -0500, Matthew Thode wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
> 
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
> 
> Nominees should also send an email to the openstack-dev list.

I'd like to nominate for PTL of the, to be formed, requirements project.

For as long as I've been working on OpenStack the requirements data, code and
process has been managed as a sort of sub-team of release management with
strong overlaps to the stable branch team(s).  The workload has grown to the
point it needs it's own team with a PTL to manage priorities and reduce the
cross project pain points.

I feel like I understand the role of the requirements team and have advocated
that the requirements team should be more active in cross project issues.

The requirements team, like probably every other team, has a lot of debt.
We've worked hard to reduce that since Austin and I see that in the near future
we'll be able to tackle some of the bigger problems.

In rough priority order:
 - Improving communication, often decisions are made in the requirements team
   that affect many projects, I have a commitment to bringing more experts in
   for strategic reviews/discussions
 - cross-project testing for upper-constraints changes.  Once this is done
   it'll make breakage, like the recent oslo.context one, much harder to hit.
 - Work closely with the release managers as there is still a lot of common
   issues there.  In that a release of $project will trigger processes in the
   requirements team.
 - Getting openstack_requirements *code* to the point it can be installed as a
   library.  We've seen issues in the past where stable branches need largish
   backports to work correctly.  Really the *code* and *data* should be treated
   independently

I suspect that if you look at the review statistics for the requirements repo
I'm much lower than many of the core team.

I believe I'm eligible for nomination due to any of the following reviews.

https://review.openstack.org/#/q/project:openstack/requirements+status:merged+owner:tonyb+after:2016-04-07

IRC: tonyb

Yours Tony.


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] [ptl][requirements] nomination period started

[Doug Hellmann]

Excerpts from Matthew Thode's message of 2016-07-27 09:19:33 -0500:
> On 07/27/2016 09:07 AM, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2016-07-27 08:41:17 -0500:
> >> We've started a period of self nomination in preparation for the
> >> requirements project fully moving into project (as it's still under Doug
> >> Hellmann).
> >>
> >> We are gathering the self nominations here before we vote next week.
> >> https://etherpad.openstack.org/p/requirements-ptl-newton
> >>
> >> Nominees should also send an email to the openstack-dev list.
> >>
> > 
> > Thanks for kicking this off, Matt! I'm looking forward to seeing this
> > team fully self-sufficient.
> > 
> > From the etherpad, I see a deadline set of August 5. Is that for
> > nominations, or the election to have an outcome?
> > 
> > For the record, Anita has agreed to be the primary election official,
> > and I will assist her.
> > 
> > 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
> > 
> 
> That's for the self nomination period.  Immediately after that is when
> the election would be, we may vote in the meeting that day for just one
> of us to be put forward or do a normal election, I don't think we've
> clarified that yet.
> 

OK. We have some time to work that out, then.

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] [ptl][requirements] nomination period started

[Tony Breeds]

On Wed, Jul 27, 2016 at 10:07:20AM -0400, Doug Hellmann wrote:

> For the record, Anita has agreed to be the primary election official,
> and I will assist her.

Thanks Doug and Anita!

Yours Tony.


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] [ptl][requirements] nomination period started

[Matthew Thode]

On 07/27/2016 09:07 AM, Doug Hellmann wrote:
> Excerpts from Matthew Thode's message of 2016-07-27 08:41:17 -0500:
>> We've started a period of self nomination in preparation for the
>> requirements project fully moving into project (as it's still under Doug
>> Hellmann).
>>
>> We are gathering the self nominations here before we vote next week.
>> https://etherpad.openstack.org/p/requirements-ptl-newton
>>
>> Nominees should also send an email to the openstack-dev list.
>>
> 
> Thanks for kicking this off, Matt! I'm looking forward to seeing this
> team fully self-sufficient.
> 
> From the etherpad, I see a deadline set of August 5. Is that for
> nominations, or the election to have an outcome?
> 
> For the record, Anita has agreed to be the primary election official,
> and I will assist her.
> 
> 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
> 

That's for the self nomination period.  Immediately after that is when
the election would be, we may vote in the meeting that day for just one
of us to be put forward or do a normal election, I don't think we've
clarified that yet.

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP 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] [ptl][requirements] nomination period started

[Doug Hellmann]

Excerpts from Matthew Thode's message of 2016-07-27 08:41:17 -0500:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
> 
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
> 
> Nominees should also send an email to the openstack-dev list.
> 

Thanks for kicking this off, Matt! I'm looking forward to seeing this
team fully self-sufficient.

>From the etherpad, I see a deadline set of August 5. Is that for
nominations, or the election to have an outcome?

For the record, Anita has agreed to be the primary election official,
and I will assist her.

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] [ptl][requirements] nomination period started

[Davanum Srinivas]

w00t!! Glad to see this happen.

-- Dims

On Wed, Jul 27, 2016 at 9:41 AM, Matthew Thode
 wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
>
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
>
> Nominees should also send an email to the openstack-dev list.
>
> --
> -- Matthew Thode (prometheanfire)
>
>
> __
> 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
>



-- 
Davanum Srinivas :: https://twitter.com/dims

__
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] [ptl][requirements] nomination period started

[Matthew Thode]

On 07/27/2016 08:41 AM, Matthew Thode wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
> 
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
> 
> Nominees should also send an email to the openstack-dev list.
> 

And here's my self nomination email

I originally joined as a packager as we use requirements for some
dependency definitions.  I have since moved on to work on making
requirements changes verify changes against outside projects so as to
not break things once merged (better testing). other than that, just
keeping up on the queue :D

If you have any questions or concerns feel free to ask.

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP 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

[openstack-dev] [ptl][requirements] nomination period started

[Matthew Thode]

We've started a period of self nomination in preparation for the
requirements project fully moving into project (as it's still under Doug
Hellmann).

We are gathering the self nominations here before we vote next week.
https://etherpad.openstack.org/p/requirements-ptl-newton

Nominees should also send an email to the openstack-dev list.

-- 
-- Matthew Thode (prometheanfire)



signature.asc
Description: OpenPGP 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