← Back to team overview

ubuntu-bugcontrol team mailing list archive

Re: Application for joining Ubuntu BugControl

 

Dear Thomas,

About these two bugs that were not valid in my application for joining the Ubuntu BugControl team, I found two great substitutes:

   After selecting to view hidden and backup files, they aren't shown
   until the window is closed
   <https://bugs.launchpad.net/nautilus/+bug/1161412>

       - I reported the bug myself, with rich detail.
       - I forwarded it upstream.
       - I would give it an importance of "low", since it's an
       usability issue that does not limit the functionality of the
       application.

   xSPIM application does not start
   <https://bugs.launchpad.net/ubuntu/+source/spim/+bug/824084>

       - I explained how this package dependencies where not correctly met.
       - I confirmed the bug was still there many releases after.
       - I tagged all the affected releases.
       - I reported the bug was still there and not as imagined by
       other user.
       - I added a work-around.
       - I would give it an importance of "high", since prevents the
       application from functioning at all and the work-around won't
       always on any Ubuntu release.

Thanks for your care,
Alberto


El 10/04/13 18:30, Thomas Ward escribió:
I should have rephrased.  Forgive me.

What I meant was do you have any examples of your own that you believe shows your ability to triage? The key point here is that two of the five bugs you posted weren't under Bug Control's purview. Do you have any other examples of bugs that are within Ubuntu which you've worked on, similar to the other three bugs you have already linked? They don't have to be the same, I'm looking for what you believe are good examples of your triage work on bugs within Bug Control's domain.

(Also, remember to hit "Reply All", so that the Bug Control mailing list is also included in your responses.)

------
Thomas

On Wed, Apr 10, 2013 at 9:55 AM, Alberto Salvia Novella <es20490446e@xxxxxxxxx <mailto:es20490446e@xxxxxxxxx>> wrote:

    El 08/04/13 18:44, Thomas Ward escribió:
    Hi there, Alberto!

    One of the things you'll need is patience, we're all busy working
    on bugs and such in preparation for the release of Raring later
    this month.

    I have a couple of concerns of the bugs you've selected to
    display as examples of your work.


    On Mon, Apr 8, 2013 at 12:20 PM, Alberto Salvia Novella
    <es20490446e@xxxxxxxxx <mailto:es20490446e@xxxxxxxxx>> wrote:

        El 22/03/13 05:52, Alberto Salvia Novella escribió:
        Here is my application:

        1. Do you promise to be polite to bug reporters even if they
        are rude to you or Ubuntu? Have you signed the Ubuntu Code
        of Conduct?

            Yes, I promise: I signed Ubuntu Code of Conduct years
            ago, and read it recently.

        2. Have you read Bugs/HowToTriage
        <https://wiki.ubuntu.com/Bugs/HowToTriage>, Bugs/Assignment
        <https://wiki.ubuntu.com/Bugs/Assignment>, Bugs/Status
        <https://wiki.ubuntu.com/Bugs/Status> and Bugs/Importance
        <https://wiki.ubuntu.com/Bugs/Importance>? Do you have any
        questions about that documentation?

            I have been an active member of Launchpad since 2007
            and, since then, the only operating system I have used
            in my computers has been Ubuntu. In this period I read
            these wiki-pages many times, and from start to end
            before writing this application.

        3. What sensitive data should you look for in a private
        Apport crash report bug before making it public? See
        Bugs/HowToTriage <https://wiki.ubuntu.com/Bugs/HowToTriage>
        for more information.

            - I should look for "CoreDump.gz" and remove it if the
            stack trace provides enough details.

            - I should check into "Stacktrace.txt" and
            "ThreadStacktrace.txt" for any sensitive information
            like passwords, bank account numbers, CSS keys, user
            names or server names.

        4. Is there a particular package or group of packages that
        you are interested in helping out with?

            There isn't. My objective is Ubuntu to be perceived
            stable as a hole, by working on bugs that are more
            obvious and making them to be triaged as fast as possible.

        5. Please list five or more bug reports which you have
        triaged and include an explanation of your decisions. Please
        note that these bugs should be representative of your very
        best work and they should demonstrate your understanding of
        the triage process and how to properly handle bugs. For
        *all* the bugs in the list, please indicate what importance
        you would give it *and* explain the reasoning. /Please use
        urls in your list of bugs./

            Bandwidth limit is not correctly enforced: Transmission
            delays are inserted between data chunk writes (of
            arbitrary sizes)
            <https://bugs.launchpad.net/ubuntuone-storage-protocol/+bug/720707>

            - I change the hole bug description to be as clear as
            possible. Also the original one didn't have proper steps
            to reproduce it.
            - I deeply investigated the origin of the bug and how to
            workaround it. I provided the tools to test it by the
            users themselves.
            - I would give it an importance of "high", since it has
            a moderate impact on a large portion of Ubuntu users.

    This above bug here isn't in the Ubuntu project itself, and
    unless I'm mistaken is outside the scope of bug control.
     (ubuntuone-storage-protocol project is not the same as the
    Ubuntu project and packages.)


            Misinformation when intending to download the 64-bit
            edition
            <https://bugs.launchpad.net/ubuntu-website-content/+bug/585940>
            - I completely rewrote the hole bug, since it didn't
            reflect the scope of the hole long discussion hold.
            - I would give it an importance of "low", since it's
            usability issue that does not limit the functionality of
            Ubuntu but rather creates a probable non-ideal
            configurations scenario.


    The above bug ALSO isn't in the Ubuntu project itself, and unless
    I'm mistaken is outside the scope of bug control.
     (ubuntu-website-content project is not the same as the Ubuntu
    project and packages.)


            Unable to upgrade "commercial/binary-i386/Packages"
            <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1072705>

            - I change the hole bug description to be as clear as
            possible.
            - I asked the user to add the missing log files as
            separate attachments, in order to have them
            automatically available. Also marked the bug as incomplete.
            - Also asked to gather information using apport, since
            it was missed.
            - I would give it an importance of "low", since the
            program itself suggest the origin of the problem is a
misconfiguration.
            upgrade issues 12.04=>12.10
            <https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1100189>
            - I transformed this but to a question, since the user
            made a cross-dependency issue himself by using an
            experimental ppa for xorg. So it wasn't a bug but a
            support request.
            - Since it is not longer a bug, its importance cannot be
            set. However is would give it an importance of "low",
            since it's hoped the user to be the only one affected.

            When selected partition is not focused, it becomes
            invisible
            <https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1079196>
            - I attached an screen-cast which clearly showed the
            problem, but now I think screen-casts are useless when
            the bug description is clear.
            - I would give it an importance of "low", since it's an
            usability issue that does not limit the functionality of
            the application.
            - I assigned the bug to the "Paper Cuts Ninja" project,
            since of its low importance in a application provided in
            the default installation.

        Or have a look at any other bug from the bunch I have here
        <https://bugs.launchpad.net/%7Ees20490446e>, although they
        aren't the most impressive in the world. But happy birthday
        to me: I recently got my twenty-fives and also got at the
        same time my hundred bugs worked in. And if you notice any
        errata in this application there will be no problem in
        asking me to improve it.

        Regards,
        Alberto Salvia Novella (es20490446e)
        <https://launchpad.net/%7Ees20490446e>


        El 08/01/13 15:10, C de-Avillez escribió:
        On Tuesday, January 08, 2013 00:36:30 Alberto Salvia Novella wrote:
        Please, accept me to join Ubuntu BugSquad and BugControl in Launchpad
        and I will show you what Raring is going to be. If you need more info
        about me and how familiar I am with the triaging process, you can have a
        look at my profile in Launchpad<https://launchpad.net/%7Ees20490446e>  <https://launchpad.net/%7Ees20490446e>.
        My fault there regarding the Ubuntu-BugSquad. I have added you in (and
        processed all other pending requests).

        For Ubuntu BugControl the process is different. You must show you understand
        how we use status and importance, and you must show bugs you triaged. This
        process is explained in [1].

        Cheers,

        ..C..


        [1]https://wiki.ubuntu.com/UbuntuBugControl



        So?

        --
        Ubuntu-bugsquad mailing list
        Ubuntu-bugsquad@xxxxxxxxxxxxxxxx
        <mailto:Ubuntu-bugsquad@xxxxxxxxxxxxxxxx>
        https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad


    Do you have any other specific selections of bugs you would like
    to showcase?

    (as well, bugsquad does not need to receive the application
    emails, so please do not include the bugsquad mailing list in
    your "To" or "Cc" fields)

    ------
    Thomas
    How could I find bugs where I will be able to clearly demonstrate
    I'm capable of managing them properly?



Attachment: smime.p7s
Description: Firma criptográfica S/MIME


Follow ups

References