Difference between revisions of "Meetings/TechnicalCommittee"
(added SLURP release note update to Open Reviews) |
(→Next Meeting) |
||
Line 10: | Line 10: | ||
=== Next Meeting === | === Next Meeting === | ||
− | * Date: June | + | * Date: 23 June 2022 |
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting | * Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting | ||
* Chair: Ghanshyam Mann | * Chair: Ghanshyam Mann | ||
Line 37: | Line 37: | ||
* Open Reviews | * Open Reviews | ||
** https://review.opendev.org/q/projects:openstack/governance+is:open | ** https://review.opendev.org/q/projects:openstack/governance+is:open | ||
− | |||
− | |||
− | |||
− | |||
==== Absence ==== | ==== Absence ==== |
Revision as of 00:17, 20 June 2022
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. You can find more information about it, such as the list of its current members or its governance charter, on the OpenStack TC governance website at https://governance.openstack.org/tc/ .
In order to include as many people as possible in the discussion, the Technical Committee relies on asynchronous communications as much as possible. We propose and vote on changes through the openstack/governance repository. Large-impact changes are discussed on the openstack-discuss mailing-list. We track current initiatives on the Technical_Committee_Tracker.
We hold office hours at various times during the week on the #openstack-tc IRC channel. We meet formally each week in #openstack-tc
Next Meeting
- Date: 23 June 2022
- Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
- Chair: Ghanshyam Mann
- Agenda to be published on the OpenStack-discuss mailing list before the meeting
- Location: IRC OFTC network in the #openstack-tc channel
Agenda Suggestions
- Roll call
- Follow up on past action items
- Gate health check
- Fixing Zuul config error in OpenStack
- (rosmaita) update on cinder-backup memory bloat issue
- Looks like it's a system/Python memory handling problem
- Gorka also has a cinder-side fix, but it only frees up 30MB
- New ELK service dashboard: e-r service
- RBAC feedback in ops meetup
- TC + Board meeting
- Open Reviews
Absence
<Please write your name if you are not able to attend the meeting>
Past meetings logs
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc