Topics

Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse

TILLOY Anne
 

Hi TSC members,

 

The previous poll enables to decide the people in charge for some repositories of the powsybl organization. The simple majority has be reached and the “yes” answer of the poll is approved. I am going to modify the CONTRIBUTING.md file in consequence. Before opening a new poll for the last repositories of the organization, I prefer to have a discussion with you as committers.

 

Remember that “in charge” means:

-          Best effort to review PR ;

-          Best effort to resolve issues ;

-          Building the releases with release notes and communication through LF Energy lists.

-          In case of impossibility, the person in charge has to ask the TSC through this list to find another committer to review the PR, resolve the issue or build the release.  

 

powsybl-hpc

Maybe Sylvain can review the Slurm part and Geoffroy can review the MPI part. Remember that all contributors can help doing this tasks, but only committers can merge.

Question: who should be in charge of the release ?

 

afs

I think that we have to create a separate repository for the application file system, called powsybl-afs with the modules afs, security-analysis-afs and the module afs-cassandra which is private for the moment.

Question: what do you suggest for the repository responsible ?

 

powsybl-gse

The reviews can be done by any contributor, but in general only Geoffroy merges the PR. The issues will be solved in general by Paul (https://github.com/powsybl/powsybl-gse/commits?author=pl-buiquang). For the powsybl-gse release, I think that we can propose to Paul that:

-          He prepares the PR with the two commits (prepare current release and prepare next release) ;

-          He prepares the release notes ;

-          Anne, Miora and Mathieu deal with the rest of the release publication ;

-          The powsybl-gse releases are synchronized with the powsybl-core releases.

 

Thanks a lot for your answers.

 

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."

LECLERC Sylvain
 

Hi Anne, all,

 

It would be OK for me to be in charge of powsybl-hpc releases.

 

It may be obvious, but please note that for “second level” repos, releases of “core” repos may require a release even though there is no evolution in that repo.

It means that there is still a need for coordination between the releases of repositories (release “trains” ?).

For instance when a project uses powsybl-core and powsybl-hpc, using a new release of powsybl-core will require to have a new release of powsybl-hpc which uses that same new release of powsybl-core.

 

Best regards,

Sylvain

 

De : powsybl-tsc@... [mailto:powsybl-tsc@...] De la part de TILLOY Anne via Lists.Lfenergy.Org
Envoyé : vendredi 8 novembre 2019 13:26
À : powsybl-tsc@...
Objet : [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse

 

Hi TSC members,

 

The previous poll enables to decide the people in charge for some repositories of the powsybl organization. The simple majority has be reached and the “yes” answer of the poll is approved. I am going to modify the CONTRIBUTING.md file in consequence. Before opening a new poll for the last repositories of the organization, I prefer to have a discussion with you as committers.

 

Remember that “in charge” means:

-          Best effort to review PR ;

-          Best effort to resolve issues ;

-          Building the releases with release notes and communication through LF Energy lists.

-          In case of impossibility, the person in charge has to ask the TSC through this list to find another committer to review the PR, resolve the issue or build the release.  

 

powsybl-hpc

Maybe Sylvain can review the Slurm part and Geoffroy can review the MPI part. Remember that all contributors can help doing this tasks, but only committers can merge.

Question: who should be in charge of the release ?

 

afs

I think that we have to create a separate repository for the application file system, called powsybl-afs with the modules afs, security-analysis-afs and the module afs-cassandra which is private for the moment.

Question: what do you suggest for the repository responsible ?

 

powsybl-gse

The reviews can be done by any contributor, but in general only Geoffroy merges the PR. The issues will be solved in general by Paul (https://github.com/powsybl/powsybl-gse/commits?author=pl-buiquang). For the powsybl-gse release, I think that we can propose to Paul that:

-          He prepares the PR with the two commits (prepare current release and prepare next release) ;

-          He prepares the release notes ;

-          Anne, Miora and Mathieu deal with the rest of the release publication ;

-          The powsybl-gse releases are synchronized with the powsybl-core releases.

 

Thanks a lot for your answers.

 

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."



"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."

RALAMBOTIANA Miora
 

Hi all,


@Sylvain: yes, there is a need for coordination for releases. I think a good solution would be to have a regular release for all repos (once every six weeks? or something like that?). Do you think there will be a need for release outside this window?


I still don't really know what to do about afs... Is there any evolution need on its repositories? Or are modifications/demands only bug fixes? Of the latter, are the demands critiqual? If they are not, we can decide to only do releases on these repo which would not be so much work i.e. only maintain them at the current state...


The bottleneck about powsybl-gse is mainly on the merging/reviews of PR. I don't really have any idea about how to handle this issue.


Miora


De : powsybl-tsc@... <powsybl-tsc@...> de la part de LECLERC Sylvain via Lists.Lfenergy.Org <sylvain.leclerc=rte-france.com@...>
Envoyé : vendredi 8 novembre 2019 13:50
À : powsybl-tsc@...
Objet : Re: [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse
 

Hi Anne, all,

 

It would be OK for me to be in charge of powsybl-hpc releases.

 

It may be obvious, but please note that for “second level” repos, releases of “core” repos may require a release even though there is no evolution in that repo.

It means that there is still a need for coordination between the releases of repositories (release “trains” ?).

For instance when a project uses powsybl-core and powsybl-hpc, using a new release of powsybl-core will require to have a new release of powsybl-hpc which uses that same new release of powsybl-core.

 

Best regards,

Sylvain

 

De : powsybl-tsc@... [mailto:powsybl-tsc@...] De la part de TILLOY Anne via Lists.Lfenergy.Org
Envoyé : vendredi 8 novembre 2019 13:26
À : powsybl-tsc@...
Objet : [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse

 

Hi TSC members,

 

The previous poll enables to decide the people in charge for some repositories of the powsybl organization. The simple majority has be reached and the “yes” answer of the poll is approved. I am going to modify the CONTRIBUTING.md file in consequence. Before opening a new poll for the last repositories of the organization, I prefer to have a discussion with you as committers.

 

Remember that “in charge” means:

-          Best effort to review PR ;

-          Best effort to resolve issues ;

-          Building the releases with release notes and communication through LF Energy lists.

-          In case of impossibility, the person in charge has to ask the TSC through this list to find another committer to review the PR, resolve the issue or build the release.  

 

powsybl-hpc

Maybe Sylvain can review the Slurm part and Geoffroy can review the MPI part. Remember that all contributors can help doing this tasks, but only committers can merge.

Question: who should be in charge of the release ?

 

afs

I think that we have to create a separate repository for the application file system, called powsybl-afs with the modules afs, security-analysis-afs and the module afs-cassandra which is private for the moment.

Question: what do you suggest for the repository responsible ?

 

powsybl-gse

The reviews can be done by any contributor, but in general only Geoffroy merges the PR. The issues will be solved in general by Paul (https://github.com/powsybl/powsybl-gse/commits?author=pl-buiquang). For the powsybl-gse release, I think that we can propose to Paul that:

-          He prepares the PR with the two commits (prepare current release and prepare next release) ;

-          He prepares the release notes ;

-          Anne, Miora and Mathieu deal with the rest of the release publication ;

-          The powsybl-gse releases are synchronized with the powsybl-core releases.

 

Thanks a lot for your answers.

 

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."



"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."


"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."

MURGEY Sebastien
 

Hi,

I have no remarks, and I agree with this proposition.

Regards,
Sébastien MURGEY

HARPER Jon
 

I agree


De : powsybl-tsc@... <powsybl-tsc@...> de la part de MURGEY Sebastien via Lists.Lfenergy.Org <sebastien.murgey=rte-france.com@...>
Envoyé : lundi 18 novembre 2019 14:41
À : powsybl-tsc@...
Objet : Re: [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse
 
Hi,

I have no remarks, and I agree with this proposition.

Regards,
Sébastien MURGEY


"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."

JAMGOTCHIAN Geoffroy
 

I also agree with the proposition.


Geoffroy


De : powsybl-tsc@... <powsybl-tsc@...> de la part de HARPER Jon via Lists.Lfenergy.Org <jon.harper=rte-france.com@...>
Envoyé : lundi 18 novembre 2019 14:49
À : powsybl-tsc@...
Objet : Re: [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse
 

I agree


De : powsybl-tsc@... <powsybl-tsc@...> de la part de MURGEY Sebastien via Lists.Lfenergy.Org <sebastien.murgey=rte-france.com@...>
Envoyé : lundi 18 novembre 2019 14:41
À : powsybl-tsc@...
Objet : Re: [powsybl-tsc] Open discussion about powsybl-hpc, powsybl-afs and powsybl-gse
 
Hi,

I have no remarks, and I agree with this proposition.

Regards,
Sébastien MURGEY


"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."


"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."

BAGUE Mathieu
 

Hi,

A summary, just to be sure I understand well the proposal:

powsybl-hpc
  • Review: Geoffroy (MPI), Sylvain (Slurm)
  • Release: Sylvain
powsybl-afs
  • Review: Paul, Geoffroy
  • Release: Paul (release notes), Mathieu/Miora (upload)
powsybl-gse
  • Review: Paul, Geoffroy
  • Release: Paul (release notes), Mathieu/Miora (upload)

About powsybl-afs and powsybl-gse repositories, the uploaders will be changed when a (new) commiter will uses these repositories.

Best,
Mathieu