Jump to: navigation, search

Difference between revisions of "Airship/Airship-TC"

m (Update meeting date)
(Overview)
 
Line 5: Line 5:
 
The Airship Technical Committee influences project strategy, helps arbitrate when there is a disagreement between Core Reviewers within a single project or between Airship projects, defines the project's core principles, performs marketing and communications, and provides product management as well as ecosystem support. The Technical Committee is also responsible for ensuring that Airship projects are adhering to the project's core principles, promoting standardization, as well as defining and organizing the Airship versioning and release process.
 
The Airship Technical Committee influences project strategy, helps arbitrate when there is a disagreement between Core Reviewers within a single project or between Airship projects, defines the project's core principles, performs marketing and communications, and provides product management as well as ecosystem support. The Technical Committee is also responsible for ensuring that Airship projects are adhering to the project's core principles, promoting standardization, as well as defining and organizing the Airship versioning and release process.
  
* Alex Bailey, AT&T
+
* Alex Bailey, Microsoft
 
* Alexey Odinokov, Mirantis
 
* Alexey Odinokov, Mirantis
 +
* Drew Walters, Microsoft
 
* Jan-Erik Mångs, Ericsson
 
* Jan-Erik Mångs, Ericsson
 
* John (JT) Williams, Dell EMC
 
* John (JT) Williams, Dell EMC
* Drew Walters, AT&T
+
* Matt McEuen, Microsoft
* James Gu, Insight Global
+
* Ruslan Aliev, Mirantis
* Kostiantyn Kalynovskyi, Mirantis
 
* Matt McEuen, AT&T
 
* Sreejith Punnapuzha, Ericsson
 
 
 
  
 
For more information, please visit [https://github.com/airshipit/governance Airship Governance].
 
For more information, please visit [https://github.com/airshipit/governance Airship Governance].

Latest revision as of 14:38, 20 September 2021

Airship Technical Committee

Overview

The Airship Technical Committee influences project strategy, helps arbitrate when there is a disagreement between Core Reviewers within a single project or between Airship projects, defines the project's core principles, performs marketing and communications, and provides product management as well as ecosystem support. The Technical Committee is also responsible for ensuring that Airship projects are adhering to the project's core principles, promoting standardization, as well as defining and organizing the Airship versioning and release process.

  • Alex Bailey, Microsoft
  • Alexey Odinokov, Mirantis
  • Drew Walters, Microsoft
  • Jan-Erik Mångs, Ericsson
  • John (JT) Williams, Dell EMC
  • Matt McEuen, Microsoft
  • Ruslan Aliev, Mirantis

For more information, please visit Airship Governance.

Meeting Logistics

Agenda and Recordings

Date

  • Bi-weekly, Monday (Beginning July 12), 1500 UTC

Conference/ Video Bridge Information

Join Zoom Meeting: https://zoom.us/j/9725717388?pwd=RDNKYUplK3FCZlNmSG5mZzZsNWFjdz09

Meeting Passcode

  • airshipit
One Tap Mobile
  • +16699006833,,384128660# US (San Jose)
  • +16468769923,,384128660# US (New York)
Dial by Your Location

Past Meeting Agenda and Minutes