...
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 net to code where is missing
Publish documentation in Compas Open SCD website
Enable script to build HTML from Jsdoc, Java doc, Tsdoc ..
...
3A/ Organise a session or company restrictions
4A/ Write unboarding documentation
6A/ Define clear roles
7A/ write in a confluence page the way of working / best practices
9A/ Write down in a clear maner where add which document
10A/ Think about communication channels for collaoration subjects
11A/ Re-check current state of SSFBadge
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
19/ Sde reviewer/maintainer
22A/ Appoint new TSC chair
Help Spinteins to get contract
Best practices
...
Best practices
- Avoid lazy concensus decision makng
...
- Sends subjects to TSC days before for decision
...
- RTE PO should prioritize in their sprint
...
- Compas tickets
...
- Introduice code owner/responsible
...
- Explicity quality checks before featuring a pluging in OpenSCD
...
- Unclear quality definition in OpenSCD
- Help Sprinteins to get a contract
...
- Define clear roles
- 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 not yet in Github)
- 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