There are many ways you can get involved in CXF:
1. Participate on the mailing lists. Propose ideas. Comment on others ideas.
2. Look at the open JIRA issues
3. Provide feedback on the current code
4. Take a look at some of the ideas below
Coding ideas for CXF newcomers
There are many interesting areas of CXF that you could potentially work on. Some ideas:
- WS-Context & Session support
- An invoker for Ode which uses CXF
- A HTML Form based "tester" for WebServices
- XMPP/Jabber transport
- Increasing unit test coverage. Adding unit tests for areas that are not covered by current test cases is always valuable to the project.
- Support for Web Service Definition Language (WSDL) 2.0
- Castor databinding
- Other WS-* support; e.g., Quality of Service (WS-Atomic Transactions and WS-Coordination), bootstrapping (WS-MetaDataExchange), WS-BusinessActivity, WS-Eventing and WS-Transfer
- See the Roadmap and jump in and help
How to submit patch
- Check out code from Source Repository
- Make your changes, test, and build successfully
- Make sure you add new files to svn before creating the patch
- Generate patch using "svn diff --show-copies-as-adds > my.patch" . This also works if you move or delete files (requires svn > 1.7)
- Open a Jira issue and attach the patch.txt file to the issue. (make sure you select the "Grant license to ASF for inclusion" option)
How to apply a patch
Becoming a committer
- First off, read about How the ASF works. Most importantly, the sections on Meritocracy and Roles. That provides a bit of background.
- The important part is that you need to earn the right to be a committer, it's not something we'll give you just because your name is James Gosling. To earn the right, you need to get involved. (see top section above)
- 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....
Hint: 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.