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 wrote:
>
> Hi Willem,
>
> I signed the ICLA on 2012-02-20 when I was activ
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
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 commit
Thanks for the information.
I saw there are some PRs from Peter in the camel-quarkus.
I'm not sure if Peter already signed the iCLA[1], if not we need it
for mass code transferation.
[1] https://www.apache.org/licenses/icla.pdf
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Wed, Jun 19,
Thanks for spotting this.
Il giorno mer 19 giu 2019 alle ore 12:22 Peter Palaga
ha scritto:
> Hi Again,
>
> just a heads up that the topic of moving Camel extensions away from the
> Quarkus source tree and generally how such externally developed
> extensions can live within the Quarkus ecosystem
Hi Again,
just a heads up that the topic of moving Camel extensions away from the
Quarkus source tree and generally how such externally developed
extensions can live within the Quarkus ecosystem is discussed on
quarkus-dev mailing list:
https://groups.google.com/forum/#!topic/quarkus-dev/yeo0
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 contri
Hi folks,
I like Peter's idea on having a separate repository for camel-quarkus.
In addition to his point, I would add that Quarkus is a newly born, cutting
edge technology, which itself should evolve fast and likely may not keep
how it works now for long as we see in, say, Node.js community. Hav
My fault about the ip-clearance. We must pass through that step. Thanks for
pointing this out Willem. The incubator name deceived me.
Il mar 4 giu 2019, 12:44 Andrea Cosentino ha scritto:
> +1 for working with the Quarkus community.
>
> I don't think this would be an incubator project btw, it sh
Hi,
I am fully welcoming the initiative to donate the code of Camel Quarkus
extensions that currently live in Quarkus git repository [1] to Apache
Camel community. I believe that's where the code can attract much more
interested developers and users.
I recently ported a couple of Camel compo
+1 for working with the Quarkus community.
I don't think this would be an incubator project btw, it should be a
subproject if it will go in a separate repo or it will be placed in the
main repo as a platform.
We can discuss this later by the way.
Il giorno mar 4 giu 2019 alle ore 12:34 Willem
+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
12 matches
Mail list logo
