The Next Great Thing: An Application Framework
richard.bair at oracle.com
Tue Feb 21 11:24:10 PST 2012
> - I'm offering to contribute time and code.
Hooray! A victim!
> - Daniel bring up some important questions. What is the game plan for
> managing contributions? Will Oracle require an Oracle employee as a team
Basically, you have to sign the OCA (instructions on the home page for openjfx / openjdk) and then you can supply patches that can be integrated. For the first little while, somebody on the project with commit rights (which at the moment is an Oracle person but once we get non-Oracle committers it could be anybody -- even you!) will commit the patch.
Each functional area has a lead already, and they will act as reviewers. Ultimately I review all public API, Jasper all visual stuff, and Steve Northover handles all of the Glass, Prism, platform integration, etc stuff. The full process for API review and so forth is being written up and will be on a wiki (when we get one...).
After a while (the OpenJDK bylaws recommend 8 non-trivial patches or about 3 months of contributions) a contributor can be voted to become a committer. If the vote passes, then you would be a committer with the same rights as any other committer or Oracle employee. At that point we'd even want to include you on phone calls with the scrum team and sprint planning and so forth.
> - There are some basic infrastructure and organization choices that need to
> be made. Perhaps they've been made, but I'm unaware. Please don't make us
> work on java.net :/
Well, for OpenJFX we don't use java.net. But what kind of infrastructure / organization choices do you have in mind?
> - Is there wiki on how to contribute?
We're working on an OpenJFX specific version. I think Steve N. has the pen (but he's on vacation).
More information about the openjfx-dev