Are JBS' policies flexible enough to welcome the JavaFX community?

[Fabrizio Giudici]

On Mon, 20 Apr 2015 10:55:33 +0200, Mario Torre <neugens at redhat.com> wrote:

> On Fri, 2015-04-17 at 11:24 +0200, Fabrizio Giudici wrote:
>> I can't speak in number, because I only have my perspective, and the one
>> of customers. But comments about workarounds are fundamental to me - let
>> me add: even the lack of comments about workarounds, because in the end
>> what one needs is to have his app working
>
> But I don't think this is the bug database role, this is for a knowledge
> base forum.

I think that bug databases are excellent in this role, indeed it doesn't  
matter a lot the kind of infrastructure, bug tracker or forum. If it's  
HTML, human-readable and googlable, it's ok. In the past I've found myself  
googling around for problems (e.g. with Hibernate) and I got the  
solution... into my own instance of Jira, where years before I've posted a  
problem+workaround about one of my projects, that in the end was related  
to the Hibernate problem. Since the issue was well described, there was  
the workaround I originally applied to my code (which proved to work fine  
even for my more recent need) and the link to the original Hibernate bug,  
to have the details.

> A bug database is a place to file bugs, not to offer customer support or
> workarounds, offering workarounds in a bug report should be limited to a
> minimum and only for particularly nasty, widespread, or un-fixable bugs.

See above - plus, in the old bugs.sun.com there's a specific place for  
workarounds. What is the rationale for restricting the policy for  
documenting workarounds? What are the benefits of writing less information?

>
> If the JavaFX Community needs such a place, it should create a separate
> tracking system that offer workarounds and help triaging those bugs into
> the main bug database.

To me either is fine, the only requisite is that the info is easily  
traceable and googlable. The important point is that the path from  
entering the search in google about the bug and getting to the best  
information about the bug, including workarounds, is the shortest.  
Honestly I think that this happens when all the info are in the same place.


-- 
Fabrizio Giudici - Java Architect @ Tidalwave s.a.s.
"We make Java work. Everywhere."
http://tidalwave.it/fabrizio/blog - fabrizio.giudici at tidalwave.it