Difference between revisions of "Airship/Airship-TC"
< Airship
m (Update meeting date) |
(→Date) |
||
| (One intermediate revision by one other user not shown) | |||
| 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, | + | * 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 | ||
| − | + | * Matt McEuen, Microsoft | |
| − | + | * Ruslan Aliev, Mirantis | |
| − | |||
| − | * Matt McEuen, | ||
| − | * | ||
| − | |||
For more information, please visit [https://github.com/airshipit/governance Airship Governance]. | For more information, please visit [https://github.com/airshipit/governance Airship Governance]. | ||
| Line 25: | Line 22: | ||
==== Date ==== | ==== Date ==== | ||
| − | * Bi-weekly, Monday (Beginning July 12), 1500 UTC | + | * Bi-weekly, Monday (Beginning July 12), 1600 UTC (time shifts between 1500 and 1600 UTC with respect to US Daylight Savings schedule) |
==== Conference/ Video Bridge Information ==== | ==== Conference/ Video Bridge Information ==== | ||
Latest revision as of 18:07, 10 January 2022
Contents
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), 1600 UTC (time shifts between 1500 and 1600 UTC with respect to US Daylight Savings schedule)
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
- +1 669 900 6833 US (San Jose)
- +1 646 876 9923 US (New York)
- Meeting ID: 384 128 660
- Find your local number: https://zoom.us/u/adA54OXFxP
Past Meeting Agenda and Minutes
- 2021-01-14: Agenda and Minutes and Play Recording Password: MB@ti6aH
- 2020-12-10: Agenda and Minutes and Play Recording Password: r+Dq1VQE
- 2020-11-12: Agenda and Minutes
- 2020-10-08: Agenda and Minutes and Play Recording Password: gTF5+=t$
- 2020-09-10: Agenda and Minutes and Play Recording Password: 1?Kpz=p$
- 2020-08-13: Agenda and Minutes and Play Recording Password: 1h^!k@j@
- 2020-07-09: Agenda and Minutes and Play Recording Password: 4r@?*8C@
- 2020-06-11: Agenda and Minutes and Play Recording Password: 7X+4%?5^
- 2020-05-14: Agenda and Minutes and Play Recording Password: 6s.6@=LR
- 2020-04-09: Agenda and Minutes and Play Recording
- 2020-03-12: Agenda and Minutes and Play Recording
- 2020-02-13: Agenda and Minutes and Play Recording
- 2020-01-09: Agenda and Minutes and Play Recording
- 2019-12-12: Agenda and Minutes and Play Recording
- 2019-10-16: Agenda and Minutes and Play Recording
- 2019-09-26: Agenda and Minutes
- 2019-09-13: Agenda and Minutes and Play Recording
- 2019-08-08: Agenda and Minutes and Play Recording (Note: (1) Password: Mmrt5mNn (2) Recording are retained for 30 days only)
