What Oracle Could Do For GlassFish Now

  1. Move the sources to GitHub (GitHub is the most popular collaboration platform). It is more likely for an individual to contribute via GitHub, than the current infrastructure.
  2. Introduce a business friendlier license like e.g. the Apache license. Companies interesting in providing added value (and commercial support) on top of existing sources would appreciate it.
  3. Implement GitHub-based, open source, CI system with nightly builds.
  4. Introduce a transparent voting process / pull-request acceptance process.
  5. Release more frequently.
  6. Keep https://glassfish.java.net as the main hub.

Community involvement is good for innovation beyond the scope of Java EE.

However: we will still need full-time engineers (and so Oracle) for the implementation of Java EE 8 RI. Java EE API implementation is far less fun and hard work. Oracle did so far a great job by writing the specifications and implementing them.

Such a bold move would foster innovation and make Java EE even more popular. Moving GlassFIsh sources to GitHub would also significantly boost Java's ranking in GitHub's programming languages index :-).

Dropping commercial support for GlassFish could also have positive effects. Modernization of the collaboration platform and making the contribution process more frictionless could indeed give GlassFish a contribution boost.


Fully agree! Is there any way to discuss this will Oracle?

Posted by Łukasz on November 08, 2013 at 06:57 PM CET #

Fully agree, too!

Also, a mirror with mercurial will be great :)

Posted by Santos ZV on November 09, 2013 at 05:49 AM CET #

It would be great if Glassfish were set up for frictionless contribution. Maybe I'd spend a day or so trying to fix the damn "Long running process" modal in the Admin interface that's been bugging me since V3 ;-)

Posted by Barry van Someren on November 09, 2013 at 01:44 PM CET #

That would indeed be a very bold and strong move from the side of Oracle. Nice thinking. It hadn't occurred to me that dropping commercial support for GlassFish could be laid out as a move forward the way you put it. I hope you'll be heard!

Posted by Lukas Eder on November 12, 2013 at 10:08 AM CET #

Brilliant ideas! Let's get the entire Java community behind this!

Posted by Jim Bethancourt on November 12, 2013 at 07:20 PM CET #

I think it is an excellent idea. Look how OpenOffice took-off after support faded!

Posted by will on December 20, 2013 at 01:57 PM CET #

It's on :)

Java EE is moving to GitHub!


Posted by Michal Stankay on April 19, 2017 at 06:27 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments