Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Apologies for Absence)
(Next Meeting)
 
(953 intermediate revisions by 43 users not shown)
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters.
 
  
The Technical Committee is formally defined in the [[Governance/Foundation/Bylaws|OpenStack Foundation bylaws]] (in particular article 4.1(b), article 4.13 and Appendix 4) and further refined in the [[Governance/Foundation/TechnicalCommittee|Technical Committee charter]].
+
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/ .
  
=== Members ===
+
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]].'''
  
{| border="1" cellpadding="2" cellspacing="0"
+
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
|- bgcolor=#eeeeee
 
| Name                 
 
| End of term   
 
|-
 
|  James E. Blair (jeblair)         
 
|  April 2014 
 
|-
 
|  Russell Bryant (russellb)     
 
|  October 2014
 
|-
 
| Thierry Carrez (ttx)         
 
|  April 2014
 
|-
 
|  Robert Collins (lifeless)         
 
|  April 2014
 
|-
 
|  Sean Dague (sdague)     
 
|  October 2014
 
|-
 
|  Anne Gentle (annegentle)     
 
|  October 2014
 
|-
 
|  John Griffith (jgriffith)     
 
|  April 2014
 
|-
 
|  Doug Hellmann (dhellmann)     
 
|  October 2014
 
|-
 
|  Vish Ishaya (vishy)           
 
|  April 2014
 
|-
 
|  Mark McClain (markmcclain)     
 
|  April 2014
 
|-
 
|  Mark McLoughlin (markmc)     
 
|  October 2014
 
|-
 
|  Michael Still (mikal)       
 
|  April 2014
 
|-
 
|  Monty Taylor (mordred)       
 
|  October 2014
 
|}
 
  
=== Mailing-list ===
 
  
The [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc openstack-tc mailing-list] is used for communication within the Technical Committee. Posting is moderated for non-members.
+
=== Next Meeting ===
  
=== Meeting ===
+
* Date: Oct 28th, 2021
 +
* 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: #openstack-tc channel on OFTC
  
Next meeting: Tuesday Dec 17, 20:00 UTC (to be confirmed)
+
==== Agenda Suggestions ====
  
==== Agenda ====
+
* Roll call
 
+
* Follow up on past action items
* Becoming a Program, before applying for incubation [http://lists.openstack.org/pipermail/openstack-dev/2013-December/022202.html]
+
* Gate health check (dansmith/yoctozepto)
* Barbican incubation request, second part [https://wiki.openstack.org/wiki/Barbican] [http://lists.openstack.org/pipermail/openstack-dev/2013-December/020830.html]
+
** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/
* J naming determination process [http://lists.openstack.org/pipermail/openstack-tc/2013-December/000444.html]
+
* Project Health checks framework
* Other minor governance changes:
+
** https://etherpad.opendev.org/p/health_check
** Provide infrastructure for publishing docs to docs.openstack.org [https://review.openstack.org/#/c/61380/]
+
** https://review.opendev.org/c/openstack/governance/+/810037
** Attach extra ATCs to programs [https://review.openstack.org/#/c/62009/]
+
* Stable team process change
* Open discussion
+
** https://review.opendev.org/c/openstack/governance/+/810721
 
+
* Technical Writing (doc) SIG need a chair and more maintainers
 
+
** Current Chair (only maintainer in this SIG) Stephen Finucane will not continue it in the next cycle(Yoga)
==== Backlog ====
+
** http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025161.html
These items have been proposed, but have not been discussed on openstack-dev for the time mandated by our bylaws yet:
+
* Open Reviews
 
+
** https://review.opendev.org/q/projects:openstack/governance+is:open
* Assert control over website and memberdata systems [https://review.openstack.org/#/c/58072/] -- pending ML thread
 
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
 
+
<Please write your name if you are not able to attend the meeting>
* Anne Gentle (jury duty)
+
*
 
 
=== Presenting a motion before the TC ===
 
 
 
Motions need to be presented at least 4 business days before the next meeting scheduled time. They should be posted to openstack-dev@lists.openstack.org, then 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.
 
 
 
Note that before being voted on, motions must now be presented as a [http://git.openstack.org/cgit/openstack/governance/ governance] change.
 
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===
  
 
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
 
Logs of past TC meetings can be accessed at: http://eavesdrop.openstack.org/meetings/tc
 +
 +
[[Category: meetings]]

Latest revision as of 15:29, 15 October 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