Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update

2017-12-01 Thread Adam Heczko 
AFAIR there was attempt to push oslo.policy into Swift but it looks like
the patch was abandoned.
https://review.openstack.org/#/c/149930/

On Fri, Dec 1, 2017 at 8:04 AM, hie...@vn.fujitsu.com <hie...@vn.fujitsu.com
> wrote:

> FYI, I have updated the topic for Heat's works [1]. And finally no more
> projects in 'Not Started' list. :-)
>
> [1]. https://review.openstack.org/#/q/status:open+project:
> openstack/heat+branch:master+topic:policy-and-docs-in-code
>
> Regards,
> Hieu
>
> > -Original Message-
> > From: Lance Bragstad [mailto:lbrags...@gmail.com]
> > Sent: Friday, December 01, 2017 12:01 PM
> > To: OpenStack Development Mailing List (not for usage questions)
>  > d...@lists.openstack.org>
> > Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
> >
> >
> >
> > On 11/30/2017 07:00 PM, hie...@vn.fujitsu.com wrote:
> > > Lance,
> > >
> > >>> For the Swift project, I don't see oslo.policy in requirements.txt
> > >>> for now, then not sure they need to implement policy in code and the
> > >>> we got the same
> > >> thing with Solum.
> > >> So does that mean these can be removed as well? I'm wondering if
> > >> there is an official process here, or just a simple sign-off from a
> project maintainer?
> > > Swift did not use oslo.policy and use their own mechanism instead, so
> I guess we
> > can remove Swift along with remaining networking-* plugins as well.
> > >
> > > BTW, ceilometer had already deprecated and removed ceilometer API from
> > > Q, thus we can also remove ceilometer from the list too. [1]
> > >
> > > I have created PR regarding all above changes in [2].
> > Merged. Thanks for looking into this. New results should be available in
> the burndown
> > chart.
> > > Thanks,
> > > Hieu.
> > >
> > > [1].
> > > https://github.com/openstack/ceilometer/commit/d881dd52289d453b9f9d94c
> > > 7c32c0672a70a8064 [2].
> > > https://github.com/lbragstad/openstack-doc-migration-burndown/pull/1
> > >
> > >
> > >> -Original Message-
> > >> From: Lance Bragstad [mailto:lbrags...@gmail.com]
> > >> Sent: Thursday, November 30, 2017 10:41 PM
> > >> To: OpenStack Development Mailing List (not for usage questions)
> > >> 
> > >> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
> > >>
> > >>
> > >>
> > >> On 11/29/2017 09:13 PM, da...@vn.fujitsu.com wrote:
> > >>> Hi all,
> > >>>
> > >>> I just want to share some related things to anyone are interested in.
> > >>>
> > >>> For the Neutron projects, I have discussed with them[1] but it is
> > >>> not really started, they want to consider more about all of
> > >>> networking projects before and I'm still waiting for the feedback to
> > >>> define the right way to
> > >> implement policy-in-code for networking projects.
> > >>> For the other extensions of Neutron, we got some
> > >>> recommendations[2][3] that we no need to implement policy-in-code
> > >>> into those projects because we already register policy in Neutron,
> > >>> so I think we can remove neutron-
> > >> fwaas, neutron-dynamic-routing, neutron-lib or even other networking
> > >> plugins out of "Not Started" list.
> > >> Awesome, thanks for the update! I've gone ahead and removed these
> > >> from the burndown chart [0]. Let me know if there are any others that
> > >> fall into this category and I'll get things updated in the tracking
> tool.
> > >>
> > >> [0]
> > >> https://github.com/lbragstad/openstack-doc-migration-
> > >> burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
> > >>> For the Swift project, I don't see oslo.policy in requirements.txt
> > >>> for now, then not sure they need to implement policy in code and the
> > >>> we got the same
> > >> thing with Solum.
> > >> So does that mean these can be removed as well? I'm wondering if
> > >> there is an official process here, or just a simple sign-off from a
> project maintainer?
> > >>> [1]
> > >>> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23opens
> > >>> ta
> > >>> ck-neutron.2017-10-31.log.html [2]
> > >>> http://eavesdrop.openstack.

Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update

2017-11-30 Thread hie...@vn.fujitsu.com 
FYI, I have updated the topic for Heat's works [1]. And finally no more 
projects in 'Not Started' list. :-)

[1]. 
https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:policy-and-docs-in-code

Regards,
Hieu

> -Original Message-
> From: Lance Bragstad [mailto:lbrags...@gmail.com]
> Sent: Friday, December 01, 2017 12:01 PM
> To: OpenStack Development Mailing List (not for usage questions)  d...@lists.openstack.org>
> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
> 
> 
> 
> On 11/30/2017 07:00 PM, hie...@vn.fujitsu.com wrote:
> > Lance,
> >
> >>> For the Swift project, I don't see oslo.policy in requirements.txt
> >>> for now, then not sure they need to implement policy in code and the
> >>> we got the same
> >> thing with Solum.
> >> So does that mean these can be removed as well? I'm wondering if
> >> there is an official process here, or just a simple sign-off from a 
> >> project maintainer?
> > Swift did not use oslo.policy and use their own mechanism instead, so I 
> > guess we
> can remove Swift along with remaining networking-* plugins as well.
> >
> > BTW, ceilometer had already deprecated and removed ceilometer API from
> > Q, thus we can also remove ceilometer from the list too. [1]
> >
> > I have created PR regarding all above changes in [2].
> Merged. Thanks for looking into this. New results should be available in the 
> burndown
> chart.
> > Thanks,
> > Hieu.
> >
> > [1].
> > https://github.com/openstack/ceilometer/commit/d881dd52289d453b9f9d94c
> > 7c32c0672a70a8064 [2].
> > https://github.com/lbragstad/openstack-doc-migration-burndown/pull/1
> >
> >
> >> -----Original Message-
> >> From: Lance Bragstad [mailto:lbrags...@gmail.com]
> >> Sent: Thursday, November 30, 2017 10:41 PM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> 
> >> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
> >>
> >>
> >>
> >> On 11/29/2017 09:13 PM, da...@vn.fujitsu.com wrote:
> >>> Hi all,
> >>>
> >>> I just want to share some related things to anyone are interested in.
> >>>
> >>> For the Neutron projects, I have discussed with them[1] but it is
> >>> not really started, they want to consider more about all of
> >>> networking projects before and I'm still waiting for the feedback to
> >>> define the right way to
> >> implement policy-in-code for networking projects.
> >>> For the other extensions of Neutron, we got some
> >>> recommendations[2][3] that we no need to implement policy-in-code
> >>> into those projects because we already register policy in Neutron,
> >>> so I think we can remove neutron-
> >> fwaas, neutron-dynamic-routing, neutron-lib or even other networking
> >> plugins out of "Not Started" list.
> >> Awesome, thanks for the update! I've gone ahead and removed these
> >> from the burndown chart [0]. Let me know if there are any others that
> >> fall into this category and I'll get things updated in the tracking tool.
> >>
> >> [0]
> >> https://github.com/lbragstad/openstack-doc-migration-
> >> burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
> >>> For the Swift project, I don't see oslo.policy in requirements.txt
> >>> for now, then not sure they need to implement policy in code and the
> >>> we got the same
> >> thing with Solum.
> >> So does that mean these can be removed as well? I'm wondering if
> >> there is an official process here, or just a simple sign-off from a 
> >> project maintainer?
> >>> [1]
> >>> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23opens
> >>> ta
> >>> ck-neutron.2017-10-31.log.html [2]
> >>> http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23opensta
> >>> ck
> >>> -lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
> >>> [3] https://review.openstack.org/#/c/509389/
> >>>
> >>> Dai
> >>>
> >>>
> >>
> ___
> >> ___
> >>>  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] [all] [tc] Policy Goal Queens-2 Update

2017-11-30 Thread Lance Bragstad 


On 11/30/2017 07:00 PM, hie...@vn.fujitsu.com wrote:
> Lance,
>
>>> For the Swift project, I don't see oslo.policy in requirements.txt for
>>> now, then not sure they need to implement policy in code and the we got the 
>>> same
>> thing with Solum.
>> So does that mean these can be removed as well? I'm wondering if there is an 
>> official
>> process here, or just a simple sign-off from a project maintainer?
> Swift did not use oslo.policy and use their own mechanism instead, so I guess 
> we can remove Swift along with remaining networking-* plugins as well.
>
> BTW, ceilometer had already deprecated and removed ceilometer API from Q, 
> thus we can also remove ceilometer from the list too. [1]
>
> I have created PR regarding all above changes in [2].
Merged. Thanks for looking into this. New results should be available in
the burndown chart.
> Thanks,
> Hieu.
>
> [1]. 
> https://github.com/openstack/ceilometer/commit/d881dd52289d453b9f9d94c7c32c0672a70a8064
> [2]. https://github.com/lbragstad/openstack-doc-migration-burndown/pull/1
>
>
>> -Original Message-
>> From: Lance Bragstad [mailto:lbrags...@gmail.com]
>> Sent: Thursday, November 30, 2017 10:41 PM
>> To: OpenStack Development Mailing List (not for usage questions) > d...@lists.openstack.org>
>> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
>>
>>
>>
>> On 11/29/2017 09:13 PM, da...@vn.fujitsu.com wrote:
>>> Hi all,
>>>
>>> I just want to share some related things to anyone are interested in.
>>>
>>> For the Neutron projects, I have discussed with them[1] but it is not
>>> really started, they want to consider more about all of networking
>>> projects before and I'm still waiting for the feedback to define the right 
>>> way to
>> implement policy-in-code for networking projects.
>>> For the other extensions of Neutron, we got some recommendations[2][3]
>>> that we no need to implement policy-in-code into those projects
>>> because we already register policy in Neutron, so I think we can remove 
>>> neutron-
>> fwaas, neutron-dynamic-routing, neutron-lib or even other networking plugins 
>> out of
>> "Not Started" list.
>> Awesome, thanks for the update! I've gone ahead and removed these from the
>> burndown chart [0]. Let me know if there are any others that fall into this 
>> category and
>> I'll get things updated in the tracking tool.
>>
>> [0]
>> https://github.com/lbragstad/openstack-doc-migration-
>> burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
>>> For the Swift project, I don't see oslo.policy in requirements.txt for
>>> now, then not sure they need to implement policy in code and the we got the 
>>> same
>> thing with Solum.
>> So does that mean these can be removed as well? I'm wondering if there is an 
>> official
>> process here, or just a simple sign-off from a project maintainer?
>>> [1]
>>> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23opensta
>>> ck-neutron.2017-10-31.log.html [2]
>>> http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack
>>> -lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
>>> [3] https://review.openstack.org/#/c/509389/
>>>
>>> Dai
>>>
>>>
>> ___
>> ___
>>>  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


__
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] [all] [tc] Policy Goal Queens-2 Update

2017-11-30 Thread hie...@vn.fujitsu.com 
Lance,

> > For the Swift project, I don't see oslo.policy in requirements.txt for
> > now, then not sure they need to implement policy in code and the we got the 
> > same
> thing with Solum.
> So does that mean these can be removed as well? I'm wondering if there is an 
> official
> process here, or just a simple sign-off from a project maintainer?

Swift did not use oslo.policy and use their own mechanism instead, so I guess 
we can remove Swift along with remaining networking-* plugins as well.

BTW, ceilometer had already deprecated and removed ceilometer API from Q, thus 
we can also remove ceilometer from the list too. [1]

I have created PR regarding all above changes in [2].

Thanks,
Hieu.

[1]. 
https://github.com/openstack/ceilometer/commit/d881dd52289d453b9f9d94c7c32c0672a70a8064
[2]. https://github.com/lbragstad/openstack-doc-migration-burndown/pull/1


> -Original Message-
> From: Lance Bragstad [mailto:lbrags...@gmail.com]
> Sent: Thursday, November 30, 2017 10:41 PM
> To: OpenStack Development Mailing List (not for usage questions)  d...@lists.openstack.org>
> Subject: Re: [openstack-dev] [all] [tc] Policy Goal Queens-2 Update
> 
> 
> 
> On 11/29/2017 09:13 PM, da...@vn.fujitsu.com wrote:
> > Hi all,
> >
> > I just want to share some related things to anyone are interested in.
> >
> > For the Neutron projects, I have discussed with them[1] but it is not
> > really started, they want to consider more about all of networking
> > projects before and I'm still waiting for the feedback to define the right 
> > way to
> implement policy-in-code for networking projects.
> >
> > For the other extensions of Neutron, we got some recommendations[2][3]
> > that we no need to implement policy-in-code into those projects
> > because we already register policy in Neutron, so I think we can remove 
> > neutron-
> fwaas, neutron-dynamic-routing, neutron-lib or even other networking plugins 
> out of
> "Not Started" list.
> Awesome, thanks for the update! I've gone ahead and removed these from the
> burndown chart [0]. Let me know if there are any others that fall into this 
> category and
> I'll get things updated in the tracking tool.
> 
> [0]
> https://github.com/lbragstad/openstack-doc-migration-
> burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
> >
> > For the Swift project, I don't see oslo.policy in requirements.txt for
> > now, then not sure they need to implement policy in code and the we got the 
> > same
> thing with Solum.
> So does that mean these can be removed as well? I'm wondering if there is an 
> official
> process here, or just a simple sign-off from a project maintainer?
> >
> > [1]
> > http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23opensta
> > ck-neutron.2017-10-31.log.html [2]
> > http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack
> > -lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
> > [3] https://review.openstack.org/#/c/509389/
> >
> > Dai
> >
> >
> ___
> ___
> >  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] [all] [tc] Policy Goal Queens-2 Update

2017-11-30 Thread Lance Bragstad 


On 11/29/2017 09:13 PM, da...@vn.fujitsu.com wrote:
> Hi all,
>
> I just want to share some related things to anyone are interested in.
>
> For the Neutron projects, I have discussed with them[1] but it is not really 
> started,
> they want to consider more about all of networking projects before and I'm 
> still waiting for the feedback to
> define the right way to implement policy-in-code for networking projects.
>
> For the other extensions of Neutron, we got some recommendations[2][3] that 
> we no need to implement
> policy-in-code into those projects because we already register policy in 
> Neutron, so I think we can remove
> neutron-fwaas, neutron-dynamic-routing, neutron-lib or even other networking 
> plugins out of "Not Started" list.
Awesome, thanks for the update! I've gone ahead and removed these from
the burndown chart [0]. Let me know if there are any others that fall
into this category and I'll get things updated in the tracking tool.

[0]
https://github.com/lbragstad/openstack-doc-migration-burndown/commit/f34c2f56692230f104354240bf0e4378dc0fea82
>
> For the Swift project, I don't see oslo.policy in requirements.txt for now,
> then not sure they need to implement policy in code and the we got the same 
> thing with Solum.
So does that mean these can be removed as well? I'm wondering if there
is an official process here, or just a simple sign-off from a project
maintainer?
>
> [1] 
> http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2017-10-31.log.html
> [2] 
> http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
> [3] https://review.openstack.org/#/c/509389/
>
> Dai
>
> __
> 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




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] [all] [tc] Policy Goal Queens-2 Update

2017-11-29 Thread da...@vn.fujitsu.com 
Hi all,

I just want to share some related things to anyone are interested in.

For the Neutron projects, I have discussed with them[1] but it is not really 
started,
they want to consider more about all of networking projects before and I'm 
still waiting for the feedback to
define the right way to implement policy-in-code for networking projects.

For the other extensions of Neutron, we got some recommendations[2][3] that we 
no need to implement
policy-in-code into those projects because we already register policy in 
Neutron, so I think we can remove
neutron-fwaas, neutron-dynamic-routing, neutron-lib or even other networking 
plugins out of "Not Started" list.

For the Swift project, I don't see oslo.policy in requirements.txt for now,
then not sure they need to implement policy in code and the we got the same 
thing with Solum.

[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%23openstack-neutron.2017-10-31.log.html
[2] 
http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2017-10-06.log.html#t2017-10-06T02:50:10
[3] https://review.openstack.org/#/c/509389/

Dai

__
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] [all] [tc] Policy Goal Queens-2 Update

2017-11-28 Thread Lance Bragstad 
We have quite a bit in progress already. The following are little things
people can do that make a big difference, outside of picking up the
implementation for a given project:

- Reviews are huge. If we can get things reviewed and +1'd from a goal
perspective (e.g. does this meet the requirements? are policies
documented? is it consistent?), then it makes things easier when a core
reviewer comes along. I'm sort of expecting the core reviewers of the
projects to ensure the policies are documented in a way that makes sense
from a project-perspective.
- Updating patches with the `policy-and-docs-in-code` topic. A lot of
patches are getting missed in tracking because sometimes the topic gets
updated with new patch sets.
- Reviewing and proposing patches to governance for projects that have
completed all the work. This just consists of double checking the work
against the goal criteria [1] and making sure we include planning and
completion artifacts for the project if they have everything done.

That should really help us push what we have in progress through to
completion.

[0] https://review.openstack.org/#/c/458677/
[1]
https://governance.openstack.org/tc/goals/queens/policy-in-code.html#completion-criteria

On 11/28/2017 11:18 AM, Harry Rybacki wrote:
> On Tue, Nov 28, 2017 at 12:14 PM, Lance Bragstad  wrote:
>> Hi all,
>>
>> As Queens 2 comes to a close next week, I figured it was a good time to
>> recap the policy goal [0]. The following is the breakdown of where projects
>> stand with how I've been tracking things.
>>
>> Not Started
>>
>> openstack/ceilometer
>> openstack/congress
>> openstack/networking-bgpvpn
>> openstack/networking-midonet
>> openstack/networking-odl
>> openstack/neutron-dynamic-routing
>> openstack/neutron-fwaas
>> openstack/neutron-lib
>> openstack/solum
>> openstack/swift
>>
> Okay, I think I can jump into these and help out a bit. Any of the
> above you would recommend as a starter?
>
>> In Progress
>>
>> openstack/barbican
>> openstack/cinder
>> openstack/cloudkitty
>> openstack/glance
>> openstack/heat
>> openstack/manila
>> openstack/mistral
>> openstack/neutron
>> openstack/panko
>> openstack/python-heatclient
>> openstack/tacker
>> openstack/tricircle
>> openstack/trove
>> openstack/vitrage
>> openstack/watcher
>> openstack/zaqar
>>
>> Completed
>>
>> openstack/designate
>> openstack/freezer
>> openstack/ironic
>> openstack/keystone
>> openstack/magnum
>> openstack/murano
>> openstack/nova
>> openstack/octavia
>> openstack/sahara
>> openstack/searchlight
>> openstack/senlin
>> openstack/zun
>>
>> Note that a lot of the projects "In Progress" are only pending reviews to
>> publish sample policy documentation. If a project you're working on has
>> already done this, please let me know and I'll get a patch posted to
>> governance to mark the status as completed. If you have patches in flight
>> the works towards this goal, please be sure to use the
>> `policy-and-docs-in-code` topic in Gerrit. It will be picked up and tracked
>> automatically [1]. With such a large change, visualizing and leaning on
>> automation in any way we can really helps in managing the goal.
>>
>> Finally, I'd like to give a huge "Thank You" to Dai Dang Van, Nam Nguyen
>> Hoai, and Hieu LE. They've all dug into to help other projects complete the
>> goal and review patches. We certainly wouldn't be seeing as many projects in
>> the Completed or In Progress list if not for their help.
>>
>> As always, feel free to come find me on IRC if you have questions. If I'm
>> missing status for your project(s), just ping me and I'll make sure things
>> get tracked and recorded.
>>
>> Thanks for the time!
>>
>> Lance
>>
>>
>> [0] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
>> [1] https://www.lbragstad.com/policy-burndown/
>>
>> __
>> 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




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] [all] [tc] Policy Goal Queens-2 Update

2017-11-28 Thread Harry Rybacki 
On Tue, Nov 28, 2017 at 12:14 PM, Lance Bragstad  wrote:
> Hi all,
>
> As Queens 2 comes to a close next week, I figured it was a good time to
> recap the policy goal [0]. The following is the breakdown of where projects
> stand with how I've been tracking things.
>
> Not Started
>
> openstack/ceilometer
> openstack/congress
> openstack/networking-bgpvpn
> openstack/networking-midonet
> openstack/networking-odl
> openstack/neutron-dynamic-routing
> openstack/neutron-fwaas
> openstack/neutron-lib
> openstack/solum
> openstack/swift
>
Okay, I think I can jump into these and help out a bit. Any of the
above you would recommend as a starter?

> In Progress
>
> openstack/barbican
> openstack/cinder
> openstack/cloudkitty
> openstack/glance
> openstack/heat
> openstack/manila
> openstack/mistral
> openstack/neutron
> openstack/panko
> openstack/python-heatclient
> openstack/tacker
> openstack/tricircle
> openstack/trove
> openstack/vitrage
> openstack/watcher
> openstack/zaqar
>
> Completed
>
> openstack/designate
> openstack/freezer
> openstack/ironic
> openstack/keystone
> openstack/magnum
> openstack/murano
> openstack/nova
> openstack/octavia
> openstack/sahara
> openstack/searchlight
> openstack/senlin
> openstack/zun
>
> Note that a lot of the projects "In Progress" are only pending reviews to
> publish sample policy documentation. If a project you're working on has
> already done this, please let me know and I'll get a patch posted to
> governance to mark the status as completed. If you have patches in flight
> the works towards this goal, please be sure to use the
> `policy-and-docs-in-code` topic in Gerrit. It will be picked up and tracked
> automatically [1]. With such a large change, visualizing and leaning on
> automation in any way we can really helps in managing the goal.
>
> Finally, I'd like to give a huge "Thank You" to Dai Dang Van, Nam Nguyen
> Hoai, and Hieu LE. They've all dug into to help other projects complete the
> goal and review patches. We certainly wouldn't be seeing as many projects in
> the Completed or In Progress list if not for their help.
>
> As always, feel free to come find me on IRC if you have questions. If I'm
> missing status for your project(s), just ping me and I'll make sure things
> get tracked and recorded.
>
> Thanks for the time!
>
> Lance
>
>
> [0] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
> [1] https://www.lbragstad.com/policy-burndown/
>
> __
> 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

[openstack-dev] [all] [tc] Policy Goal Queens-2 Update

2017-11-28 Thread Lance Bragstad 
Hi all,

As Queens 2 comes to a close next week, I figured it was a good time to
recap the policy goal [0]. The following is the breakdown of where
projects stand with how I've been tracking things.
*
Not Started**
*
openstack/ceilometer
openstack/congress
openstack/networking-bgpvpn
openstack/networking-midonet
openstack/networking-odl
openstack/neutron-dynamic-routing
openstack/neutron-fwaas
openstack/neutron-lib
openstack/solum
openstack/swift
*
In Progress*

openstack/barbican
openstack/cinder
openstack/cloudkitty
openstack/glance
openstack/heat
openstack/manila
openstack/mistral
openstack/neutron
openstack/panko
openstack/python-heatclient
openstack/tacker
openstack/tricircle
openstack/trove
openstack/vitrage
openstack/watcher
openstack/zaqar
*
Completed

*openstack/designate
openstack/freezer
openstack/ironic
openstack/keystone
openstack/magnum
openstack/murano
openstack/nova
openstack/octavia
openstack/sahara
openstack/searchlight
openstack/senlin
openstack/zun
**
Note that a lot of the projects "In Progress" are only pending reviews
to publish sample policy documentation. If a project you're working on
has already done this, please let me know and I'll get a patch posted to
governance to mark the status as completed. If you have patches in
flight the works towards this goal, please be sure to use the
`policy-and-docs-in-code` topic in Gerrit. It will be picked up and
tracked automatically [1]. With such a large change, visualizing and
leaning on automation in any way we can really helps in managing the goal.

Finally, I'd like to give a huge "Thank You" to Dai Dang Van, Nam Nguyen
Hoai, and Hieu LE. They've all dug into to help other projects complete
the goal and review patches. We certainly wouldn't be seeing as many
projects in the Completed or In Progress list if not for their help.

As always, feel free to come find me on IRC if you have questions. If
I'm missing status for your project(s), just ping me and I'll make sure
things get tracked and recorded.

Thanks for the time!

Lance


[0] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
[1] https://www.lbragstad.com/policy-burndown/


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