20230605 OpenSCD

Daniel: Still writing tests for later-binding subscriber plugin (and fighting with CI) and looking at a few SCL functions with Jakob. 

Pascal: Had discussion with Jakob. About current mixins(?). Moved to OpenSCD class. Will fox a alot of issues. A story will be created to remove the functionality from the mixins and move them into the OpenSCD class. It won't make sense to have OpenSCD without Editing and Plugin functionality. Also, would like to add an Angular example. Open question: I found out that the OpenSCD GitHub organization is growing fast with repositories for new components and plugins. Would it be nice to group some components into a monorepo?

Christian: Was on vacation last week. Worked on oscd-tree-explorer component before the vacation. Made great strides in performance. Currently considering a rename to oscd-tree-table, but Daniel is against that because he prefers style over substance ;-P. Continuing to improve on it.

Jakob B.: Internal discussions about how OMICRON can dedicate more resources to the project on an ongoing basis

Juan: Looking into external sonarcloud; Juan like to contribute to an improved filtered list. Guide newcomers on components. Juan will create a repository with example code vue.js integration with OpenSCD-core.

Sander: Elia is looking into CoMPAS/OpenSCD and wanted to test 61850-90-4
Quick documentation review of Sprinteins plug-ins. Recommends Daniel's readme on Goose: danyill/oscd-subscriber-later-binding: IEC 61850 subscription for GOOSE and SV in OpenSCD (github.com)

Steffen: Clear what we want from components. 

Tamas: Has a full week!

Tim: Talk to Tamas on PDF plugin. Two different PDF's. Needs preview. Working on Telegram

Rebecca: styling plugins. 

Ben: Had a very inspiring weekend at the LFEnergy event in Paris on the weekend. Suggested using pad.riseup.net for collaborative meeting protocols, hopes we could take 1-2 minutes after the close of the meeting to perfect those notes.

Refinement

What does a maintainer do? Responsibilities. 
Current expectation of Pascal: Reviewer should only check softwarecode
Chrision: Maintainer sets the review rules. Mainainter is reponsible for the code-quality.

Concern: interchangeability of a reviewer

Possible solutions:
Guidelines per repository
General guidelines

Pascal will look into a guideline for this specific repository
Next week: get back to this topic next week.

Pascal: A lot of repositories popping up. Move (a combination of) Components into a single repository. Some conciderabtion to merge them into a repository:
    Maintainer
    Funcions allign

Function: oscd-form-elements/foundation.ts at main · openscd/oscd-form-elements (github.com)

https://github.com/openscd/oscd-form-elements/blob/main/src/lib/foundation.ts#L8 

Action: No action for now

Tamas:
Name suggestions for the depupe plug-in:

  • Relink      
  • Relinker      
  • Type Relink    
  • Refactor     
  • Type Refactor 
  • Optimiser    
  • Type Optimiser  
  • Relink Duplicates
  • Relink Redundancies  
  • Optimise Redundancies
  • Reducer
  • Type Switcher
  • Type combiner
  • Type uniter
  • Type replacer
  • Uniter
  • Condenser
  • concentrator
  • abstractor
  • digester
  • type-bunch-together
  • unifyer