Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[kuksa-dev] Improve repo structure, Break out W3C visserver

Hi KUKSA,

 

We have some people staring to work with w3C-visserver, however, it is quite confusing to them, that is hidden somewhere with millions of unrelated components in kuksa.invehicle

 

We would like to break it out, preferably inside KUKSA. The suggestion is to make a new repository

 

kuksa.val    (Vehicle Abstraction Layer, we want to be careful with “W3C” on top level, as this is only one implementation of a W3C standard, not some official W3C work)

 

We would move w3c specific code from in.vehicle over to there and replace it with a link/submodule. That would not harm KUKSA functionality, but makes it much easier for people to contribute.

 

Any opinions on this? We would prefer to keep the work in Eclipse, and not forking outside. What would be procedure?

 

Mit freundlichen Grüßen / Best Regards

 

Sebastian Schildt

CR/AEX1

Threema / Threema Work: T8YWYXJ9

 


Back to the top