Slides shown during the Oslo onboarding session in Vancouver, May 2018.

1. Oslo
Project Onboarding
OpenStack Summit Vancouver
May 2018
Ben Nemec, Jay Bryant, Ken Giusti

2. Agenda
● Overview
● Projects
● Team
● Processes and Policies
● IRC and Meetings
● Get Involved
● Q&A

3. Overview
● Mission: To produce a set of python libraries containing code shared by
OpenStack projects. The APIs provided by these libraries should be high
quality, stable, consistent, documented and generally applicable.
● Team: A combination of generalist code reviewers and specialist API
maintainers.
● Fun fact: Independent contributors are one of the largest sources of
commits and reviews in Oslo.
● Projects: Around 40, covering things like messaging, database, config, and
many other areas.
● Details: https://wiki.openstack.org/wiki/Oslo

4. Projects
● Automaton
● Castellan
● Cliff
● Cookiecutter
● Debtcollector
● devstack-plugin-[amqp1|kafka]
● Futurist
● Mox3
● Oslo-cookiecutter
● Oslo.cache
● Oslo.concurrency
● Oslo.config
● Oslo.context
● Oslo.db
● Oslo.i18n
● Oslo.limit
● Oslo.log
● Oslo.messaging
● Oslo.middleware
● Oslo.policy
● Oslo.privsep
● Oslo.reports
● Oslo.rootwrap
● Oslo.serialization
● Oslo.service
● Oslo.tools
● Oslo.utils
● Oslo.versionedobjects
● Oslo.vmware
● Oslosphinx
● Oslotest
● Osprofiler
● Pbr
● Pycadf
● Sphinx-feature-classification
● Stevedore
● Taskflow
● Tooz

5. Team
● PTL
● Ben Nemec (bnemec)
● Cores
● ChangBo Guo (gcb)
● Davanum Srinivas (dims)
● Doug Hellmann (dhellmann)
● Josh Harlow (harlowja)
● Ken Giusti (kgiusti)
● Mehdi Abaakouk (sileht)
● Stephen Finucane (stephenfin)
● Project-specific Cores

6. Processes and Policies
● Policies documented in the specs repo
● http://specs.openstack.org/openstack/oslo-specs/#team-policies
● Liaison program
● https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo
● No more namespace packages
● Weekly releases

7. IRC and Meetings
● #openstack-oslo on Freenode
● Weekly meetings Monday at 1500 UTC

8. Get Involved
● Don’t need to be full time. Most (all?) Oslo cores have other
responsibilities outside Oslo.
● Pick a project, review code, fix bugs. It is not necessary to learn all of
Oslo to contribute. Experts in specific areas are very welcome.

9. Q&A

10. Q&A