This repository has been archived by the owner on Dec 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 51
Proposal for splitting of KUKSA.val
Sebastian Schildt edited this page Jun 27, 2023
·
7 revisions
There is a new Github organization eclipse-kuksa. Over time it is proposed that content in this repository shall be moved to one or more new repositories in the new organization. This page proposes a possible split
| Folder | Suggested new repo | Comment / Used By |
|---|---|---|
| data/vss-core | kuksa-common | |
| doc | kuksa-doc | |
| jwt | kuksa-common | |
| kuksa_databroker (except *.proto) | kuksa-databroker | |
| kuksa_databroker (*.proto only) | kuksa-common | |
| kuksa-client | kuksa-python-client | Add python to name to separate from other clients? |
| kuksa-val-server | kuksa-val-server | Seb: Might not migrate it at all, just archive at old position? |
| Kuksa_apps (s3) | kuksa-s3-app | Or do we want to see this as a service, e.g. kuksa-s3-service |
| Kuksa_apps (node red) | kuksa-node-red-app | Or do we want to see this as a service, e.g. kuksa-node-red-service: Seb:Might potentially into kuksa-viss when adapted to databroker (I do think we will only do the websocket thingies there, as that is possible with vanilla node.red, GRPC would mean writing cusotm nodejs modukes). Maybe have legacy in val-server |
| kuksa_go_client | kuksa-go-client | |
| proto | kuksa-common | |
| test | kuksa-test | Repo for general integration tests involving multiple components |
- Do we want separate repos for JSON, certificates, proto or a joint one?
- First create new repos for content that are shared by multiple applications like Proto files, example certificates. At this time do not delete anything from this repo
- Start moving applications. When CI works for the component in the location add a prominent "deprecation" note in corresponding READMEs in this repo.
- Move strategy is by taking a snapshot of latest master/main, i.e. old tags will not be moved. The new repos shall be refactored to use Proto/VSS/JWT from shared repo rather than from local copies
- Keep the old repo (i.e. this repo) open for 6 months for critical bug fixes (if any) and or backports of new functionality. This is to give downstream projects some time to move to the new structure
- After 6 months put this repo in read-only-mode