Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
Fabrizio Moggio (Chair) | TIM | x |
---|---|---|
Robert Ludovic | INNOV/NET | x |
Fan Yang | China Unicom | x |
Rafal Artych | T-Mobile | x |
Enlai Chu | Productive.ai | |
Stefano Falsetto | CK Hutchison | x |
Agenda
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 legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF. |
- Last Meeting Report Approval
- Open Discussions
- Conditional/Unconditional
- Release Management
- Documentation
- Next Steps
- Action Items
Slides: TBD
Minutes
- Last meeting minutes approved
- conditional/unconditional options (see slides - updated during the meeting)
- Each option presented by fabrizio moggio and discussed with the team
- Option 5 has global team preference (its granularity allows flexibility to market, to manage consent at each level and accommodate partial implementation)
- Release management
- Current proposal in discussion could be challenged as it is still work in progress in Release Management team
- API documentation
- UC #2 will be added
- UC #3 needs more discussion but move to option 5 allows us to add it in future.
- MegaLinter Integration
- Rafal Artych has run the tool and provided an issue with the result
- The yaml needs to be first clean up before to integrate the MegaLinter tool.
- Test Definition: in stand by in Commonalities
Task report
TBD
Action items
- 2-1: create User Story for UseCase-2 (Fan Yang)
- 2-3: integration of the Linting tool (Rafal Artych )
- Rafal Artych makes a pre-run
- Fix the yaml according to the issue #28 (fabrizio moggio )
- Rafal Artych integrates the MegaLinter tool
- 3-1: Draft for the API Documentation (fabrizio moggio)
- 4-1: Update YAML according to option 5
- Update the documentation as well