...
Too many subgroups working indepently
6A/ Define clear roles
7A/ write in a confluence page the way of working / best practices
clear and documented way of working
9A/ Write down in a clear maner where add which document
10A/ Think about Create communication channels for collaoration subjects
11A/ Re-check current state of SSFBadge
Do we want to go throught Early adoption this year
OpenSSF badge (quality, security)
13A/ Create Issue templates on Github
14A/ Create Pull Request template on Github
17A/ Explicitly show in Compas which version of OpenSCD is used
18A/ Stop supporting open-scd-core
Divergence in core package
19/ Sde Reorganize reviewer/maintainer
Maintenance costs a shaned limited, Availabiliy from Tamas to review PRs
22A/ Appoint new TSC chair
Check priority and alignement, TSC member and their roles
23A/Help Spinteins to get contractCreate dedicated communication channel
Best practices
- 5B/ Avoid lazy concensus decision makng
...
- 8B/ Sends subjects to TSC days before for decision
- 12B/ RTE PO should prioritize in their sprint compas tickets
- 15B/ Introduice code owner/responsible
- 16B/ Explicity quality checks before featuring a pluging in OpenSCD
- unclear quality definition in OpenSCD
- 20B/ Help Sprinteins to get a contract
- Define clear roles
- 21B/ For upcoming people changing in project, wait for clear visibility of R#Space project
- Write document next to code where it is missing
- Announce earlier refinement topics