Open Sourcing Status Report

[Richard Bair]

Hi John,

On Oct 18, 2012, at 2:37 PM, John Smith wrote:

> Thanks for the hard work on open sourcing JavaFX.
> I noticed some of the fxml work was open sourced recently, so that's progress.
> 
> Looking at the repository, this is a list of modules currently open sourced:
>  javafx-beans-dt
>  javafx-concurrent	
>  javafx-designtime	
>  javafx-fxml	
>  javafx-ueber-jar	
>  javafx-ui-charts	
>  javafx-ui-common	
>  javafx-ui-controls	
>  javafx-util-converter	
>  test-stub-toolkit
> I also think WebKit source modifications are open source somewhere.
> 
> It would be nice to have an equivalent list of modules which will be open sourced.
> 
> For example, it is unclear to me whether or not things like the browser plugin, the packaging infrastructure (javafx ant tasks and javafxpackager source) and the packager embedded launcher and fallback code will be open source.  Also, will all of the code for the native libraries supporting prism, glass, media, opengl and direct3d bindings be open source by February?

Right, deployment is an open question because I don't know what all the bits are in the javafx-deploy workspace right now. Certainly the JavaSE plugin / deployment code is not open source yet, and so I would imagine any FX bits derived from it will likewise not be open. But hopefully we can get a replacement in the open, much like IcedTea has for applets.

All the native libs for prism, glass, media, opengl, direct3d, etc should all be open sourced by February. Its a tall order (since native code is harder to finish security audits for), but that is definitely the goal. And definitely all of these will be open sourced.

The list of modules presently would include:

javafx-annotation-processor
javafx-util-converter
javafx-anim
javafx-beans
javafx-common
javafx-logging
javafx-mx-common
javafx-ui-common
javafx-concurrent
decora-compiler
decora-d3d
decora-es2
decora-jsw
decora-prism
decora-prism-ps
decora-prism-sw
decora-runtime
decora-sse
glass
javafx-font
javafx-geom
javafx-iio
javafx-sg-common
javafx-sg-prism
javafx-ui-quantum
pisces
prism-common
prism-d3d
prism-es2
prism-es2-eglfb
prism-es2-eglx11
prism-es2-mac
prism-es2-win
prism-es2-x11
prism-j2d
prism-null
prism-ps
prism-sw
prism-util
javafx-ui-desktop
decora-compiler
javafx-beans-dt
javafx-designtime
decora-d3d-native
decora-sse-native
javafx-font-native
javafx-iio-native
prism-common-native
prism-d3d-native
prism-es2-native
prism-sw-native
javafx-ui-charts
javafx-ui-controls
javafx-ui-webnode
webnode-prism
javafx-embed-swing
javafx-embed-swt
javafx-fxml

This doesn't include benchmarks or apps, just the core runtime libraries. Apps and benchmarks will also be added, and hopefully a pile of SQE tests.

> In terms of project infrastructure, any chance that github could be used as the primary infrastructure or as a mirror of the existing infrastructure (similar to how redhat manage Ceylon https://github.com/ceylon/)?  Access via github might help the project feel a little more accessible and a bit more like a community project than an Oracle project.   Just asking, I understand if the answer to that question is no.

I don't know how that would work? Certainly we want to host things on the openjfx / openjdk, especially as we get more integrated in their processes (gulp). However Danno has a bitbucket mirror up, would this be essentially the same thing? Its an open source project so mirroring the open bits is certainly not a problem, but the main repos will remain here on openjdk.

Cheers
Richard