yeah, so my understanding is…
this header file comes (directly) from the haken firmware repo, which is private (understandably) - its then copied (now) into the release.
that repo will not be made public, so it comes does to how do you share one file.
what Ive suggested to Christophe (to request to Lippold) is.
create a new github public repo (Haken API), containing just this file (and a license !).
then Lippold can include this public repo into the firmware repo via GitHub submodule.
this is what I do with these kind of interfaces, as it creates a nice separation for the public interface.
that said, I completely understand why it was done as-is, there’s going to be very few of us that use this header file, so doesn’t make a lot of sense to spend a lot of time on this.
and if you are not familiar with things like GitHub submodules it might seem like quite a faff for a couple of devs. ofc, those of us that use it, know its very quick/easy to do.
ofc, there are other options, e.g. using GitHub workflows to publish the api to a specific location or another repo.
all that said, Ive not spoken to Lippold about this header file.
so its possible, there may be non-logistical/technical reasons to not do the above.
e.g. intellectual property, control/support of 3rd party devs etc.
anyway, lots of options, hopefully we will be sorted soon
my main concern is the license side at the moment, as I do stuff under GPL.