20230816 OpenSCD Additional refinement

Owned by ben van 't ende
Aug 31, 2023
1 min read

Participants: Ben, Sander, Pascal, Tamás, Jakob V. (partly)

Open Source & Energy predictions (question by Dan Brown)


  • We are planning to produce a series of articles to be contributed to media and/or blog posts for LFEnergy.org focused on current technology trends in the energy sector. We would appreciate input from the community that can be used to produce these. The pieces will be round ups of this input, positioning you all as experts on the energy transition. Please take a few minutes to complete this form https://docs.google.com/forms/d/e/1FAIpQLSdZX0FNrJlZH4_oFymTYxli-xWtNX9xO24ddXMlfLONF-w1fA/viewform?usp=sf_link[]. All the questions are optional, so you can answer as many or as few as you like. I would request that feedback be submitted by August 18.


NPM
On NPM is version has version 0.0.2; The source code is not coming from the OpenSCD-core repository but a fork. @openscd/open-scd-core - npm (npmjs.com)
 Pascal shows release-please

https://npm.io/package/@openscd/open-scd-core is a different package than https://www.npmjs.com/package/@openscd/open-scd-core

To use release please, it is needed to conform to the convention: https://www.conventionalcommits.org/en/v1.0.0/ [A specification for adding human and machine-readable meaning to commit messages]

Mixin is a different discussion. 

The 'OpenSCD Next' branch gives an outlook on what it could look like.

There are 2 possible solutions:
    Big bang: move everything to OpenSCD-core
    Gradual move function to a modular monolith

Tamás suggests to keep OpenSCD and gradually move into the OpenSCD-core approach.