> Date: Tue, 12 Jun 2007 19:31:19 +1200 > From: Matthew Paul Thomas <[EMAIL PROTECTED]> > Subject: Re: Remote bug tracker > To: Launchpad-users Users <launchpad-users@lists.canonical.com> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > Hello Shirish
Hello Matthew, > On Jun 12, 2007, at 1:56 AM, shirish wrote: > > > > Hi all, > > Interesting system remote bug watch > > https://launchpad.net/bugs/bugtrackers I registered two remote bug > > watches but was unable to register 2 . Perhaps because they use the > > same base url ? > > > > Case in point :- > > 1. Libburnia, cdrskin and Libisofs all of them use one bug tracker, > > similar perhaps to GNOME bugzilla . Now I was able to register > > Libburnia & did do the needful for cdrskin as well as libisofs but > > they aren't there. Can somebody see what I'm doing wrong ? > > Why are you trying to register the same bug tracker twice? My mistake I realized later on. Sorry. > > Also how do I link them to the source packages ? > > The "Packaging information" page for libburnia, for example > <https://launchpad.net/libburnia/+distributions> describes how: "To add > a Packaging Record, visit the page for the specific release series that > has been packaged, and select 'Link to Any Package'." > > > 2. Can it be made so there is an e.g. for people who are new to > > registering a remote bug tracker. > > > > It isn't helpful when you get > > > > -------- > > > > An URL-friendly name for the bug tracker, such as "mozilla-bugs". > > > > when it would have been perhaps more better to have > > > > An URL-friendly name for the bug tracker, such as "mozilla-bugs". > > ... > > I'm not sure what you mean. Can you give an example of the type of help > you would like? The webpage is user-unfriendly. https://bugs.beta.launchpad.net/bugs/bugtrackers/+newbugtracker The required ones are :- Name (Required) Title (Required) Summary (Required) Base URL (Required) Contact details (Required) and finally the Add button :P for reference I used https://bugs.beta.launchpad.net/bugs/bugtrackers/ati-linux-bugs/+edit when I was adding the remote-bug tracker . Now the ones which are problematic are 1. The differences between Name (Required) & Title (Required) are they always the same or are there differences sometimes. This does confuse newcomers. In the reference model its one & the same. If this is true in all cases then why is Title (Required) there, it could be some kind of silent thing so the name becomes the Title. If there can be differences then something which illustrates what choices or needs to be written should be pointed out. 2. Another thing which is confusing is the way the page is structured wouldn't it be much much better if for e.g. we had something like :- Name (Required) An URL-friendly name for the bug tracker, such as "mozilla-bugs". (box to fill) Summary (Required) A brief introduction or overview of this bug tracker instance. (box to fill) Base URL (Required) The top-level URL for the bug tracker. This must be accurate so that Launchpad can link to external bug reports. (box to fill) Contact details (Required) The contact details for the external bug tracker (so that, for example, its administrators can be contacted about a security breach). (box to fill) It could be (box to fill) and then the instruction or the order above either of it doesn't make a difference as all the info. is in one place. Right now it does add to the confusion esp. for noobs. 3. Contact Details (Required) While its ok when there is a single admin or something like that what if there are co-developers or more than one contact details. would something like [EMAIL PROTECTED], [EMAIL PROTECTED] & so on & so forth is good or needs only one. Apart from re-designing the page for point 2 (which is confusing for me) the other answer perhaps would be to link the same to a help/example page for noobs like me so the trial & error things will happen a lot less. I spent well over 2 hrs. trying out things wrestling against the system & then put the bug in launchpad. Another thing, there needs to be a team or place to notify when a new bug tracker is done. I am not the project admin or anything for a remote bug tracker but would like that the bug tracker gets associated as upstream not limited to n no. of packages using the same bugzilla. For e.g. GNOME bugzilla which has so many products for which it is the bugzilla. Lastly, if there is a bug & upstream is available then which upstream to choose ? Hypothetical :- Let's say I have problem with the deluge-torrent package, now I do know that deluge-torrent package is firstly packaged by debian while the deluge guys also have their own trac (bugzilla) where they provide support. In this case should I choose one or can I choose both? sending a bug report to debian as well as posting the same at deluge so both people can look & find a solution. Sorry for the mail being so long. Cheers ! > Cheers > -- > Matthew Paul Thomas > http://mpt.net.nz/ > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: PGP.sig > Type: application/pgp-signature > Size: 186 bytes > Desc: This is a digitally signed message part > Url : > https://lists.ubuntu.com/archives/launchpad-users/attachments/20070612/7198dfe9/attachment-0001.pgp > > ------------------------------ -- Shirish Agarwal This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/ 065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17 -- launchpad-users mailing list launchpad-users@lists.canonical.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users
