Skip to content

Individuals

One of the five consortium members is a person rather than a company — a maintainer who carries the project in a personal capacity, alongside the four organisations. The libraries themselves go back to their original author, Andreas Linde.

Kai Takac

Kai Takac

Maintainer

Software engineer working in the energy sector from Linz, Upper Austria. Member of the enbility group since 2025.

Original author · no longer an active consortium member

Andreas Linde

Andreas Linde

Original author of ship-go, spine-go and eebus-go

Wrote ship-go, spine-go and eebus-go and released them publicly in December 2022, after which the libraries went from a personal project to the reference EEBUS implementation in Go — picked up by evcc within weeks.

Carried the project single-handedly through its first three years, including the protocol analysis published in July 2025 that set out what the specification documents actually permit, measured against what devices do in the field. Everything the consortium maintains today builds on that work.

Why individuals matter here

A consortium of companies can fund and staff a project, but maintainers who work on the code in a personal capacity keep it independent of any one employer's priorities. They are full members with the same vote as a company, not contractors.

The route stays open. Contributors are promoted to committer and then maintainer of the repositories they work on, by simple-majority vote of the existing maintainers. Joining the group itself is a separate step: the Steering Committee admits new members by simple majority, after a commitment declaration and at least one meaningful contribution in code or operations.

How maintainers and members are appointed

Other partners

All partners