Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Apologies for Absence)
(Next Meeting)
 
(479 intermediate revisions by 32 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html governance charter], on the OpenStack TC governance website at https://governance.openstack.org/tc/ . It meets weekly in an open meeting in the <code>#openstack-meeting</code> IRC channel on Freenode.
+
The OpenStack Technical Committee is one of the [https://governance.openstack.org governing bodies] of the OpenStack project. You can find more information about it, such as the list of its [https://governance.openstack.org/tc/ current members] or its [https://governance.openstack.org/tc/reference/charter.html 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 [http://git.openstack.org/cgit/openstack/governance openstack/governance repository]. Large-impact changes are discussed on the openstack-discuss mailing-list. '''We track current initiatives on the [[Technical_Committee_Tracker]].'''
  
=== Next Meeting ===
+
We hold office hours at [https://governance.openstack.org/tc/#office-hours various times] during the week on the [http://eavesdrop.openstack.org/irclogs/%23openstack-tc/ #openstack-tc] IRC channel. We meet formally [http://eavesdrop.openstack.org/#Technical_Committee_Meeting each week] in  #openstack-tc
  
* April 18th, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
  
 +
=== Next Meeting ===
  
==== Agenda ====
+
* Date: 30 June 2022
 
+
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
* Add TC repo project-navigator-data [https://review.openstack.org/453867]
+
* Chair: Ghanshyam Mann
* Resolution on OpenStack's mission for cloud applications [https://review.openstack.org/447031]
+
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
* Add a "docs:install-guide-verified" tag [https://review.openstack.org/445536]
+
* Location: IRC OFTC network in the #openstack-tc channel
* Remove App Catalog from official projects [https://review.openstack.org/452086] (initial discussion)
 
* Propose the addition of an status:maintenance-mode [https://review.openstack.org/449925]
 
* Stalled reviews
 
** Add monitorstack to OpenStack-Ansible [https://review.openstack.org/444325]
 
** Add tag assert:never-breaks-compat [https://review.openstack.org/446561]
 
* Open discussion
 
** TC election - last days to vote [https://governance.openstack.org/election/]
 
** ttx off next week
 
** TC vision: feedback & next steps
 
 
 
 
 
==== Backlog ====
 
These items have been proposed, but are not put on the agenda just yet. Could be that they have not been discussed on openstack-dev for the time mandated by our charter yet, or are blocked for some other reason, or are just delayed while we process the earlier requests backlog:
 
 
 
* Update diversity tags [https://review.openstack.org/448667] (Apr 25)
 
* Driver teams [https://review.openstack.org/403829] [https://review.openstack.org/403836] and networking-cisco's standing request [https://review.openstack.org/363709] (Apr 25)
 
* Describe what upstream support means [https://review.openstack.org/440601] (might be unnecessary if we decide to contract for technical reasons)
 
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (work in progress)
 
* deprecate postgresql in OpenStack [https://review.openstack.org/427880] (needs clarity about whether we would drop it even if we received support, forum discussion)
 
* assert:supports-api-compatibility tag [https://review.openstack.org/418010] (pending API change guidelines update [https://review.openstack.org/421846])
 
 
 
 
 
==== Apologies for Absence ====
 
 
 
* Emilien Macchi (April 18th)
 
* thingee
 
 
 
=== Proposing discussion topics, motions or other governance changes before the TC ===
 
  
Motions need to be presented before Friday 0800 UTC to be added to the next Tuesday meeting agenda for discussion. They should either be posted as a proposed change to the [http://git.openstack.org/cgit/openstack/governance/ governance] repository (on review.openstack.org) or as a "[tc]" thread to openstack-dev@lists.openstack.org, with a pointer to that thread should be posted to openstack-tc@lists.openstack.org to make sure it gets the required attention from TC members. Upon verification, the TC Chair will put the motion on the agenda for the next meeting.
+
==== Agenda Suggestions ====
  
Before being finally voted on, motions will have to be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change. As mandated by our charter, the vote on motions won't be closed until we spent a minimum of 4 business days of public discussions, to give a chance to our wider community to chime in on proposed changes.
+
* Roll call
 +
* Follow up on past action items
 +
* Gate health check
 +
* Bare 'recheck' state
 +
** https://etherpad.opendev.org/p/recheck-weekly-summary
 +
* New ELK service dashboard: e-r service
 +
** https://opensearch.logs.openstack.org/_dashboards/app/discover?security_tenant=global
 +
** http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028346.html
 +
* RBAC community-wide goal
 +
** https://etherpad.opendev.org/p/rbac-zed-ptg#L171
 +
** https://review.opendev.org/c/openstack/governance/+/847418
 +
* Create the Environmental Sustainability SIG
 +
** https://review.opendev.org/c/openstack/governance-sigs/+/845336
 +
* Open Reviews
 +
** https://review.opendev.org/q/projects:openstack/governance+is:open
  
Additions of code repositories to existing project teams, as well as other instances of governance repository housekeeping, do not constitute a "motion". Those will be approved a week after being proposed, if they have the required approvals (PTLs in the case of a repository addition) and no TC member -1 vote. A -1 vote will result in the proposed change to be reviewed at the next TC meeting.
+
==== Absence ====
 +
<Please write your name if you are not able to attend the meeting>
  
 +
* rosmaita (will miss 23 June and 30 June meetings)
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 20:50, 24 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

Agenda Suggestions

Absence

<Please write your name if you are not able to attend the meeting>

  • rosmaita (will miss 23 June and 30 June meetings)

Past meetings logs

Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc