[Starlingx-discuss] TSC minutes - January 24th, 2019

[Jones, Bruce E]

> Change to Multi-OS PL - Bruce -> Cesar
>             Submit a change to governance repo - project primes - update
>             Bruce to submit the change

Change https://review.openstack.org/633043 has been submitted, please review and approve.

The change does not include a TL for the team as I believe that is yet to be determined.

       brucej


From: Jolliffe, Ian [mailto:Ian.Jolliffe at windriver.com]
Sent: Thursday, January 24, 2019 8:48 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] TSC minutes - January 24th, 2019

Hi All;

Please see below the minutes from the call:

We reviewed the open specs and discussed how to move forward and close them off.  The spec submission deadline is behind us and the doc team has received an exception, to provide an overarching view of the documentation plan for the next release.

MultiOS review in Google Docs: [0]
-          Saul, Victor, Ken, Jason and others have been iterating in the above doc.
-          The multi-OS team will have a call on Monday morning to work on the above doc
-          Stay tuned for a meeting notice from the multi-OS team

Openstack patch elimintation status - Bruce
Details can be found here: [1]
58 items - 20 at risk/unlikely
Many items are At Risk for the release.  We have several options:
We could release without any patches to OpenStack and accept the functional / robustness issues
We can selectively apply one or more of the pending patches
We can do this pro-actively or reactivly e.g. to resolve bug reports
We can do this once the changes are accepted upstream (post-Stein)
How can we adjust and carry forward for items that don't make it
We can apply all of the patches for the outstanding issues
Issues are staffing and cross project working.

Feature priorities for the next release next steps  - Brent
We need Users / Partner feedback - Bruce
Brent to open an ethercalc - need upfront investigation and planning for the larger items
Identify which ones need the investigations
Are there people on TSC who want champion ideas - Curtis volutunteers, looking for other volunteers outside of TSC as well.

Change to Multi-OS PL - Bruce -> Cesar
Submit a change to governance repo - project primes - update
Bruce to submit the change

Tagging issues/bugs with "good first issue" "bitesize" "help wanted", etc - Curtis
Make this somehow easily linkable/available [2]
From an outsider perspective - would be a good idea on the website - how to contribute, good first issues for someone to jump on.  Take a look at Kata as an example.  Tagging - Curtis willing to help tag these kinds of issues.
Ken and Ghada have some automation that could be leveraged.
Curtis to take the next step and reach out to Ken/Ghada

STX Denver Summit Workshop: - thanks Curtis for setting this up – Etherpad [3]
Shuquan - drafting abstract and will update the etherpad

Packet.com edge CBRS: [4]
John Studarus from community call yesterday – highlighted the opportunity
Looks like a very interesting opportunity to showcase STX in the real world situations.
Tie in marketing team to promote this work as it evolves.

Doc spec underway and will be posted shortly - Bruce

Performance framework proposal - sent to ML - Victor looking for feedback from TSC members.
Google doc posted - Victor to check permissions: [5]

When people propose talks to an event – please list them on this etherpad that Ildiko created. [6]

Links:
=====
[0] https://docs.google.com/document/d/188nuV98w90xG0WWRFKItoxcsCzH5xB95dy-MD1MDR5c/edit?usp=sharing
[1] https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing
[2] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002647.html
[3] https://etherpad.openstack.org/p/stx-denver-2019-workshop
[4] https://etherpad.openstack.org/p/starlingx-packet-edge-pilot
[5] https://docs.google.com/document/d/1js5uaeJRz4mX_WkioqiGwK5FC7pVOW0mdELAr2yuvKI/edit
[6] https://etherpad.openstack.org/p/edge-cfp-for-industry-events








-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190124/7020e0b3/attachment-0001.html>