Hack, eat, sleep, repeat: Our 2022-11 dev meeting was one big hackathon event where we joint forces to solve problems with the code. It was so intense, we even forgot to taka a photo. (We were some 15 very enthusiastic hackers.) There are a couple important decisions to be communicated:
The next release of solph (v0.5) is in feature freeze. We will just update the documentation and finalise making arguments explicit and release afterwards.
Multi-period optimisation and renaming Transformer to Converter will follow with v0.5.1 with a merge to mainline solph right after v0.5.0. The changed name will have a wrapper so it is not API breaking.
Stephan Günther, Caroline Möller, and Patrik Schönfeldt form the new board of the oemof association.
Also, today was an important day for the oemof association. After everything was agreed on by the general assembly on November 10th, 2022, the protocol as well as the statute were notarised and sent to the register of associations. By chance we also received the final documents needed to apply for our non-profit status. So, now we have to wait until things are processed until the association gets it final legal status.
We finally opened registration for the omof developer meeting 2022. As suggested last year’s dev meeting, it will take place at Magdeburg University from the 09th to the 11th of November. One focus will definitely be on the next release of solph, but the agenda is kept flexible to meet the demands of the participants and will continuously developed at https://github.com/oemof/oemof/wiki/Meeting-2022.11.
Developer meetings are no closed shop but a great opportunity for a first contact for those who are considering to collaborate. In fact, it’s rather common that people join a developer before actively contributing. With this regard, the upcoming meeting is a particular good opportunity as there are a couple of freshly developed features also new to long-term developers.
Hereby we invite you to the general assembly (GA) of the oemof association. It will be held at the University of Magdeburg at 13:30 on the 10th of November 2022, as a part of this year’s developer meeting (9th to 11th of November). As we elect our representatives for one year, elections are the crucial point of this GA. To get used to the standard procedure, the agenda includes all typical points even if i.e. the financial report will be really short. If you have further points to discuss, please send an email to firstname.lastname@example.org or post them at https://github.com/oemof/oemof/issues/105.
We want to thank all participants of this year’s oemof spring meeting. It’s always a joy to have a few days reserved for concentrated discussions around the things you create and investigate using oemof. Some of you already provided their slides, these are now available in the collection of oemof publications.
This year’s spring meeting wasn’t only the biggest in-person meeting but also probably the most international one. It was located almost in sight of the Danish/German border. Some of the almost 40 participants arrived from Italy and Spain just for the meeting. Not to speak about contributions from people who stay in Germany for longer. This confirmed us in our decision to also keep the organisation of the oemof association in English. (Side node: It was in the middle of the association’s general assembly that we realised that the about ten persons joining that particular session were able to understand German.)
We invite you to a general assembly (GA) of the oemof association that will take place on the 19th of May as part of the oemof user/dev meeting in Flensburg. The assembly will be located at the meetings venue (European University Flensburg Building VIL1, Auf dem Campus 1, Flensburg) and start at 14:00.
Opening and welcome
Agreement on the agenda
Acceptance of the minutes of the last GA
Bylaws and membership fee regulations
The changed statute can be found at GitHub (binding German version, informative English translation). The changes are marginal and probably required by the German authorities. We decided to let the GA decide before the authorities file a formal complaint. Formally, the decision will be on the full (changed) statute rather than the changes, as it makes live easier to have everything in one protocol. According to our statute, all members can already vote on the changed statute. To do so, you can leave a review (approve/object) at the PR at GitHub. Alternatively, you can write an email to email@example.com to get instructions how to vote by (paper) mail.
We are about to move oemof.org to a new web space. To allow for a smooth transition, the new page (this one) is already on-line. So, hopefully, the posts announcing the transitions here and there (at the old site) will be the mayor signs of the relocations. But there is more:
Improved control: By doing more on our own, we have more flexibility on what we do. Several times already, we came to the point that we wanted to implement something for the page but were not able to because of our web page plan. This will be different from now on.
Improved data protection: The first thing we use our newly gained power for, is sniping of the trail of your data to third parties. Also, hosting has moved from the US to Europe.
More to come: This is not planned to be a relaunch but a smooth transition. Honestly, I would not even write this if I did not have to test the post notification mailer.
The next oemof developer meeting will be held from Wednesday the 2nd to Friday the 4th of December 2020. It will be an online event full of virtual workshops and discussions about technical and organisational aspects of oemof. One topic will be the current status of the “oemof foundation” (working title), which is planned be incorporated at the next in-person meeting.
Anyone who is interested is cordially invited to participate and to contribute topics. All topics including additional information will be collected at the oemof organisation wiki page for the 2020 December Meeting. If you want to register, please contact us in the according ticket at GitHub. You can also suggest additional topics at the same place, we will continue shaping the agenda based on your input at least until the 23rd of November.
After oemof v0.3.2, we decided to make oemof’s structure more clear: Both, the framework (including e.g. TESPy) and the Package for energy system optimisation (using solph) were called the same – oemof. With the release of v0.4.0, there are now split packages for oemof.solph, oemof.network, and oemof.tools.
With v0.3, the API of the GenericStorage has changed. Due to the open structure of solph, the old parameter names were still accepted, but practically ignored. Therefore users may not notice that a default value is used instead of the value they wanted. Especially after an update from v0.2.x to v0.3.0, code often still runs but produces different results. With the new v0.3.1 release, an error is raised when legacy parameter names are used. We work on a structure to avoid such problems in the future. To update, just: