cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r986098 - in /websites/production/cxf/content: cache/main.pageCache getting-involved.html
Date Tue, 19 Apr 2016 16:47:28 GMT
Author: buildbot
Date: Tue Apr 19 16:47:28 2016
New Revision: 986098

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/getting-involved.html

Modified: websites/production/cxf/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/cxf/content/getting-involved.html
==============================================================================
--- websites/production/cxf/content/getting-involved.html (original)
+++ websites/production/cxf/content/getting-involved.html Tue Apr 19 16:47:28 2016
@@ -99,7 +99,7 @@ Apache CXF -- Getting Involved
          <td height="100%">
            <!-- Content -->
            <div class="wiki-content">
-<div id="ConfluenceContent"><p>There are many ways you can get involved in CXF:</p><p>1.
Participate on the <a shape="rect" href="mailing-lists.html">mailing lists</a>.
Propose ideas. Comment on others ideas. <br clear="none"> 2. Look at the open <a
shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CXF">JIRA
issues</a><br clear="none"> 3. Provide feedback on the current code<br clear="none">
4. Take a look at some of the ideas below</p><h2 id="GettingInvolved-CodingideasforCXFnewcomers">Coding
ideas for CXF newcomers</h2><p>There are many interesting areas of CXF that you
could potentially work on. Some ideas:</p><ul><li>WS-Context &amp; Session
support</li><li>An invoker for <a shape="rect" class="external-link" href="http://ode.apache.org/">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 shape="rect"
href="roadmap.html">Roadmap</a> and jump in and help</li></ul><h2
id="GettingInvolved-Howtosubmitpatch">How to submit patch</h2><ul><li>Check
out code from <a shape="rect" href="source-repository.html">Source Repository</a></li><li>Make
your changes, test, and build successfully</li><li>Make sure you add new files
to git before creating the patch</li><li>Generate patch using "git diff HEAD &gt;
my.patch" or via a "git format-patch"</li><li>Open a <a shape="rect" class="external-link"
href="https://issues.apache.org/jira/browse/CXF">Jira</a> issue and attach the patch.txt
file to the issue</li></ul><p>Alternative method:</p><ul><li>Fork
the project o
 n GitHub: &#160;<a shape="rect" class="external-link" href="https://github.com/apache/cxf"
rel="nofollow">https://github.com/apache/cxf</a></li><li>Commit any changes
to your fork. &#160;It's suggested that if this is targeting a JIRA issue, add &#160;[<a
shape="rect" class="unresolved" href="#">CXF-####</a>] to the commit comment</li><li>Submit
a pull request through GitHub's normal pull request mechanism</li></ul><h2
id="GettingInvolved-Howtoapplyapatch">How to apply a patch</h2><ul><li>patch
-E -p1 &lt; my.patch</li></ul><h2 id="GettingInvolved-Becomingacommitter">Becoming
a committer</h2><ul><li>First off, read about <a shape="rect" class="external-link"
href="http://www.apache.org/foundation/how-it-works.html">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 <strong>earn</strong> the right to be a committer,
it's not something we'll give you just because your name is
  <a shape="rect" class="external-link" href="http://en.wikipedia.org/wiki/James_Gosling"
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></ul><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 emoticon-smile"
src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.p
 ng" data-emoticon-name="smile" alt="(smile)"></p></div>
+<div id="ConfluenceContent"><p>There are many ways you can get involved in CXF:</p><p>1.
Participate on the <a shape="rect" href="mailing-lists.html">mailing lists</a>.
Propose ideas. Comment on others ideas. <br clear="none"> 2. Look at the open <a
shape="rect" class="external-link" href="http://issues.apache.org/jira/browse/CXF">JIRA
issues</a><br clear="none"> 3. Provide feedback on the current code<br clear="none">
4. Take a look at some of the ideas below</p><h2 id="GettingInvolved-CodingideasforCXFnewcomers">Coding
ideas for CXF newcomers</h2><p>There are many interesting areas of CXF that you
could potentially work on. Some ideas:</p><ul><li>WS-Context &amp; Session
support</li><li>An invoker for <a shape="rect" class="external-link" href="http://ode.apache.org/">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 shape="rect"
href="roadmap.html">Roadmap</a> and jump in and help</li></ul><h2
id="GettingInvolved-Howtosubmitapullrequest">How to submit a pull request</h2><ul><li>Open
a <a shape="rect" class="external-link" href="https://issues.apache.org/jira/browse/CXF">Jira</a>
issue</li><li>Fork the <a shape="rect" class="external-link" href="https://github.com/apache/cxf"
rel="nofollow">github cxf mirror</a></li><li>In most cases you should
base your changes on the master branch. The committers can backport to the maintenance branches
then</li><li>Create a new branch named like the JIRA issue you want to edit (e.g
CXF-6738)</li><li>Make your changes, test, and build succ
 essfully</li><li>Ideally put all changes into one commit. The commit should contain
the issue id (e.g [CXF-6738] Replace synchronized blocks ... )</li><li>Push the
change to your forked repo into your branch</li><li>If the commit is named like
above it will automatically show up in the JIRA issue making it easier to see what changes
belong to the issue</li><li>If you need to do changes to your pull request then
you should ideally rewrite your commit and do a push -f to your own branch</li></ul><h2
id="GettingInvolved-Applyingapullrequest">Applying a pull request</h2><ul><li>Merge
the pull request into the branch it is based on</li><li>Make sure the build works</li><li>Make
sure the commits refer to the issue they solve</li></ul><h2 id="GettingInvolved-Becomingacommitter">Becoming
a committer</h2><ul><li>First off, read about <a shape="rect" class="external-link"
href="http://www.apache.org/foundation/how-it-works.html">How the ASF works</a>.
Most importantly, the sections on Meritoc
 racy and Roles. That provides a bit of background.</li><li>The important part
is that you need to <strong>earn</strong> the right to be a committer, it's not
something we'll give you just because your name is <a shape="rect" class="external-link"
href="http://en.wikipedia.org/wiki/James_Gosling" 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></ul><p><em>Hint:</em>
submitting pull requests 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 commi
 ttership just to stop having to review patches. <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)"></p><p>&#160;</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message