ubuntu-bugcontrol team mailing list archive

[kurt belgrave <trinikrono@xxxxxxxxx>]

On Wed, Sep 14, 2011 at 11:46 AM, C de-Avillez <hggdh2@xxxxxxxxxx> wrote:

> On 08-09-2011 20:06, kurt belgrave wrote:
>
>  Hi Kurt
>
> >
> > On Wed, Sep 7, 2011 at 9:29 PM, David Tombs <cyan.spam@xxxxxxxxx
> > <mailto:cyan.spam@xxxxxxxxx>> wrote:
> >
> >     On 09/04/2011 12:53 PM, kurt belgrave wrote:
> >     > https://launchpad.net/~trinikrono
> >     <https://launchpad.net/%7Etrinikrono>
> >     <https://launchpad.net/%7Etrinikrono>
> >     >
> >     > 1. I Kurt Belgrave have signed the ubuntu code of conduct, i
> >     promise to
> >     > be nice to reporters even if they are meanies.
> >     >
> >     > 2. I understand the conventions used in HowtoTriage, Status and
> >     > Importance and if i do understand i will ask someone who
> >     knows better.
> >     > Also not to assign bugs to people or teams except in rare
> >     cases where
> >     > the bug is in progress.
> >     >
> >     > 3. I know how to mark a bug report visible, once it does not
> >     have any
> >     > personal info.
> >     >
> >     > 4. List of reports that i gotten to triaged
> >     >
> >     > <https://launchpad.net/bugs/787685>
> >     > https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/835920
> >     > https://bugs.launchpad.net/debian/+source/checkgmail/+bug/382267
> >     > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/355856
> >     > https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/236046
> >     > https://bugs.launchpad.net/ubuntu-website-content/+bug/710302
> >     > https://bugs.launchpad.net/ubuntu/+source/smplayer/+bug/606607
> >     >
> >     > Special mention
> >     >
> >     > https://launchpad.net/bugs/787685 - Reported bug so that
> >     apport will
> >     > pull grub.cfg.
> >     >
> >     > https://wiki.ubuntu.com/DebuggingPlymouth - Debugging info
> >     for Plymouth
> >     > that i made
> >     >
> >     > Joined Alpha Mentorship Program in March 16 it expires on
> >     the 13th of
> >     > this month so that is why i applying now :D
> >     >
> >     > Cheers
> >
> >     Hi there Kurt,
> >
> >     Thanks for applying, but you missed a couple instructions. Please
> >     improve your answer to #3 and, for each bug report, "indicate
> >     what importance you would give it and explain the reasoning."[1]
> >
> >     Thanks,
> >     David
> >
> >     [1] https://wiki.ubuntu.com/UbuntuBugControl#Application
> >
> > David
> > Please find missed instructions, thank you for your attention and
> > let me know if i can clarify anything else
> >
> >
> > #3 i would look for anything like passwords, servernames,
> > usernames bank account numbers in the stacktrace files
> > (Stacktrace.txt ThreadStacktrace.txt) before clicking make public
> > on the top right hand side. I need more practice with this i guess.
>
> And the coredump... why is it that most forget coredumps?
>
> A bug that has a coredump attachment *cannot* be made public.
>
> >
> > https://launchpad.net/bugs/787685 i would say medium because it
> > affects alot of users since it is asking for a change to the
> > information that apport collects.
>
> This is not a bug you triaged, this is a bug you opened. Even though
> it is a good finding, this is *not* triaging.
>
> * i just wanted to show a apport hook bug (i put this is at the last second
thinking it would of been nice to show, not as a serious evaluation, note i
had it as a mention)

> >
> > https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/835920 Low
> > I would say low because of the amount of users that are affected
> > by this bug are a small amount.
>
> I am unsure on what was done here as triage. All I see from your
> actions was to add an upstream task for the upstream bug the OP
> her/himself added in.
>
> Although this is a required step in setting a bug to triaged, there
> is still no real show of your triaging skills here.
>
* i was hoping you would of seen the other report(marked as a dupe), where i
found the bug in the upstream tracker, i should of specified that work was
done in that report also.
https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/792379


> >
> > https://bugs.launchpad.net/debian/+source/checkgmail/+bug/382267 Low
> > Again i would say low because small amount of users, and package
> > is in universe archive.
>
> Indeed. Good work, some comments:
>
> 1. It was a good idea -- sort of, see below -- to request a valgrind
> log. But we do not make any usage of these logs... upstream does.
>
> (On the other hand, the first valgrind has many entries with missing
> debug symbols; also, checkgmail is written in Perl -- as such,
> Valgrind was run against Perl... although it is possible to get some
> sense from the valgrind output and the actual Perl code, it is not
> as easy, or productive.)
>
> 2. I browsed upstream. My feeling is the project is either dead, or
> near death; last update was Nov/2010; there seems to be some few
> updates every year or so for a while. Perhaps it might be better to
> open a bug on Debian, they seem a bit more active there.
>
> >
> > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/355856 Wishlist
> > I say wishlist because it is a small feature request.
>
> Indeed.
>
> >
> > https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/236046 Low
> > Again Low, since the bug only appears when not using the default
> > theme in ubuntu, and they is a patch attached to the bug report,
> > so they is also a workaround availible.
>
> Good work. It seems Sandro (the Debian maintainer) will not apply it
> on our upstream (checkgmail comes from Debian for us).
>
> A good point Sandro makes is that we should also have opened a bug
> on Debian -- this matches my feeling that Debian (i.e., Sandro, the
> package maintainer) is much more active.
>
> To summarise this bug: upstream seems to be unresponsive; Debian has
> stated the patch in the bug will not be applied. So now we have to
> decide if this justifies a local delta (and we will then have to
> merge the Debian package), or if we close this bug WONTFIX. If we go
> for a local patch, this will have to be discussed with the MOTU,
> since this is an universe package.
>
> An observation for all: although in most cases the upstream we want
> is where the real developers code, Debian is an integral part of
> Ubuntu. Opening a corresponding bug in Debian (as upstream) is
> usually warranted, and a good way to have the Debian
> Developers/Maintainers involved.
>
> >
> > https://bugs.launchpad.net/ubuntu-website-content/+bug/710302 Medium
> > I would say medium since, anyone using the website would of been
> > of affected, so had the potential to affect anyone who was trying
> > to download the Netbook edition iso.
>
> Agreed.
>
> >
> > https://bugs.launchpad.net/ubuntu/+source/smplayer/+bug/606607 Low
> > Again Low, since only users that installed mplayer and then
> > smplayer would be affected, also smplayer still runs after
> > generating the error.
>
> Agreed.
>
> A pending +1...
>
> I am torn between a +0 and a +1. I have been following you on
> #ubuntu-bugs, and I know you have been more active, and doing a
> better work than what you show here. So my "pending +1": I am
> relying on what I know of you, not from what you are showing.
>
> I will use the moment and try to explain it a bit better to all (and
> will consider re-writing the instructions):  What we want to see
> here is your crème de la crème, the very best examples, of your
> triaging work. We want to know, to be sure, you understand how
> triaging goes on Ubuntu. You do not need to know all -- nobody does
> [1]. But you should strive to show us your very best. Really. You
> are going to be considered by what you show. Take your time, look
> around, select.
>
> Cheers,
>
> ..C..
>
>
>
> [1] well, except for the bugmeister, and a certain member of my
> tribe ;-)
>
>
> * i was not sure if to respond or not, so just my two cents for now. It
seems like most of my best work, never ended up with a triaged bug though,
alot of the times the bug would end up being invalid after all that work,
and i did not want to put those. Maybe if i can find a bug or two of better
quality to impress you guys more.
About the private bugs, if the bugs are private and only members of bug
control can see them, how would us as not being members find those bugs to
work on in the first place. I really have not seen a bug report that has
coredump.gz attached to it anyways, So i am wondering how would we get
experience in triaging private bugs if we can not see them in the first
place. I thought that we would get experience with them after joining bug
control but i may of missed a thing or two.

Cheers