May 5th TSC meeting report #tsc-meeting-report
Our eighth monthly TSC meeting was 5th May. You can find the presentation in files section of compas-tsc mailing list.
Here are the conclusions / decisions taken during this meeting.
List of attendees :
1-Review of previous meeting report
Proposal of report is accepted.
2-Review of actions
From January Meeting:
1-Validation of technical choices (discussion on slack, PR?)(Action for Rabah)
=> In progress,some points to discuss
From February meeting:
-Add scrum US method : Action for RTE => To do
3-See how not to use issue for US : Action RTE => To do
From previous meeting:
4-4-Among GE TSC members, ask who would like to receive License scan report: Action for Frédéric
=> Add Jean-François to mailing list => To do but problem because only member of TSC can be added => TSC members from GE stay the same.
Is there anyone else on the GE side?
5-Try to integrate API from Alliander as a plugin in OpenSCD => To do
6-Share COMPAS and OPENSCD roadmap and architecture during next TSC meetings => Dedicated meeting scheduled for May 5 => Done
From previous meeting:
7 - Action for GE: see if Jean Francois could be TSC member instead of a colleague => See previous point
8 - Action for RTE: see if using quarkus is possible. What could be the impacts?=> In progress
9 - Action for Frédéric : Add reviewers to Maintainers file => Done.
10 - Action for Rob: planned a community call extended on PR => To do during next community call.
3-Speak about March LFEnergy Survey
Survey was completed.
Concerning the last question, Sander is seeing with his communication department if he could be main contact for COMPAS communication.
4-LF Energy Foundation Technical Project Lifecycle – Check incubation criteria and actions to do
Action for Frédéric: Work on the files according to TAC criteria (rename MAINTAINERS to COMMITERS; create a GOVERNANCE file with link to the COMPAS Technical Charter; launch a Release file with a first release planned in September, and create a SUPPORT file with links to mailing lists, slack…) => To do
5- IEC XSD legal issue and the solution
According to legal departments from Alliander and RTE, it seems be possible to use XSD file in Github but it is necessary to be clear that this file is not under CoMPAS License.
It is decided to create a public repository to put it in and add the legal informations.
We can too use a script from Jean François to verify if it is the latest version and download it if not.
A dedicated meeting must be organized to speak more in depth about our difficulties to converge.
-Branch settings across CoMPAS repositories are not the same. Needs to be consistent.
-How do we handle reviews of big Pull Requests? (Some are 100+ changed files)
These items was postponed to another meeting (for example the community call) due to lack of time.