Legal has requested changes. LFC advisory board has requests.
1.9 Release
CI changes needed.
Testing continues. No fatal issues found yet.
Want to entirely drop the patched HTTP proxy. Need to document this whole project (see), since there is a general lack of documentation. Need to create a ticket. #followup
Review a few old ones that require followup action
Bug Bounty Program
Starter Kit / Kubernetes / container
Connect5G is starting K8s internally. Kernel 5.4 and below. No eBPF in MVP, to be completed later.
Waiting on supplier (SP) for quote on starter kit hardware. Know 4G radio, 5G radio is TBD. Next steps: POS, firm component list. UE, controller, SIM card known, USRP unknown
Review a few old ones that require followup action
Bug Bounty Program
Starter Kit / Kubernetes / container
Outreach Report
Review Latest Q&A
Minutes
Call for vote: - Ready to forward upwards to other parties as a proposed proposal, but not for final approval - If they ask for changes, they will be made before acceptance - Whether or not they make changes, there will be a later vote on final acceptance - Approvers (unanimous): Jordan, Jim, Yogesh, Som, Lucas
Need to write these for the forwarding note: - Explanation of why - Itemize and explain changes. Consider using Word. Lucas to share the versions with Jordan to compose the doc. - CC the final note and documentation to the TSC, as a snapshot of whatever we're forwarding
Need to elect a TSC chair per the latest but not earlier charter. Need to choose period of election - one or two weeks? Followup: Sandra to draft an email to put that question to the TSC
15 APR email sent, nomination is open and it's closing on 24 APR.
55 Proposals pending on GitHub, we need to go over the proposals and mark the proposals that are discussed as "Accepted" or "Rejected" and bring the rest of the proposals on the next TSC meetings. AP: discuss the proposals on the next outreach meeting.
Mickey raises the issue of program management debt in proposal list. Also debt in open issues that should be closed. Yogesh proposes closing zombie proposals after 1.9. Mickey proposes returning to the scheme of labeling proposals with status. https://github.com/magma/magma/blob/master/docs/docusaurus/versioned_docs/version-1.8.0/proposals/p014_proposal_process.md . The person to do this work must be in TSC because they will have the knowledge and influence necessary. Followup unclear. 15 APR to be discussed on next Outreach meeting.
Need to elect a TSC chair per the latest but not earlier charter. Need to choose period of election - one or two weeks? Followup: Sandra to draft an email to put that question to the TSC
Mickey raises the issue of program management debt in proposal list. Also debt in open issues that should be closed. Yogesh proposes closing zombie proposals after 1.9. Mickey proposes returning to the scheme of labeling proposals with status. https://github.com/magma/magma/blob/master/docs/docusaurus/versioned_docs/version-1.8.0/proposals/p014_proposal_process.md . The person to do this work must be in TSC because they will have the knowledge and influence necessary. Followup unclear.
Yogesh to post 1.9 update list, and community as a whole to document new functionality and user-visible changes. Related: documentation on 1.9 as a whole.
Create a seed for future work on eSim support. Jordan to open new Discussions topic.
Yogesh to include Bruno Faria and Nathaniel Bennett in #15388 NAS improvements. Lucas to invite Bruno and Jordan to Security WG.
Call for votes to award bug bounty on rate limiting. Motion by Jordan, second by Lucas. Yes votes from Jordan, Yogesh, and Lucas. The motion is carried. Pierre to submit invoice.
Organize program management for payments after TSC approval. Verify with LF what the right process is. Related issues - accounting; bug bounty payment flows. Sandra to research; Som and Lucas to consult.
Make sure that governance reset plan is in accord with legal requirements at LF. Sandra and Lucas to discuss.
WRT #15371 Som suggests a leading practices document e.g. for rate limiting reverse proxy. Distinguish between software insecurity and deployment insecurity. Lucas to document deployment practices to handle in the insecurity notice in the README.
- Potential performance cost - Could release 1.9 with documentation on these known issues - Veltris can research the C++ port timeline in more detail, assuming it's in 1.9.2. How long will testing really take? - Lucas proposes holding off release of 1.9 until patches are available - Bruno points out that fixing C may take as long as C++
Really good mindshare but OVS Sidecar or whatever for AGW needs to be figured out. Connect5G will figure this out as part of Kubernetes migration and come back with investigation result.
Technical solution to runner problem has been found using free Ubuntu regular runner but run time has doubled from 3 to 6 hours. Consensus is to stick with this and optimize later.
Mac-OS large runner PRs was tried but the builds are still failing. Working with LF team with admin permissions on Github in order to bump up disk space.
Ubuntu Regular runners (free) were tried but getting stuck with disk space
Next step is to run the Ubuntu Large runners but might need help from the admin.
New proposals
Yogesh suggests adding some open PRs that were not planned for inclusion
Bug Bounty Program
Som has researched LF policy and found that if we make any substantial changes to a bounty item, like bumping up the amount of an existing bug bounty, we need to coordinate with LF.
Som to find out the amount that we got approved.
Starter Kit (we have updates of estimated cost – Som Sikdar ) The following assume a purchase of 10 units which seems to be minimum ordering number so far from vendors)
Radio (exact model TBD - we have candidates) - $ 15000 (for ten units)
Magmacore controller:
Mini version (4x Arm A53) - approx $ 10K
Maxi version (beefier processor) - approx $ 25K
This is for a pool of 10 kits that will be shared among the community (we still need to figure out FOB point)
Community members will be able to procure directly from vendors
TSC needs to decide on final numbers and send a formal request for funding and the logistics of the proposal to Linux Foundation
Need to research:
Mini vs maxi vs both
Buy vs share
Application process
Support
Vendor
Parties who want a unit
POC unit. Carnegie Mellon might be able to test.
Followup: Som to create a framework for discussion
Yogesh to ask DevOps engineer to push the button to pay and see what happens
Tim to work in parallel towards next release
New proposals
Bootstrap new documentation project. Feedback requested by Jordan.
Bug Bounty Program
Outreach Report
K8s / virtualization
was voted last week. Proposal adopted. No need for standing topic. Followup: remove from standing
Need to move away from Vagrant. For ARM move to Docker containers - Connect5G and Tim also. This runs into complications with Openvswitch needing to deploy the kernel module.
Reminder to Review Latest Q&A
Followup Tasks
Lucas to add committers Jim Blakely, Micky Kumar, Som Sikdar, Javier Vargas
Add to workflows: freeze this compilation at end of quarter
Add Starter Kit to standing topics
Yogesh to go ahead on upsizing VM without syncing with Tim
Inform Tim that his work will be in version after 1.9, not 1.9
Remove K8s from standing topics
February 5, 2024
Attendees and their affiliation
Lucas Gonze (Independent)
Yogesh Pandey (Veltris)
Micky Kumar (Veltris)
akhila (Veltris)
Vijayakumar R Tawker (Veltris)
Jim Blakley (Carnegie Mellon University)
Jordan Vrtanoski (Connect 5G)
Som Sikdar (Independent)
Topics
New Business
1.9.2 release
Add "Post 1.9" items from Yogesh' issue list
Add fixes for recent disclosures from Nathaniel Bennett and Jorge Vargas
ASN.1 Compiler - Need coordination with other LF groups about usage. Sandra Jackson is there a way to check this with other groups/PMs?
No blocking. Will be merged post 1.9
Starter Kit - In last outreach meeting we discussed if a paid project/resource from LF can help for starter kit. Topic to be discussed here (TSC)
Blocked on documentation and on 1.9. Hardware is complete.
Jordan to create a proposal for documentation funding.
Outreach plan and travel/speaker budget - Discussed at last outreach and also separately as part of LFC foundation fundraising. Should consider this in TSC and set a tartget to get this done
This may not be possible any more (4.22.2024) We are not ready
Need to know how much is available. TSC to ask Sandra whether LF would cover a budget of $X. Work out details in Outreach meeting.
LF Connectivity Foundation Fund-raising - This process has been kicked off by Linux Foundaiton and advisory board. I shall report back with the proposed charter and activity here as it progresses
Draft PDF of proposed LF Connectivity proposed participation agreement - Feb 2, 2024 copy
There is a plan to do a Q&A session from LF to answer questions about this new foundation. Prospective members will be invited to attend.
It is recommended that the current community member attend or track this session