Sep 16
o
Title: “StarlingX Overview”
o
10 - 15 minute recording with time for live text chat Q&A (max session time of 30 minutes)
o
Oriented toward beginner audience
o
High-level overview suggested touch points:
·
Explain what the project is
·
Where it fits in the software stack
·
Open source projects it integrates with
·
Tools used to contribute/where to find us online
·
How it follows the 4 Opens
§
Yong volunteered to do the recording, thank you! He and/or community members can cover the Q&A
o
The on-boarding deck on www.starlingx.io is one option for this content, but that deck is out of date a bit. Bruce can update it - Ildiko please see if you have the source.
·
Current de-branding changes should merge in an orderly way. Start with below patches -
o
https://review.opendev.org/#/c/687401/
o
https://review.opendev.org/#/c/687403/
§
These can be merged once we get some +2's from the Cores - Scott will then remove the -1.
·
Focus on the changes that are visible to end users first, e.g. messages written to log files.
·
Limit to those that ARE tied to the build infrastructure. e.g. TIS_PATCH_VER in build_srpm.data and %{?_tis_dist}.%{tis_patch_ver} in spec files.
·
Changing text in source code comments and other innocuous places is not a priority
·
Google docs spreadsheet with fields for package, file path, reference type, reference value - ability to filter and/or sort on a field. change in a co-ordinated fashion.
§
Nic/Yang: feedback from test perspective on stx.4.0 lessons learned - not set up yet
§
Docker images - Scott - we are OK on the build side, not sure if we are OK from the test side (60-100 image limit from one IP per hour)
§
AR: Release Team discuss whether or not we should just go ahead & nuke stx.2.0 now, as is our stated policy