Ursula Junque

Seeking perfection, one day at a time

User information

Launchpad Id:
ursinha
Email:
Log in for email information.
Jabber:
<email address hidden>
Member since:
2007-02-11
Icon of APTonCD-Dev Team Icon of Canonical Launchpad Engineering Icon of Laptop Testing Team Icon of Launchpad Beta Testers Icon of Launchpad Development mailing list Icon of Launchpad Documentation Team Icon of Launchpad Translators Icon of Launchpad Users Icon of League of Scripters Icon of Ubuntu Brasil Icon of Ubuntu Brazilian Members Icon of Ubuntu Brazilian Planet Icon of Ubuntu Chumby Hackers Icon of Ubuntu Drivers Icon of Ubuntu Local Community Teams Icon of Ubuntu Members Icon of Ubuntu Phone Icon of Ubuntu Server Team Icon of Ubuntu-Women Team
Signed Ubuntu Code of Conduct:
Yes
IRC:
Ursinha on irc.freenode.net
_starbuck on irc.freenode.net
OpenPGP keys:
025EEA90, 77EDE89F
SSH keys:
ursula@devpad
ursula@neverlaio
ursula@neverlaio
ursula@neverlaio
Languages:
Brazilian Portuguese, English, English (United Kingdom)
Time zone:
America/Sao_Paulo (UTC-0300)
Karma:
1990 Karma help

All assigned blueprints Assigned blueprints

Rationale: We have lots and lots of bugs filed on a daily basis, bugs that could, given a set of heuristics, be automatically triaged. By triaged we mean flagged as important/unimportant. We want to do that with some level of certainty, to avoid missing important reports but removing the need of manually triaging ev...
How will we build the list of desktop bugs that we think we should work on the during the LTS cycle? The current list from Pedro and Qa are a nice but they only cover selected set, how do we get visibility on i.e foundation issues, kernel bugs, plymouth issues, etc that impact on what we are doing?