- As a member of the ~ubuntu-foundations-team <https://launchpad.net/~ubuntu-foundations-team> I would like to be a member of the ~ubuntu-bugcontrol <https://launchpad.net/~ubuntu-bugcontrol>. -
> *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 promise to be polite to bug reporters even if they are rude to me. I am aware that bug reporters may perceive me as a representative of the Ubuntu community, so it is very important that I give a good impression. I have signed the Ubuntu Code of Conduct (See: ~dviererbe <https://launchpad.net/~dviererbe>). *2. Have you read Bugs/Triage <https://wiki.ubuntu.com/Bugs/Triage>, > Bugs/Assignment <https://wiki.ubuntu.com/Bugs/Assignment>, Bugs/Status > <https://wiki.ubuntu.com/Bugs/Status> and Bugs/Importance > <http://Bugs/Importance>? Do you have any questions about that > documentation?* > Yes I have read all the listed documents. I currently have no questions, but I will ask for guidance from my team colleagues if required. *3. What sensitive data should you look for in a private Apport crash > report bug before making it public? See Bugs/Triage > <https://wiki.ubuntu.com/Bugs/Triage> for more information.* > I am aware of the Bugs/Triage "Apport Crash Reports" Section <https://wiki.ubuntu.com/Bugs/Triage#Apport_crash_reports>. Just to summarize what I have read/learned there: - A bug containing a Coredump.gz attachment should *never* be marked as public, because it could contain private/sensitive data. - I should check any stacktrace attachments if they contain anything that looks like sensitive data passed as function arguments (e.g. passwords, bank account numbers, keys, usernames, server names). - There is no requirement to make a report public. Keeping it private in most cases is fine. *4. Is there a particular package or group of packages that you are > interested in helping out with?* > Bug tasks/packages I will work with as a member of the ~ubuntu-foundations-team <https://launchpad.net/~ubuntu-foundations-team> (e.g. bug tasks tagged foundations-todo, packages in proposed which are blocked, dotnet related packages). *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.* > Unfortunately I do not have a proper answer for this question, but Graham Inggs (~ginggs <https://launchpad.net/~ginggs>) recommended that I should apply nonetheless. I have "triaged" only 2 bugs until now: - LP#1990621 PXE Boot contains wrong suggested link to ISO for live file system <https://bugs.launchpad.net/ubuntu/jammy/+source/casper/+bug/1990621>I would have rated this as LOW, because it is a bug that affects a non-essential aspect and limited scope of the application with a low impact. - LP#1992159 [SRU] Syntax error defien in socket.h <https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1992159>I would have rated this bug also as LOW, because it has an easy work-around (just correcting the header file locally) and has a low impact. Best Regards, Dominik Viererbe
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
