[Starlingx-discuss] Community Call (Oct 9, 2019)

[Zvonar, Bill]

Notes from today's meeting...

- standing topics
    - any Gerrit reviews that need attention?
        - nothing specific, but Saul noted that cores should be checking for reviews on a regular basis - general agreement w/ this
        - AR: Dean to present an overview of cool things you can do in Gerrit to watch/monitor your reviews (sneak preview: https://opendev.org/x/gerrit-dash-creator)
    - sanity - any reds since last call?
        - ISO 20191003 was red: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006397.html
            - same issue as next day? - yes
        - ISO 20191004 was red: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006412.html
            - fixed by https://bugs.launchpad.net/starlingx/+bug/1846540
            - per Ghada, it was due to the K8s upversion not being tested in the air-gapped proxy environment - agreement that it was not unreasonable for Sanity to pick this up 
    - any unanswered calls for assistance on the mailing list?
            - nothing this week (add note here re: Sai Chandu's email)

- debranding mirror and local repo (Saul), see http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006442.html
    - Saul to bring this to the next build meeting 
    - AR: Frank is going to see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done 

- election - self-nomination period is underway - Ildiko's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006415.html
    - Identifying project team contributors for projects without repos (ildikov)
          - Utilizing the projects.yaml file under starlingx/governance
          - PLs to provide a list of contributors
          - Affected project teams
               - MultiOS
               - Networking
               - Openstack-distro
               - Release
               - Security
    - do we want to maintain a contributor list to all projects?
    - today's discussion... 
               - we need to ask each PL for a list of contributors for their project
               - then maintain this in the projects.yaml file 
               - see the 'extra-atcs' field that OpenStack uses (active technical contributors) 
               - https://opendev.org/openstack/governance/src/commit/69d2ef8c1c79323a3d9eb0b1f7d741cef3d2c59f/reference/projects.yaml#L651-L795
               - there's also apcs, for project contributors
               - Bart: is this for all contributors, or just the ones that didn't do commits 
               - Ildiko: could do it either way
               - Bart: would be better if we just do it for those that aren't committers - everyone seemed to agree with this 
               - actions... 
                  - Bill send out the lists that did get generated for each sub-project
                  - PLs/TLs review & add 
                      - add to the projects.yaml file otherwise send to the election officials 
                  - TSC to push that through by end of next week 
               - Ildiko: going forward, PLs/TLs maintain this 

Open Action Required (AR) Updates

- Sep 25, 2019 -- Release Team -- add release notes to the RC1 checklist
   - Oct 9: done
- Sep 25, 2019 -- Doc Team -- find a place for Sai Chandu's images/documentation 
   - Oct 9: done, per last week's udpate
- Sep 11, 2019 -- TEAM -- complete project sub-team re-alignment, need to finish this before we start the PL/TL election cycle, per TSC and https://review.opendev.org/#/c/680514/
   - Oct 8: this is done
- Sep 11, 2019 -- Ildiko -- look into documenting the process of having documentation part of the development process to the contributor guide 
   - Oct 9: Release Team has added a checklist item for the feature PL @Milestone-3 that user documentation input for a given feature has been provided 
- Sep 11, 2019 -- Bruce -- identify the feature documentation gaps
   - Oct. 9: Because the test team is currently working on the items below, Abraham proposes collaboration between QA and Developers to write the corresponding guides. 
       If the test team simply writes down the steps they are using to execute the tests and fills in a few blanks, handing off to the doc team, that would be a huge head start.
       - Distributed Cloud -- https://storyboard.openstack.org/#!/story/2005181
       - GPU Kubernetes Plugin
       - TSN -- subtask 36405 in https://storyboard.openstack.org/#!/story/2006289
       - Redfish
       - Infrastructure and cluster
- June 26, 2019 -- Abraham -- provide a forecast for providing a Docker image list
   - Oct 9: done, Maria now linking Christopher's container list at the bottom of the sanity reports


-----Original Message-----
From: Zvonar, Bill 
Sent: Tuesday, October 8, 2019 8:28 AM
To: 'starlingx-discuss at lists.starlingx.io' <starlingx-discuss at lists.starlingx.io>
Subject: Community Call (Oct 9, 2019)

Hi all, reminder of the Community call tomorrow.

Feel free to add to the agenda at [0]... 

- upcoming elections and project/repo restructuring

- and the usual standing topics... 
            - Gerrit reviews that need attention
            - Red sanity learnings
            - unanswered requests for help in the mailing list
            - open AR review 

Bill...

[0] etherpad: https://etherpad.openstack.org/p/stx-status
[1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call
[2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191009T1400