Choose a single location for examples

[oscerd]

We had some discussion here: #2731

I think it's important to have a single location for examples, because it would be much easier to maintain and also we could be able to tag them without having the camel-k release enriched with examples.

My vote is to move all the examples in the https://github.com/apache/camel-k-examples repository

But I'd like to get more feedback and votes.

[squakez]

Yes, it was something I planned to do in the past, but went out of my radar (#2462). As mentioned in that discussion, I am good with moving everything in the dedicated repository. In that case, I suggest we apply the same branching strategy of the main project.

[oscerd]

Ok, I'm going to work on this.

[astefanutti]

It sounds good to me. Having the examples promoted into their own repository will certainly make them more visible. Possibly, it'll even make things easier to setup automated testing and foster test coverage in this new repository.

[github-actions]

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

[oscerd]

Do we still want to move everything in a different repository?

[squakez]

+1 for me. We can link the example folder to the new location.

[oscerd]

The examples are now in https://github.com/apache/camel-k-examples/tree/main/generic-examples

I'll see how to remove the examples from the main folder once we released 1.9.0

[squakez]

Great, thanks @oscerd ! I wonder if we should also remove the CamelSource examples.

[oscerd]

Where are them?

[squakez]

Where are them?

This one for instance: https://github.com/apache/camel-k-examples/tree/main/04-aws-kinesis-source-basic

[oscerd]

Yeah, I think we need to focus on kamelets and generic-examples.