Airship Update - February 2020
What follows is the Airship Community Update for the month of February 2020, brought to you by the Airship Technical Committee.
SPOTLIGHT ON ....
The Airship Technical and Working Committees each had special elections in January. We welcome:
- Airship's year in review was featured in the OpenStack Foundation Annual Report. For more information see this blog post.
The Airship blog is a great way to keep up with what's going on in the community. The Airship community publishes blog posts regularly, including the recent Airship 2.0 Blog series. These blog posts introduce the changes from Airship 1.0 to Airship 2.0, highlight new features, and detail the evolution of each component. The first six Airship 2.0 Blog posts are already available:
- Airship Blog Series 1 - Evolution Towards 2.0
- Airship Blog Series 2 - An Educated Evolution
- Airship Blog Series 3 - Airship 2.0 Architecture High Level
- Airship Blog Series 4 - Shipyard - an Evolution of the Front Door
- Airship Blog Series 5 - Drydock and Its Relationship to Cluster API
- Airship Blog Series 6 - Armada Growing Pains
AIRSHIP 2: THE SEQUEL
Recently Ryan van Wyk narrated a great, short, video discussing Airship - and the evolution to Airship2. It's a must see for anyone interested in Airship:
JIRA MIGRATION TO GITHUB ISSUES
- Anyone can create issues.
- Ease of communication between community members on issues.
Intuitive labels allowing contributors to find specific categories of issues easily such as:
- "Good first issue" for new contributors to Airship 2.0.
<componentName>" for developers looking to work on specific components such as the config module.
To date 43 issues have been created, and 9 of them have been completed already. Join us each week on the Airship Flight Plan call to groom and discuss issues that the community is working on.
This page lists everything you need to know to get involved and start contributing.
Alexander Hughes, on behalf of the Airship Technical Committee