Re: [I] [Discussion] Camel K 2024 roadmap [camel-k]

["orpiske (via GitHub)" <gi...@apache.org>]

orpiske commented on issue #5019:
URL: https://github.com/apache/camel-k/issues/5019#issuecomment-1877180746

   This looks very nice @squakez! Some comments:
   
   * Remove kamel CLI in favour of other toolings
   
   Personally, I would like to see us consolidating on the Camel JBang as the de-facto CLI tool for Camel and every other sub-project. This, of course, might add some additional complexity to Camel Core and reduce further the cohesion of the core project, so we should probably evaluate [CAMEL-20264](https://issues.apache.org/jira/browse/CAMEL-20264) as a preliminary step for that. 
   
   * Enhance quality of code
   
   If there is interest, we can also evaluate adding Camel K bits to the SonarCloud instance. It has been a trusted source of cleanup material for the [Camel Core bits](https://sonarcloud.io/project/overview?id=apache_camel) (granted: I don't know how well it works for Go, so, probably needs further investigation). 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org