search

eclipse-kuksa / kuksa.cloud

Kuksa Cloud repo
Eclipse Public License 2.0
17 stars 18 forks source link

Discussion on archiving kuksa.cloud repo #187

Open SebastianSchildt opened 11 months ago

SebastianSchildt commented 11 months ago

Hi KUKSA Community,

The KUKSA cloud repository hasn't seen activity for quite some time. The projects that have been combined in here still live on in the Eclipse IOT working group https://iot.eclipse.org and meanwhile there are much newer releases than the ones used here.

KUKSA itself is currently not doing any "cloud" side development. Therefore, I would suggest archiving this repository. If there are still useful components in here, they might be a fit for one of the Eclipse SDV Blueprints https://projects.eclipse.org/projects/automotive.sdv-blueprints.

Please comment on this issue so we can come to a conclusion on how to further proceed.

eriksven commented 11 months ago

Hello @SebastianSchildt

I (unfortunately) agree that we need to archive this repository. The last commit was a while ago, and we would require substantial work to keep the components up to date.

As mentioned by @SebastianSchildt , the focus of the development around the Eclipse Kuksa project has been shifted towards the Vehicle Abstraction Layer (VAL) and KUKSA.val Databroker. By the time we designed the current version of the Eclipse Kuksa.cloud the Databroker did not exist yet.

In addition, the App Store of the Kuksa.cloud requires in the vehicle as a counterpart the application runtime from Eclipse Kuksa.InVehicle repository. In the meantime, we have already archived this repository. Instead, with Eclipse Leda, there is another in-vehicle environment that deploys the KUKSA Databroker and uses Eclipse Kanto for Container Management.

Besides the maintenance aspect, the integration of the Databroker and adapting to another In-Vehicle runtime would require substantial changes to the overall architecture of the Eclipse Kuksa.Cloud too.

I do not see a component that we need to move to another repository, e.g., towards Eclipse SDV Blueprints. However, there is the option to consume components from the Eclipse Kuksa.Cloud later and contribute an updated version somewhere else if required.

erikbosch commented 10 months ago

I have not heard anyone mentioning any interest in kuksa.cloud for a long time, so I have no objection if it gets archived.

bs-jokri commented 10 months ago

+1 also from my side. No active contributions seen for that part for quite some time.

kulta4 commented 10 months ago

Hi KUKSA Community,

The KUKSA cloud repository hasn't seen activity for quite some time. The projects that have been combined in here still live on in the Eclipse IOT working group https://iot.eclipse.org and meanwhile there are much newer releases than the ones used here.

KUKSA itself is currently not doing any "cloud" side development. Therefore, I would suggest archiving this repository. If there are still useful components in here, they might be a fit for one of the Eclipse SDV Blueprints https://projects.eclipse.org/projects/automotive.sdv-blueprints.

Please comment on this issue so we can come to a conclusion on how to further proceed.

Hi team, I have tried this kuksa.cloud for long time but I didn't get any update or successful move in this. the suggested one was fleet-management, but I would like to continue explore this kuksa cloud because of the components which you included here and if it has some proper guidance then it will be more helpful to forward

eriksven commented 10 months ago

@kulta4 thank you for your feedback. I would still opt to archive this repository. The content will still be visible after the archival, and in #189 we provide some hints on where to check and ask for alternatives.

As mentioned above, the current content of the repository requires substantial work to be updated because it has not seen much activity in the last year. The reason is that the focus of the Eclipse Kuksa development has shifted towards the Databroker and the referenced projects. Because of that, I am afraid that currently, no one will provide the requested level of guidance through contributions to this repository.