Seeking perfection, one day at a time

User information

Launchpad Id:
Log in for email information.

<email address hidden>
Member since:
Icon of APTonCD-Dev Team Icon of Landscape Icon of Laptop Testing Team Icon of Launchpad Beta Testers Icon of Launchpad Translators Icon of Launchpad Users Icon of League of Scripters Icon of Martin Pitt's fan Icon of Ubuntu Brazilian Members Icon of Ubuntu Brazilian Planet Icon of Ubuntu Chumby Hackers Icon of Ubuntu Drivers Icon of Ubuntu Members Icon of Ubuntu Phone Icon of Ubuntu Server Team Icon of Ubuntu-Women Project
Signed Ubuntu Code of Conduct:
Ursinha on
_starbuck on
OpenPGP keys:
025EEA90, 77EDE89F
SSH keys:
Brazilian Portuguese, English, English (United Kingdom)
Time zone:
America/Sao_Paulo (UTC-0300)
1316 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?