Jump to: navigation, search

Difference between revisions of "Meetings/TechnicalCommittee"

(Agenda)
 
(123 intermediate revisions by 15 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 on the first Thursday of each month in #openstack-tc at 1400 UTC.
  
* April 25th, 20:00 UTC
 
* Chair: Doug Hellmann (dhellmann)
 
  
 +
=== Next Meeting ===
  
==== Agenda ====
+
* Date: 10 October 2019
 
+
* Chair: asettle
* Welcome new membership
+
* Agenda to be published on the openstack-discuss mailing list before the meeting
** Approve new roster [https://review.openstack.org/458770]
 
** Elect chair [https://review.openstack.org/458774] (add your candidacy here)
 
** Reminder of current house rules
 
* Adjustments to status:maintenance-mode tag definition [https://review.openstack.org/457794]
 
* Presentation of User Survey findings (heidijoy - heidijoy@openstack.org)
 
** See a 4-minute [https://www.openstack.org/user-survey video overview] of report highlights
 
** [https://www.openstack.org/assets/survey/April2017SurveyReport.pdf Download] the full User Survey report
 
** [http://openstack.org/analytics Analyze data yourself] with six global filters
 
** Key findings for the TC:
 
*** Report represents 44% more deployments (nearly 600) and 22% more organizations than [https://www.dropbox.com/s/8ihd6rw7efhdalj/1.1%20Compare%20to%20prior%20cycle.png?dl=0 ever before], however, fewer total respondents
 
*** The majority of OpenStack users are on an unsupported release: [https://www.dropbox.com/s/8hukz6lzaged46j/3.4%20Release%20used%20-%20all%20.png?dl=0 all deployments] / [https://www.dropbox.com/s/wnlx6yx3t239wn2/3.5%20Releases%20used%20-%20deployments.png?dl=0 deployments in production]
 
*** NPS scores declined for [https://www.dropbox.com/s/vejq9ou4xu8ytiu/2.2b%20NPS%20over%20time.png?dl=0 users overall] and for those with [https://www.dropbox.com/s/6x2d56eor2dzpvl/NPS%20Deployments%20only.png?dl=0 deployments] - see the [https://www.openstack.org/assets/survey/April2017SurveyReport.pdf full report] for verbatim comments
 
*** 12 projects asked specific questions to inform future development. See answers on pages 58-65 of the [https://www.openstack.org/assets/survey/April2017SurveyReport.pdf report].
 
*** See the report "Deployment Decisions" section (pages 42-57) for installation/configuration insights.
 
* Update diversity tags [https://review.openstack.org/448667]
 
* Next steps (if any) for Driver teams [https://review.openstack.org/403829] [https://review.openstack.org/403836] and networking-cisco's standing request [https://review.openstack.org/363709]
 
* Abandoning the weekly meeting (flaper87)
 
* 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:
 
  
* Describe what upstream support means [https://review.openstack.org/440601] (might be unnecessary if we decide to contract for technical reasons)
+
* Follow up on past action items
* Add Queens goal split out tempest plugins [https://review.openstack.org/369749] (work in progress)
+
** ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
* deprecate postgresql in OpenStack [https://review.openstack.org/427880] (needs clarity about whether we would drop it even if we received support, forum discussion)
+
** ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
* assert:supports-api-compatibility tag [https://review.openstack.org/418010] (pending API change guidelines update [https://review.openstack.org/421846])
+
** Release Naming - Results of the TC poll - Next action
* Draft technical committee vision for public feedback [https://review.openstack.org/453262] (waiting for feedback)
 
* Fix comment about design summits [https://review.openstack.org/454070] (waiting for new revision)
 
  
 +
* New initiatives and/or report on previous initiatives
 +
** Help gmann on the community goals following our new goal process.
 +
*** It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
 +
** mugsie: to sync with dhellmann or release-team to find the code for the proposal bot
 +
** jroll - ttx: Feedback from the forum selection committee -- Follow up on https://etherpad.openstack.org/p/PVG-TC-brainstorming -- Final accepted list?
 +
** mnaser: sync up with swift team on python3 migration
 +
* addendums
 +
** define goal select process schedule
 +
*** This is different discussion to select goals. We need to make sure we can have a schedule for cycles to follow. So we know when exactly to ask for goal idea, ask for champion, start +1 cycle goal select process, and start +2 cycle select process.
 +
** Maintain issue with Telemetery
 +
** overall review for TC summit and PTG plans
  
 
==== Apologies for Absence ====
 
==== Apologies for Absence ====
  
* Thierry Carrez (April 25th)
+
evrardjp - Travelling
 
 
 
 
=== 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.
 
  
 +
cloudnull - Holiday
  
 
=== Past meetings logs ===
 
=== Past meetings logs ===

Latest revision as of 13:41, 10 October 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: 10 October 2019
  • Chair: asettle
  • Agenda to be published on the openstack-discuss mailing list before the meeting

Agenda Suggestions

  • Follow up on past action items
    • ricolin: Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline
    • ttx: contact interested parties in a new 'large scale' sig (help with mnaser, jroll reaching out to verizon media)
    • Release Naming - Results of the TC poll - Next action
  • New initiatives and/or report on previous initiatives
    • Help gmann on the community goals following our new goal process.
      • It includes 1. Ussuri goal proposals update 2. Plan for V cycle goal discussion 3. One more TC member to Volunteer
    • mugsie: to sync with dhellmann or release-team to find the code for the proposal bot
    • jroll - ttx: Feedback from the forum selection committee -- Follow up on https://etherpad.openstack.org/p/PVG-TC-brainstorming -- Final accepted list?
    • mnaser: sync up with swift team on python3 migration
  • addendums
    • define goal select process schedule
      • This is different discussion to select goals. We need to make sure we can have a schedule for cycles to follow. So we know when exactly to ask for goal idea, ask for champion, start +1 cycle goal select process, and start +2 cycle select process.
    • Maintain issue with Telemetery
    • overall review for TC summit and PTG plans

Apologies for Absence

evrardjp - Travelling

cloudnull - Holiday

Past meetings logs

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