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
From:
kanto-dev <kanto-dev-bounces@xxxxxxxxxxx> on behalf of Carlton Bale via kanto-dev <kanto-dev@xxxxxxxxxxx>
Date: Friday, 17 November 2023, 21:04
To: Martin Brown <martin.brown@xxxxxxxxxxx>, kanto-dev@xxxxxxxxxxx <kanto-dev@xxxxxxxxxxx>
Cc: Carlton Bale <carlton.bale@xxxxxxxxxxx>, emo@xxxxxxxxxxxxxxxxxxxxxx <emo@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [kanto-dev] Cummins Kanto Contributions - Question on project structure
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?