Open sashko opened 5 years ago
@rkollataj, @dmiespdx, @pragma1ce, could you please clarify whether anyone maintaining this project or is it dead and should not be considered? Thank you.
JLR is working actively on it. Other OEMs have been putting in work as well. Please note that we tend to focus on different areas of improvement on the project, depending on what we use it for internally.
VSS is also used by Visteon Phoenix (https://developer.visteon.com/phoenix/) as its vehicle signal API, as well as by the W3C VISS standard.
Although development is quite organic (== unorganized) at this point, it does move forward.
Great, thanks for replying back. We'll try to contribute, but please do not ignore PRs.
Will try. There is one open right now that needs rebasing. I just pinged Daniel about that.
@magnusfeuer, good to hear from you.
VSS is also used by Visteon Phoenix (https://developer.visteon.com/phoenix/) as its vehicle signal API, as well as by the W3C VISS standard.
Yes for sure that is the case. And I could provide even more information on the usage of VSS since I participate in the W3C work on version 2 of VISS. But note that this question is in the VSI repository.
Let me know if I should exchange the VSI maintainer from @dmiespdx to something else, and also if you prefer that I (as GENIVI Development Lead) monitor this repository and give some maintenance/merging assistance when PRs go unanswered.
The shared memory heap is great, I'm glad to see the project will move on. there is few similar open source project on the internet.
There should be separate
include
folder, so it's clear which header should be used/deployed on the system for development.Meanwhile, could you please clarify which headers are development headers and should be packaged in
-dev
package.Thank you.