cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache CXF > Getting Involved
Date Wed, 12 Dec 2012 15:40:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2042/9/15/_/styles/combined.css?spaceKey=CXF&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Getting
    <h4>Page <b>edited</b> by             <a href="">Christian
        <div id="versionComment">
        Document how to correctly create and apply patches<br />
                         <h4>Changes (3)</h4>
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >* Check out code from [Source Repository]
<br>* Make your changes, test, and build successfully <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
Generate patch using &quot;svn diff&quot; <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
Make sure you add new files to svn before creating the patch <br>* Generate patch using
&quot;svn diff --show-copies-as-adds &gt; my.patch&quot; . This also works if
you move or delete files (requires svn &gt; 1.7) <br></td></tr>
            <tr><td class="diff-unchanged" >* Open a [Jira|]
issue and attach the patch.txt file to the issue.  (make sure you select the &quot;Grant
license to ASF for inclusion&quot; option) <br> <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">h2.
How to apply a patch <br> <br>* patch -E -p0 &lt; my.patch  <br> <br></td></tr>
            <tr><td class="diff-unchanged" >h2. Becoming a committer <br>
            <tr><td class="diff-snipped" >...<br></td></tr>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <p>There are many ways you can get involved in CXF:</p>

<p>1. Participate on the <a href="/confluence/display/CXF/Mailing+Lists" title="Mailing
Lists">mailing lists</a>.  Propose ideas. Comment on others ideas. <br/>
2. Look at the open <a href="" class="external-link"
rel="nofollow">JIRA issues</a><br/>
3. Provide feedback on the current code<br/>
4. Take a look at some of the ideas below</p>

<h2><a name="GettingInvolved-CodingideasforCXFnewcomers"></a>Coding ideas
for CXF newcomers</h2>
<p>There are many interesting areas of CXF that you could potentially work on. Some

	<li>WS-Context &amp; Session support</li>
	<li>An invoker for <a href="" class="external-link" rel="nofollow">Ode</a>
which uses CXF</li>
	<li>A HTML Form based "tester" for WebServices</li>
	<li>XMPP/Jabber transport</li>
	<li>Increasing unit test coverage.  Adding unit tests for areas that are not covered
by current test cases is always valuable to the project.</li>
	<li>Support for Web Service Definition Language (WSDL) 2.0</li>
	<li>Castor databinding</li>
	<li>Other WS-* support; e.g., Quality of Service (WS-Atomic Transactions and WS-Coordination),
bootstrapping (WS-MetaDataExchange), WS-BusinessActivity, WS-Eventing and WS-Transfer</li>
	<li>See the <a href="/confluence/display/CXF/Roadmap" title="Roadmap">Roadmap</a>
and jump in and help</li>

<h2><a name="GettingInvolved-Howtosubmitpatch"></a>How to submit patch</h2>

	<li>Check out code from <a href="/confluence/display/CXF/Source+Repository" title="Source
Repository">Source Repository</a></li>
	<li>Make your changes, test, and build successfully</li>
	<li>Make sure you add new files to svn before creating the patch</li>
	<li>Generate patch using "svn diff --show-copies-as-adds &gt; my.patch" . This
also works if you move or delete files (requires svn &gt; 1.7)</li>
	<li>Open a <a href="" class="external-link"
rel="nofollow">Jira</a> issue and attach the patch.txt file to the issue.  (make
sure you select the "Grant license to ASF for inclusion" option)</li>

<h2><a name="GettingInvolved-Howtoapplyapatch"></a>How to apply a patch</h2>

	<li>patch -E -p0 &lt; my.patch</li>

<h2><a name="GettingInvolved-Becomingacommitter"></a>Becoming a committer</h2>

	<li>First off, read about <a href=""
class="external-link" rel="nofollow">How the ASF works</a>.  Most importantly, the
sections on Meritocracy and Roles.   That provides a bit of background.</li>
	<li>The important part is that you need to <b>earn</b> the right to be
a committer, it's not something we'll give you just because your name is <a href=""
class="external-link" rel="nofollow">James Gosling</a>.  To earn the right, you need
to get involved. (see top section above)</li>
	<li>If you become involved, participate in email discussions, submit patches, etc...
the current devs may invite you to become a committer through a vote.   If the vote passes,
that will trigger a bunch of things such as submitting a CLA, creating accounts, etc....</li>

<p><em>Hint:</em> submitting patches to Jira issues is the best way.   It
shows that you are digging into the code, are following best practices, writing tests, etc....
  It also annoys the developers to constantly have to review patches and if your patches are
all acceptable, they'll start the process to grant committership just to stop having to review
patches.  <img class="emoticon" src="/confluence/images/icons/emoticons/smile.gif" height="20"
width="20" align="absmiddle" alt="" border="0"/></p>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
        <a href="">View
        <a href="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message