Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Next Meeting)
 
(518 intermediate revisions by 32 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
  
The [[Governance/Foundation/TechnicalCommittee|OpenStack Technical Committee]] is one of the [[Governance|governing bodies]] of the OpenStack project. You can find more information about it, such as the list of its [http://governance.openstack.org current members] or its [http://governance.openstack.org/reference/charter.html governance charter], on the OpenStack governance website at http://governance.openstack.org . 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
  
* March 29th, 20:00 UTC
 
* Chair: Thierry Carrez (ttx)
 
  
 +
=== Next Meeting ===
  
==== Agenda ====
+
* Date: Sept 30th, 2021
 
+
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
* Appointed PTLs for Newton [https://review.openstack.org/296360]
+
* Chair: Ghanshyam Mann
* Remove rolling-upgrade tag from swift/ceilometer [https://review.openstack.org/292334]
+
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
* Update Kuryr mission statement [https://review.openstack.org/289993]
+
* Location: IRC: #openstack-tc channel on OFTC
* Changes to clarify project election requirements
 
** Add leaderless programs amendment for inactivity [https://review.openstack.org/295581]
 
** Mention in project requirements about ptl election [https://review.openstack.org/295609]
 
* Stale cross-project specs (thingee) [http://lists.openstack.org/pipermail/openstack-dev/2016-March/089115.html]
 
* Tags to describe deployment and packaging deliverables
 
** Introduce type:deployment tag [https://review.openstack.org/295528]
 
** Modify asserts for upgrades to include deployment [https://review.openstack.org/295529]
 
** Introduce a type:packaging tag [https://review.openstack.org/295971]
 
* Open discussion
 
 
 
  
==== Backlog ====
+
==== Agenda Suggestions ====
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:
 
  
* Call out GPL style licenses in testing/validation. [https://review.openstack.org/293140] (pending an update)
+
* Roll call
* Change mission statement by recent change [https://review.openstack.org/292610] (pending board decision)
+
* Follow up on past action items
* Retire the kite/python-kiteclient projects [https://review.openstack.org/297803] (not submitted in time for this meeting)
+
* Gate health check (dansmith/yoctozepto)
* Separating cross-project specs and guidelines [http://lists.openstack.org/pipermail/openstack-dev/2016-March/090156.html ML Discussion] & [https://review.openstack.org/#/c/296571/ Review] (not submitted in time for this meeting)
+
** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/
* Add type:deployment to release:cycle_with_miestones [https://review.openstack.org/298278] (not submitted in time for this meeting)
+
* Project Health checks framework
 +
** https://etherpad.opendev.org/p/health_check
 +
** https://review.opendev.org/c/openstack/governance/+/810037
 +
* Open Reviews
 +
** https://review.opendev.org/q/projects:openstack/governance+is:open
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
+
<Please write your name if you are not able to attend the meeting>
* tbd
+
*
 
 
 
 
=== 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.
 
 
 
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.
 
 
 
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.
 
 
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 18:58, 24 September 2021


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

Apologies for 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