Is JavaFX going to truly be a community project?
Werner Van Belle
werner at yellowcouch.org
Sat Sep 1 13:05:23 UTC 2018
Just put it on github and let people fork it however they want.
That would be "open".
PS: I _am_ seriously pissed at Oracle about this shit. I spend the last
years specializing in their newest technology 'which they would never
ever drop' and now they just drop it.
On Sat, 2018-09-01 at 22:38 +1000, John-Val Rose wrote:
> Hi Pedro,
> I just happen to agree with you in this issue.
> But, out of all the possible new custodians of JavaFX, I have to say
> that I am always in awe of what Johan and Gluon have already
> contributed and accomplished.
> So how do we ensue that OpenJFX is truly “open”?
> I agree that even though Gluon are doing a fantastic job, JavaFX
> should not be a “Gluon product”.
> I think it’s a great move for Oracle to basically relinquish control
> of JavaFX - but to whom?
> I’m not familiar enough with FOSS projects to offer any sage advice
> but I totally agree that a “community” project has to be as open to
> everyone as possible and no person or entity should have a commercial
> advantage over others.
> So, basically I like your question, I don’t believe the current
> scenario is satisfactory but unfortunately I confess I can’t offer
> any suggestions of better scenarios.
> John-Val Rose
> > On 1 Sep 2018, at 22:00, Pedro Duque Vieira <pedro.duquevieira at gmai
> > l.com> wrote:
> > Hi,
> > For JavaFX to start being, truly, a community project it is
> > important that
> > it is perceived as a real community effort. Right now it's starting
> > to look
> > more like it's changing hands, from being an Oracle project to
> > being a
> > Gluon project.
> > I don't have anything against Gluon, I'd say the same if for
> > instance,
> > instead of Gluon it was JPro or Karakun, or whatever...
> > Hosting the JavaFX docs, builds, installations, etc on a company
> > owned site
> > or a company endorsed site sounds like a really bad idea. Which is
> > what's
> > happening right now. If it's to be a community project it should be
> > owned
> > by the community as a whole. As well as being perceived to be owned
> > by the
> > community as a whole.
> > Being a one company project will deter the contributions of other
> > players
> > in the JavaFX space. Other players that also offer consultancy
> > services,
> > and JavaFX products will have a big disadvantage towards the
> > company
> > hosting the JavaFX assets and downloads. At the very minimum think
> > about
> > the huge advantage this company will have in publicity when
> > compared to the
> > others.
> > A community project is a project where various players join efforts
> > to
> > mutually benefit each other. As soon as this starts being a project
> > that's
> > benefiting one particular company more than the others it ceases to
> > be a
> > community project.
> > I don't think that anyone would like to join in on the efforts in
> > this
> > scenario.
> > Thanks,
More information about the openjfx-dev