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 <lbrags...@gmail.com> 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