| 2am PST | 5am EST | 09:00 UTC | 10:00 BST | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |
(please feel free to correct and update your names Thank you very much!!!)
Mailings
Time | Item | Who | Notes |
---|---|---|---|
00:00 | Chair topic | no update | |
00:01 | Admin | 2022-07-06: Martin Skorupski 2022-07-13: Martin Skorupski 2022-07-20: Martin Skorupski 2022-06-27: Martin Skorupski | |
00.05 | Equipment #13 | Thorsten Heinze | The TransmitterEquipment specification should be complemented by some prescription about where to document/find the type of the physical connector. More connectors should be added to the list, which are already known to be relevant, for avoiding vendor specific modules that will add them. Vendors to provide the list of necessary connectors by 28th of June. Issue to be approved next week, 29th of June. More connector types added (check syntax of yang identifiers: On the agenda for next week to add more connector types. |
00.15 | Equipment #14 | Thorsten Heinze | isHotSwappable needs a new comment to describe exactly the conditions when an equipment is hot swappable Proposal: instead of adding the text on a new attribute and augment the core-model, the comment should be changed from the core-model itself while pruning and refactoring, avoiding then a duplication of the attribute. Issue to be approved next week, 29th of June. Approved as proposed. For documentation purposes we create a new issue in CoreModel repo referencing Equipment #14. Please see: https://github.com/openBackhaul/core/issues/26 |
00:30 | Michael Binder | must statements in leaf-refs towards capability data Approved as proposed. For documentation purposes we create a new issues in the affected repos referencing AirInterface #55. | |
00:35 | Synchronization | Michael Binder , all | Default values
Issue Tracking:
|
END OF THE MEETING | |||
00:00 | Backup and Restore | @Sentival | Requirements from TEF: https://github.com/openBackhaul/firmware/blob/tsp/BackUpAndRestore/BackUpAndRestoreRequirements.md Comments could be addressed by adding issues in GitHub.
|