You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Date

Attendees

Discussion items

TimeItemWhoNotes
1minChange in name of the project: Welcome OpenSTEFFrank
10minDetermine how to effectuate the name change throughout the repo’s
Do we want to change openstf to openstef everywhere? 
FrankFrank: No concerns raised for chaning name of python package. Let's implement this a.s.a.p.
10minInstruction on Developer Certificate of Origin (DCO)JonasSee: Contribution and Compliance Guidelines for LF Energy Foundation hosted projects
5minPlan session on Roadmaps 2022
Sharing roadmaps of Alliander, RTE, Sogno
Frank

Florian: Please pick this up with Marcos

Maxime: 2022 ambition is to use OpenSTEF formain forecasting at RTE and add features along the way

1minBiweekly in-depth refinementJan MaartenWednesdays 15:00 (Amsterdam time), odd weeks.
If you work on features you want to add to OpenSTEF or get input on ideas, this is the moment to discuss.

Action items

  • Frank: Change openstf to openstef everywhere (inlcuding python package)
  • Jonas: Make sure Arjan checks Technical Charter (with shortened mission) → bring into next TSC meeting for approval by TSC (Link by John: )
  • Frank: check up on logo-brief and website description (see also Project Intake TODO list)
  • Jonas: add DCO instruction to the CONTRIBUTING.md so new people easily get the hang of this (nice if vscode/pycharm are also included)
  • Frank: Check-up with Marcos on Sogno roadmap; 
  • Jan Maarten: add OpenSTEF refinements to OpenSTEF community agenda (you can ask Jonas for help)
  • Frank: Skip next TSC meeting. 
  • No labels