As of Java 7, OpenJDK is the Reference Implementation (RI) for Java. In essence, the OpenJDK is the Java we use every day! With legal and technical barriers become smaller every day, it is now more possible than ever to get involved in the language and VM that we all love.
Many individuals, JUGs and organisations, see Who Is Adopting OpenJDK
An overall guideline for this program is that we want to gather up the enthusiasm and skill sets of Java developers around the world, but then focus their efforts at specific areas within the OpenJDK. For example, this means that we'll encourage most Adopt OpenJDK members to tackle library level and/or low hanging fruit categories of changes (we acknowledge that we're not all language designers). A smaller number of JUG members who are really qualified in the area of library design, hotspot internals etc (if you think syntax is the important bit, then this probably isn't you) will be encouraged to contribute in more advanced areas. This of course includes enthusiasts who are willing to put in the time to really learn about this stuff. As Yara from SouJava pointed out at Devoxx, this is a great opportunity to also mentor budding experts in the various parts of the OpenJDK, so that there is a path for those who want to travel it!
You can participate in the program via:
There are a couple of steps you should take if you are going to contribute to the OpenJDK
In order to have any serious amounts of work approved into the OpenJDK there's also the matter of liaising with a very busy OpenJDK team. Please ensure that you have an OpenJDK project sponsor for the work that you're doing. Typically you can email the Adopt OpenJDK group to get one arranged.
Again, we don't want to overwhelm the OpenJDK committers! So when organising a workshop/hackday we strongly recommend the following process:
This section covers the myriad ways in which you can contribute to the Adopt OpenJDK program
There are some General Instructions for Small Changes which apply to most of the sub projects below.
In order to get a patch ready for committing, you need to have written the patch, but there are several other things you need to do.
First off, you should be comfortable with building OpenJDK & keeping up to date with the head of the relevant repo.
You should also know (from having watched the mailing lists, or by asking on the AdoptOpenJDK mailing list) which project you should be targeting for your patch. Note that this may not necessarily be the OpenJDK 8 mainline project.
You should also have installed jtreg as that will be needed for testing your patch.
There are two parts to this. Project Jigsaw itself and project Penrose, a splinter project investigating OSGi/Jigsaw interaction
Read Alex Blewitt's blog post for some background information on the JEP process. Some JEPs can be classed as intermediate level proposals:
Read Alex Blewitt's blog post for some background information on the JEP process. Some JEPs can be classed as advanced level proposals:
See the Downloads section for this project (left hand menu).