Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Attendees: 



Agenda Item NotesOwnerActions / Next Steps
Updates on Release 1.9
  • #15164: td-agent version pinning
  • #15520: Cwag-CI taking huge disk-space
  • #15217: NMS yarn test (unit test) failing
  • #15222: Summarizing the current state of CI Issues.
  • Discuss DevOps workflows for patch-level semvers if we move from 1.9 to 1.9.0 label. Can we have smaller + more frequent releases?

Sikander-Wavelabs


Lucas reached out to yogesh, for C++ changes and new feature changes to look into security POV for 1.9, no longer blocked on CI/CD dashboard, next eng meeting need to review old prs and start cleaning up. 

  • Yogesh catch up with features group to pick release date: No discussion as the participation was very low.
  • Jordan → propose mid august for 1.9 release date, discuss when we have quorum of TSC members
  • Max - has not been a pr since 2nd may : Need to fix other CI issues (like CWAG, NMS)
  • Jordan→ Ubuntu, need to plan upgrade, bring to features group
  • Max → suggest we do a survey related to Docker
    • Survey:
      • Which deployment are you using, Debian or Docker?
      • What do you expect in 1.9?
    • Customers still using 1.6/debian
  • Som → is it possible/feasable to make 1.9 docker only?
  • Lucas → suggest debian for 1.9 and docker after
  • Max → ensure features group changes go through TSC vote (folks agreed)
  • Yogesh → testing tool
    • Som → action, resurrect tool/lab request process
    • Lucas → suggest start thinking about 1.10 and 1.10 is docker and performance testing
    • Max → not looking or thinking about docker is the equivalent of dropping it, not supporting docker in this release is essentially a vote against 
    • Lucas → connect5g can not live without docker
  • Action → Yogesh will repost notes to TSC for feedback
Bug Bounty Program
  • Ben - discuss "pay for work" model 

    • Lucas proposed "refactor reviewdog-workflow.yml for security" https://github.com/magma/security/issues/147

    • Som proposed windowing scheme
    • The Security WG discussed disclosure of security weakness in bounties for fixing them
    .
  • Hackerone likely not the right platform. Given use cases we would use Github sponsorhsips.
  • Arrived on policy for disclosing security issues: ok to disclose if trivial, otherwise we will reserve bug bounties for trusted contributors
    • .

    Bounty amounts need to be defined
    • Shubham to document two bounty proposals: upgrade Kubernetes; create CI job to scan Docker images for vulnerabilities using trivy
    • Som to create a page in the LF wiki on the bounty program.

      • Som will coordiate with Ben once bounty program proposal has been fully greenlit
    • Need draft Quickstart for anyone who wants to recommend a bug bounty program (process & timeline) - Jordan will start doc, Ben add in budget info. 
    • Bounty amounts need to be defined
    • Bounty Program Process
      [ NEED TO CLOSE THIS - TSC members please review/comment]
    • Folks will review and comment this week
    • Ben
    Reward readme document needs to be written and vetted by LF legal.
    • Draft README for github
    • Discuss in outreach Decide on budget and budget per issue.
    Outreach Report

    No working meeting last week. Latest updates in MagmaOutreach-meeting-6.8.2023 - Google Docs

    Upcoming town hall meeting planner - July, 2023 - Town Hall planner

    Secured Town Hall keynote speaker

    • Action items and next steps are captured in document
    •  Pick topics and date for next town hall
    • Develop aggressive comms plan as part of town hall planning

    Other:

    • eBPF 
    General discussion on interest in eBPF project (migration from OVS)@Pravin Shelar
    • Shubham Tatvamasi , Suresh (Wavelabs), Som are interested
      @pbshelar@fb.com will start the document. Contact him over slack if you are interested in participating.
    • Lucas → is this stalled we have not seen updates in awhile.
    • Action-> ben reach out to 3 folks listed here for updates
    Branch protectionTo enable the CI dashboard fix to go into production ASAP, Max had to suspend branch protection rules in order to enable force merging. Let's discuss when and how to take this step in the future.
      • Revisit due to slack discussion
      • TSC Will Vote On The Following
        • Force merging is off by default
        • Only Linux Foundation, IE Benjamin Sternthal, is allowed to set it to on.
        • LF may only enable it by vote of the TSC.
    Requires 4 present for quorum
        • Lucas proposed change → Requires two TSC members to vote on approval
      • Max → unclear on what goals we are tying to accomplish
      • Vote will be recorded here
    Security issue 151
    OpenSSF Best Practices Badge update

    Review progress and future steps


    Max Agenda Item Placeholder
    Maximilian Huber 

    Max → time to step down from TSC, make room for other folks to join TSC

    Action → ben to work on dates and election

    Review Latest Q&A In Github, Review Slack For Candidate Github Topics

    Recording:

    https://zoom.us/rec/share/FHAUKUaj62TRDr57P7pXJunfSNV3lni3brrMZ_sv3-7KWAaJ34aM0nY3gECOjHhMvR0BjL7fQIFM9YNKCs80JLZztffpQaoxDIOLI_7030XP_2r6nWJQPWDK.GVaPGo-SaPsi9M8gRAOS7j.x28OXiHNHZmFeNvy