geodes-sms/lowkey

A low-level and transparent framework for collaborative modeling.

lowkey's Issues

Design a safer and more efficient messaging

The current messaging is suboptimal in some aspects.

• The prevention of double updates is at the Client side which is unsafe.
• When broadcasting messages, the Server should identify the original sender and not bother it with a message it was the originator of. Currently, Clients recognize such messages and throw them away.

Identify three-four model editors to integrate with for demonstration purposes

Some candidates below.

Tool	Pros	Risks
WebGME	web-based; prototypical inheritance; REST API; well-maintained; publication potential	technological heterogeneity (js)
MetaEdit+	top industry-scale language workbench with strong academic ties	requires maturity from our framework before we can propose to work with them
Meriem's CD Editor	in-house; advanced recommendation mechanisms are being developed; allows demonstrating EMF integration	no support can be expected due to this being a one-man project
metaDepth or Melanee	bona-fide multi-level modeling frameworks; the MLM framework of metaDepth (possibly also Melanee?) follows the OCA principles which is complementary to lowkey's; publication potential	they bring their own MLM choices: this could necessitate revising many of our choices around the Physical metamodel; unclear if they are maintained

Allow Clients to be turned on and off dynamically

This would require an API method that allows the orchestrator to turn on/off receiving and producing messages. This is useful in cases such as the AToMPM CSWorker/ASWorker architecture.

Design and implement a safe and efficient garbage collection mechanism

Assess GitHub Actions as an alternative to Travis-CI

Set up the SonarCloud integration with GitHub Actions

Set up CI/CD with Travis under the new organization

The migration broke the link with Travis-CI. As a consequence, unit tests and QA aren't executed upon commits.