Organizing
Differences between revisions 1 and 43 (spanning 42 versions)
|
Size: 11513
Comment: Initial draft
|
Size: 7348
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(BugSquad/Header)]] | <<Include(BugSquad/Header)>> |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 5: | Line 5: |
| Running a BugDay is a great way to get acquainted with the community and learn some new skills. |
Running a HugDay is a great way to get acquainted with the community and learn some new skills. It's all very informal so don't be shy. :) |
| Line 10: | Line 9: |
| Organizing a Bugday starts with choosing a list of bugs to hug. You can choose whatever packages matter most to you but here are few examples. ||<rowbgcolor="#FFEBBB"> '''Hotplugging Bugs:''' || '''Desktop Bugs:''' || '''Laptop bugs:''' || '''Networking bugs:''' || || [https://launchpad.net/ubuntu/+source/hal/+bugs hal] || [https://launchpad.net/~desktop-bugs/+packagebugs Bug overview] || [https://launchpad.net/ubuntu/+source/gnome-power-manager/+bugs gnome-power-manager] || [https://launchpad.net/ubuntu/+source/udev/+bugs udev] || || [https://launchpad.net/ubuntu/+source/gnome-volume-manager/+bugs gnome-volume-manager] || [https://wiki.ubuntu.com/DesktopTeam/Bugs Triaging Information] || [https://launchpad.net/ubuntu/+source/acpi-support/+bugs acpi-support] || [https://launchpad.net/ubuntu/+source/netcfg/+bugs netcfg] || || || || [https://launchpad.net/ubuntu/+source/acpid/+bugs acpid] || [https://launchpad.net/ubuntu/+source/netbase/+bugs netbase] || || || || [https://launchpad.net/ubuntu/+source/powernowd/+bugs powernowd] || [https://launchpad.net/ubuntu/+source/netbase/+bugs ifupdown] || || || || [https://launchpad.net/ubuntu/+source/pbbuttonsd/+bugs pbbuttonsd] || || || || || [https://launchpad.net/ubuntu/+source/kdeutils/+bugs klaptopdaemon] || || ||<rowbgcolor="#FFEBBB"> '''Crash reports:''' || '''KDE/Kubuntu Bugs:''' || '''Firefox Bugs:''' || '''["XSwat"] Bugs''' || || [https://launchpad.net/ubuntu/+bugs?field.searchtext=crash&search=Search crash] || [https://launchpad.net/~kubuntu-team/+packagebugs Bug list] || [https://launchpad.net/ubuntu/+source/firefox/+bugs?field.searchtext=&orderby=-priority%2C-severity&advanced=1&field.assignee=&field.unassigned.used=&field.include_dupes.used=&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status-empty-marker=1&field.severity-empty-marker=1&field.attachmenttype-empty-marker=1&search=Search Unconfirmed firefox bugs] || [https://launchpad.net/~ubuntu-x-swat/+packagebugs package overview] || || [https://launchpad.net/ubuntu/+bugs?field.searchtext=segfault&search=Search segfaults] || [https://launchpad.net/~jr/+assignedbugs more bugs] || || [http://tinyurl.com/9gs46 Unconfirmed Bugs] || || [https://launchpad.net/ubuntu/+bugs?field.searchtext=backtrace&search=Search backtrace] || [https://launchpad.net/ubuntu/+bugs?field.searchtext=kdebase+%7C+kdeutils+%7C+kdelibs+%7C+kdepim+%7C+kde-guidance+%7C+kubuntu-meta+%7C+adept+%7C+kaffeine+%7C+knetworkmanager&orderby=datecreated&search=Search&field.status%3Alist=Unconfirmed&field.importance%3Alist=Undecided&field.importance%3Alist=Medium&assignee_option=any&field.assignee=&field.owner=&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used= Untriaged bugs] || || [http://tinyurl.com/8oaky NeedsInfo Bugs] || || [https://launchpad.net/ubuntu/+bugs?field.searchtext=apport&search=Search Reported via apport] || || || [http://tinyurl.com/9zma4 Confirmed Bugs] || Other: * [https://launchpad.net/ubuntu/+source/gnome-screensaver/+bugs gnome-screensaver bugs] * [https://bugs.edge.launchpad.net/ubuntu/+source/linux Kernel Team Bugs Overview] |
Organizing a HugDay starts with choosing a list of bugs to hug. You can choose whatever packages matter most to you but check out [[UbuntuBugDay/Planning]] for previous and planned HugDay and add your ideas! |
| Line 35: | Line 13: |
| To make sure everyone is on the same track, and that there are no other plans for the week, send a simple e-mail to the following members of BugSquad who are regularly involved with the Hugday organization. The cookie cutter e-mail is just an example, you should put your own twist in. | To make sure everyone is on the same track, and that there are no other plans for the week, send a simple e-mail to BugSquad after adding your idea to the [[UbuntuBugDay/Planning]] page. The cookie cutter e-mail is just an example, you should put your own twist in. |
| Line 37: | Line 15: |
| pedro@ubuntu.com, yuriy.kozlov@gmail.com, nick.ellery@ubuntu.com, daniel.holbach@ubuntu.com, brian@ubuntu.com, dereck@gmail.com | ubuntu-bugsquad at lists.ubuntu.com |
| Line 40: | Line 18: |
| Hugday Target | HugDay Target |
| Line 52: | Line 30: |
| If you have a target in mind but not sure whether to add it to the Planning page just ask us at #ubuntu-bugs on FreeNode or contact PedroVillavicencio. == Wiki Planning == After identifying a target you need to add it to the Ideas section on the Planning page as described: * https://wiki.ubuntu.com/UbuntuBugDay/Planning?action=edit * Add your idea * Add your name to the organizers section |
|
| Line 57: | Line 44: |
| * https://wiki.ubuntu.com/BugSquad/Header?action=edit * Change the date for the next HugDay to yours, assuming that the listed HugDay has passed. |
=== Date Changes === After choosing a date you need to change three pages, those are: * https://wiki.ubuntu.com/BugSquad/Header/Hugday?action=edit |
| Line 60: | Line 50: |
| * Change the date for the next HugDay to yours, assuming that the listed HugDay has passed. | * https://wiki.ubuntu.com/Bugs/Events?action=edit * Move past HugDays down and put yours on the list === Hug day page creation === |
| Line 62: | Line 56: |
| * The date should be a combination of <year><month><day> 20080215 = Feb 15, 2008 * Paste the following into the new page and fill in the details * Save and keep reading on how to make the list of bugs semi automaticly |
* The date should be a combination of <year><month><day> 20100318 = March 18, 2010 * Select the UbuntuBugDay/TaskTemplate on the left side list when creating the new page. * <<<TARGET>>> should be replaced with your HugDay target * <<<DATE>>>> should be replaced with the date of the hug day for the 5-a-day statistics. * Save and keep reading on how to make the list of bugs semi-automatically |
| Line 66: | Line 62: |
| * You could use editmoin with the template page like so: | |
| Line 67: | Line 64: |
| [[Include(BugSquad/Header)]] ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| This week's Hug Day will focus on '''TARGET NAME'''! The goal of today's bug day will be to DESCRIBE THE REASON YOU CHOOSE THE TARGET. Here we have a sampling of bugs to work on for Hug Day. After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding '''lightgreen''' in the first cell of the column after "background-color:" and before ";". This will let people know that the bug in that row has been hugged. == 5-a-day-ing == During hug days you can also do [https://wiki.ubuntu.com/5-A-Day 5-A-Day] for this one you can do the following in order to tag your work on the hug day: * 5-a-day --add-tag hugday-20080710 * Add bugs to 5-a-day as usual * And when done with hug day run: 5-a-day --remove-tag hugday-20080710 == Stock Responses == '''Waiting for reply''' ## Add any common responses that might be useful for your huggers so they don't have to spend time to think one up or search for them. ["Bugs/Responses"] will be useful. Also add a comment to recomend when it should be used and other action than should be performed. Replace the example with your own brew. Set the status to 'invalid' if there is not enough information to fix the issue and the bug reporter has not responded to requests for more information. Reiterate the needed information for the record. {{{ Thank you for taking the time to report this bug and helping to make Ubuntu better. There has been no communication for over two months, I am setting the report to invalid until the needed information can be attached. Please attach the following information: * * * After attaching the information requested above, set the bug status to 'new' to signify that it is ready for triage / review. }} } ##remove the space here For '''other''' problem specific Stock Responses See: ["Bugs/Responses"] == 150 Bugs for '''Hug Target''' == '''To mark it off the list you should:''' * Verify the bug is still not fixed * Subscribe to the bug report * Comment with a stock reply or your own to get any needed info ||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || == Progress == ## it is nice to have pictures which you can do by directly linking to a graph at http://people.ubuntu.com/~brian/complete-graphs/ just by adding a hyperlink to the graph in the wiki page ## example - http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png ## at the end of day I usually save the graph to my local system and then add it as an attachment to the wiki page ## example - attachment:compiz-1day-new.png == More Bugs == ## If you think the list you made might be depleted, or want to let others know how to find similar bugs in the future, add a link to a 'live' version. This list is just a nibble of the [https://bugs.edge.launchpad.net/ubuntu/+expirable-bugs bigger picture]. ---- CategoryBugSquad |
editmoin -t UbuntuBugDay/TaskTemplate https://wiki.ubuntu.com/UbuntuBugDay/<Your Date Here> |
| Line 134: | Line 66: |
| Line 138: | Line 69: |
| In attempt to make sure the most recent bugs also are hugged but all timezones are considered, I would usually generate the list of bugs two days ahead of the big day. | In attempt to make sure the most recent bugs also are hugged but all timezones are considered, I would generate the list of bugs two days ahead of the big day. |
| Line 140: | Line 71: |
| === Bughelper === The first method is a command line utility designed just for this task. |
=== Ubuntu BugDay script === The Ubuntu Bug Day script from ubuntu-qa-tools will help create lists of bugs to target for the day. First grab the code with: |
| Line 143: | Line 76: |
| sudo apt-get install bughelper | bzr branch lp:ubuntu-qa-tools |
| Line 146: | Line 79: |
| Here are some example usages that will save the list to AFile.txt so that you can copy and paste the list to the wiki. {{{ bugnumbers --status=confirmed -p xorg --format=bugday --sort=nr --file=AFile.txt bugnumbers --status=Incomplete -p xorg --format=bugday --sort=nr --file=AFile.txt bugnumbers --status=New -p xorg --format=bugday --sort=nr --file=AFile.txt bugnumbers --status=New -p acpi-support --format=bugday --sort=nr --file=AFile.txt |
and for use it just pass the name of the target as: {{{ cd ubuntu-qa-tools/launchpadlib-scripts ./ubuntu-bugday.py --package alacarte |
| Line 153: | Line 85: |
First you need to authorize the script and if you did it correctly, the script will create a target.txt (ie: alacarte.txt) file with all the bug lists that you can copy & paste into the bug day page. If you discover any bugs about the tools please [[https://bugs.launchpad.net/ubuntu-qa-tools/+filebug | report them]]. |
|
| Line 157: | Line 93: |
| Copy the table of bugs into Open Office, then delete all the columns except the # and Description. Column A should be the bug #'s and B should be the description. Then fill C with the following formula. Now you can copy and paste column C to the wiki. | Copy the table of bugs into Open Office, then delete all the columns except the # and Description. Copy the following to cell A1: {{{ ||<rowstyle="background-color: ;"> [[https://bugs.launchpad.net/bugs/ }}} Make sure the ';' after background-color does not become a ','. If it does, change it back to ';'. Now copy the list of bug numbers to column B and the list of descriptions to column C. Now fill column D with the following: {{{ =CONCATENATE($A$1,B1,"|",B1,"]] || ",C1," || ||") }}} Now you can copy and paste column D to the wiki. == Announcement E-mail == Since the bug day page is now ready, now we just need people to know where to show up!, The Announcements needs to be sent at least two days before the bug day. Change your name, the dates, the target, and add any other information that might help that to triage those bugs, please notice that if you're not subscribed to those lists you need to ping a moderator to allow the message to go trough, just ask on #ubuntu-bugs for someone to moderate that message. |
| Line 159: | Line 110: |
| =concatenate("||<rowstyle=\"background-color: ;\"> [https://launchpad.net/bugs/",A1," ",A1," ] || ",B1," || ||") | ubuntu-bugsquad at lists.ubuntu.com, ubuntu-devel-announce at lists.ubuntu.com, ubuntu-bugcontrol at lists.launchpad.net, brian at ubuntu.com }}} {{{ Announcing the Next Ubuntu Bug Day! - <<<DATE>>> }}} {{{ Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* <<<TARGET>>>! * #<<<Number of New Bugs>>> New bugs need a hug * #<<<Number of Incomplete Bugs>>> Incomplete bugs need a status check * #<<<Number of Confirmed Bugs>>> Confirmed bugs need a review <<<What is the package being triaged and how is it important>>> Bookmark it, add it to your calendars, turn over those egg-timers! * <<<DATE>>> * http://wiki.ubuntu.com/UbuntuBugDay/<<<DATE>>> Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, YOUR NAME HERE [From the BugSquad] |
| Line 162: | Line 151: |
| == Announcement E-mail == The big day is ready, now we just need people to know to where to show up! For the same reasons as above, I would do this two days before the big day. Change to your name, the dates, the target, and add what spin you wish, it's your message! You will have to subscribe to each list before sending the mail. |
Inform the Ubuntu-News-Team about the next BugDay and its target '''until Saturday evening (The week before the BugDay)''' so they are able to add information about the BugDay to the [[https://wiki.ubuntu.com/UbuntuWeeklyNewsletter|Ubuntu Weekly Newsletter]]. You will have to subscribe to the list before sending the mail. |
| Line 166: | Line 155: |
| ubuntu-bugsquad@lists.ubuntu.com, ubuntu-devel-announce@lists.ubuntu.com, ubuntu-users@lists.ubuntu.com, ubuntu-news-team@lists.ubuntu.com, ubuntu-motu@lists.ubuntu.com, ubuntu-motu@lists.ubuntu.com, ubuntu-desktop@lists.ubuntu.com | ubuntu-news-team at lists.ubuntu.com |
| Line 168: | Line 157: |
| Line 169: | Line 159: |
| Hug Day!! | Announcing the Next Ubuntu Hug Day! - <<<DATE>>> |
| Line 171: | Line 161: |
| Line 172: | Line 163: |
| Fellow Ubuntu Lovers! | Hey folks, |
| Line 174: | Line 165: |
| My name is YOUR NAME, hanging around IRC as HANDLE HERE. I'm helping organize this week's HUG DAY! |
Here are the information for the next BugDay: |
| Line 177: | Line 167: |
| This week's target is *drum roll please* TARGET! * 135 New bugs need a hug * 39 Confirmed bugs just need a review Bookmark it, add it to your calenders, turn over your egg-timers! * Thursday July 03rd * http://wiki.ubuntu.com/UbuntuBugDay/20080703 Can't stress it enough: everyone can help! BLOG IT! Especially those on the Planet! There are people who want to help but don't know how and sit on the sidelines of the blog-o-sphere reading; I need your help to get those eyes from blogs to bugs. Let us combine blog-powers to educate, "Bug work is a fun way to get involved!" I think the best effect will be if we coordinate together in our blogs: * Publish about the Hug Day Thursday July 03rd to get everyone excited. * Hug some bugs and add yourself to the HugDay's wiki for your readers! Make a difference: Join the Hug Day on Thursday the 3rd. We will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/HelpingWithBugs |
Date: <<<DATE>>> Target: <<<TARGET>>> Page: https://wiki.ubuntu.com/UbuntuBugDay/<<<DATE>>> IRC: #ubuntu-bugs Infos: http://wiki.ubuntu.com/HelpingWithBugs/ |
| Line 206: | Line 176: |
| (from the BugSquad) | [From the BugSquad] |
| Line 209: | Line 179: |
| == Fridge Calendar == After announce the event please add it to the [[http://fridge.ubuntu.com|Fridge]] Calendar, instructions on how to do it are available [[https://wiki.ubuntu.com/Fridge/Calendar|here]] |
|
| Line 211: | Line 184: |
| Thank you! That's a message from me to you. | |
| Line 213: | Line 185: |
| Enjoy! and Thank you! That's a message from all the Ubuntu Bugsquad to you ;-). |
Running a HugDay is a great way to get acquainted with the community and learn some new skills. It's all very informal so don't be shy. 
Identify a Target
Organizing a HugDay starts with choosing a list of bugs to hug. You can choose whatever packages matter most to you but check out UbuntuBugDay/Planning for previous and planned HugDay and add your ideas!
Initial E-mail
To make sure everyone is on the same track, and that there are no other plans for the week, send a simple e-mail to BugSquad after adding your idea to the UbuntuBugDay/Planning page. The cookie cutter e-mail is just an example, you should put your own twist in.
ubuntu-bugsquad at lists.ubuntu.com
HugDay Target
Hi, I am ... from ... I enjoy ... and ... I would like to organize a HugDay for <package> on <date>. Are there any other plans for this day? Your Name Here. In accordance with https://wiki.ubuntu.com/UbuntuBugDay/Organizing
If you have a target in mind but not sure whether to add it to the Planning page just ask us at #ubuntu-bugs on FreeNode or contact PedroVillavicencio.
Wiki Planning
After identifying a target you need to add it to the Ideas section on the Planning page as described:
https://wiki.ubuntu.com/UbuntuBugDay/Planning?action=edit
- Add your idea
- Add your name to the organizers section
Wiki Stuff
After you're ready to run, add your HugDay to the wiki!
Date Changes
After choosing a date you need to change three pages, those are:
https://wiki.ubuntu.com/Bugs/Events?action=edit
Move past HugDays down and put yours on the list
Hug day page creation
https://wiki.ubuntu.com/UbuntuBugDay/<Your Date Here>?action=edit
The date should be a combination of <year><month><day> 20100318 = March 18, 2010
Select the UbuntuBugDay/TaskTemplate on the left side list when creating the new page.
<<<TARGET>>> should be replaced with your HugDay target
<<<DATE>>>> should be replaced with the date of the hug day for the 5-a-day statistics.
- Save and keep reading on how to make the list of bugs semi-automatically
- You could use editmoin with the template page like so:
editmoin -t UbuntuBugDay/TaskTemplate https://wiki.ubuntu.com/UbuntuBugDay/<Your Date Here>
Generate the bug list
In attempt to make sure the most recent bugs also are hugged but all timezones are considered, I would generate the list of bugs two days ahead of the big day.
Ubuntu BugDay script
The Ubuntu Bug Day script from ubuntu-qa-tools will help create lists of bugs to target for the day. First grab the code with:
bzr branch lp:ubuntu-qa-tools
and for use it just pass the name of the target as:
cd ubuntu-qa-tools/launchpadlib-scripts ./ubuntu-bugday.py --package alacarte
First you need to authorize the script and if you did it correctly, the script will create a target.txt (ie: alacarte.txt) file with all the bug lists that you can copy & paste into the bug day page.
If you discover any bugs about the tools please report them.
Open Office
Sometimes Bughelper cannot query what you want exactly, so to turn a search results from LaunchPad into the proper format for the wiki here you are.
Copy the table of bugs into Open Office, then delete all the columns except the # and Description.
Copy the following to cell A1:
||<rowstyle="background-color: ;"> [[https://bugs.launchpad.net/bugs/
Make sure the ';' after background-color does not become a ','. If it does, change it back to ';'.
Now copy the list of bug numbers to column B and the list of descriptions to column C. Now fill column D with the following:
=CONCATENATE($A$1,B1,"|",B1,"]] || ",C1," || ||")
Now you can copy and paste column D to the wiki.
Announcement E-mail
Since the bug day page is now ready, now we just need people to know where to show up!, The Announcements needs to be sent at least two days before the bug day. Change your name, the dates, the target, and add any other information that might help that to triage those bugs, please notice that if you're not subscribed to those lists you need to ping a moderator to allow the message to go trough, just ask on #ubuntu-bugs for someone to moderate that message.
ubuntu-bugsquad at lists.ubuntu.com, ubuntu-devel-announce at lists.ubuntu.com, ubuntu-bugcontrol at lists.launchpad.net, brian at ubuntu.com
Announcing the Next Ubuntu Bug Day! - <<<DATE>>>
Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* <<<TARGET>>>! * #<<<Number of New Bugs>>> New bugs need a hug * #<<<Number of Incomplete Bugs>>> Incomplete bugs need a status check * #<<<Number of Confirmed Bugs>>> Confirmed bugs need a review <<<What is the package being triaged and how is it important>>> Bookmark it, add it to your calendars, turn over those egg-timers! * <<<DATE>>> * http://wiki.ubuntu.com/UbuntuBugDay/<<<DATE>>> Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, YOUR NAME HERE [From the BugSquad]
Inform the Ubuntu-News-Team about the next BugDay and its target until Saturday evening (The week before the BugDay) so they are able to add information about the BugDay to the Ubuntu Weekly Newsletter. You will have to subscribe to the list before sending the mail.
ubuntu-news-team at lists.ubuntu.com
Announcing the Next Ubuntu Hug Day! - <<<DATE>>>
Hey folks, Here are the information for the next BugDay: Date: <<<DATE>>> Target: <<<TARGET>>> Page: https://wiki.ubuntu.com/UbuntuBugDay/<<<DATE>>> IRC: #ubuntu-bugs Infos: http://wiki.ubuntu.com/HelpingWithBugs/ Have a nice day, YOUR NAME HERE [From the BugSquad]
Fridge Calendar
After announce the event please add it to the Fridge Calendar, instructions on how to do it are available here
What Now?
Enjoy! and Thank you! That's a message from all the Ubuntu Bugsquad to you ;-).
UbuntuBugDay/Organizing (last edited 2017-10-10 05:01:07 by sbeattie)