Attendees & Representation
Casey Cain Marek Chwal Alexandre Levine Edward Ting
Agenda
- Start the Recording
- We will start by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company's legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.
- Agenda Bashing, Roll Call, Action Items
- TF-Operator-Framework: How community developer may develop/test it? Currently TF Operator supports AWS and BMS deployment. However, BMS requires a machine with huge capabilities. Is there any community AWS account or pool of servers for developers?
- When the project is migrated from Juniper to Tungsten Fabric, shouldn't original code authors be mentioned? For example, TF Operator was developed as an open repository under Juniper's account on GitHub with Apache 2.0 license which usually contains AUTHORS file and is propagated to all derivative products - currently, newly created repositories contain in commits only people that migrated repository from Juniper to Tungsten Fabric and no original authors.
Minutes
- What are the artifacts we need to have to say that we released the TF? Release notes, build in docker hub, anything else?
- TF-Operator-Framework:
- TF-Operator-Framework is in Vexhost
so any code provided will be tested and deployed by the CI - If there would be any developer that would like to use the environment to deploy the TF he might need to contact someone from TF (Casey, TCS?)
- It was agreed a long time ago that all code moved to TF-repositories should be squashed. Maybe this rule should be changed at the TSC meeting?
Action items
- Type your task here. Use "@" to assign a user and "//" to select a due date.