This would be a super nice addition to the components list. First I would open the PR against main and then against camel-3.x
We are always available if you need help. Thanks a lot! Il giorno mar 25 apr 2023 alle ore 17:46 Otavio Rodolfo Piske < angusyo...@gmail.com> ha scritto: > Hi, > > LGTM ... some additional pointers: > > 1. In general, you can send a PR to camel-3.x. In the past, we used (but > not always) to add major new features and components on non-LTS versions so > it would mature for a few releases. I don't think we'll have non-LTS > versions on 3.x anymore, so I guess sending to camel-3.x is probably fine > (and, in this case, I would send to Camel 4 prior to sending it to Camel 3 > ... but that's just my personal preference). > 2. If possible, try to include a test-infra container for it, so the > testing is easier and reusable > 3. If, half way through the changes, you are unsure and would like to > request for comments ... sending a draft PR is totally fine. I think > most/all of us we'll be happy to review and provide feedback. > 4. And, lastly, you can always reach out on the chat for specific > discussions and questions as well. > > Kind regards > > > > > > On Tue, Apr 25, 2023 at 5:36 PM Petr Kuzel <petrku...@eurofins.com > .invalid> > wrote: > > > Hi dev@Camel, > > > > We are considering development of a component to address > > > > https://issues.apache.org/jira/browse/CAMEL-19279 > > > > Looking around I guess the component could be merged in > > > > > https://github.com/apache/camel/tree/camel-3.x/components/camel-azure > > > > and named > > > > camel-azure-files > > > > Does it make sense, please? > > > > Next I'm not sure how new Camel components are incubated. > > It there any guideline, please? It surely differs from > > patching some already existing component, as it starts > > from zero and effort/scale is bigger. > > > > Best regards > > Cc. > > > > > > -- > Otavio R. Piske > http://orpiske.net >
