cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r904788 - in /websites/production/cxf/content: cache/main.pageCache getting-involved.html source-repository.html
Date Thu, 03 Apr 2014 20:48:09 GMT
Author: buildbot
Date: Thu Apr  3 20:48:08 2014
New Revision: 904788

Log:
Production update by buildbot for cxf

Modified:
    websites/production/cxf/content/cache/main.pageCache
    websites/production/cxf/content/getting-involved.html
    websites/production/cxf/content/source-repository.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 Thu Apr  3 20:48:08 2014
@@ -99,36 +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 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 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.  (make sure you select the "Grant license to ASF for inclusion" option)</li></ul>
-
-
-<h2 id="GettingInvolved-Howtoapplyapatch">How to apply a patch</h2>
-
-<ul><li>patch -E -p0 &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-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png"
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-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-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emotic
 ons/smile.png" data-emoticon-name="smile" alt="(smile)"></p></div>
            </div>
            <!-- Content -->
          </td>

Modified: websites/production/cxf/content/source-repository.html
==============================================================================
--- websites/production/cxf/content/source-repository.html (original)
+++ websites/production/cxf/content/source-repository.html Thu Apr  3 20:48:08 2014
@@ -110,7 +110,7 @@ Apache CXF -- Source Repository
            <div class="wiki-content">
 <div id="ConfluenceContent"><h2 id="SourceRepository-WebBrowsingofGIT">Web Browsing
of GIT</h2><p>To browse via the web use the GIT web interface:</p><p><a
shape="rect" class="external-link" href="https://git-wip-us.apache.org/repos/asf?p=cxf.git">https://git-wip-us.apache.org/repos/asf?p=cxf.git</a></p><p>Or
via Fisheye courtesy of <a shape="rect" class="external-link" href="http://www.atlassian.com"
rel="nofollow">Atlassian</a>:</p><p><a shape="rect" class="external-link"
href="http://fisheye6.atlassian.com/browse/cxf" rel="nofollow">http://fisheye6.atlassian.com/browse/cxf</a></p><h3
id="SourceRepository-CheckingoutfromGIT">Checking out from GIT</h3><p>The source
code can be checked out anonymously over HTTPs by doing:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[git
clone https://git-wip-us.apache.org/repos/asf/cxf.git]]></script>
-</div></div></div>
+</div></div><p>&#160;</p><h3 id="SourceRepository-ForkingonGitHub">Forking
on GitHub</h3><p>CXF's git repo is automatically mirrored on github at:&#160;<a
shape="rect" class="external-link" href="https://github.com/apache/cxf" rel="nofollow">https://github.com/apache/cxf</a>&#160;&#160;</p><p>You
can fork that repository, commit changes to your fork, and submit pull requests through GitHub's
pull request mechanisms.</p><p>&#160;</p></div>
            </div>
            <!-- Content -->
          </td>



Mime
View raw message