...
For the bests practices for improving our way of working, they will be in this wiki and everybody can add new elements.
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 ..
...
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, attendance 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
clear and documented way of working
9A/ Write down in a clear maner where add which document
10A/ 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/ 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 contract
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
Actions (issues on Github)
- Define clear roles
- Write down in a clear maner where add which document
- Re-check current state of SSFBadge
Do we want to go throught Early adoption this year
OpenSSF badge (quality, security)
- Reorganize reviewer/maintainer
Maintenance costs a shaned limited, Availability from Tamas to review PRs
- Appoint new TSC chair
Check priority and alignement, TSC member and their roles
- Help Spinteins to get contract