Take the red pill.
Why should I join?
PicketLink is not only 100% open source, it is also developed for and by its community of users. Developers join from all over the world, and they contribute in many different ways. We are grateful for all contributions, whether it be a new feature, a bug fix, wiki entires, helping other members, or even just filling a bug report. The relationship is symbiotic, every contribution you make encourages others to in turn contribute in ways that will likely benefit you. The experience is also rewarding. Let's look at why.
Build Awesome New Technology
You get to work on the latest and greatest technology. It's extremely exciting working on what defines the future of application development. It's always changing and never boring.
Working on server runtimes and development frameworks is no slice of pie. But what fun is the easy level? While it can be challenging, solving tricky problems leaves you feeling a real sense of accomplishment.
Learn Something New
PicketLink is a big project covering many areas. You are bound to learn something new with every contribution you make. Even our top contributors are learning something new everyday, and they love it.
When contributing you get to work with some amazing people, and forging relationships with other sharp minds is always great professionally and personally.
Experience contributing to WildFly looks fantastic on a resume, and on a contracting reference list. It demonstrates talent and personal commitment beyond a normal job.
Be a Part of Something Big
Your contribution will be forever archived on the internet, and will benefit many others. They will tackle a hard problem using your work, they will learn by reading your work, and they will likely return the favor.
How do I get started?
Getting involved is easier than you think. All resources that you need are available on the internet.
The first step to get started is to build PicketLink yourself. This requires creating a GitHub account, forking PicketLink, and cloning your private fork. The "Hacking On WildFly" wiki article contains complete instructions for this and the patch construction and submission process.
Find Something To Work On
After you are comfortable building the server, the next step is to find something that you would like to work on. Scan through bug tracking system and look for an issue you would like to fix. We also stick features that have not been scheduled / assigned into a special version called Awaiting Volunteers. It is usually best to start with something small though like a minor priority bug. If you need help locating a task, feature, or bug to work on, just join our IRC channel and ask for help. When you do locate an issue be sure to announce you intention in the JIRA so that others don't end up duplicating your effort.
Subscribe to our Mailing List
If you are intending to contribute, it's a good idea to join the development mailing list. All design and general development discussions take place on this list. We also will send out important notifications, like release schedule updates and system availability.
Submit A Pull Request
Follow the directions in the above linked wiki article on how to submit the pull request. Once your pull request is submitted our automated CI environment will test it, and report any test failures. You will get email notifications in case this happens. A reviewer will also perform a human review, and request additional changes or clarification if required.
After your patch is successfully merged, it's time to celebrate!
Getting up to speed as a contributor is much easier if you know where to look. Here is the most common set of resources to assist you.
We highly recommend the following books, which we consider essential to working on system code.