Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda Suggestions)
 
(121 intermediate revisions by 14 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]].'''
 +
 
 +
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.
  
  
 
=== Next Meeting ===
 
=== Next Meeting ===
  
* March 28st, 20:00 UTC
+
* Date: 5 September 2019
* Chair: Emilien Macchi (EmilienM)
+
* Chair: mnaser
 +
* Agenda to be published on the openstack-discuss mailing list before the meeting
  
 +
==== Agenda Suggestions ====
 +
* Release Naming - Results of the TC poll
  
==== Agenda ====
+
* Follow up on past action items
  
* Move shade into its own top-level team [https://review.openstack.org/446426]
+
** mnaser to contact alan to mention that tc will have some presence at shanghai leadership meeting
* More tbd
 
* Open discussion
 
  
 +
** ricolin update sig guidelines to simplify process for new sigs
  
==== Backlog ====
+
** ttx contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
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:
 
  
* Add a "docs:install-guide-verified" tag [https://review.openstack.org/445536] (work in progress)
+
* Active initiatives
* Add tag assert:never-breaks-compat [https://review.openstack.org/446561] (work in progress)
 
* Driver teams [https://review.openstack.org/403829] [https://review.openstack.org/403836] and networking-cisco's standing request [https://review.openstack.org/363709] (deferred until Doug and Mike are both around)
 
* Describe what upstream support means [https://review.openstack.org/440601] (might be unnecessary if we decide to contract for technical reasons)
 
* deprecate postgresql in OpenStack [https://review.openstack.org/427880] (needs clarity about whether we would drop it even if we received support)
 
* assert:supports-api-compatibility tag [https://review.openstack.org/418010] (pending API change guidelines update [https://review.openstack.org/421846])
 
  
 +
** Python 3: mnaser to sync up with swift team on python3 migration
  
==== Apologies for Absence ====
+
** mugsie to sync with dhellmann or release-team to find the code for the proposal bot
  
* dhellmann - 21 March and 28 March, PTO
+
** https://etherpad.openstack.org/p/PVG-TC-brainstorming (ttx, 14:15:33)
* mtreinish (on a plane again)
 
  
=== Proposing discussion topics, motions or other governance changes before the TC ===
+
** http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008188.html
  
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.
+
** Make goal selection a two-step process (needs reviews at https://review.opendev.org/#/c/667932/)
  
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.
+
* Summary meeting minutes from 8 August
 
+
 
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.
+
  http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-08-08-14.00.txt
  
 +
==== Apologies for Absence ====
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 16:07, 4 September 2019


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 on the first Thursday of each month in #openstack-tc at 1400 UTC.


Next Meeting

  • Date: 5 September 2019
  • Chair: mnaser
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Release Naming - Results of the TC poll
  • Follow up on past action items
    • mnaser to contact alan to mention that tc will have some presence at shanghai leadership meeting
    • ricolin update sig guidelines to simplify process for new sigs
    • ttx contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
  • Active initiatives
    • Python 3: mnaser to sync up with swift team on python3 migration
    • mugsie to sync with dhellmann or release-team to find the code for the proposal bot
  • Summary meeting minutes from 8 August
 http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-08-08-14.00.txt

Apologies for Absence

Past meetings logs

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