JavaFX JIRA issues moving to JBS

[Adam Granger]

A crazy out-there suggestion...

Could OpenJDK work in partnership with stackoverflow on this through via
either a new tag - e.g.[javafx-possible-bug] or a whole new stackoverflow
site?

IMHO forums aren't the best way to work through coding problems, it's just
unorganised noise, the stackoverflow structured
question/answer/comment/vote approach is much better suited.... poor
quality questions (bug reports) will automatically get culled by the
crowd, sscce questions are encouraged, better community involvement
etc....

Adam.

> I will also add a suggestion that I think would be reasonable.  Take
> advantage of the OTN forum.  Anyone without a JBS account could be asked
> to
> post their first bug report to the forum.  If it's not a bug, the forum
> community can help with the issue.  The forum community can also help
> people learn to write a good bug report.
>
> If someone submits a decent quality bug report to the forum, they could be
> invited to use JBA.  The threshold could be more than one good bug report
> to the forum if needed.  That gives new users and entry point into the
> community and it filters out most of the noise on the actual bug tracker.
>
> You could probably even come up with a strategy for letting the community
> nominate people for JBS invites so the developers wouldn't have to sift
> through the forums looking for users that would make good JBS
> participants.
>
> Ryan Jaeb
>
>
>
> On Wed, Apr 15, 2015 at 10:03 AM, Fabrizio Giudici <
> Fabrizio.Giudici at tidalwave.it> wrote:
>
>> On Wed, 15 Apr 2015 17:55:19 +0200, Robert Krüger <krueger at lesspain.de>
>> wrote:
>>
>>  Understandable. IMHO a certain "seriousness threshold" to reduce the
>> noise
>>> makes sense.
>>>
>>
>> I was thinking on a score system such as the one at StackOverflow, but
>> I'm
>> not aware of any support of Atlassian.
>>
>>  What if you at least had a policy where someone in your team
>>> can propose people they know from the mailing list for a while for
>>> accounts? I don't think what's needed is to have a completely open
>>> system
>>> with one-click self-registration but don't draw the line where you draw
>>> it
>>> now, which means you're missing qualified input from people who are
>>> ready
>>> to invest qualified time (e.g. to build test cases and good
>>> descriptions
>>> of
>>> issues) but do not submit patches.
>>>
>>
>> I would add that having a corporate collective account could probably
>> help. I'm thinking of a case in which there are a couple of dozen
>> developers from the same corporate that could share the same email
>> alias.
>> Even in this case self-subscribing wouldn't be needed, actually it might
>> make sense to have a control process to be sure that the corporate
>> account
>> is official, I mean the corporate is in charge for it.
>>
>>
>> --
>> Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
>> "We make Java work. Everywhere."
>> http://tidalwave.it/fabrizio/blog - fabrizio.giudici at tidalwave.it
>>
>