Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.21 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Thu, 14 Jun 2012 11:37:58 -0700
Subject: Re: Want to Contribute
Thread-Topic: Want to Contribute
Thread-Index: Ac1KXLUmnXYG1jAZQLCG9B+I8sjUTQ==
Message-ID: <CBFF7D76.835B%fil@adobe.com>
In-Reply-To: 
 <CAP7NMPraVzXk_jWsqwF6sBFVehbGHmNXb-gSncYbkr0S6AyWLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.2.120421
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Just a quick note that a CLA is not required unless the contributions are
deemed "significant" by the community of committers in this project.

That said, always a good idea to sign it :)

On 6/14/12 11:35 AM, "Michael Brooks" <michael@michaelbrooks.ca> wrote:

>Hi Charith,
>
>Looking through JIRA is a good start.
>
>Before we can accept a code contribution, we need you to sign the Apache
>CLA (contributor license agreement) [1].
>
>If you're on a Mac, then you can use Preview to digitally sign the
>document
>(Preview =3D> Preferences =3D> Signatures) and you use HelloFax [2] to fax=
 the
>document in a more modern way.
>
>JIRA is the best place to get started with contributions. Each issue has a
>"Fix Version" field that shows what release we plan to fix that issue. So
>1.9.0 are the next release, 2.0.0 are the following, and Master means we
>have no release set. Once you find an issue that you're into, just comment
>on it and let the maintainers know that you're looking into.
>
>At the moment, our Github mirrors [3] are not mirroring -
>it's embarrassing for us and frustrating for our users. You can still fork
>a Github repo and clone down your fork, but you will want to update the
>source by adding the official Apache repository [4] as a remote. You can
>combien the Apache repo URL with the repository name to form the
>repository's clone address. For example, the Apache Git repository for
>Cordova-iOS is
>https://git-wip-us.apache.org/repos/asf/incubator-cordova-ios.git.
>
>To add the apache remote and update your fork, you would:
>
># change this address to the platform you forked
>$ git remote add apache
>https://git-wip-us.apache.org/repos/asf/incubator-cordova-ios.git
>$ git checkout master
># update your master to the latest source
>$ git pull apache master
># create a branch to make your contribution (JIRA issue 642)
>$ git checkout -b jira-642
># when done, push this branch to Github and send a pull request
>$ git push origin jira-642
>
>Hope that helps,
>Michael
>
>[1] https://incubator.apache.org/cordova/#contribute
>[2] http://hellofax.com
>[3] http://github.com/apache
>[4] https://git-wip-us.apache.org/repos/asf
>
>On Thu, Jun 14, 2012 at 10:54 AM, Simon MacDonald
><simon.macdonald@gmail.com
>> wrote:
>
>> Read up on how to contribute here:
>>
>> https://incubator.apache.org/cordova/#contribute
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>> On Thu, Jun 14, 2012 at 4:57 AM, charithsoori <charithsoori@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I am very much interested in contributing to Apache through Corodova .
>> > I went through Jira issue tracker and observed few tasks. But still I
>> > like to get some idea from you guys.
>> >
>> >  ..
>> >
>> > Thanks & regards,
>> > Charith Sooriyaarachchi
>> >
>> > Software Engineer- 99x Technology.
>> > @charithsoori
>>