> Hiram:
> How about if we can get at least 3 committers to agree to help maintain the
> component then it should get accepted.
Maybe instead we could establish a kind of "Scala team" among the
Camel committers? These volunteers could declare that they would
handle Scala-related escalations in th
Hiram, that would be greet indeed.
Fwiw, my comment didn't refer to scala per se, but any component that we
don't have the ability to support ourselves. With java at least I
believe there are quite a few of us who could jump in and fix things,
with scala it's less the case. And socially, what
How about if we can get at least 3 committers to agree to help maintain the
component then it should get accepted. I think we should make efforts to
grow the camel community past just Java components if possible.
On Thu, Feb 7, 2013 at 7:51 PM, Willem jiang wrote:
> Putting the components int
> Hadrian:
> We know however from past experience that the community's ability to
> support scala based code was not at par with the rest of the code base.
This is changing. Scala is getting more popular among Java people. And
this trend is visible almost within our community. Year ago I wouldn't
Oh, I don't agree with that Scomp component is written in Scala we should find
other place to host it.
As an open source project we should alway encourage people to contribute, and
we can always find someone who willing to maintain the code, if we have lots of
users to use component.
--
Wi
Willem, I know all that. I understand it makes sense from the
contributor's point of view. It saves contributors time, effort and
costs. It ensures the their component will continue to work with future
versions of camel. That benefits the community too. Personally I applaud
that attitude.
How
Putting the components into Apache Camel umbral could save some work of
contributor when we release the Camel. We add the camel-extra due to the
license issue only. It is hard to say no for the contributing to Apache Camel
if the component has the ASF license already. That is way we have more th
I also believe Apache Camel the way it is organized now is not the place
for the scomp component. We are not debating the quality of the scomp
component. We know however from past experience that the community's
ability to support scala based code was not at par with the rest of the
code base.
Please find my comments inline.
Best,
Christian
On Thu, Feb 7, 2013 at 9:20 PM, Henryk Konsek wrote:
> > Because Camel and Camel-Extra are Java based projects, I don't think we
> > should integrate this component (even if it's a cool component for Scala
> > guys).
>
> I'm afraid I must disagree
> So once we have Scomp updated we are good to go.
First of all we need to figure out where the component should go, as
apparently there is some disagreement related to the proper place for
the Scala-related components.
BTW Camel Stomp definition made my day :P .
--
Henryk Konsek
http://henryk-
I have to say I kinda agree with this.
We could mark a component as possibly "less quickly patched",
but nixing contributions on a component level seems kinda wrong to me...
On Feb 7, 2013, at 1:20 PM, Henryk Konsek wrote:
>> Because Camel and Camel-Extra are Java based projects, I don't think
> Because Camel and Camel-Extra are Java based projects, I don't think we
> should integrate this component (even if it's a cool component for Scala
> guys).
I'm afraid I must disagree :) .
We support Scala as the 1st class citizen DSL language for Camel and I
don't see any reason why we should e
se.
>>>
>>> Great :) Just keep me in the loop.
>>>
>>> --
>>> Henryk Konsek
>>> http://henryk-konsek.blogspot.com
>>>
>>>
>>> If you reply to this email, your message will be added to the discussion
>> below:
>
nent-tp5726153p5726700.html
> > To unsubscribe from Contributing Apollo Component, click here.
> > NAML
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contributing-Stomp-Component-tp5726868.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
> below:
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153p5726700.html
> To unsubscribe from Contributing Apollo Component, click here.
> NAML
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-Contributing-Scomp-Component-was-Contri
15 matches
Mail list logo
