We have "decomposed" non-reference code out of the neutron tree. Are we providing
external projects with the support they need to integrate with Neutron? What are the pain
points? Can we agree on a prioritized list of improvements to aid pluggability? What is
the roadmap for neutron-lib and API micro-versioning? These are some of the topics
we will discuss in this session.
This is part of the Neutron 'Core' track series.
Who is this session for:
This is a track of Neutron sessions for OpenStack/Neutron developers. If you are not a developer
you'll find these sessions incredibly boring or hard to decipher. Having said that, if you are a
relatively new contributor and intend to be more involved with the community, you are more than
welcome to attend so that we can grow the Neutron developer team. Save the usability issues
and long term picture project discussions for the other two tracks below.
Relevant tracks:
'Next' track 'Labs' track Core track theme:
Topics are 'boring' day-to-day activities that need to happen for moving the project forward,
and do not have a direct impact to users or operators. Processes, testing, integration with other
projects are typically what we talk about. Topics are non-controversial stuff that must happen
one way or another, the objective of the session is to go home with an idea of how big a task
is, and who does what. Typically these activities are a single-person effort. They span all the
neutron core projects: neutron, and neutron-*-aas.
etherpad Chair: HenryG
