Technical Committee Weekly Meeting 2016.06.21

Meeting time：　　 2016.June.21 1:00~2:00

Chairperson：　　  Thierry Carrez

Meeting summary：

1.Add current house rules for reference

　　This lists exceptions to the formal votes for various changes

　　in the openstack/governance repository. It corresponds to

　　house rules as they were proposed to the Newton membership in

　　our introductory meeting, with additional wording to cover

　　the exceptions proposed by Doug Hellmann at our last meeting.

　　Link: https://review.openstack.org/#/c/330442/1/reference/house-rules.rst

2.Update team tags for some projects

　　congress: To provide governance as a service across any collection of cloud service. =>team:diverse-affiliation

　　solum: Software Development Lifecycle Automation service. =>team:single-vendor

　　zaqar: To produce an OpenStack messaging service. =>team:diverse-affiliation

　　Link: https://review.openstack.org/#/c/332093

3.Remove Packaging-Deb project team

　　PTL: Monty Taylor

　　Desc: Maintain packages for Debian (and other deb based distributions) as a community.

　　Status: abondoned

　　Reason: I proposed this because Packaging-Deb is the only official project team without any visible activity.

　　I'm not in favor of removing this as the project team in question is currently in the middle of good-faith effort to implement the needed things.

　　1) the repositories can't be moved without losing existing CI functionality, and fixing that would be a distraction.

　　2) this is close to getting the necessary infra support for proper CI within OpenStack.

　　3) this effort is deep enough that we wouldn't pursue it (or prioritize it) if the project was not official.

　　Agreed: grace period for Packaging-Deb extended to end of August.

　　Link: https://review.openstack.org/329430

4.Add 'type:horizon-plugin' tag

　　Define a new deliverable type tag to describe deliverables

　　that are specifically meant to be loaded by Horizon to provide UI for a given project.

　　Link: https://review.openstack.org/#/c/329479/

5.Add 'level playing field' requirement

　　From an upstream perspective, I see us as being in the business

　　of providing open collaboration playing fields in order to build

　　projects to reach the OpenStack Mission. We collectively provide

　　resources (infra, horizontal teams, events...) in order to enable that open collaboration.

　　Require: 

　　The new project shall provide a level and open collaboration playing field

　　for all contributors. The project shall not benefit a single vendor, or

　　a single vendors product offerings; nor advantage contributors from a

　　single vendor organization due to access to source code, hardware,

　　resources or other proprietary technology available only to those contributors.

6.Open Discussion

　　1) We'll have most TC members in Ann Arbor next week for the leadership training, so we'll skip that meeting.

2) Release Coordinator Nominations

======= ============ ================ ========== ========== ==================
Release Coordinator Nominations Open Poll Open Poll Close Geographic Region
======= ============ ================ ========== ========== ==================
M Monty Taylor 2015-06-01 2015-06-08 2015-06-15 N/A
N Monty Taylor 2015-11-08 2015-11-30 2015-12-07 Texas Hill Country
O Monty Taylor 2015-11-08 2015-11-30 2015-12-07 Catalonia
P Monty Taylor 2016-06-22 2016-07-06 2016-07-13 New England
Q Monty Taylor 2016-06-22 2016-07-06 2016-07-13 New South Wales
======= ============ ================ ========== ========== ==================

　　Link: https://review.openstack.org/#/c/332193