Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.220.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=uDvCUhueMwOwYqrJ4KP1BQbnUz/++eRrjTdfQt/nV9qFUWOOD6aE/06sD4DU9k961m
         8M8Kuy6RcgMUQrbuFqSgJRLzGb9FnH153Aa9/2xl7v+0EDKZDoIQ16y/3uPOIT0wyCNW
         DQhyl7/t0MabL6X/zhfSKv0oHEi5A6L1OLINk=
MIME-Version: 1.0
In-Reply-To: <23754070.post@talk.nabble.com>
References: <23754070.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 28 May 2009 06:15:46 +0200
Message-ID: <5380c69c0905272115o35965a85qb38787ee25a265e6@mail.gmail.com>
Subject: Re: Adding New Component For General Camel Use
To: dev@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Thu, May 28, 2009 at 4:12 AM, joehoe <jhoffert@dre.vanderbilt.edu> wrote:
>
> Hi.
>
> I will be working on a specific data dissemination component for Camel. I'd
> like for this component to be generally available. What are the procedures
> to follow and/or standards to be met in order to include a component for
> Camel distribution?
Hi

Fantastic and welcome on the Camel ride.

The contributing page explains some bits about this:
http://camel.apache.org/contributing.html

Usually it starts like this with a mail thread. Then when you feel
like the code is ready for review or others to take a look at,
then create a JIRA ticket for it and attach it there.

If the component has a general and broad usage then its a good
candidate for inclusion at Apache Camel.
The code must however be Apache License.

The code should follow the checkstyle ruling that we use.
You can run it from maven using:

mvn compile -Psourcecheck

And it should be unit tested with a good coverage.

And most importantly you should also be willing to do the
doucmentation it takes at the Camel wiki pages.


>
> Thanks for your help.
>
> -Joe
> --
> View this message in context: http://www.nabble.com/Adding-New-Component-For-General-Camel-Use-tp23754070p23754070.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>


-- 
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus