blob: a569fd72989fc601ae6b27ecb1c576c031041ab6 [file] [log] [blame] [view]
jfarrell347a5eb2014-04-05 12:20:07 -04001## How to contribute
2
Konrad Grochowski23b60b52014-10-02 17:25:47 +02003 1. Make sure your issue is not all ready in the [Jira issue tracker](http://issues.apache.org/jira/browse/THRIFT)
4 1. If not, create a ticket describing the change you're proposing in the [Jira issue tracker](http://issues.apache.org/jira/browse/THRIFT)
jfarrell347a5eb2014-04-05 12:20:07 -04005 1. Contribute your patch using one of the two methods below
Konrad Grochowski3bc64242015-02-04 16:43:26 +01006
jfarrell347a5eb2014-04-05 12:20:07 -04007### Contributing via a patch
Konrad Grochowski3bc64242015-02-04 16:43:26 +01008
jfarrell347a5eb2014-04-05 12:20:07 -040091. Check out the latest version of the source code
Konrad Grochowski3bc64242015-02-04 16:43:26 +010010
11 * git clone https://git-wip-us.apache.org/repos/asf/thrift.git thrift
jfarrell347a5eb2014-04-05 12:20:07 -040012
131. Modify the source to include the improvement/bugfix
Konrad Grochowski3bc64242015-02-04 16:43:26 +010014
15 * Remember to provide *tests* for all submited changes
16 * When bugfixing: add test that will isolate bug *before* applying change that fixes it
17 * Verify that you follow [Thrift Coding Standards](/coding_standards) (you can run 'make style', which ensures proper format for some languages)
jfarrell347a5eb2014-04-05 12:20:07 -040018
191. Create a patch from project root directory (e.g. you@dev:~/thrift $ ):
Konrad Grochowski3bc64242015-02-04 16:43:26 +010020
21 * git diff > ../thrift-XXX-my-new-feature.patch
jfarrell347a5eb2014-04-05 12:20:07 -040022
231. Attach the newly generated patch to the issue
241. Wait for other contributors or committers to review your new addition
251. Wait for a committer to commit your patch
Konrad Grochowski3bc64242015-02-04 16:43:26 +010026
jfarrell347a5eb2014-04-05 12:20:07 -040027### Contributing via GitHub pull requests
28
291. Create a fork for http://github.com/apache/thrift
Konrad Grochowski3bc64242015-02-04 16:43:26 +0100301. Create a branch for your changes
jfarrell347a5eb2014-04-05 12:20:07 -0400311. Modify the source to include the improvement/bugfix
jfarrell347a5eb2014-04-05 12:20:07 -040032
Konrad Grochowski3bc64242015-02-04 16:43:26 +010033 * Remember to provide *tests* for all submited changes
34 * When bugfixing: add test that will isolate bug *before* applying change that fixes it
35 * Verify that you follow [Thrift Coding Standards](/coding_standards) (you can run 'make style', which ensures proper format for some languages)
36
371. Commit and push changes to your branch
381. Issue a pull request with the jira ticket number you are working on in it's name
jfarrell347a5eb2014-04-05 12:20:07 -0400391. Wait for other contributors or committers to review your new addition
401. Wait for a committer to commit your patch
41
42### More info
Konrad Grochowski3bc64242015-02-04 16:43:26 +010043
jfarrell347a5eb2014-04-05 12:20:07 -040044 Plenty of information on why and how to contribute is available on the Apache Software Foundation (ASF) web site. In particular, we recommend the following:
Konrad Grochowski3bc64242015-02-04 16:43:26 +010045
jfarrell347a5eb2014-04-05 12:20:07 -040046 * [Contributors Tech Guide](http://www.apache.org/dev/contributors)
47 * [Get involved!](http://www.apache.org/foundation/getinvolved.html)
48 * [Legal aspects on Submission of Contributions (Patches)](http://www.apache.org/licenses/LICENSE-2.0.html#contributions)