Hi all; Below are the minutes of our last TSC meeting of 2018 – looking forward to an exciting 2019 with the community. Our next meeting in the normal slot will be on Jan 10th. The Jan 17th meeting will be cancelled as the TSC will be meeting at the F2F in Chandler on Tuesday and Wednesday next week – the agenda is here [0]. Meeting minutes: Dec 20th, 2018. Compiler option item from the prioritization SS * It sounds like there are patches out there? What projects are compiled with these options? – Curtis * Can we leverage OPNFV performance test frameworks? * On going evolution of community test infrastructure is important to make these things easier to assess. * Need to work with technical leads and due to lower priority this work fall after the higher priority items Help requested for Nova spec review: https://review.openstack.org/#/c/620959/ (brucej) * Chris to review * This change has been merged OpenStack Pilot Project Promotion Process update - brucej - 10 mins Current draft proposed by Intel to the BoD includes this: Pilot Projects can be promoted to a Confirmed Project when the Officers determine that the following Criteria have been met: 1) The project continues to be strategic to the Foundation’s mission, falls within the scope of software infrastructure and is aligned with one of the OSF strategic focus areas. 2) The project has adopted the Four Opens as defined in [1]: All code is Open Source (not “open core”); uses Open Design & Open Development processes; and Open Community practices are upheld. 3) The project has contribution and engagement from a variety of companies in order to appeal to a broad ecosystem. Needs to be a focus area for community and TSC 4) The project has well defined governance spearheaded by technical leaders who set the project’s direction and own its roadmap while facilitating the Four Opens. The project’s governance shall be documented, maintained and approved by the project’s leadership and the Foundation. See Exhibit A for more indicators of open governance. 5) The project does regular and periodic releases at least twice per year (more releases is better). If the project is aligned with OpenStack and subject to agreement between the Officers and the Pilot Project team, the project’s releases and CI/CD framework should be coordinated with that of the OpenStack project to ensure compatibility with relevant OpenStack components. 6) The project can show proof of having users of code in production environments (one metric for maturity, there may be others.) Action: Need a mechanism to track this - should we consider an adopters file? Logo page in our documentation and web site for StarlingX Action: Bruce to take action back to Doc team 7) The project adheres to the OpenStack Foundation Code of Conduct. Action: We should start tracking users for this metric. I suggest asking users to self register in an Adopters file and/or wiki page. Other items: Should we have a home location - for miscellaneous items Dean is looking for input - add to F2F agenda No meetings - Dec 27 or Jan 3rd Victor and Brent met to discuss big picture multi OS Encourage community members to attend Multi-OS meeting Regards; Ian [0] https://etherpad.openstack.org/p/stx-chandler-meetup