__NOTOC__

This is the list of etherpads for the Projects Team Gathering in Shanghai, 2019.
This page was dumped from [http://ptg.openstack.org/etherpads.html ptgbot page] after the PTG.

* airship: https://etherpad.opendev.org/p/airship-virtual-ptg-2020
* api-sig: https://etherpad.opendev.org/p/victoria-ptg-api-sig
* automation-sig: https://etherpad.openstack.org/p/victoria-ptg-automation-sig
* barbican: https://etherpad.openstack.org/p/victoria-ptg-barbican
* blazar: https://etherpad.opendev.org/p/blazar-ptg-victoria
* charms: https://etherpad.openstack.org/p/victoria-ptg-charms
* cinder: https://etherpad.openstack.org/p/victoria-ptg-cinder
* cyborg: https://etherpad.opendev.org/p/cyborg-victoria-goals
* diversity-wg: https://etherpad.openstack.org/p/victoria-ptg-diversity-wg
* edge: https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020
* first-contact: https://etherpad.openstack.org/p/victoria-ptg-first-contact
* glance: https://etherpad.opendev.org/p/Glance-Victoria-PTG-planning
* heat: https://etherpad.opendev.org/p/heat-victoria-vptg
* horizon: https://etherpad.opendev.org/p/horizon-v-ptg
* interop-wg: https://etherpad.openstack.org/p/victoria-ptg-interop-wg
* ironic: https://etherpad.opendev.org/p/Ironic-VictoriaPTG-Planning
* kata: https://etherpad.openstack.org/p/victoria-ptg-kata
* keystone: https://etherpad.openstack.org/p/victoria-ptg-keystone
* kolla: https://etherpad.opendev.org/p/kolla-victoria-ptg
* magnum: https://etherpad.openstack.org/p/victoria-ptg-magnum
* manila: https://etherpad.openstack.org/p/victoria-ptg-manila
* monasca: https://etherpad.opendev.org/p/monasca-ptg-victoria
* multiarch-sig: https://etherpad.opendev.org/p/Multi-arch-2020-VPTG
* neutron: https://etherpad.opendev.org/p/neutron-victoria-ptg
* nova: https://etherpad.opendev.org/p/nova-victoria-ptg
* octavia: https://etherpad.opendev.org/p/octavia-virtual-V-ptg
* opendev: https://etherpad.opendev.org/p/opendev-virtual-ptg-june-2020
* ops-meetup: https://etherpad.openstack.org/p/victoria-ptg-ops-meetup
* os-ansible: https://etherpad.openstack.org/p/victoria-ptg-os-ansible
* os-ansible-modules: https://etherpad.openstack.org/p/victoria-ptg-os-ansible-modules
* os-helm: https://etherpad.opendev.org/p/openstack-helm-ptg-victoria
* oslo: https://etherpad.opendev.org/p/oslo-victoria-topics
* qa: https://etherpad.opendev.org/p/qa-victoria-ptg
* relmgt: https://etherpad.opendev.org/p/relmgmt-victoria-ptg
* scientific-sig: https://etherpad.openstack.org/p/victoria-ptg-scientific-sig
* sdk-cli: https://etherpad.opendev.org/p/sdk-victoriaptg-planning
* security-sig: https://etherpad.opendev.org/p/security-sig-ptg-victoria
* starlingx: https://etherpad.opendev.org/p/stx-virtual-PTG-June
* swift: https://etherpad.opendev.org/p/swift-ptg-victoria
* tacker: https://etherpad.opendev.org/p/Tacker-PTG-Victoria
* tc: https://etherpad.opendev.org/p/tc-victoria-ptg
* tripleo: https://etherpad.opendev.org/p/tripleo-ptg-victoria
* uc: https://etherpad.openstack.org/p/victoria-ptg-uc

PTG/Ussuri/Etherpads

2019-11-13T13:08:18Z

__NOTOC__

This is the list of etherpads for the Projects Team Gathering in Shanghai, 2019.
This page was dumped from [http://ptg.openstack.org/etherpads.html ptgbot page] after the PTG.

* airship: https://etherpad.openstack.org/p/shanghai-ptg-airship
* auto-scaling-sig: https://etherpad.openstack.org/p/shanghai-ptg-auto-scaling-sig
* barbican: https://etherpad.openstack.org/p/barbican-ussuri-ptg
* blazar: https://etherpad.openstack.org/p/blazar-ptg-ussuri
* cinder: https://etherpad.openstack.org/p/shanghai-ptg-cinder
* cyborg: https://etherpad.openstack.org/p/shanghai-ptg-cyborg
* edge-computing-group: https://etherpad.openstack.org/p/PVG-ECG-PTG
* fenix: https://etherpad.openstack.org/p/Shanghai2019-Fenix-PTG
* financial-wg: https://etherpad.openstack.org/p/shanghai-ptg-financial-wg
* first-contact-sig: https://etherpad.openstack.org/p/shanghai-ptg-first-contact-sig
* gitea: https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019
* glance: https://etherpad.openstack.org/p/shanghai-ptg-glance
* heat: https://etherpad.openstack.org/p/shanghai-ptg-heat
* horizon: https://etherpad.openstack.org/p/horizon-u-ptg
* i18n: https://etherpad.openstack.org/p/shanghai-ptg-i18n
* infra-opendev: https://etherpad.openstack.org/p/OpenDev-Shanghai-PTG-2019
* interviews: https://etherpad.openstack.org/p/shanghai-ptg-interviews
* ironic: https://etherpad.openstack.org/p/shanghai-ptg-ironic
* k8s-sig: https://etherpad.openstack.org/p/shanghai-ptg-k8s-sig
* karbor: https://etherpad.openstack.org/p/shanghai-ptg-karbor
* kata-containers: https://etherpad.openstack.org/p/shanghai-ptg-kata-containers
* keystone: https://etherpad.openstack.org/p/shanghai-ptg-keystone
* loci: https://etherpad.openstack.org/p/shanghai-ptg-loci
* manila: https://etherpad.openstack.org/p/shanghai-ptg-manila
* meta-sig: https://etherpad.openstack.org/p/shanghai-ptg-meta-sig
* monasca: https://etherpad.openstack.org/p/shanghai-ptg-monasca
* neutron: https://etherpad.openstack.org/p/Shanghai-Neutron-Planning-restored
* nova: https://etherpad.openstack.org/p/nova-shanghai-ptg
* octavia: https://etherpad.openstack.org/p/octavia-shanghai-U-ptg
* openstack-charms: https://etherpad.openstack.org/p/shanghai-ptg-openstack-charms
* openstack-docs: https://etherpad.openstack.org/p/shanghai-ptg-openstack-docs
* openstack-tc: https://etherpad.openstack.org/p/PVG-TC-PTG
* ops-meetup: https://etherpad.openstack.org/p/shanghai-ptg-ops-meetup
* oslo: https://etherpad.openstack.org/p/oslo-shanghai-topics
* placement: https://etherpad.openstack.org/p/placement-shanghai-ptg
* public-cloud-sig: https://etherpad.openstack.org/p/shanghai-ptg-public-cloud-sig
* qa: https://etherpad.openstack.org/p/shanghai-ptg-qa
* release-management: https://etherpad.openstack.org/p/shanghai-ptg-release-management
* sahara: https://etherpad.openstack.org/p/shanghai-ptg-sahara
* scientific-sig: https://etherpad.openstack.org/p/shanghai-ptg-scientific-sig
* self-healing-sig: https://etherpad.openstack.org/p/shanghai-ptg-self-healing-sig
* starlingx: https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai
* storlets: https://etherpad.openstack.org/p/shanghai-ptg-storlets
* storyboard: https://etherpad.openstack.org/p/shanghai-ptg-storyboard
* swift: https://etherpad.openstack.org/p/swift-ptg-shanghai
* tacker: https://etherpad.openstack.org/p/shanghai-ptg-tacker
* tripleo: https://etherpad.openstack.org/p/shanghai-ptg-tripleo

Forum/Shanghai2019

2019-11-04T08:53:35Z

Amotoki: /* Monday November 4 */

== Etherpads ==
The grand list of all of the Shanghai 2019 [[Forum]] etherpads. Please add links to etherpads below!
(You might use the prior Forum entries for ideas: https://wiki.openstack.org/wiki/Forum/Berlin2018 or https://wiki.openstack.org/wiki/Forum/Denver2019)

At the Forum the entire OpenStack community (users and developers) gathers to brainstorm the requirements for the next release, gather feedback on the past version and have strategic discussions that go beyond just one release cycle. The Berlin Forum was the start of the planning phase for the '''U''' development cycle. Please prepare session ideas with feedback from the '''Train''' release in mind.

=== Monday November 4 ===
* [10:50-11:30] [https://etherpad.openstack.org/p/PVG-billing-openstack How should we do billing for OpenStack deployments?]
* [11:40-12:20] [https://etherpad.openstack.org/p/PVG-Deletion-of-resources Project Resource Cleanup]
* [11:40-12:20] [https://etherpad.openstack.org/p/shanghai-ptg-ops-war-stories Ops War Stories]
* [13:20-14:00] [https://etherpad.openstack.org/p/placeholder Placeholder]
* [14:10-14:50] [https://etherpad.openstack.org/p/PVG-how-using-cinder-volume-types How are you using Cinder's Volume Types?]
* [14:10-14:50] [https://etherpad.openstack.org/p/PVG-ironic-operator-feedback Ironic Operator Feedback]
* [15:00-15:40] [https://etherpad.openstack.org/p/PVG-ironic-snapshot-support Ironic - Snapshots?]
* [16:00-16:40] [https://etherpad.openstack.org/p/PVG-edge-wg-forum Edge Use Cases and Reference Architectures Discussion]
* [16:50-17:30] [https://etherpad.openstack.org/p/PVG-keystone-forum-policy Next steps for policy in OpenStack]

=== Tuesday November 5 ===
* [09:00-09:40] [https://etherpad.openstack.org/p/placeholder Placeholder]
* [09:50-10:30] [https://etherpad.openstack.org/p/placeholder Placeholder]
* [10:50-11:30] [https://etherpad.openstack.org/p/placeholder Placeholder]
* [11:40-12:20] [https://etherpad.openstack.org/p/placeholder Placeholder]

=== Wednesday November 6 ===

==List of Brainstorming Etherpads==

===Catch-alls===
If you want to post an idea, but aren't working with a specific team or working group, you can use these:
*[https://etherpad.openstack.org/p/PVG-UC-brainstorming UC Catch All ]

===Etherpads from Teams and Working Groups===
* Auto-scaling SIG: https://etherpad.openstack.org/p/PVG-auto-scaling-sig
* Charms: https://etherpad.openstack.org/p/shanghai-ptg-openstack-charms
* Cinder: https://etherpad.openstack.org/p/cinder-shanghai-forum-proposals
* Cyborg: https://etherpad.openstack.org/p/PVG-forum-cyborg
* First Contact SIG: https://etherpad.openstack.org/p/shanghai-forum-fc-sig-brainstorming
* Heat: https://etherpad.openstack.org/p/PVG-heat
* Manila: https://etherpad.openstack.org/p/manila-shanghai-forum-brainstorming
* Meta SIG: https://etherpad.openstack.org/p/PVG-meta-sig
* Neutron: https://etherpad.openstack.org/p/neutron-shanghai-forum-brainstorming
* Oslo: https://etherpad.openstack.org/p/oslo-shanghai-topics
* QA: https://etherpad.openstack.org/p/PVG-forum-qa-brainstorming
* Self-healing SIG: https://etherpad.openstack.org/p/SHA-self-healing-SIG
* StoryBoard: https://etherpad.openstack.org/p/storyboard-shanghai-ptg-planning
* TC: https://etherpad.openstack.org/p/PVG-TC-brainstorming
* Keystone: https://etherpad.openstack.org/p/PVG-keystone-forum
* Public Cloud SIG: https://etherpad.openstack.org/p/PVG-PublicCloud-SIG-brainstorming
* OpsMeetups Team: https://etherpad.openstack.org/p/PVG-OPS-Forum-Brainstorming

===Etherpads from Pilot projects===
* StarlingX: https://etherpad.openstack.org/p/PVG-StarlingX-brainstorming

Meetings/Horizon

2019-10-17T03:45:38Z

Amotoki: /* Agenda for Next Meeting */

2019-06-25T09:44:47Z

Amotoki: /* PDF for Project Docs - Community Goal */

{{OpenStack_Documentation_Navbar}}



The focus here is the creation, maintenance and organization of the OpenStack documentation found at the http://docs.openstack.org site. While the Docs team helps create a good framework, it's the entire OpenStack community -- and especially contributors like you -- that provides the expert content and corrections for the documentation.

{| border="1" cellpadding="2" cellspacing="0" class="wikitable"
|-
!colspan="2"|OpenStack Documentation Project Team
|-
| Full name
| OpenStack Documentation
|-
| Code name
| None
|-
| Status
| Related
|-
| Source code
| openstack-manuals; api-site
|-
| Bug tracker
| http://bugs.launchpad.net/openstack-manuals and http://bugs.launchpad.net/openstack-api-site
|-
| Blueprints
| http://blueprints.launchpad.net/openstack-manuals
|-
| Contributor doc
| [https://docs.openstack.org/doc-contrib-guide/ Documentation Contributor Guide]
|-
| Current PTL
| See https://governance.openstack.org/tc/reference/projects/documentation.html
|-
| Meetings
| [[Meetings/DocTeamMeeting|Documentation team meeting]]
|-
| IRC channel
| #openstack-doc on Freenode ([https://wiki.openstack.org/wiki/IRC more about OpenStack on IRC])
|-
| Mailing list
| [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev OpenStack development mailing list] (use the [docs] tag in subject)
|-
|}

= OpenStack documentation =

== Published docs and their location ==

The public interface to all documentation is the [http://docs.openstack.org/ docs.openstack.org] web site. It contains continuously updated manuals. If you like to edit one of these, see [[Documentation/Builds#Documentation_source_and_target_locations|Documentation source and target locations]] for a list of documents and their source repositories.

== Source repositories ==
Doc source is mirrored on GitHub. Everyone can propose changes to docs, see [[Documentation/HowTo]]. Here are the repositories that build to docs.openstack.org.

For a list of source repositories, see [https://governance.openstack.org/tc/reference/projects/documentation.html#deliverables Deliverables].

For more information on which docs are published, see [https://docs.openstack.org/contributor-guide/blueprints-and-specs.html Content specification].

== Releases ==
Lists current development release and past releases, with links to downloads and release notes (what's new and what's changed in each release as well as known issues and potential workarounds)

* [https://releases.openstack.org/ OpenStack Releases]

== Support ==
How to find or ask for support.

* [[MailingLists|Mailing Lists]]
* [http://www.openstack.org/projects/openstack-faq/ OpenStack Community Q & A]
* [https://ask.openstack.org Ask OpenStack]

== Glossary ==
* [http://docs.openstack.org/glossary/content/glossary.html Glossary] - Contains terms that are our definitions for OpenStack, cloud computing, and open source.

= Project documentation =

This is general information about OpenStack.

== Development ==
How to contribute code to [http://www.openstack.org OpenStack] or develop using the OpenStack projects.

* [http://docs.openstack.org/infra/manual/developers.html Developer's Guide in the Infra Manual]
* [[HowToContribute|How to Contribute ]]
* Sign the [http://docs.openstack.org/infra/manual/developers.html#account-setup Contributor agreement]
* [[BasicDesignTenets|Design Tenets]]
* [http://docs.openstack.org/project-team-guide/ Project Team Guide]
* [[CodingStandards|Coding Standards]]
* [[GettingTheCode|Getting the Code]]

== Launchpad reference ==
How we use Launchpad to track features, bugs and releases.

* [[Blueprints]]
* [[Bugs]]
* [[LaunchpadGroups|Launchpad groups]]

= Writing documentation =

First, read the [http://docs.openstack.org/contributor-guide/ Documentation Contributor Guide].

* [[Documentation/HowTo|How to contribute to the documentation]]
* [[Documentation/Conventions|Conventions to follow when writing documentation]]
* [[Documentation/Migrate|DocBook to RST Migrations]]
* [[Documentation/DocImpact|DocImpact]]
* [[Documentation/Troubleshooting|Troubleshooting doc builds]]
* [[Documentation/DocComments|Comments on Documentation]]
* [http://docs.rackspace.com/writers-guide/content Rackspace's Writers Guide]
* [[Documentation/ReviewGuidelines|Review Guidelines]]
* [[Documentation/MitakaDocTesting|Mitaka Documentation Testing - Installation Guide and Configuration Reference]]
* [[Documentation/Release|How to make a documentation release]]
* [[Documentation/UserAnalysis|Documentation user analysis]]
* [[Documentation/PikeDocTesting]]

= Admin access to to the documentation site =

There are some areas where only trusted infrastructure or doc team members have access to configure or manage part of the documentation site. Examples include:
* FTP credentials to the Cloud Sites that houses the files for docs.openstack.org and developer.openstack.org.
* Google Custom Search Engine (CSE) configuration.
* Google Analytics account information and configuration.

For these shared identities, we use the following process to ensure limited access to the information that grants access.

* At the Summit or another in-person meeting, ensure we verify identities with IDs similar to a GPG party.
* With those identities and shared trust in place, create a server with a place to store the account information.
* Enable access to the shared account info by granting access to the server.

Currently the infrastructure core team and Docs PTL has access to the FTP credentials. The Docs PTL has access to the Google CSE information and the Google Analytics account information. The Docs PTL can grant access to the shared Google information. The infrastructure core team can grant access to the FTP credentials.

= PDF for Project Docs - Community Goal =

{| border="1" cellpadding="2" cellspacing="3" class="wikitable"
|-
| '''Full name (IRC nickname)'''
| '''Project name'''
| '''Test status'''
|-
| Akihiro Motoki (amotoki)
| Neutron
| TBD
|-
|Donny Davis
| Nova
| TBD
|-
|Michael Johnson (johnsom)
| Octavia
| TBD
|-
|Luigi Toscano (tosky)
| Sahara
| TBD
|-
|Bogdan Dobrelya (bogdando)
| TripleO
| TBD
|-
|
|
|
|-
|}

= References =

There are many additional publications about OpenStack by third party publishers. Please search for them on your favorite bookseller site.

----
[[Category:HowTo]]
[[Category:Documentation]]
[[Category: Horizontal_Team]]

Meetings/Horizon

2019-05-22T15:06:19Z

Amotoki: /* Agenda for Next Meeting */

Meetings/Horizon

2019-05-15T12:43:23Z

Amotoki:

2019-04-29T18:06:13Z

Amotoki: /* Monday April 29 */

2018-05-01T14:04:57Z

Amotoki: /* Agenda for Next Meeting */

2018-03-05T14:29:42Z

Amotoki: /* Transition to OSC */

The OpenStack Networking Team ([[Neutron]]) holds public meetings as advertised on [http://eavesdrop.openstack.org/#Neutron_Team_Meeting OpenStack IRC Meetings Calendar]. If you are unable to attend, please check the most recent [http://eavesdrop.openstack.org/meetings/networking/ logs.]

=== Announcements / Reminders ===

* Next milestone, Queens RC2, will take place on February 19 - 24
* Rocky release schedule: https://releases.openstack.org/rocky/schedule.html
* Rocky PTG topics and agenda: https://etherpad.openstack.org/p/neutron-ptg-rocky
* Neutron team dinner in Dublin will take place on Thursday March 1st, 7pm at http://thecelt.ie/ . Reservation under Miguel Lavalle
* PTG Summary Email - http://lists.openstack.org/pipermail/openstack-dev/2017-September/122583.html

=== Blueprints ===

Current milestone: https://launchpad.net/neutron/+milestone/queens-rc2

RC2 patch: https://review.openstack.org/#/c/544749

Current cycle: https://blueprints.launchpad.net/neutron/queens

==== OVO/no API downtime ====

List here patches/topics that need core reviewer attention.

* add your patch here

=== Starter Approved RFEs ===

This section is for advertising approved RFEs that the Neutron Drivers team have deemed suitable for new contributors:

* Network router:external field not exported: https://bugs.launchpad.net/neutron/+bug/1653932

=== Bugs and Gate issues ===

Bug deputy report for week of February 12th: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127560.html

A full hour is dedicated to this topic, and more during the following meeting:

* https://wiki.openstack.org/wiki/Meetings/NeutronCI
* [https://bugs.launchpad.net/neutron/+bugs?field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.tag=gate-failure Confirmed gate failures]
* [https://bugs.launchpad.net/neutron/+bugs?field.tag=needs-attention Bugs that need attention]
* [https://bugs.launchpad.net/neutron/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.tag=deprecation All bug reports associated to deprecation issues]
* [https://goo.gl/KtEwbL Bugs Sheet]
* [http://grafana.openstack.org/dashboard/db/neutron-failure-rate Grafana dashboards]

==== Bug deputy ====

You can find more information about what the role is here: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-bug-deputy

During the Denver PTG we made the decision to institute a fixed rotation for the the bugs deputy role. The current scheduled rotation is the following:

{| class="wikitable" style="text-align: center;"
|-
! Date !! who
|-
| January-8-2018 || Hirofumi Ichihara (hichihara)
|-
| January-15-2018 || Gary Kotton (garyk)
|-
| January-22-2018 || Akihiro Motoki (amotoki)
|-
| January-29-2018 || Jakub Libosvar (jlibosva)
|-
| February-5-2018 || Boden Russel (boden)
|-
| February-12-2018 || James Anziano (janzian)
|-
| February-19-2018 || Ihar Hrachyshka (ihrachys)
|-
| February-26-2018 || Slawek Kaplonski (slaweq)
|-
| March-5-2018 || Brian Haley (haleyb)
|-
| March-12-2018 || Zhao Bo(bzhao)
|-
| March-19-2018 || Armando Migliaccio (armax)
|-
| March-26-2018 || Swaminathan Vasudevan (Swami)
|-
| April-2-2018 || Lujin Luo(lujinluo)
|-
| April-9-2018 || YAMAMOTO Takashi (yamamoto)
|-
| April-16-2018 || Miguel Lavalle (mlavalle)
|}

In preparation for their duty week, deputies are encouraged to review the Neutron bugs policy: https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html

=== Docs ===

* The future of OpenStack documentation - http://lists.openstack.org/pipermail/openstack-dev/2016-July/099012.html
* Documentation bugs - https://bugs.launchpad.net/neutron/+bugs?field.tag=doc

=== CLI/SDK ===
Status of changes to deliver OSC
* https://etherpad.openstack.org/p/osc-transition-priorities
* http://docs.openstack.org/developer/python-neutronclient/devref/transition_to_osc.html

=== Neutron-lib, planned refactoring and other impacts ===

List here any planned potential disruption that may be caused by a new neutron-lib release and adoption of its latest features.

'''DO NOT TOP POST - ADD PATCHES TO THE BOTTOM OF THE LIST'''

* Open issues: https://review.openstack.org/#/q/status:open+message:%22NeutronLibImpact%22
** In most cases all consumers using neutron/neutron-lib stable branches are updated as part of consumption. For those who "pin" neutron/neutron-lib, they will have to address the consumption as they move their "pin" up.
** To see all consumption patches for a lib impact change, view the topic branch of the corresponding lib impact change (or search using the same subject).
* Patches that need high-level input from neutron cores: https://review.openstack.org/#/q/message:%22NeutronCoreInputNeeded%22
* Past issues: https://review.openstack.org/#/q/status:merged+message:%22NeutronLibImpact%22
* UpgradeImpact changes: https://review.openstack.org/#/q/status:open+message:%22UpgradeImpact%22+project:openstack/neutron
* Periodic neutron-lib check: http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen

* <Highlight patch(es) here for discussion>

=== On Demand Agenda ===

We can only pick one or two topics we can talk in the time left of the meeting. People should add ideas to the topics section. We will select one or two topics we can chew during the next meeting. Please follow the template below:

* Topic for the meeting (keep this template, please):
** (your nickname): brief description.
*** More details
* Typo fixing patches
** (jlibosva, slaweq) There has been some patches coming from a certain group of people that just fix one typo in either a comment in code or documentation. e.g. https://review.openstack.org/#/c/540225/ . There has been already a ML thread started about this behavior in our community: http://lists.openstack.org/pipermail/openstack-dev/2017-September/122472.html Although typo fixes bring some value, they bring a very tiny value being sent one by one as that triggers CI systems and require two cores to approve such patch. This topic is to kick off the discussion about what approach should Neutron cores take.

== Previous meeting logs ==
* Previous meetings, with their notes and logs, can be found [http://eavesdrop.openstack.org/meetings/networking/ here].
** [http://eavesdrop.openstack.org/meetings/networking/2017/?C=M;O=D networking-2017]
** [http://eavesdrop.openstack.org/meetings/networking/2016/?C=M;O=D networking-2016]
** [http://eavesdrop.openstack.org/meetings/networking/2015/?C=M;O=D networking-2015]
** [http://eavesdrop.openstack.org/meetings/networking/2014/?C=M;O=D networking-2014]
** [http://eavesdrop.openstack.org/meetings/networking/2013/?C=M;O=D networking-2013]
** [http://eavesdrop.openstack.org/meetings/quantum/2013/?C=M;O=D quantum-2013]
** [http://eavesdrop.openstack.org/meetings/quantum/2012/?C=M;O=D quantum-2012]