JavaFX JIRA issues moving to JBS
Fabrizio.Giudici at tidalwave.it
Wed Apr 15 09:13:32 UTC 2015
> I had not realized that ...
Just be safe that everybody here is aligned to the focus of the
discussion... As I previously said, I think the problem lies with the
access policy. From the JBS official page:
OpenJDK Roles, Groups, and Projects are explained in the OpenJDK Bylaws.
This JBS guide will use terms defined in the bylaws; the bylaws should be
consulted for details.
An individual with at least one OpenJDK Project role of Author or higher
has sufficient cause to get a JBS account. A JBS account grants an
individual general read and write access to issues, including the ability
to file new issues, transitioning issues among the states of the workflow,
adding comments, changing field values (including adding and removing
labels). The holder of a JBS account can also be the assignee of an issue.
A user's JBS username is his or her OpenJDK name. The password reset page
can be used both to reset a lost password and to establish a an initial
At the time of launch, self-service account creation is not supported.
Users without an account can browse JBS anonymously or use bugs.sun.com to
view a time-delayed and simplified snapshot of bug state. Users without an
account can also use bugs.sun.com to submit an issue. When such an issue
is submitted, a record is created in the Java Incidents (JI) project in
JBS; at the time of launch, the JI project is not publicly visible. Issues
in the JI project have an identifier like JI-9XXXXXX, where the numeric
portion corresponds to the bug identifier sent back to the submitter.
After an initial triage process, if the incidents needs further review, it
can be transferred to be an issue in the JDK project. When such a transfer
occurs, the issue gets a new identifier in the JDK project (JDK-8YYYYYY)
but references to the original JI-9XXXXXX number will be redirected.
There are a few points to discuss, and sure everybody has his own
priority. For me, one of the most important ones is the capability to
comment. For instance, today I can go here (issue picked at random)
https://javafx-jira.kenai.com/browse/RT-30705 and add a comment, because
perhaps I've run into the issue and I have something to add. If I don't
have an account, because it's my first time, I can istantly create one at
Kenai. I have a few customers using JavaFX (as well as many other FLOSS
projects) and sometimes they run into an issue; I encourage them to
directly login and report/comment.
From what I see, JBS still doesn't support self-creation of accounts. I
don't have one, if I remember well, because I don't have any role in
OpenJDK projects. For the kind of job I do, that is a consultant focused
on Java, perhaps I can ask for one and perhaps Oracle would grant one (to
be verified). But I don't think this would apply for a common employee of
a corporate that, among other things, also develops in Java; not
mentioning that not having the possibility of instantly signing in is not
good, and would discourage almost everybody I know. The "bridge" offered
by bugs.sun.com is cumbersome too. In any case, this is completely
different from any other FLOSS project around, where access to the issue
tracker is immediate and easy.
I think this expands the point that some earlier mentioned about being a
"user" vs a "developer" of OpenJDK.
I understand that, being Java so popular, Oracle might fear some kind of
massive, low-level posting of issues, that would be expensive to manage.
If this is the case, let's discuss it.
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giudici at tidalwave.it
More information about the openjfx-dev