proposal: provided kamelets #1957
Conversation
|
LGTM Thought its 2021 so the yyyy should be updated. And I noticed there was 2 x single in the text in the top |
|
|
||
| == Proposal | ||
|
|
||
| We should start to add Kamelets to https://github.com/apache/camel-kamelets, and help people contributing their own. |
There was a problem hiding this comment.
I think we must define guidelines in order to know what kind of Kamelets are expected and how much generic they should be.
There was a problem hiding this comment.
Yeah, I think we can find out some criteria considering the context of ingress/egress from a generic platform. But of course there's some more work to do.
I.e. I think, after all, it would be acceptable to have a "beer-source" Kamelet provided by us. But is it also ok to provide a "chuck-source"? (I don't have the answer). These are just some concerns regarding publicly available APIs, but there are many others...
|
Let's merge the proposal and we'll follow up on https://github.com/apache/camel-kamelets for the guidelines. |
A proposal to move forward with Kamelets.
cc: @davsclaus , @oscerd , @astefanutti , @squakez , @doru1004 , @lburgazzoli
Release Note