On 2 January 2014 10:44, Suvayu Ali <fatkasuvayu+li...@gmail.com> wrote:
> On Thu, Jan 02, 2014 at 10:36:43AM +0000, Dave Cross wrote:
>> On 2 January 2014 09:51, Patrick O'Callaghan <pocallag...@gmail.com> wrote:
>> >
>> > On Thu, Jan 2, 2014 at 9:26 AM, Dave Cross <dav...@gmail.com> wrote:
>> >>
>> >> I realise that I haven't given you enough to go on here, but these
>> >> kinds of problems are well outside my Linux experience. Tell me what
>> >> diagnostics will we helpful and I'll provide them.
>> >
>> > It would be worth reporting this kind of problem to Bugzilla (two reports,
>> > one for each problem). Feel free to post the BZ links here.
>>
>> Good suggestion. Thanks.
>>
>> Suspend: https://bugzilla.redhat.com/show_bug.cgi?id=1047828
>> Wifi: https://bugzilla.redhat.com/show_bug.cgi?id=1047831
>>
>> It's slightly annoying that Bugzilla insists on you giving a
>> component. I have no idea what is causing these problems so in both
>> cases I've guessed at "kernel" (because they seem pretty fundamental
>> problems to me).
>
> Without a component, it might go to the wrong developer.  I think the
> idea is to choose your best guess.  If there is a mistake, the dev can
> change it to the appropriate component later on.  In this case kernel
> sounds about right to me.

That's a fair point, but I worry that an experienced bug reporter
(like me) would be more likely to assign it to the wrong component
than an experienced bug triager who volunteered to assign the
unassigned bugs.

But then I'm probably just inventing work for experienced Fedora
contributors who have far better ways to spend their time :-)

Dave...

-- 
Dave Cross :: d...@dave.org.uk
http://dave.org.uk/
@davorg
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Reply via email to