...
- N3000 vRouter-DPDK building process. The details should be discussed and decided on the future meetings. The presentation is available here: TF N3000 building process proposal.pdf
- TSC priorities:
- Ongoing survey about community priorities - check the bottom of the page → 2021 TSC Priorities
- Results of the survey after one week:
- Communication regarding the development of TF features and bugs is done in TF JIRA - Critical
- Test documentation is stored in the TF repository and can be freely accessed - Highly needed
- Build procedure is written down and it’s stored in docs.tungsten.io - Critical / Highly needed
- Script for building TF are stored in tf-jenkins repository - Critical
- CI is managed by clearly nominated LF administrators with all needed privileges - Needed
- CI infrastructure is documented - Highly needed / Needed
- Documentation of where release artifacts are stored (docker hub etc.) is in docs.tungsten.io and what naming convention they follow - Critical
- LF administrators have access to all places where release artifacts are stored (docker hub etc.) - Highly needed / Needed
- Release artifacts are published by LF administrators, or people designated by TSC, after TSC approval - Critical / Highly needed
- All code added to TF is exposed in TF either through WebUI, API, or CLI. This means there is no code that is consumed only by proprietary additions - Highly needed
- PTL responsible for the development of new features delivers Release Notes for those features at the moment required by a milestone description - Critical
- PTL responsible for the development of new features delivers documentation for those features at the moment required by a milestone description - Critical
- PTL complies with TF release procedure (keeping EPIC up-to-date, TSC approvals, planning, delivery of the code, documentation, etc.) - Critical / Highly needed
- There is a person responsible for de-contralization of the source code - Highly needed
- There is a roadmap of code de-contralization - Highly needed / Needed
- Code added to TF repo doesn’t use naming other than Tungsten Fabric / TF - Highly needed / Needed
- All documents/blueprints/tests added to TF repo doesn’t use naming other than Tungsten Fabric / TF - HARD TO DECIDE
- All code migrated or added to TF has at least unit tests coverage and tests cannot be omitted from the development process - Critical / Highly needed
- Marketing channels (twitter, linkedin etc.) are managed by a person selected by the TSC or LFN representative - Highly needed
- Transparent project roadmap for the next release - Critical / Highly needed
- Reminder about the Auth0 Migration
- Technical Work Stream on Tuesday - a place to present new features, a place to ask questions
- Next week Pradeep Choudhary will talk about vRouter multihoming https://github.com/tungstenfabric/tf-specs/blob/master/R2105/l3mh.md
- Who from the community can participate in what way?
- LFN Ops Survey
...