Hi
Yeah one of the hardest problem is naming, and after that renaming as
a lot of old stuff "expects" the old name.
I am also leading to Binding, as we have other concepts in Camel K
that are neutral named (no Camel or product in the name) like
Integration, IntegrationKit.
And they are all in
+1 for Binding
Dropping the Kamelet part makes it clearer that you can bind more
than just Kamelets.
Keeping it as "Binding" gives Kubernetes users a pretty good idea of what
it's going to do without reading the documentation.
On Mon, Aug 16, 2021 at 2:04 PM Antonin Stefanutti
wrote:
> Hi
