Not too impressed with the quality of F14 at this time

["Jóhann B. Guðmundsson"]

  On 09/13/2010 08:17 PM, Michal Jaegermann wrote:
> See, for example,
> https://bugzilla.redhat.com/show_bug.cgi?id=624316
> which kills video after suspend on a particular laptop running F12
> and F13 but which maintainer does not want to touch.  There is a
> patch there.  It can be argued that this is a kernel bug but in
> practice that does not help very much.
> https://bugzilla.redhat.com/show_bug.cgi?id=546994  is still NEW.

As the maintainer mention in comment  6 [1]

"Thanks for info. AFAIK KMS should correctly work without quirks, that's 
why the quirks are removed. I checked with my Intel graphics and 
everything is working OK without quirks. Thus this seems to be a bug 
related to your HW that should be fixed in kernel driver. Quirks from 
user space is not correct way how to handle it and also it can break 
things for other users -> I will reassign this to kernel."

I agree with the maintainers perspective that things should be dealt 
with at the root of the problem not worked around them.

However he forgets to reassign this to the kernel as he mentions he's  
going to do,

Now if a maintainer responds that this is not my component but component 
y reporters should not hesitated to reassign the bug themselves to the 
component that the maintainer points out/suggests that is the correct 
one and many maintainers expect the reporter to do that since after all 
he will need to provide necessary feed back to the maintainers of the 
component that the report got assigned to.

So basically the rule of thumb is if a maintainers says its not his 
component but that one and he does not reassigned the bug report to that 
component immediately then do it your self right away.

I just reassigned the bug 624316 to xorg-x11-drv-intel so the intel 
maintainers actually get a chance to look at it.

I'm not so sure we have any Intel ninja on board with us so..
( we got David for radeon and Ben for nouveau )

Perhaps someone from FESCO can chime in what's the policy in situation 
like this bug ( regression deliberate being created to flush out bugs 
but not made sure the bugs that get reported get fixed at the proper 
level ).

1. https://bugzilla.redhat.com/show_bug.cgi?id=624316#c6