Thanks Andrea for the post. I also +1 to the proposal.
What I like the most too is the idea of the Kamelets marketplace. I too
believe that creating a vibrant community-based marketplace is the
essential step for the future success of Camel and Kamelets. We should
nurture a place something similar
Hi Andrea,
I think those are good ideas and I believe it would be beneficial for the
project to make the Kamelets a more prominent concept within our projects.
I believe we can reach a larger audience by doing so. In particular, I like
the idea of the Kamelets marketplace.
All in all, it's +1 fro
I think the first point to address is about the Kamelet API [1]. Right now
this is living (and evolving) as part of Camel K. If we decide to spin off
something different, then we need a new project (or reuse the catalog) to
take care of the API maintenance (also the CRD part). As an alternative, we
Hi
Thanks for starting this important topic.
I will come back with more thoughts later.
But one thing that stood out to me is that the kamelets documentation today
is tied into knative [1] and kamelet bindings.
it looks a bit like the documentation is auto generated for that part.
There's a lot o
Hello,
Kamelets are becoming an important and universal higher-level components /
building-blocks of Apache Camel; that are universal usable in all of Camels
runtimes and projects, whether its Camel on Spring Boot, Camel Standalone,
Camel Kafka Connector, Camel Quarkus, Camel JBang and Camel K as
