Comments on: Downstream: Sugar Labs reporting Fedora tickets http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-tickets/ Braindumps on things Mel Chua has found shiny lately. Sun, 12 Feb 2012 18:28:26 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: C. Scott Ananian http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-tickets/comment-page-1/#comment-2391 C. Scott Ananian Mon, 10 Aug 2009 14:50:43 +0000 http://blog.melchua.com/2009/08/06/downstream-sugar-labs-reporting-fedora-tickets/#comment-2391 In the project I'm currently employed by, Ubuntu is our upstream. If you look at https://bugs.launchpad.net/bugs/+filebug the first question is an either/or "Distribution & package" or "Project", and then a one-line summary line. Special projects like ours get a special "Project name". You just enter that in the "Project" box and then you can skip all the confusing "what package is this in" stuff and enter the bug report. Our upstream engineer will sometimes reassign or fork a bug to an upstream package if it turns out to be an upstream problem, but the point is that it's easy to (a) get the bugs into the tracker, (b) look at all the "sugar" bugs (because they'd be in the "sugar" project, and (c) track upstream changes required to support the "sugar" project bugs (using the standard bug dependency features of the bug tracker). I believe that making a custom frontend page of this sort for Fedora's bug tracker is possible -- it's just a custom HTML form which submits to the standard Fedora bugzilla url but pre-fills some fields, or else a custom servlet which takes some info and preprocesses it before *then* generating an HTML form which submits to the standard Fedora bugzilla. I think that would help a lot with guiding people through submitting upstream bugs. In the project I’m currently employed by, Ubuntu is our upstream. If you look at https://bugs.launchpad.net/bugs/+filebug the first question is an either/or “Distribution & package” or “Project”, and then a one-line summary line. Special projects like ours get a special “Project name”. You just enter that in the “Project” box and then you can skip all the confusing “what package is this in” stuff and enter the bug report. Our upstream engineer will sometimes reassign or fork a bug to an upstream package if it turns out to be an upstream problem, but the point is that it’s easy to (a) get the bugs into the tracker, (b) look at all the “sugar” bugs (because they’d be in the “sugar” project, and (c) track upstream changes required to support the “sugar” project bugs (using the standard bug dependency features of the bug tracker).

I believe that making a custom frontend page of this sort for Fedora’s bug tracker is possible — it’s just a custom HTML form which submits to the standard Fedora bugzilla url but pre-fills some fields, or else a custom servlet which takes some info and preprocesses it before *then* generating an HTML form which submits to the standard Fedora bugzilla. I think that would help a lot with guiding people through submitting upstream bugs.

]]>