Christian Robottom Reis <kiko@xxxxxxxxxxxxx> writes: > On Thu, Oct 02, 2008 at 09:15:12AM +0200, Reinhard Tartler wrote: >> While I don't think we can really solve this problem in the short term, >> it would be generally helpful if the launchpad bug describing and >> discussing the change would point to at least attempts to forward it >> upstream. This might be a bugtracker, a mailing list or an email with >> CC. > > Attempts to forward what? The patch to the upstream bugtracker or > contact? If my memory is correct, this (rather old thread) was about forwarding bugs upstream. This is mainly making the upstream developers aware of the issue. "The problem" here is that ubuntu developers need some coordination: - is the bug already forwarded? - is the bug already acknowledged upstream? - is the the bug report complete enough? - who has forwarded the bug? - who has received the report? bug links are almost ideal for that and they are already heavily used AFAIUI. It doesn't help much with point 3, however. Point 4 and 5 are also only answerable by looking at the remote bug tracker. And what about projects that do not use a (launchpad supported) bugtracker? >> As for the long to mid-term solution of the problem documenting how >> upstream prefers contributions/patches, perhaps launchpad could provide >> metadata about that in the project description and provide a link to >> that on the bug pages? > > If the project description was editable by you, would that be enough? that might work, however having an extra field with 'bug forwarding policy' editable by both project administrators and ubuntu developers would be even better, I'd think. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)