...
Actions (issues on Github)
1A/ Buid CI/CD script to access code documented to know how well or poor it is
Write Documentation next to code where is missing
Publish documentation in Compas Open SCD website
Enable script to build HTML from Jsdoc, Java doc, Tsdoc ..
2A/ Ask Daniel (for making a proposal to Transpower Distribtion to re-unite with OpenSCD)
Lack Lack or broken communication / trust between distribution devs
Issue attribution and tracking
3A/ Organise a session or company restrictions
Compas-OpenSCD and SCT link not established
Framework different for collaboration (Technology stuck)
Release are done unpredictably
4A/ Write unboarding documentation
Growing community Rotations in teams Long term visibility and priority management
Refinements topics are late or not announced, not too much time dedicated, some decisions on discussions are not discussed
Lot of discussions without concrete step or follow ups, attendancy of openSCD meetings is low, meeting that could've been emails
Difference in views on topics, matter of coordination on who do what, Developping ealierly feature before finishing harmonisation
Too many subgroups working indepently
6A/ Define clear roles
7A/ write in a confluence page the way of working / best practices
...