47th meeting (18 June 2025)
- Sander Jansen
URL to join the meeting: https://zoom-lfx.platform.linuxfoundation.org/meeting/98343708243?password=4f93f05d-bec4-4c31-be57-1f4933cf97aa
Participants: @Sander Jansen @Jean-Etienne LEMAIRE @Christian Ruopp
TSC voting members missing: @pascal wilbrink @Stefan Baumgartner
1-Review of previous TSC notes
No commets, approved
2-Review of the growth plan actions
@Sander Jansen shared the next release: New LF Energy CoMPAS release! | Sander Jansen
@Sander Jansen reached out to CEATI
@Jean-Etienne LEMAIRE create a demo of the SCD generated file
@Jean-Etienne LEMAIRE did show a the result of a generated substation (100 to 150 Megabyte)
3-LF energy CoMPAS meetup
Review of the agenda
Do we need to add something about the OpenSCD discussions? What is our common ground in the OpenSCD ecosystem? We should tackle the issue of OpenSCD common ground more early.
Background on the OpenSCD history: https://openscd.zulipchat.com/user_uploads/65854/JA3x_tHDsATvRotsmhV56DTQ/OpenSCD-onboarding-workshop-20250604-1337-1.mp4
Status check community reach-out for the community meetup
TenneT germany: Stefan,
Amprion: Sander,
Elia: Sander,
Stedin: Sander,
APG: Stefan,
Enexis: Sander,
TenneT NL: Sander,
Vendors: Sprecher: Stefan, Hitachi; Stefan, GE: Sander;
4-LF energy summit talks
@Sander Jansen talk got accepted
5-Status of contributions
Bearingpoint (David is looking into openscd core)
RTE (go live by the beginning of July)
Alliander (Top down, bay approach)
Pascal (not present)
6-Roadmap review/update
https://lf-energy.atlassian.net/wiki/spaces/SHP/pages/32538737
7-Annual review
CoMPAS annuval project review last week:
Discuss: to we want to move to the early adoptoption stage? Take it to the meetup
If so, we need to comply with the silver level: BadgeApp
Todo: Have an open and documented technical governance, including:
A LICENSE file in every code repository, with the license chosen an OSI-approved license.
A README file welcoming new community members to the project and explaining why the project is useful and how to get started.
A CONTRIBUTING file explaining to other developers and your community of users how to contribute to the project. The file should explain what types of contributions are needed and how the process works.
A CODEOWNERS or COMMITTERS file to define individuals or teams that are responsible for code in a repository; document current project owners and current and emeritus committers.
A CODE_OF_CONDUCT file that sets the ground rules for participants’ behavior associated and helps to facilitate a friendly, welcoming environment. By default projects should leverage the Linux Foundation Code of Conduct unless an alternate Code of Conduct is approved prior.
A RELEASE file that provides documentation on the release methodology, cadence, criteria, etc.
A GOVERNANCE file that documents the project’s technical governance.
A SUPPORT file to let users and developers know about ways to get help with your project.
How to go about this?
Proposal:
Check License and readme.md (readable, clear)
Refer to CoMPAS Contributing · Contributing to the CoMPAS project in the Contributing files
Codeowners files needs to be added
Code of conduct: see https://com-pas.github.io/contributing/
RELEASE: see https://com-pas.github.io/contributing/ (To be added)
GOVERNANCE: Governance · CoMPAS Contributing
SUPPORT: Add a support section to https://com-pas.github.io/contributing/
Codeowner:
Check current rights
Generate them out of the commits (David will look how other will do this)
Check current proposal below:
Repository | Description | Current codeowner |
Repository with the readme.md | sander3003 | |
A substation configuration description editor for projects using SCL IEC 61850-6 Edition 2 or greater | Alliander | |
System Configuration Tool (SCT) components | RTE | |
CoMPAS Deployment repository | Alliander | |
A bay typical editor plugin | Alliander | |
Service to store and retrieve the SCL XML to a database | Alliander | |
Service to auto align SCL files without coordinates | Alliander | |
Service to Map CIM Data to SCL Data | Alliander | |
Project's architecture documentation | Alliander | |
Contributing guide, code of conduct and more. | Alliander | |
Repository containing the official IEC-61850-6 SCL XSD Supported Documents | RTE | |
Core components | RTE | |
Validation Service to validate SCL File | Alliander | |
CoMPAS Siemens Sitipe Service | Alliander | |
CoMPAS for Siemens SITIPE; This allow to SITIPE 61850 privates in IEC61850 SCL retrieved from the SITIPE database. | Alliander | |
elemental UI components from compas-open-scd for SCL documents' operations | Alliander | |
.allstar (to be investigated) | CoMPAS Allstar Configuration Repository | Alliander |
virtual-template-ied (to be investigated) | IED generation menu plugin for CoMPAS Open SCD (next) | Alliander |
Repository hosting the root of GitHub Pages. | Alliander | |
| Alliander | |
Dev oriented repository to showcase the use of web components using Lit across several different frameworks | Alliander |
Bearingpoint will take over the CoMPAS official plug-ins maintenance and take the code ownership.
RTE team will change, maintenace will keep going
8-Shared maintenance
How to we share the dependabot workload to stay current and secure?
Suggestion: once a month do a dependabot round and test a new release.
Criticals need to monitored and fixed sooner
David will contact the TransnetBW to see what their policy is.
9-Agenda topics
Do we want to maintain the CoMPAS TSC’s during the summer?
Cancel the 9th of July for a holiday break, other TSC’s can continue.
CoMPAS developer allignment updated.
@Jean-Etienne LEMAIRE will ask who can join from the RTE side
10-Open discussion
OpenSCD organization restructure status update