Date   

Next TSC meeting

TILLOY Anne
 

Hi everybody !

 

We have a planned TSC meeting on the 19th of August. I know that many of you are in holiday, so I think that I am going to cancel this event. The next one will be in September, the 16th.

 

Powsybl project has its TAC annual review on the 31st of August. I am going to follow these requirements: Technical Project Lifecycle - LF Energy - LF Energy

All the other projects of the LFE will be present and could give advices, so maybe it will be interested to have one of you with me for more technical questions. Just let me know about it !

 

Thanks a lot and see you soon.

 

Best regards,

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Event: TSC meeting - 08/19/2021 #cal-reminder

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

Reminder: TSC meeting

When:
08/19/2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Cancelled Event: TSC meeting - Thursday, July 22, 2021 #cal-cancelled

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

Cancelled: TSC meeting

This event has been cancelled.

When:
Thursday, July 22, 2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Cancelled Event: TSC meeting - Thursday, July 22, 2021 #cal-cancelled

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

Cancelled: TSC meeting

This event has been cancelled.

When:
Thursday, July 22, 2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: TILLOY Anne

Description:
Please register one for all meetings here:
https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0
Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.
Regards,

Anne.



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Event: TSC meeting - 07/22/2021 #cal-reminder

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

Reminder: TSC meeting

When:
07/22/2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Happening Now: TSC meeting - 06/24/2021 #cal-notice

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

TSC meeting

When:
06/24/2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Next TSC meeting

TILLOY Anne
 

Hi everybody,

Our next TSC meeting will be on June 24th.

 

For this public meeting, it would be great if we follow these items:

 

Release of powsybl-core (4.3.0-alpha-1) since May 25th, please refer to the release notes to know what the release contains: Release v4.3.0-alpha-1 · powsybl/powsybl-core (github.com)

 

This intermediate release contains the new security analysis API, including the new feature that monitors the buses and branches results (voltage, angle, active and reactive powers) for pre-contingency state and for post-contingency states. We also support contingency on three windings transformers with this new version, and new limit violation types. OpenLoadFlow has been released too.

 

To be compliant with the European Merging Function, we can now maintain the power factor constant when loads are scaled. A tutorial is in progress to show how to implement the EMF with Powsybl.

 

And as usual, some bus fixes and other quality evolutions.

 

Next release of powsybl-core (4.3.0) expected on July 7th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

 

New extension to model remote reactive power control for generators (breaking change) ;

A first version of the CGMES importer from a unique EQ file : it is a beta feature mainly used just after SCADA system ;

The possibility to export flows at switches in SV file ;

Still WIP:

- The new sensitivity API ;

- PSSE updated export ;

- Extensions for measurements compliant ;

- Support of CGMES 3.0 ;

- UCTE: use double instead of float. The extension MergedXNode will change too.

 

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR every month. Having a clear, detailed and updated roadmap is key for external contributions.

 

Technical discussion

Sylvain, Florian and Mathilde are working on a schematic vision of the network to provide SVGs. The SVGs could be integrated in an interface such GridStudy (gridsuite.org) or created from a python script by pypowsybl users (PyPowSyBl’s user documentation — pypowsybl documentation). They imagine that there is a JavaScript component that can be shared between these two applications. Sylvain is going to share some slides before our meeting.

 

Thanks for joining the TSC. Remember that meetings are scheduled here:

powsybl-tsc@... | Calendar

 

See you soon !

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Event: TSC meeting - 05/27/2021 #cal-notice

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

TSC meeting

When:
05/27/2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

View Event

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Re: Next TSC meeting

TILLOY Anne
 

Some of you don’t have any invitation for tomorrow (yes, indeed it is on the 27th of May). All our meetings are publicly in this calendar:

 

powsybl-tsc@... | Calendar

 

I have updated the meetings, so you have been notified. In the notification, you have an “invite.ics” that you can add to your outlook calendar or add it to all TSC members as I did minutes ago.

 

Sorry for that… but our calendar must remain public.

 

Anne

 

De : TILLOY Anne
Envoyé : mercredi 26 mai 2021 12:07
À : 'powsybl-tsc@...' <powsybl-tsc@...>
Objet : Next TSC meeting

 

Hi everybody,

Our next TSC meeting will be on May 28th.

 

For this public meeting, it would be great if we follow these items:

 

Release of powsybl-core (4.2.0) since May 25th, please refer to the release notes to know what the release will contain: Release v4.2.0 · powsybl/powsybl-core (github.com)

 

Main features or bug fixes:

- CGMES import: consider transformer at boundary ;

- CGMES export: export flows for branches and three windings transformers ;

- CGMES: support of TYNDP CGM files with workarounds ;

- Make import of control areas optional ;

- CGMES: import of Xnode HVDC type for balances adjustment ;

- IIDM: improve network notification performance ;

- IIDM: fix connect bug ;

- IIDM: allow bPerSection to be negative ;

- PSSE: start of support DC conversion ;

- Scalable: add new DanglingLine scalable with both convention supported ;

- LoadFlow: add synchronous and connected numbers to results ;

- LoadFlow: add new parameters dcUseTransformerRatio, countriesToBalance and connectedComponentMode ;

- Triplestore: Blazegraph has been removed ;

 

Next release of powsybl-core (4.3.0) expected on July 7th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

 

The new API of security analysis is ready, the implementations should adapt. WIP on OpenLoadFlow side. What about Dynawo? We plan to do an intermediate release for that breaking change.

 

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR before tomorrow. Having a clear, detailed and updated roadmap is key for external contributions.

 

Technical discussion

Free for the moment.

 

If you have subjects, do not hesitate to send it to me.

 

Thanks for joining the TSC.

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


TSC meeting

TILLOY Anne
 

Please register one for all meetings here:
Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.
Regards,
 
Anne.
 


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Updated Event: TSC meeting #cal-invite

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

TSC meeting

When:
Thursday, 27 May 2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels
Repeats: Every 4 weeks on Thursday

Organizer: Anne Tilloy anne.tilloy@...

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Next TSC meeting

TILLOY Anne
 

Hi everybody,

Our next TSC meeting will be on May 28th.

 

For this public meeting, it would be great if we follow these items:

 

Release of powsybl-core (4.2.0) since May 25th, please refer to the release notes to know what the release will contain: Release v4.2.0 · powsybl/powsybl-core (github.com)

 

Main features or bug fixes:

- CGMES import: consider transformer at boundary ;

- CGMES export: export flows for branches and three windings transformers ;

- CGMES: support of TYNDP CGM files with workarounds ;

- Make import of control areas optional ;

- CGMES: import of Xnode HVDC type for balances adjustment ;

- IIDM: improve network notification performance ;

- IIDM: fix connect bug ;

- IIDM: allow bPerSection to be negative ;

- PSSE: start of support DC conversion ;

- Scalable: add new DanglingLine scalable with both convention supported ;

- LoadFlow: add synchronous and connected numbers to results ;

- LoadFlow: add new parameters dcUseTransformerRatio, countriesToBalance and connectedComponentMode ;

- Triplestore: Blazegraph has been removed ;

 

Next release of powsybl-core (4.3.0) expected on July 7th, please refer to the draft release notes to know what the release will contain: Release v4.3.0 (expected date: 2021-07-07) · powsybl/powsybl-core (github.com)

 

The new API of security analysis is ready, the implementations should adapt. WIP on OpenLoadFlow side. What about Dynawo? We plan to do an intermediate release for that breaking change.

 

Roadmap

Roadmap update by annetill · Pull Request #24 · powsybl/.github

Please try to update the PR before tomorrow. Having a clear, detailed and updated roadmap is key for external contributions.

 

Technical discussion

Free for the moment.

 

If you have subjects, do not hesitate to send it to me.

 

Thanks for joining the TSC.

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


TSC meeting - Thu, 04/29/2021 #cal-notice

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

TSC meeting

When:
Thursday, 29 April 2021
1:00pm to 2:00pm
(GMT+02:00) Europe/Brussels

Organizer:
anne.tilloy@...

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


Re: Licence scanning

JAMGOTCHIAN Geoffroy
 
Edited

Not easy because we need protobuf compiler which is platform dependent, so it means powsybl-hpc would be painful to build.


Re: Licence scanning

BAGUE Mathieu
 

Hi,

I don't know if it's easily feasable, but generated source files should be in the target/generated-classes. If I remember well, we decided to commit it to reduce compilation time. Could it make sense to remove this file from the repo and generate it from the protobuf IDL file in the target directory?

Best,
Mathieu

Le mardi 27 avril 2021 à 07:50 -0700, JAMGOTCHIAN Geoffroy via lists.lfenergy.org a écrit :
EXPÉDITEUR EXTERNE: Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe à moins qu’ils ne proviennent d’un expéditeur fiable, ou que vous ayez l'assurance que le contenu provient d'une source sûre.

Hi,

For powsybl-hpc/computation-mpi/src/main/java/com/powsybl/computation/mpi/generated/Messages this is a generated file so maybe we should configure the scanner to exclude it. It does not make sense (or maybe is illegal?) to add a licence/authorship to a generated file.

For the preventive strategy, I would go for a Maven plugin instead because we can test it locally before pushing the code (same kind of check as checkstyle).
Indeed it will only check Java files but that is 99% of our files (powsybl cpp excluded)

Geoffroy


"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Re: Licence scanning

JAMGOTCHIAN Geoffroy
 

Hi,

For powsybl-hpc/computation-mpi/src/main/java/com/powsybl/computation/mpi/generated/Messages this is a generated file so maybe we should configure the scanner to exclude it. It does not make sense (or maybe is illegal?) to add a licence/authorship to a generated file.

For the preventive strategy, I would go for a Maven plugin instead because we can test it locally before pushing the code (same kind of check as checkstyle).
Indeed it will only check Java files but that is 99% of our files (powsybl cpp excluded)

Geoffroy


Licence scanning

TILLOY Anne
 

Hi TSC member,

 

Here are the results of the license scanning performed by the LFE: https://lfscanning.org/reports/lfenergy/powsybl-2021-04-20-ed46eeb7-b4a3-4f66-8266-e757e3fb0c46.xlsx

 

We miss some license headers and sometimes the author is missing too. I have fixed the powsybl-core java files, using the year of the first commit for the copyright. I am going to fix also the tutorials and the powsybl-open-loadflow repository. It remains the underlying files. Please open a PR on each repository with the changes requested. Note that this email only focus on Java source file.

 

Note that a preventive strategy could be to use the check REUSE https://github.com/marketplace/actions/reuse-compliance-check Who is volunteer to help on that subject if you all agree?

 

Thanks a lot.

 

Anne.

 

powsybl-gse/gse-network-map/src/main/test/com/powsybl/gse/map/DataTest

java

powsybl-core/loadflow/loadflow-api/src/test/java/com/powsybl/loadflow/json/JsonLoadFlowParametersTest

java

powsybl-core/iidm/iidm-impl/src/test/java/com/powsybl/iidm/network/impl/TapChangerAttributeTest

java

powsybl-core/security-analysis-api/src/test/java/com/powsybl/security/SecurityAnalysisResultBuilderTest

java

powsybl-core/security-analysis-api/src/test/java/com/powsybl/security/json/JsonSecurityAnalysisParametersTest

java

powsybl-core/cgmes/cgmes-model/src/test/java/com/powsybl/cgmes/model/test/FakeCgmesModel

java

powsybl-core/triple-store/triple-store-test/src/test/java/com/powsybl/triplestore/test/QueryCatalogTest

java

powsybl-core/entsoe-util/src/test/java/com/powsybl/entsoe/util/MergedXnodeXmlSerializerTest

java

powsybl-core/entsoe-util/src/test/java/com/powsybl/entsoe/util/EntsoeAreaXmlSerializerTest

java

powsybl-core/entsoe-util/src/test/java/com/powsybl/entsoe/util/XnodeXmlSerializerTest

java

powsybl-core/math/src/test/java/com/powsybl/math/graph/GraphUtilTest

java

powsybl-core/math/src/main/java/com/powsybl/math/matrix/package-info

java

powsybl-core/computation/src/test/java/com/powsybl/computation/CompletableFutureTaskTest

java

powsybl-core/time-series/time-series-api/src/test/java/com/powsybl/timeseries/ReadOnlyTimeSeriesStoreAggregatorTest

java

powsybl-core/action/action-dsl/src/main/java/com/powsybl/action/dsl/RuleType

java

powsybl-hpc/computation-mpi/src/main/java/com/powsybl/computation/mpi/generated/Messages

java

powsybl-network-store/network-store-iidm-impl/src/main/java/com/powsybl/network/store/iidm/impl/VoltageLevelUtil

java

powsybl-network-store/network-store-iidm-impl/src/main/java/com/powsybl/network/store/iidm/impl/SubstationUtil

java

powsybl-network-store/network-store-server/src/main/java/com/powsybl/network/store/server/NetworkStoreApplication

java

powsybl-tutorials/loadflow/initial/src/main/java/powsybl/tutorials/loadflow/LoadFlowTutorial

java

powsybl-tutorials/sensitivity/initial/src/main/java/powsybl/tutorials/sensitivity/SensitivityTutorial

java

powsybl-open-loadflow/src/test/java/com/powsybl/openloadflow/network/NodeBreakerNetworkFactory

java

powsybl-afs/afs-spring-server/src/test/java/com/powsybl/afs/server/AppDataWrapperTest

java

powsybl-afs/afs-core/src/main/java/com/powsybl/afs/package-info

java

 

 

logo

Anne TILLOY
PES/DSIT/DDL
Immeuble window - 7c place du dome
92800 Paris la defense
T+33 (0)1 41 02 15 32 – P+33 (0)6 46 16 22 39

 

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Next TSC meeting

TILLOY Anne
 

Hi everybody,

Our next TSC meeting will be on April 29th.

 

For this public meeting, it would be great if we follow these items:

 

Release of powsybl-core (4.2.0) expected on May 20th, please refer to the release notes to know what the release will contain: Release v4.2.0 (expected date: 2021-05-20) · powsybl/powsybl-core (github.com)

 

Main features or bug fixes: please refer to the draft release notes.

 

We except a version 4.1.2 for bug fixes tomorrow. The bug concerns the JSON serialization of Line and TwoWindingsTransformer contingencies.

 

Roadmap

For this TSC, I suggest to focus our roadmap on how growing our community (users + contributors)?

- Vattenfall for grid capacity estimation for DSO and TSO via PTDFs and LFs ; the methodology has to be defined and harmonized ; see slides attached.

- ACER: via pypowsybl, ACER is firstly interested in :

1) Calculation of zone-to-zone PTDFs for AC borders

2) Calculation of zone-to-zone PTDFs for DC borders/DC lines

3) Modification and creation of bidding-zones (e.g. shuffling nodes, e.g. for DK1)

- Control Room of the Future (Control Room of the Future - TenneT) : it is a working group inside the LFE. Powsybl could be used here.

- Other?

 

Technical discussion

I think that you all know that we pass the CII best Practices badge (BadgeApp (coreinfrastructure.org)) with 185%!

Key points must be underlined after reaching the first 100%:

- Documentation, especially in the web-site is a central subject ;

- Release candidates should be used for major release ;

- We have to focus on vulnerabilities (of the project itself and of its dependencies) ;

- Slack and official mailing lists must be used in priority ;

- Some committers must have a secure development knowledge (Secure Software Development Fundamentals Professional Certificate | edX)  + OWASP Top 10 ;

- Jars must be signed ;

- Dynamic code analysis: using Valgrind for the C++ analysis should become automatic + It is SUGGESTED that the project use a configuration for at least some dynamic analysis (such as testing or fuzzing) which enables many assertions. In many cases these assertions should not be enabled in production builds.

Key points after reaching the last 85%:

- The project MUST document what the user can and cannot expect in terms of security from the software produced by the project ;

- The project MUST automatically enforce its selected coding style(s) if there is at least one FLOSS tool that can do so in the selected language(s) ;

- TODO: It is SUGGESTED that in the version control system, each important version tag (a tag that is part of a major release, minor release, or fixes publicly noted vulnerabilities) be cryptographically signed and verifiable as described in signed_releases ;

- Other security issues: the project MUST provide an assurance case that justifies why its security requirements are met. The assurance case MUST include: a description of the threat model, clear identification of trust boundaries, an argument that secure design principles have been applied, and an argument that common implementation security weaknesses have been countered : best-practices-badge/security.md at main · coreinfrastructure/best-practices-badge (github.com)

- Gold: double authentication in Github, not via SMS.

 

If you have subjects, do not hesitate to send it to me.

 

Thanks for joining the TSC.

 

Anne

 

 

 

logo

Anne TILLOY
PES/DSIT/DDL
Immeuble window - 7c place du dome
92800 Paris la defense
T+33 (0)1 41 02 15 32 – P+33 (0)6 46 16 22 39

 

 



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."


Updated Event: TSC meeting - Thursday, 29 April 2021 #cal-invite

powsybl-tsc@lists.lfenergy.org Calendar <noreply@...>
 

TSC meeting

When:
Thursday, 29 April 2021
1:00pm to 2:00pm
(UTC+02:00) Europe/Brussels

Organizer: Anne Tilloy anne.tilloy@...

Description:
Please register one for all meetings here:

https://us02web.zoom.us/meeting/register/tZ0pdO6hqDgpGNxvNPvgTyzrxTO3xK0psIc0

Note for members: the Technical Steering Committee (TSC) is composed of voting members elected by the active committers as described in the project’s Technical Charter. The TSC is responsible for the technical direction of the Powsybl organization. Fill free to give our point of view for PowSyBl library, respecting our code of conduct. Remember that if we need to vote, the quorum is required! And if you cannot make it, just tell me in advance.

Regards,

Anne.


LFE Spring Summit

TILLOY Anne
 

Hi PowSyBl Community!

 

LF Energy’s Spring Summit is happening on April 14th.

 

Although we are not presenting this time, there is a great program including many topics connected to our works. Please take a look at the schedule (see in particular the power system operations and microservices tracks): https://events.linuxfoundation.org/lf-energy-spring-summit/program/schedule/

 

Here is the registration link: https://events.linuxfoundation.org/lf-energy-spring-summit/register/

 

I look forward to meeting you there,

 

Anne



"Ce message est destiné exclusivement aux personnes ou entités auxquelles il est adressé et peut contenir des informations privilégiées ou confidentielles. Si vous avez reçu ce document par erreur, merci de nous l'indiquer par retour, de ne pas le transmettre et de procéder à sa destruction.

This message is solely intended for the use of the individual or entity to which it is addressed and may contain information that is privileged or confidential. If you have received this communication by error, please notify us immediately by electronic mail, do not disclose it and delete the original message."

81 - 100 of 158