Hi Peter， Thanks for the clarification, in this case you don't need to do any paperwork. Happy hacking camel quarkus code :)
Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Jul 1, 2019 at 5:54 PM Peter Palaga <[email protected]> wrote: > > Hi Willem, > > I signed the ICLA on 2012-02-20 when I was active in another ASF > project. So I hope there is nothing else I should do now? > > Thanks, > > -- Peter > > On 01/07/2019 03:57, Willem Jiang wrote: > > Hi, > > > > I just went through the code commit logs of quarkus camel extension, > > lots of commits are from Apache Camel committer (gnodet) and ppalaga > > is the main maintainer. > > It's clear that Redhat has the copyright. As Red Hat has the CLA with > > ASF, it make sense that a Red Hat employee who is Camel committer to > > transfer the code to Apache Camel. > > > > If I remembered right, we accepted the new component donation from > > JIRA with iCLA granted. When moving to the github PRs, I'm not sure if > > we go through the iCLA check any more. > > If the contribution is big enough (more than 100 lines in my mind), we > > still need to the iCLA for the contributor who is new to ASF. > > > > I just fill a JIRA[1] to add github pull request template to Camel > > repo for the user to send a PR. Please feel free to polish the PR > > template by adding comments on the JIRA. > > > > [1]https://issues.apache.org/jira/browse/CAMEL-13704 > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > On Thu, Jun 6, 2019 at 11:06 PM Hiram Chirino <[email protected]> > > wrote: > >> > >> I'm not sure this is much different from a new camel component > >> contribution. The whole Quarkus project is not being donated, this just > >> the camel integration with Quarkus. It was mostly worked on by camel > >> committers. I think that a Red Hat employee that's a Camel comitter should > >> be able to contribute this code to camel like other components get donated > >> periodically. If we can't find a committer that is confident it's 100% Red > >> Hat copyright, then yeah let's go through the ip-clearance. > >> > >> On Tue, Jun 4, 2019 at 6:34 AM Willem Jiang <[email protected]> wrote: > >> > >>> +1 for working with Quarkus to make the Camel Application more light and > >>> fast. > >>> > >>> For the code donation part, we need to go through the IP clearance > >>> process[1]. > >>> Please let me know if you have any questions about this. > >>> > >>> [1]https://incubator.apache.org/ip-clearance/ > >>> > >>> Willem Jiang > >>> > >>> Twitter: willemjiang > >>> Weibo: 姜宁willem > >>> > >>> On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli <[email protected]> > >>> wrote: > >>>> > >>>> Hi, > >>>> > >>>> In the past months some folks at Red Hat have been working on the > >>>> integration between Apache Camel and Quarkus. For those not familiar > >>>> with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java > >>>> framework tailored for GraalVM and HotSpot that bring fast startup > >>>> and low memory footprint to Java based application by leverage clever > >>>> build time optimizations and AOT compilation through Substrate VM [1]. > >>>> > >>>> The result of the experimentation is available in the Quarkus > >>>> repository [2][3] and I’m also working on an experimental branch > >>>> on Camel K [4] to bring Quarkus on the K side based on my latest > >>>> blog “Adventures in GraalVM: polyglot Camel (k) native routes > >>>> with Quarkus” [5] > >>>> > >>>> I do believe that both communities can benefit from a collaboration: > >>>> > >>>> Apache Camel can benefit from Quarkus to become > >>>> a) Even more suitable for microservices > >>>> b) Suitable for serverless workloads as Quarkus among others enables > >>>> built-time warmup of the Camel Context, and elimination of dead-code > >>>> (code that was only used during warmup) which is a key enabler for > >>>> very fast start-up and low memory footprint Apache Camel can be on > >>>> the innovative forefront with a cloud native Java stack for running > >>>> modern serverless workloads on Kubernetes/Knative with Camel K and > >>>> Camel Quarkus > >>>> > >>>> So I’m proposing to officially support Quarkus in Apache Camel’s main > >>>> repository (or a dedicated one if it suits better) by creating a new > >>>> platform along with those we support as today (Spring Boot, Karaf). > >>>> > >>>> Quarkus’ people is keen to donate the code related to Apache Camel > >>>> hosted in theirs repository to the Apache Software foundation. > >>>> > >>>> There has been some other users in the community whom have tried > >>>> Quarkus and Camel together and written blogs [6] about their experience, > >>>> and Claus also posted a quick gif animation of native compiled Camel > >>>> with Quarkus starting up in 7 milliseconds and taking up only 15mb > >>>> of memory [7]. > >>>> > >>>> Thoughts ? > >>>> > >>>> Luca > >>>> > >>>> [1] https://quarkus.io/ > >>>> [2] https://github.com/quarkusio/quarkus/tree/master/extensions/camel > >>>> [3] > >>> https://github.com/quarkusio/quarkus-quickstarts/tree/master/camel-java > >>>> [4] > >>>> > >>> https://github.com/lburgazzoli/apache-camel-k-runtime/tree/quarkus-runtime > >>>> [5] https://bit.ly/2HvOrh0 > >>>> [6] https://bit.ly/2WDtCbW > >>>> [7] > >>>> > >>> https://www.linkedin.com/feed/update/urn:li:activity:6521869236153970688/ > >>>> > >>>> --- > >>>> Luca Burgazzoli > >>> > >> > >> > >> -- > >> Hiram Chirino > >> Engineering | Red Hat, Inc. > >> [email protected] | redhat.com > >> skype: hiramchirino | twitter: @hiramchirino >
