OpenJFX just doesn't feel like a community-driven project, in a large part because of how contributors are told to "report" an issue to Oracle. That's what you do as a customer, not as a contributor. Contributors want to discuss issues and share their findings, and a mailing list really is no substitute for an openly accessible issue tracker like GitHub.
At this point in time and with the severely understaffed situation of the OpenJFX project, I think fully embracing GitHub and moving issue tracking and discussions over there would benefit the project tremendously. Am Sa., 20. März 2021 um 18:13 Uhr schrieb Philip Race <philip.r...@oracle.com>: > > Oracle has a very different mind set about privacy than Google or Facebook. > It might be very hard to convince the powers that be to add a "please > sell my personal information" checkbox .. > > -phil. > > On 3/20/21 8:16 AM, Abossolo Foh Guy wrote: > >> I'm surprised credit is considered important ... . > > > > You're right, but for some of your external contributors it's a > > business model useful to communicate with their employers or patrons. > > I tried to explain it in a Twitter post but without success :) GitHub > > is like a vitrine where one can see the community working. To be > > credited in the reprository is personnal satisfaction but it's also > > like receiving "java-coins", a win-win strategy without additional > > work from the owner since a gauge shows each contributor activity. > > > >> But FX never used the github bug tracker. ... > > https://github.com/javafxports/openjdk-jfx, did. A really amazing > > experience ! The new repository closed this first open window :( > > > > Guy. > > > > ------------------------------------------------------------------------------ > > > > > > Le 2021-03-19 20:37, Philip Race a écrit : > >> Interesting that there's no way to add an attachment (image or > >> otherwise). > >> I'll ask why that can't be made possible. > >> > >> I'm surprised credit is considered important but I think that the > >> current way of doing things is > >> more focused on protecting privacy of bug reporters and that they > >> might instead want their email addresses advertised > >> will quickly run into problems getting past that. > >> There's even an assurance on the bug submission form that your > >> personal info won't be shared. > >> > >> But FX never used the github bug tracker. It should never have been > >> possible to submit bugs there. > >> > >> > >> -phil. > >> > >> On 3/19/21 12:23 PM, John Neffenger wrote: > >>> On 3/19/21 11:05 AM, Philip Race wrote: > >>>> If this was important to him I don't understand why just a blog > >>>> post and not a bug report .. > >>> > >>> If I had to guess, it might be because, in the age of GitHub, this > >>> is not what people expect when they try to report a bug: > >>> > >>> Report a Bug or Request a Feature > >>> https://bugreport.java.com/bugreport/ > >>> > >>> There are two main problems: > >>> > >>> 1. You can't attach images. > >>> > >>> 2. You don't get credit. > >>> > >>> I speak from experience. I spent five years frustrated with a JavaFX > >>> font bug, but it was only when I could properly format a report and > >>> include images that I bothered to open this issue: > >>> > >>> Reduce color fringes in FreeType subpixel rendering > >>> https://github.com/javafxports/openjdk-jfx/issues/229 > >>> > >>> Formatting and images shouldn't matter, but two other people tried > >>> to report that bug using the Oracle Web form, and both were closed > >>> as "Not an Issue." You can send images later by e-mail, eventually, > >>> but that's not explained anywhere. > >>> > >>> There was a brief window when the OpenJFX project accepted bug > >>> reports on GitHub, but now it's back to the Oracle Web form. That > >>> brief window is the reason I'm a contributor to the project now. I > >>> understand the need for gate-keeping. We just shouldn't be too > >>> surprised when people decide that the gate's too high. > >>> > >>> I think Oracle could fix the two problems and keep the Web form, and > >>> we might get more quality bug reports instead of frustrated blog > >>> posts. I also think that it would help a lot to enable the JIRA > >>> markup[1] in the Java Bug System as Apache NetBeans has done. As an > >>> example, I can't imagine trying to report a bug like the following > >>> without formatting or in-line images: > >>> > >>> Attaching JavaFX Javadoc and Sources > >>> https://issues.apache.org/jira/browse/NETBEANS-3296 > >>> > >>> John > >>> > >>> [1] > >>> https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all >
