Hi,
I am working to organize it, but this month is a bit tough for our team as well. I will keep you updated.
Поздрави / Best regards,
Kristiyan Gostev
Bosch IoT Edge (BD/PAD-DDA-ES1)
Bosch.IO EOOD | 47B Tsarigradsko Shose | Sofia 1124 | BULGARIA | bosch.io
Tel. +359 895 01 8535 | Kristiyan,Gostev@xxxxxxxxx
From:
Martin Brown <martin.brown@xxxxxxxxxxx>
Date: Wednesday, 13 December 2023, 16:17
To: Gostev Kristiyan (BD/PAD-DDA-ES1) <Kristiyan.Gostev@xxxxxxxxx>, kanto developer discussions <kanto-dev@xxxxxxxxxxx>
Cc: Carlton Bale <carlton.bale@xxxxxxxxxxx>, emo@xxxxxxxxxxxxxxxxxxxxxx <emo@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Cummins Kanto Contributions - Question on project structure
Hi Kristiyan, just following up to see where you propose we would push our code for Kanto for the J1939 and UDS Translator. I know we chatted in zoom just now about
meeting next week to discuss where we could push it. Do you think we could try to resolve it this week? Asking because of the upcoming holidays; it would be more challenging for Cummins team members to coordinate internally to get it pushed after Dec 19th.
Thanks.
Martin K. Brown
From: Gostev Kristiyan (BD/PAD-DDA-ES1) <Kristiyan.Gostev@xxxxxxxxx>
Sent: Monday, November 20, 2023 2:21 AM
To: kanto developer discussions <kanto-dev@xxxxxxxxxxx>; Martin Brown <martin.brown@xxxxxxxxxxx>
Cc: Carlton Bale <carlton.bale@xxxxxxxxxxx>; emo@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Cummins Kanto Contributions - Question on project structure
EXTERNAL SENDER: This email originated outside of Cummins.
Do not click links or open attachments unless you verify the sender and know the content is safe.
Hi Carlton,
I am not a big fan of that idea to start it inside Kanto, as I am afraid that this won’t continue anywhere else, and it really does not fit right in the core Kanto scope.
I have another proposal, an idea that we already talked about, that I will format in a proposal and write it here:
https://github.com/eclipse-kanto/kanto/discussions/277 in very soon.
Best regards,
Kristiyan
My preference would be to start this as “Protocol Translation” repo inside the existing Kanto project. This is the simplest solution to get started.
If that repo grows in scope or become too far away from the core focus of Kanto, the repo could then be moved to a separate sub-project under Kanto, with a separate governance structure.
Kanto Team, do you agree with this approach?
|