Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda Suggestions)
(Agenda Suggestions)
 
(82 intermediate revisions by 11 users not shown)
Line 5: Line 5:
 
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]].'''
 
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]].'''
  
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 on the first Thursday of each month in #openstack-tc at 1400 UTC.
+
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  
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* Date: 6 February 2020
+
* Date: February 25th, 2021
* Chair: ricolin
+
* Time: 15.00 UTC: http://eavesdrop.openstack.org/#Technical_Committee_Meeting
* Agenda to be published on the openstack-discuss mailing list before the meeting
+
* Chair: Mohammed Naser
 +
* Agenda to be published on the OpenStack-discuss mailing list before the meeting
  
 
==== Agenda Suggestions ====
 
==== Agenda Suggestions ====
  
 
* Follow up on past action items
 
* Follow up on past action items
** Report on large scale sig (ttx)
+
* Audit SIG list and chairs (diablo_rojo)
*** review AP January: post a summary of large scale sig's meeting on the ML this week
+
** https://etherpad.opendev.org/p/2021-SIG-Updates
*** report to see if momentum is still there
+
** http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019994.html
** Report on tc/uc merge (ttx)
+
* Gate performance and heavy job configs (dansmith)
*** report on the investigations and discussions with UC/with the foundation over bylaws
+
** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/
** report on the post for the analysis of the survey (jungleboyj)
+
* Student Programs (diablo_rojo)
*** review AP January on updating the patch
+
** Google Summer of Code: https://summerofcode.withgoogle.com/get-started/
** Report on the convo Telemetry (ricolin)
+
*** Feb 19th
*** where are we now?
+
** Outreachy: https://www.outreachy.org/communities/cfp/
** Report on multi-arch SIG (ricolin)
+
*** March 7th
** report on infra liaison and static hosting (mnaser)
+
* Recommended path forward for OSarchiver (ttx)
*** check if there is progress / follow up
+
** OVH released https://github.com/ovh/osarchiver as open source, and they are interested in pushing it under OpenStack governance to increase discoverability
** report on stable branch policy work (mnaser)
+
** One option is to make it its own smallish project on the "Operations tooling" side of the map
*** review AP january: mnaser to push an update to distill what happened on the ML in terms of stable branch policy
+
** Another option is to place it under the "Operation Docs and Tooling" SIG in the OSops repository, but that seems mostly abandoned
** report on the oslo metrics project (mnaser jroll)
+
** What's the TC's recommendation for them to follow?
*** has code appeared since last convo, any update from the spec from LINE, any update of the large scale SIG?
+
* Open Reviews
** report on the community goals for U and V, py2 drop (gmann)
+
** https://review.opendev.org/q/project:openstack/governance+is:open
** report on release naming (mugsie)
 
*** W progress?
 
** report on the ideas repo (evrardjp)
 
*** static hosting
 
*** first ideas
 
*** governance dashboard
 
** charter change (evrardjp)
 
** ricolin: (in March 2020): Report on whether SIG guidelines worked.
 
** volunteers to represent OpenStack at the OpenDev advisory board (evrardjp)
 
** Report on the OSF board initiatives (evrardjp)
 
** Dropping side projects: using golden signals (ttx)
 
* addendums
 
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====

Latest revision as of 14:45, 25 February 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

Past meetings logs

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