BugDays
Overview
Ubuntu One bug days are no longer active.
How to help
The Ubuntu One team appreciates all the help we get from the community. Our bug days are another way you can help us make Ubuntu One better. You can do this by helping us triage bugs. Below is the information you'll need to do this.
Communication
Please join us on #ubuntuone on IRC to get and give help to all working on Ubuntu One bugs.
Resources
The links below may be helpful:
UbuntuOne/BugWorkFlow - Start here to understand how to properly mark bugs as you triage them
UbuntuOne/Bugs - Provides tips, tricks and common issues you may see along the way
Common bug triage scenarios
The list of bugs you'll triage are new and need an initial response. Below are the most likely scenarios you will run into and how to best go about handling them:
Known issue - You've either seen this behavior before or can find it documented in the Ubuntu One Common Bugs wiki page. Mark the bug as a duplicate of the appropriate bug number and leave the following response (replacing XXXXXX with the duplicate bug number):
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug XXXXXX, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.
Need more information - Bugs that aren't duplicates and don't have a known fix/workaround may need more information. Look at the Procedures and Responses section of the Ubuntu One bugs wiki page for ways to request the information and which information the look for. Set the bug status to Incomplete.
New issue that can be confirmed - Bugs that are new (no known duplicates exist) and can either be reproduced by you or another user should have their bug status set to Confirmed. An importance should also be set. Ask an Ubuntu One team member on the #ubuntuone IRC channel for help on determining and setting importance. For reference on determining importance, see Setting Importance section of the Ubuntu One bug triage wiki page. A comment along these lines should be left for the user:
I'm sorry to hear Ubuntu One isn't working properly for you. I am marking this bug as confirmed and the Ubuntu One team will look into it further. If you find anymore information that you think might help, please add it to this bug report. Thank you,
New feature request - Bugs that are asking for new functionality should have their status set to Wishlist. It's best to do a quick search on Ubuntu One wishlist bugs to see if this request can be marked as a duplicate. If it is a duplicate, mark it as such with the appropriate bug number. Leave a comment similar to this one for the user:
Thank you for your taking the time to file this bug report! I'm marking this as a Wishlist item since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu One. The Ubuntu One team will consider adding this feature in the future.
Bugs to work on
New bugs for package: ubuntuone-client
Total: 258
New bugs for package: ubuntuone-control-panel
Total: 8
New bugs for package: ubuntu-sso-client
Total: 2
New bugs for package: bindwood
Total: 5
New bugs for package: couchdb
Total: 11
New bugs for package: couchdb-glib
Total: 0
New bugs for package: desktopcouch
Total: 78
New bugs for package: erlang
Total: 19
New bugs for package: evolution-couchdb
Total: 6
New bugs for package: libubuntuone
Total: 6
New bugs for package: pyinotify
Total: 2
New bugs for package: python-configglue
Total: 0
New bugs for package: python-couchdb
Total: 1
New bugs for package: rhythmbox-ubuntuone-music-store
Total: 65
New bugs for package: ubuntuone-storage-protocol
Total: 1
New bugs for package: ubuntuone-control-panel
Total: 8
UbuntuOne/BugDays (last edited 2011-02-10 21:56:51 by 173-25-16-30)