Re: More community participation in JavaFX

On 07.02.2018 08:24, Johan Vos wrote: I'm still all in favour of Open Source, but it should be sustainable. Meta: I'd recommend reading the "Why Modern Open Source Projects Fail" paper from last year at https://arxiv.org/pdf/1707.02327.pdf for a thorough, and very useful analysis (rather than

Re: More community participation in JavaFX

com <mailto:kevin.rushfo...@oracle.com>> To: "openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>" <openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>>

Re: More community participation in JavaFX

;>>>>>> an upstream bug/feature request. Automating the >>>>>>> process with patch sets, >>>>>>> webrevs, formatting/lint >>>>>>> results, etc. would b

Re: More community participation in JavaFX

>> managed to build OpenJFX >>>>>> with OpenJDK on Win 10 I might have some >>>>>> relevant input. >>>>>> >>>>>> --- Building OpenJFX

Re: More community participation in JavaFX

>>>>to date ( >>>>> https://bugs.openjdk.java.net/browse/JDK-8194645 >>>>> <https://bugs.openjdk.java.net/browse/JDK-8194645>). >>>>>* The above doesn't mean that the process >>>>>

Re: More community participation in JavaFX

most open source > >>>> > >>>>projects > >>>> > >>>> on > >>>>Github (not advocating git over hg): clone > >>>>into the IDE

Re: More community participation in JavaFX

nJFX --- >>>> >>>>* It should be clear which tests need to run >>>> for a specific patch. >>>>Changes >>>>can be made anywhere from the documentation >>>

Re: More community participation in JavaFX

;>> * The Jcheck tool seems archaic to me. It >>> should be ported to IDE >>> formatters which are to be distributed with >>> the source. No reason to >&g

Re: More community participation in JavaFX

   To: "openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>"     <openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>>     Subject: More community participation in     JavaFX   

Re: More community participation in JavaFX

gt; To: "openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>" <openjfx-dev@openjdk.java.net <mailto:openjfx-dev@openjdk.java.net>>

Re: More community participation in JavaFX

>> 2018-02-06 14:29 GMT+01:00 dalibor topic : >>> >>> >>> >>> On 02.02.2018 00:26, Kevin Rushforth wrote: We are specifically looking to discuss ideas around the following areas: * Easing barriers to contribution (e.g., making JavaFX easier to

Re: More community participation in JavaFX

t know if it's technically >>>>>> >>>>>> >>>>> possible >>> >>> >>>> in this case, but it's a target. >>>>>> * The repository needs a good cleanup before contributors start >>>>>> >>>

Re: More community participation in JavaFX

On 02.02.2018 00:26, Kevin Rushforth wrote: We are specifically looking to discuss ideas around the following areas: * Easing barriers to contribution (e.g., making JavaFX easier to build, better documentation, making it easier to test changes) I'd suggest explicitly asking for feedback

Re: More community participation in JavaFX

Hi, Well Eclipse.org repositories at Github have support to track if you signed a CLA with the Eclipse Foundation and I'm unable to merge PRs if that check fails. Tom On 06.02.18 13:48, dalibor topic wrote: > > > On 05.02.2018 15:41, Kevin Rushforth wrote: >> Yes, this sounds like a good step

Fwd: More community participation in JavaFX

I don't kow if it is sufficient. But there's a CLA assistant for GitHub repositories: https://github.com/cla-assistant/cla-assistant Regards, Michael -- Michael Hoffer Twitter: @mihosoft Webpage: www.mihosoft.eu Goethe-Zentrum für Wissenschaftliches Rechnen (G-CSC) Goethe-Universität

Re: More community participation in JavaFX

On 05.02.2018 15:41, Kevin Rushforth wrote: Yes, this sounds like a good step in the right direction. This would give anyone (with a signed OCA) the ability to create their own branch, commit changes to it, submit a PR, etc. One non-obvious point to keep in mind is that you do need to make

Re: More community participation in JavaFX

> Date: Mon, 5 Feb 2018 08:11:05 +0100 > From: Alexander Ny?en <alexan...@nyssen.org> > To: Kevin Rushforth <kevin.rushfo...@oracle.com> > Cc: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > Subject: Re: More community participation in Ja

Re: More community participation in JavaFX

Yes, me too. I think it’s logical to establish *how* to make contributions first (and it’s great to see a lot of progress with this so far) but then there clearly needs to be a discussion of exactly *what* those contributions are, who decides which ones are important or permitted and how are

Re: More community participation in JavaFX

"I think a discussion on "where we should take the platform" is a good one to have...just not as part of this thread. " I'm looking forwards to the new thread :)

Re: More community participation in JavaFX

I think a discussion on "where we should take the platform" is a good one to have...just not as part of this thread. -- Kevin Stephen Desofi wrote: Yes, probably me. Sent from iCloud On Feb 03, 2018, at 09:35 PM, John-Val Rose wrote: Well, then one of us is "off

Re: More community participation in JavaFX

h organization instead of the current email system. I have no concrete solution for this. - Nir Message: 1 Date: Thu, 01 Feb 2018 15:26:24 -0800 From: Kevin Rushforth <kevin.rushfo...@oracle.com> To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.

Re: More community participation in JavaFX

t; definitely update a page or 2 there and so would other developers as > they > >>> gain knowledge. I don't know yet how permissions for that should be > >>> handled. > >>> * Code conventions should be clearly listed. > >>> * Separate sections with

Re: More community participation in JavaFX

Hi Kevin, the issue tracker is usually the first contact point for any future contributor. Making it publicly accessible would IMHO be an important first step. Be aware that before being appointed as author, one is not even allowed to reply to questions related to those issues one has created

Re: More community participation in JavaFX

gt;>> >>> --- Review policy --- >>> >>> * I have no experience with review policies or project roles so I can't >>> help here much (maybe after a discussion starts). >>> * One thing I do know is that reviewers should be extremely >>>

Re: More community participation in JavaFX

re aren't many qualified. Because of this, if it >> becomes "too" easy to contribute to OpenJFX, careful measures need to be >> taken as to not to swamp the few reviewers with many patches (though some >> would say this is an ideal situation). Some sort of review queue might &

Re: More community participation in JavaFX

tion for this. > > - Nir > > > Message: 1 > > Date: Thu, 01 Feb 2018 15:26:24 -0800 > > From: Kevin Rushforth <kevin.rushfo...@oracle.com> > > To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > > Subject: More communit

Re: More community participation in JavaFX

e solution for this. - Nir Message: 1 > Date: Thu, 01 Feb 2018 15:26:24 -0800 > From: Kevin Rushforth <kevin.rushfo...@oracle.com> > To: "openjfx-dev@openjdk.java.net" <openjfx-dev@openjdk.java.net> > Subject: More community participation in JavaFX > Message-ID: <5a73a

Re: More community participation in JavaFX

I looked up progress in Kotlin and Kotlin/native and you are right, they are doing most of the things I had suggested for JavaFX. Thanks, Steve Sent from my iPhone > On Feb 4, 2018, at 12:06 AM, John-Val Rose wrote: > > Well, if your interest is mainly in the

Re: More community participation in JavaFX

Well, if your interest is mainly in the future “cross platform king” of languages, you might just want to have a look at Kotlin and Kotlin/Native. Oh, and I have heard you can develop JavaFX apps with Kotlin too! > On 4 Feb 2018, at 13:37, Stephen Desofi wrote: > > Yes,

Re: More community participation in JavaFX

Yes,  probably me. Sent from iCloud On Feb 03, 2018, at 09:35 PM, John-Val Rose wrote: Well, then one of us is "off topic"... Kevin Rushforth: "We are specifically looking to discuss ideas around the following areas: * Easing barriers to contribution (e.g., making

Re: More community participation in JavaFX

Well, then one of us is "off topic"... Kevin Rushforth: "We are specifically looking to discuss ideas around the following areas: * Easing barriers to contribution (e.g., making JavaFX easier to build, better documentation, making it easier to test changes) * Code review policies * API /

Re: More community participation in JavaFX

John,      I think you and I are thinking on two different levels.    You are talking about the mechanics of making contributing to JavaFX easier.    I am talking about making the motivations of contributing to JavaFX easier. Steve Sent from iCloud On Feb 03, 2018, at 09:14 PM, John-Val

Re: More community participation in JavaFX

Stephen, 1. Swift and your "crystal ball" view of its spectacular success in the future has nothing whatsoever to do with making contributing to JavaFX easier. 2. Like everyone else who already wants to contribute to JavaFX, we don't need someone to provide us with "a compelling story as to why

Re: More community participation in JavaFX

John,      The point I am making is that Swift is catching up as a cross platform toolkit and is available on: Mac and iOS, (Full Support) https://www.swift.org Android (early) https://academy.realm.io/posts/swift-on-android/ Linux:  (early) https://itsfoss.com/use-swift-linux/ Windows:

Re: More community participation in JavaFX

Stephen - I’m not quite following you. This thread is about improving the ease with which the community can contribute to JavaFX. I see no point in comparing JavaFX (a cross platform graphics toolkit for JVM languages) with a Swift (a general purpose programming language that runs on Apple

Re: More community participation in JavaFX

Hi Chris, I'm more than happy to keep the community JavaFX build server at chriswhocodes.com running and host JDK 8/9/10/n + FX builds there. At the moment it's mostly used by the Raspberry Pi community to grab JavaFX overlays for JDK8 on ARM. I can also build and host OSX and Windows builds

Re: More community participation in JavaFX

This begs the question, why has the bar been set too low? I am new to this community and don’t know much history other than a couple weeks of bug fix messages flying by. I am not even clear of what our role and purpose is supposed to be. Are we here for only bug fixes, and follow the

Re: More community participation in JavaFX

I think Kevin outlined in his opening post what would be considered "out of scope". However, I agree with you on the basic premise that, in general, the bar has been set way too low as to the potential use cases and performance of JavaFX. In fact, I firmly believe that games & complex

Re: More community participation in JavaFX

I don’t understand why discussing new graphics capabilities such as gaming or WebGPU, etc is so off limits. Can you explain that? Steve Desofi Sent from my iPhone > On Feb 2, 2018, at 8:51 PM, Kevin Rushforth > wrote: > > Looks like we have some good discussion

Re: More community participation in JavaFX

Looks like we have some good discussion so far. I see a few themes emerging (build/test, sandbox on GitHub, ease of filing bugs, etc) along with some discussion on graphics performance (which is fine as long as the discussion doesn't veer too far into discussing specific graphics features).

Re: More community participation in JavaFX

enjfx-dev digest..." Today's Topics: 1. More community participation in JavaFX (Kevin Rushforth) 2. Re: More community participation in JavaFX (Michael Ennen) 3. Re: More community participation in JavaFX (Richard Steiger)

Re: More community participation in JavaFX

Hi, I fully agree with what you said with one exception. Via the bug report form it is possible to add any kind of attachments. So this is no problem. The rest is sadly true. Cheers Michael Am 02.02.18 um 18:29 schrieb John Neffenger: On 02/01/2018 03:26 PM, Kevin Rushforth wrote: We are

Re: More community participation in JavaFX

On 02/01/2018 03:26 PM, Kevin Rushforth wrote: We are specifically looking to discuss ideas around the following areas: * Easing barriers to contribution (e.g., making JavaFX easier to build, better documentation, making it easier to test changes) Thank you for asking. In my case, the

Re: More community participation in JavaFX

Hi Kevin, I'm more than happy to keep the community JavaFX build server at chriswhocodes.com running and host JDK 8/9/10/n + FX builds there. At the moment it's mostly used by the Raspberry Pi community to grab JavaFX overlays for JDK8 on ARM. I can also build and host OSX and Windows builds

Re: More community participation in JavaFX

ect line so it is more specific > than "Re: Contents of openjfx-dev digest..." > > > Today's Topics: > >1. More community participation in JavaFX (Kevin Rushforth) >2. Re: More community participation in JavaFX (Michael E

Re: More community participation in JavaFX

Kevin - thanks so much for this extremely well thought-out, informative and positive email. It’s the best post I’ve ever seen from Oracle on this list! It clearly highlights 2 things: 1. The future of JavaFX is heavily reliant on community involvement. 2. Oracle are actually listening to

Re: More community participation in JavaFX

Hi Kevin, As a long-time observer of the OpenJFX project, let me put all my chips at this point on making builds more stable, bullet-proof, and automated, and give equal weight making them so on Win10 and OS/X, specifically, the same weight as is given to making building and developing on

Re: More community participation in JavaFX

I think that having a public sandbox mirror on GitHub, as you mentioned, is a great idea. The idea is that PRs could be opened and the test suites could be run using CI for the platforms supported by JavaFX. The PR itself would never be directly merged into the OpenJFX hg repository. Instead the

More community participation in JavaFX

To: OpenJFX Developers We are looking to grow the community of contributors to the OpenJFX project, especially serious contributors who will stick around long enough to become reviewers, to help us keep the platform vibrant. To this end we are looking at ways to encourage more participation