An interesting read when discussing what to do about our bugs...

Jon Ciesla limb at jcomserv.net
Wed Jan 23 20:20:01 UTC 2008


> On Wed, 23 Jan 2008 11:06:22 -0900
> "Jeff Spaleta" <jspaleta at gmail.com> wrote:
>
>> I think you are wrong. Dead wrong.
>> it does absolutely no good for me to attempt to act as a proxy for
>> hardware breakage that I can't re-confirm with my own hardware.  At
>> some point the person experiencing the hardware problem has to be able
>> to talk directly with a developer who is in a position to confirm and
>> fix.  Whether that means driving upstream developers to the fedora
>> bugreport or driving users to upstream developers.... it doesn't
>> matter. I refuse..REFUSE... to stop asking users with hardware
>> specific breakage to be proactive and tap into the upstream resource
>> when I can't confirm the problem.
>
> There is a huge difference between engaging the user and helping them
> to contact upstream, or getting upstream in contact with the user,
> basically facilitating that wonderful communication, and saying "Shut
> up, that's upstream, go away" and closing the bug.

Very true, it MUST be a collaborative exercise.

> --
> Jesse Keating
> Fedora -- All my bits are free, are yours?
> --
> fedora-devel-list mailing list
> fedora-devel-list at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list


-- 
novus ordo absurdum




More information about the fedora-devel-list mailing list