Developer focus for Fedora workstation

[Lars Seipel]

On Thu, Aug 21, 2014 at 01:13:07PM -0600, Chris Murphy wrote:
> If it can be fixed in Fedora, but we need more time or whatever to get it fixed, then I think we should block. But we're not allowed to block on anything vbox specific no matter what the problem or solution is.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1103496

The problem with that bug doesn't seem to be a lack of time but more a
lack of interest. If no one cares enough about the bug to go after it,
it won't get magically fixed by just waiting for it, except maybe by
coincidence. Blocking the release on it might coerce some contributor
into fixing it but that's not a viable long-term strategy for a project.

To support something you really need people interested in working on it.
In all the time that bug has been open apparently no one thought about
talking to Virtualbox upsream and going through the instructions for
debugging such issues. At least the bug shows no evidence of that.

This action has to come from Virtualbox users. Anyone else is unlikely
to set up a testing environment (which is a pretty invasive thing to do
with vbox and unlikely to work with recent kernels) to work on a bug he
or she personally does not care for.