JavaFX JIRA issues moving to JBS

[Ryan Jaeb]

My frustration isn't aimed at anyone on the list, so I hope it didn't seem
like that.

I don't usually post to the list, but I follow it enough to know that, once
we see an announcement like the one Kevin delivered, the decision has been
made and there's no going back.  If I've misinterpreted, I apologize.
Please correct me.

The thing that's particularly frustrating with this incident is that it's
going to have a predictable, negative impact on people like me who feel
like submitting bug reports is the most effect contribution we can make to
the JavaFX community.  Being told that we should engage the JBS folks after
the decision has been made isn't acceptable.  Whoever made the decision to
merge with JBS should already have engaged the JBS folks and advocated for
changes on behalf of the JavaFX community before the decision was
finalized.  The message Kevin delivered should have included the results of
that advocacy.

Regardless, what's done is done.  If we need to have someone engage the JBS
people to ask for policy changes, I think we'd do well to nominate whoever
made the original decision.  If they have enough influence to get a project
merged into the JBS, they're effort will be far more effective than that of
a random person from the community.

We've been told that Oracle wants to see more participation from the JavaFX
community.  This is an excellent opportunity for someone with a decision
making role at Oracle to take action and demonstrate to the community that
they're willing to help facilitate some of that participation.

Ryan Jaeb

On Wed, Apr 15, 2015 at 6:24 PM, Richard Bair <richard.bair at oracle.com>
wrote:

> > Why can't an effort be made to influence JBS policies before making the
> switch?
>
> I think the way to do this is to engage the JBS folks on their alias, I
> don’t think they watch this one and Kevin doesn’t have the ability to
> change this policy. He’s just the messenger!
>
> Richard