ubuntu-bugcontrol team mailing list archive

[Sudip Mukherjee <sudipm.mukherjee@xxxxxxxxx>]

Hi,

I am Sudip (sudip in irc and sudipmuk in launchpad). Relatively new to
Ubuntu ecosystem but I am a DD for quite a few years now. I am sure you
must have seen me in irc (#ubuntu-bugs) requesting to assign a certain
series to some bugs. And that is the main reason why I will like to join
the Ubuntu Bug Control Team so that I don't have to distub others all
the time with my request to assign series to bugs when they might be
doing something important.

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?

I have signed the Ubuntu Code of Conduct, and I do promise to continue
being polite to bug reporters even if they behave rudely.

2) Have you read Bugs/Triage, Bugs/Assignment, Bugs/Status and Bugs/Importance?
   Do you have any questions about that documentation?

I have read those documents, and have no questions.

3) What sensitive data should you look for in a private Apport crash report bug
   before making it public? See Bugs/Triage for more information.

Anything that looks like personal information, like email address,
full names, password, bank account numbers, encryption keys, credit card
numbers, social security numbers etc.

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

I am mostly interested in Universe packages. Its community maintained and seems
to have more bugs untriaged or unfixed compared to packages in Main.

5) Please list five or more bug reports which you have triaged and include
   an explanation of your decisions.

a) https://bugs.launchpad.net/ubuntu/+source/lxqt-archiver/+bug/2052880

The reporter first tried by reporting upstream and when upstream rejected
the issue, the reporter opened a bug in Ubuntu.

Since I could reproduce the bug with Noble and also with Debian, I reported
the bug to Debian. And then worked with upstream developers to fix the issue
upstream and then add the relevant patch to Ubuntu via sponsored upload.

So, accordingly the bug was marked as Confirmed and then "In Progress"
when I started working on that and then back to Confirmed when I added
Ubuntu Sponsors.

I would have set the importance to Medium as the package is mostly usable
and only one particular feature was affected.

b) https://bugs.launchpad.net/ubuntu/+source/mirage/+bug/1994145

The importance for this one should have been High as the application was
completely unusable on all releases.

Worked with upstream to find the initial workaround and then had to go to
upstream cpython developers also and they identified the problem. which
was then fixed in upstream mirage and then Ubuntu and in Debian.

Status was changed to Confirmed, then "In Progress" when I started workig
on that and then back to Confirmed when I added Ubuntu Sponsors.

c) https://bugs.launchpad.net/ubuntu/+source/fsvs/+bug/1875642

The importance for this one should have been Medium as the package was
still usable. It only affected those users who used SVN via HTTP.
With upstream's help the issue debugging was done and subsequently was
fixed in Debian as a QA upload and then in all Ububtu releases.

Status was initially marked as "Fix commitied", that was done by upstream.
But that was wrong status, I changed it to New and opened upstream issue.
And then marked Noble status as "Fix Released" when the Debian fix was
synced.

d) https://bugs.launchpad.net/ubuntu/+source/color-picker/+bug/2036267

The importance for this one should have been High as opposed to Critical
which has been set in this bug. The application was completely unusable
on all releases but it did not affect the whole system and so should not
be Critical.

After debugging the fix was sent to upstream and also then fixed in all
Ubuntu release via sponsored upload.

Status was changed to Confirmed, then "In Progress" when I started workig
on that and then back to Confirmed when I added Ubuntu Sponsors.

e) https://bugs.launchpad.net/ubuntu/+source/linphone/+bug/2047458
The importance for this one should have been High as the application was completely unusable.
Status was marked as Confirmed after I could reproduce the issue.


-- 
Regards
Sudip