Hi
Camel 2.x is not active anymore. We only do security patch releases of
the 2.25.x branch.
2.x will be EOL in summer 2021 or later.
We do not accept new components or other development on Camel 2.x.
You can always build a custom component on your own and use it with Camel 2.x.
On Fri, Nov 6,
Hello team
I am trying to develop some camel components to connect with huawei cloud
services and this would be my first contribution as a developer. Have
following questions
- Would like to start with developing to support the camel 2.24.x version
because we need that support for our existing p
I’d like to verify my understanding of the jira and PR workflows and update the
contributing.adoc page with some more details.
Here’s how I think camel works:
- Camel operates with an informal review-then-commit policy for PRs. If you
are a committer, please wait for at least one approval bef
oscerd merged pull request #97: CAMEL-14061 camel-website - Add page for
contributing
URL: https://github.com/apache/camel-website/pull/97
This is an automated message from the Apache Git Service.
To respond to the message
akieling opened a new pull request #97: CAMEL-14061 camel-website - Add page
for contributing
URL: https://github.com/apache/camel-website/pull/97
Point to Contributing page instead of CONTRIBUTING.md on GitHub.
PS My editor automatically removes unnecessary spaces at the end of
Here you are:
http://camel.apache.org/staging/community/team/
Il giorno mar 2 lug 2019 alle ore 07:58 Andrea Cosentino
ha scritto:
> Hello,
>
> We can add you to the list of contributors. To become committer the
> process is a bit more complex and longer.
>
> Thanks.
>
> Il giorno mar 2 lug 201
Hello,
We can add you to the list of contributors. To become committer the process
is a bit more complex and longer.
Thanks.
Il giorno mar 2 lug 2019 alle ore 07:41 Otávio Prado <
otaviofelipedopr...@gmail.com> ha scritto:
> Hello everyone, everything good? I would like to have my name added on
Hello everyone, everything good? I would like to have my name added on the
list of camel apache commiters, it would be a great honor for me :) Name:
Otávio Prado Thank you guys!
lburgazzoli closed pull request #29: Adding contributing guide
URL: https://github.com/apache/camel-k/pull/29
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request
nicolaferraro opened a new pull request #29: Adding contributing guide
URL: https://github.com/apache/camel-k/pull/29
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub
Hi Bennet
Yeah sure that sounds good, to have more validation at build time.
We have already a camel-maven-plugin that can do a bunch of stuff, but
it does not check properties files.
https://github.com/apache/camel/blob/master/tooling/maven/camel-maven-plugin/src/main/docs/camel-maven-plugin.ado
Hi,
I wrote a Maven plugin some time ago. I heavily used it for my Mule projects to
ensure that all properties files (including key and values) are consistent in
all development stages (test, prod, and so on).
Without this plugin it could happen that I run into runtime errors when using a
Mule
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2078
---
GitHub user fhassak opened a pull request:
https://github.com/apache/camel/pull/2078
update contributing link
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhassak/camel Readme
Alternatively you can review and apply these
nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797374.html
Sent from the Camel Development mailing list archive at Nabble.com.
ks
>
> /Preben
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797131.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclau
ere i can.
>
> On Fri, 7 Apr 2017 at 11:32, Preben.Asmussen wrote:
>
> > Sure I'll fix it + the doc and missing features during the weekend I
> hope.
> >
> > And thanks
> >
> > /Preben
> >
> >
> >
> > --
> > View this mess
en
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797131.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
--
Sent from my iPhone
Sure I'll fix it + the doc and missing features during the weekend I hope.
And thanks
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797131.html
Sent from the Camel Development mailing list archi
Could it be an idea to start with the "milo" component. And push the other
two (of mine) two to 2.20.
I personally think that Milo is the most beneficial one anyway.
On Fri, Apr 7, 2017 at 9:39 AM, Claus Ibsen wrote:
> On Thu, Apr 6, 2017 at 2:34 PM, Jens Reimann wrote:
> > I personally don't
On Thu, Apr 6, 2017 at 2:34 PM, Jens Reimann wrote:
> I personally don't know this protocol. So I can't say much about it.
>
> But I guess adding a bunch of IoT related Camel components in one release
> would make sense.
>
We are closing down on Camel 2.19 and intend to cut the RC in week 16
so t
gt; to do a PR.
>
> /Preben
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797095.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibs
nd if PubNub would bring value to the Camel community I'll be happy
to do a PR.
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-a-set-of-IoT-related-components-tp5797075p5797095.html
Sent from the Camel Development mailing list archive at Nabble.com.
I personally don't know this protocol. So I can't say much about it.
But I guess adding a bunch of IoT related Camel components in one release
would make sense.
On Thu, Apr 6, 2017 at 1:52 PM, Claus Ibsen wrote:
> Hi
>
> Welcome to the Apache Camel community.
> Thanks for taking the time to exp
Hi
Welcome to the Apache Camel community.
Thanks for taking the time to explain this for us on the @dev mailing list.
If you guys can help support and maintain these IoT specific
components that would be really good.
AFAIR we only have Henryk Konsek as a Camel committer whom has been
playing and
Hi everyone,
As just mentioned on IRC, I would like to contribute a bunch of IoT related
Camel components I made to Apache Camel. Those are independent of each
other, so please consider them separately.
## Milo
Eclipse Milo is an OPC UA protocol implementation. This component provides
a cl
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1366
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1366
CAMEL-10528 - Add contributing file for Apache Camel
Add contributing file for Apache Camel
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
information to users, how they can contribute to the project.
>
> Projects at github often do this, and also the github points users to this
> file.
>
> https://help.github.com/articles/setting-guidelines-for-repository-contributors/
>
> We do have some information at
&g
rs to
>>this file.
>>
>>https://help.github.com/articles/setting-guidelines-for-repository-contributors/
>>
>>We do have some information at
>>http://camel.apache.org/contributing
>>
>>Which we can polish and add the good parts to
gt;Projects at github often do this, and also the github points users to
>this file.
>
>https://help.github.com/articles/setting-guidelines-for-repository-contributors/
>
>We do have some information at
>http://camel.apache.org/contributing
>
>Which we can polish and add
to the project.
>
>Projects at github often do this, and also the github points users to
>this file.
>
>https://help.github.com/articles/setting-guidelines-for-repository-contributors/
>
>We do have some information at
>http://camel.apache.org/contributing
>
>Which we c
://help.github.com/articles/setting-guidelines-for-repository-contributors/
We do have some information at
http://camel.apache.org/contributing
Which we can polish and add the good parts to this file.
We can also find inspiration at sister ASF projects where some of them
have this file
https
It takes some time to trigger a website update, so have patience.
On Sun, Dec 27, 2015 at 4:24 PM, Asaf Mesika wrote:
> I just edited my first page (http://camel.apache.org/kafka.html), saved,
> but I don't see my change. The edit was in Confluence, but it's not
> reflected in this HTML.
> What t
I just edited my first page (http://camel.apache.org/kafka.html), saved,
but I don't see my change. The edit was in Confluence, but it's not
reflected in this HTML.
What trigger it to be updated?
On Fri, Sep 25, 2015 at 10:34 AM, Claus Ibsen wrote:
> I have granted your user karma to edit the do
I have granted your user karma to edit the docs. Thanks for helping the project.
On Fri, Sep 25, 2015 at 9:23 AM, Asaf Mesika wrote:
> Ok. I have a user on the Confluence wiki page named "asafm" (Asaf Mesika).
>
> What's next?
>
>
> On Thu, Sep 24, 2015 at 5:03 PM, Claus Ibsen wrote:
>
>> Sorry
Ok. I have a user on the Confluence wiki page named "asafm" (Asaf Mesika).
What's next?
On Thu, Sep 24, 2015 at 5:03 PM, Claus Ibsen wrote:
> Sorry that was many years I did that. Click on the edit link in the
> bottom of a Camel web page, and it opens it in wiki, I assume it has
> some login
Sorry that was many years I did that. Click on the edit link in the
bottom of a Camel web page, and it opens it in wiki, I assume it has
some login / create account button somewhere.
For example:
https://cwiki.apache.org/confluence/pages/editpage.action?pageId=49116
Anyone who has recently done t
Thanks, I'm happy to help.
I searched in the wiki, but couldn't find any "Create user" button.
Can you send me a link to that?
On Mon, Sep 21, 2015 at 5:59 PM, Claus Ibsen wrote:
> Hi
>
> When your name is on this page
> http://people.apache.org/committer-index.html
>
> Then create an account o
Hi
When your name is on this page
http://people.apache.org/committer-index.html
Then create an account on the wiki and let us know your username and
post here again. Then we can grant karma.
Thanks for helping with the project.
On Mon, Sep 21, 2015 at 4:57 PM, Asaf Mesika wrote:
> Hi,
>
> I've
Hi,
I've signed and emailed the ICLA to the secretery, in a goal to contribute
to the wiki.
What do I do next?
Ok, karma granted!
Looking forward to your first contribution.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/
Oh, silly me.
I am now "alvrod" in Confluence too.
Thanks
Alvaro.
On Thu, Feb 6, 2014 at 5:13 PM, Christian Müller
wrote:
> Both user names are not known in Confluence (Confluence is not JIRA ;-) ).
> You have to create an account in Confluence too, if you would like to edit
> our WIKI.
>
> Best,
Both user names are not known in Confluence (Confluence is not JIRA ;-) ).
You have to create an account in Confluence too, if you would like to edit
our WIKI.
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Ca
Correction: Thanks to dkulp I've regained control of "alvrod" so I can
be myself :-)
Regards
Álvaro.
On Wed, Feb 5, 2014 at 10:32 PM, Alvaro Rodriguez
wrote:
> Hello, thanks everyone for the warm welcome.
> I happen to be "calefox" in JIRA because alvrod was already taken.
> Unless someone reserv
achricht-
> Von: Alvaro Rodriguez [mailto:alvaro.rodrig...@gmail.com]
> Gesendet: Donnerstag, 6. Februar 2014 01:32
> An: dev@camel.apache.org
> Betreff: Re: Contributing
>
> Hello, thanks everyone for the warm welcome.
> I happen to be "calefox" in JIRA because alv
Hello, thanks everyone for the warm welcome.
I happen to be "calefox" in JIRA because alvrod was already taken.
Unless someone reserved it for me. :-)
Regards
Alvaro
On Wed, Feb 5, 2014 at 6:30 PM, Christian Müller
wrote:
> Welcome Alvaro!
>
> Looking forward to your first contribution. If you w
Welcome Alvaro!
Looking forward to your first contribution. If you want to get your hands
on the Camel code, have a look at the easy to resolve issues [1].
If you tell us your Confluence user name, we will grant the karma to edit
the WIKI.
[1] https://issues.apache.org/jira/browse/CAMEL-7156?filt
Hi
Welcome to the community and looking foward to any help of yours.
I assume you have read this page and the links it refer to about edit
the website and providing code patches etc.
http://camel.apache.org/contributing
On Wed, Feb 5, 2014 at 1:24 AM, Alvaro Rodriguez
wrote:
> Hello,
>
Woohoo! the more the merrier! look forward to your contributions...
pick some JIRAs (or create some) and send some pull requests/patches.
On Tue, Feb 4, 2014 at 5:24 PM, Alvaro Rodriguez
wrote:
> Hello,
> I sent an ICLA to Apache, received confirmation from jcarman, and I
> can see my name in the
Hello,
I sent an ICLA to Apache, received confirmation from jcarman, and I
can see my name in the "Unlisted CLAs" page.
I'd like to contribute to the project. I was thinking about editing
the website first if that's ok. I'll also try to at least get the
tests running on my box so I can contribute
grant me access as well. I have already signed the icla. My
> username is nerses_am.
>
> Thanks :)
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733641.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
reposting because I forgot to subscribe to mailing list.
Hi Christian,
Can you also grant me access as well. I have already signed the icla. My
username is nerses_am.
Thanks :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733641.html
Sent
gt; Thanks in advance,
> Frank
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733565.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Hi Christian,
my username is frank_e.
Thanks in advance,
Frank
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-tp5733544p5733565.html
Sent from the Camel Development mailing list archive at Nabble.com.
iled (see Unlisted CLAs
> <http://people.apache.org/committer-index.html#unlistedclas> ). To start
> contributing I would like to edit some wiki pages. Could you please create
> an account for me?
>
> Frank
>
>
>
> --
> View this message in context:
> http:
Hi,
I send a CLA which has been filed (see Unlisted CLAs
<http://people.apache.org/committer-index.html#unlistedclas> ). To start
contributing I would like to edit some wiki pages. Could you please create
an account for me?
Frank
--
View this message in context:
http://camel.465
> 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
he 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 then one hundred components today.
Current the hard part is the Stomp Component is written with Scala, as we
have the camel-sc
nts 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 t
> 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
el. 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 then one hundred components today.
> >
> > Current the hard part
tting 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 the
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
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:
>
ep 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:
> >
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Compo
> 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
> That is a good approach.
> ..
> I am waiting for a response.
Great :) Just keep me in the loop.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
enryk-konsek.blogspot.com
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153p5726597.html
> To unsubscribe from Contributing Apollo Component, click here.
> NAML
Hi Ian,
> The original project has not been maintained for more than a year.
> ...
> I have tried to contact Dejan to get his input in this regard.
> ...
> I am happy to collaborate with the original author but it might be simpler
> to work of the branch
In my opinion core Camel components shou
-
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153p5726521.html
> To unsubscribe from Contributing Apoll
> We would appreciate STOMP component written in Java.
Sorry, my mistake. I understood that you created Scala component for
STOMP Java library. However since Scomp is a pure Scala library I
think that Scomp component written in Scala can be safely committed to
the ASF Camel (after review process o
gt;>>> and in-out exchange patterns.
>>>>
>>>> I assume its a generic stomp component, so you can use it with any
>>>> stomp compliant brokers,
>>>> eg also ActiveMQ. eg its not only for Apollo. Right?
>>>>
>>>>
>&g
On Tue, Jan 29, 2013 at 8:21 PM, Henryk Konsek wrote:
Claus had some good arguments there not to use Scala.
Nevertheless, I think your code should be published at camel-extra or
github!
>
> Actually Camel Extra is not a right place to put there components
> written in Scala. I'
>>> Claus had some good arguments there not to use Scala.
>>>
>>> Nevertheless, I think your code should be published at camel-extra or
>>> github!
Actually Camel Extra is not a right place to put there components
written in Scala. I'm afraid this component need to be rewritten to
Java in order to
from the
>>>> Scomp project.
>>>> Is there any interest in this and if so what would be the process to
>>>> contribute the code.
>>>> Kind regards
>>>> Ian
>>>>
>>>>
>>>>
>>>> -
omp project.
> > > Is there any interest in this and if so what would be the process to
> > > contribute the code.
> > > Kind regards
> > > Ian
> > >
> > >
> > >
> > > --
> > > View this message in context:
> > http://camel.465427
; Ian
> >
> >
> >
> > --
> > View this message in context:
> > http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153.html
> > Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
> --
> Cla
> Scomp project.
> > Is there any interest in this and if so what would be the process to
> > contribute the code.
> > Kind regards
> > Ian
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Cont
sage in context:
> http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: htt
ritten in Scala to
> > integrate with other protocols like Stomp. Is it possible to (re-) write it
> >
> > in Java?
> > Only a few committer are familiar with Scala and are able to maintain this
> > component.
> >
> >
ala and are able to maintain this
> component.
>
> Best,
> Christian
>
> On Thu, Jan 24, 2013 at 4:19 PM, Willem jiang <[hidden email]>wrote:
>
> > contributing
>
>
>
>
>
> --
>
>
> If you reply to this email, your message will
le to maintain this
component.
Best,
Christian
On Thu, Jan 24, 2013 at 4:19 PM, Willem jiang wrote:
> contributing
--
It sounds cool.
Please take some time to go through the contributing page[1], you can fill a
JIRA and attach your patch into it.
[1]http://camel.apache.org/contributing.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
regards
Ian
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-Apollo-Component-tp5726153.html
Sent from the Camel Development mailing list archive at Nabble.com.
uence wiki, click on your name (menu) at
the top and select Profile. On the right side, next to the Personal
widget there is an Edit link. Click on it, update the address, save and
ping us again.
Thanks,
Hadrian
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-to
u) at
> the top and select Profile. On the right side, next to the Personal
> widget there is an Edit link. Click on it, update the address, save and
> ping us again.
>
> Thanks,
> Hadrian
>
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-to-
I can confirm that. However, the confluence (wiki) account address
points to another address. That's the one you need to update.
If you can log into the confluence wiki, click on your name (menu) at
the top and select Profile. On the right side, next to the Personal
widget there is an Edit lin
AM, jkorab wrote:
>>> Hi,
>>>
>>> I'd like an account in order to contribute to the Camel wiki. My ICLA
>>> has
>>> been accepted at Apache:
>>>
>>> http://people.apache.org/committer-index.html#unlistedclas
>>>
>>
apache.org/committer-index.html#unlistedclas
>>
>> Thanks,
>>
>> Jakub Korab
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Contributing-to-wiki-tp5678315.html
>> Sent from the Camel Development mailing list archi
A has
been accepted at Apache:
http://people.apache.org/committer-index.html#unlistedclas
Thanks,
Jakub Korab
--
View this message in context:
http://camel.465427.n5.nabble.com/Contributing-to-wiki-tp5678315.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Hadrian Zbarcea
Sorry about that, wrong manip.
On Thu, Jun 17, 2010 at 19:10, wrote:
>
> Contributing<https://cwiki.apache.org/confluence/display/CAMEL/Contributing>
> Page
> *moved* by Guillaume
> Nodet<https://cwiki.apache.org/confluence/display/~gnodet>
>
&
Hi,
Thanks for granting the editing rights! I'll start looking at some of the
component docs next week, though it looks like Claus has already made some
big improvements there in recent days.
Cheers,
Fintan
--
View this message in context:
http://www.nabble.com/Contributing-to-Camel-Comp
o a bit of copy editing,
re-ordering
sections, and so on. I promise not to mess up any content written
by expert
contributors! But if there are any obvious gaps in the component
documentation, I might my hand at contributing material myself
(since an
inexpert contribution is probably better than
yout, do a bit of copy editing,
> > re-ordering
> > sections, and so on. I promise not to mess up any content written by
> expert
> > contributors! But if there are any obvious gaps in the component
> > documentation, I might my hand at contributing material myself
1 - 100 of 102 matches
Mail list logo
