On Sun, Jul 11, 2010 at 8:42 AM, Frank Murphy <frankly3d@xxxxxxxxx> wrote: > On 11/07/10 05:13, Kevin Kofler wrote: > >> Providing a patch is actually hard. Reporting a bug in the upstream bug >> tracker is just a matter of filling out the form, if the reporter refuses to >> do that, it's only pure laziness. >> >> Kevin Kofler >> > > It could be fear. > "Do these people (upstream) asking me this questions use Fedora?" > "What are these terms they are using?" > "I'm so out of my depth" > > Maybe wording could play a part on Fedoras' end? > > I am going to place this bug on the 'Developers Bug Tracker' > and will add you as a cc: > 1: So both of us will know what progress is made with the bug. > 2: In case there is any information they may need to ask you. > That would be nice, but AFAIK you can't Cc: people who are not registered on the bug tracker. But perhaps we could provide a template for a "file upstream" instruction, e.g.: 1. Why they need to file upstream. Frank's suggested wording sounds appropriate here 2. If this is a project that our Bugzilla understand, instruction on how to modify the Fedora bug report to include reference to the upstream bug 3. otherwise, instruction to Cc: the package owner when reporting the bug. Package owner should make sure that email address is registered on the upstream bug tracker Regards, -- Michel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
