...
| Excerpt |
|---|
30 min, Thomas Kulik Pawel Pawlak Discussion across ONAP community on how to handle unmaintanied unmaintained code and how it impacts ONAP documentation. Best practices from other projects are welcome. |
...
Across ONAP release new project appear and some projects are abandoned. It is crucial to agree on how to handle unmaintained code and how this would reflect ONAP documentation.
Slides & Recording
| Info | ||
|---|---|---|
| ||
Please indicate your session type in the blank space below and then remove this Info field.
LFN Staff may elect to publish some videos to YouTube. Please indicate here if you do not want your session to be published to YouTube. |
Live interactive session
Agenda
Awesome presentation
- Problem description
- Discussion on best solution
- Wrap-up
Minutes
Action Items
Live interactive session
| View file | ||||
|---|---|---|---|---|
|
| View file | ||||
|---|---|---|---|---|
|
Minutes
- Much time spent running tests / scans on unused code.
- Consensus that this needs to be addressed as a priority
- Need to stop being "scared" of deprecating unused code.
- Discussion of the role that obsolete wiki pages play in confusing what is relevant.
- ODL renames pages as "__DEPRECATED:"
Action Items
- Kenny Paul get discussion on a future TAC agenda
- Kenny Paul look at kernel model for decision making around unmaintained code.