Greetings OpenStack community, Our main new topic for today was making sure that we take a more active role in curating the bugs that are now being kept in launchpad [4] by including review of those bugs in the workshopping that we do in each meeting. If you find issues in the existing guidelines or think a guideline is missing, make a bug. The meeting logs are in the usual place. [5] # New guidelines * A guideline for links https://review.openstack.org/354266 # API guidelines proposed for freeze The following guidelines are available for broader review by interested parties. These will be merged in one week if there is no further feedback. * Add the beginning of a set of guidlines for URIs https://review.openstack.org/#/c/322194/ # Guidelines currently under review These are guidelines that the working group are debating and working on for consistency and language. We encourage any interested parties to join in the conversation. * Clarify backslash usage for 'in' operator https://review.openstack.org/#/c/353396/ * Clear the case if the version string isn't parsable https://review.openstack.org/#/c/346846/ # API Impact reviews currently open Reviews marked as APIImpact [1] are meant to help inform the working group about changes which would benefit from wider inspection by group members and liaisons. While the working group will attempt to address these reviews whenever possible, it is highly recommended that interested parties attend the API-WG meetings [2] to promote communication surrounding their reviews. To learn more about the API WG mission and the work we do, see OpenStack API Working Group [3]. Thanks for reading and see you next week! [1] https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z [2] https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda [3] http://specs.openstack.org/openstack/api-wg/ [4]: https://bugs.launchpad.net/openstack-api-wg [5]: http://eavesdrop.openstack.org/meetings/api_wg/