Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kuksa-dev] Improve repo structure, Break out W3C visserver
Hi,

I requested the new repository [1] yesterday and it was just created. Committers are now waiting to receive access via the Eclipse sync tool.
Zoom link [2] still exists and calls continue on even calendar weeks as stated in [3].

Also, we just received Eclipse Kuksa 0.2.0 approval :-)
I will tag the repositories and set the release shortly.
Thanks to all committers, contributors, and everyone else who made this possible!


Looking forward to hearing from you tomorrow and best regards,
Robert

On Jan 21, 2020, at 16:02, Schildt Sebastian (CR/AEX1) <Sebastian.Schildt@xxxxxxxxxxxx> wrote:

Hello,
 
Then from my side I would like to formally request the creation of a kuksa.val repository. Is there any formal process/voting we would need to do for this? Will there be a tech meeting call Thursday, where we can discuss this? I saw an email to that effect, but no “real” (.ics or or otherwise) invitation. Does the Zoom still exist?
 
Of course, once it is there, we would take care of moving stuff and doing the appropriate PRs (probably first a PR with the moved part in kuksa.val and then, once that did work, a PR, that would add an appropriate link in the kuksa.invehicle repos, so we do not loose any functionality/code during the process
 
Mit freundlichen Grüßen / Best Regards
 
Sebastian Schildt
CR/AEX1
Threema / Threema Work: T8YWYXJ9
 
Von: kuksa-dev-bounces@xxxxxxxxxxx <kuksa-dev-bounces@xxxxxxxxxxx> Im Auftrag von Robert Hoettger
Gesendet: Dienstag, 21. Januar 2020 15:38
An: Kuksa developer discussions <kuksa-dev@xxxxxxxxxxx>
Betreff: Re: [kuksa-dev] Improve repo structure, Break out W3C visserver
 
Hi,
 
+1 from me too.
 
We would have to ask Eclipse for another repository (kuksa.val).
If the new repository is granted, we would have to move the W3C parts.
 
Best regards,
Robert


On Jan 21, 2020, at 15:06, Kristan Johannes (IOC/ESW6.31-T) <Johannes.Kristan@xxxxxxxx> wrote:
 
Hi Sebastian,
 
Thank you for the suggestion. Sounds sensible as this is the api definition and the other parts are rather implementation specific. 
 
So +1 from my side.
 

How about the other contributors? Are you ok with a separate  repository for the api?

Kind regards,
Johannes 
Von: kuksa-dev-bounces@xxxxxxxxxxx <kuksa-dev-bounces@xxxxxxxxxxx> im Auftrag von Schildt Sebastian (CR/AEX1) <Sebastian.Schildt@xxxxxxxxxxxx>
Gesendet: Montag, 20. Januar 2020 16:05:21
An: kuksa-dev@xxxxxxxxxxx
Betreff: [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
 
_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/kuksa-dev
 
_______________________________________________
kuksa-dev mailing list
kuksa-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/kuksa-dev

Back to the top