Hi TSC members,

This is a reminder that to ensure transparency for everyone, anyone creating a new repository in the powsybl organization should:

• submit a poll here (on powsybl-tsc) before creating it to make certain everyone in the TSC is aware and consents to the creation of the repository
• update the MAINTAINERS file in the .github repository
• send a message on powsybl-announce indicating the creation of the repository, its name and a small description of which purpose it serves

If you agree with this steps and to apply them in this situation, please vote Yes to this poll. If you don't, vote No and develop your point of view as answer.

Thank you and have a good day,
Miora Ralambotiana

And also we should vote for any maven module, class, package and variable naming, right?

This is mainly to prevent TSC members (people responsible of the technical direction of powsybl) ignoring what the point is of some repositories - a situation that can happen when repositories are created during  night with no warning. Since we are only 8 members, if we agree that we need the majority to have consent, it means 4 votes which is not so much... If in the future we are more and/or it takes too much time to validate a change, we can rethink that, for now I don't think the constraint is very significant. It really doesn't need to be formal, it's just to keep TSC members informed with a minimum delay.
Updating MAINTAINERS file and sending an information email is really just to keep transparency with powsybl's contributors and users.

I think we can also create a page on the website to describe, for each repository, which features it offers. With the multiplication of the repositories, we need to have somewhere a clear picture of what modules exist, and maybe the dependency between the modules. I will try to create this page.
@Geoffroy: could you complete this new page to describe/fix the description of the new repositories?

I created a PR in the documentation, to add a technical documentation section, a micro-services architecture  diagram (and repo mapping) and a short description of each of the micro-service.

https://github.com/powsybl/powsybl.github.io/pull/105

Could you please review this PR?

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