Organizing
Differences between revisions 2 and 15 (spanning 13 versions)
|
Size: 11419
Comment: Announcement Mailing List change
|
Size: 8022
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@lists.ubuntu.com |
| Line 40: | Line 18: |
| Hugday Target | HugDay Target |
| Line 57: | Line 35: |
| * https://wiki.ubuntu.com/UbuntuBugDay/Planning?action=edit * Add your idea * Move past HugDays down to the 'past' section. |
|
| Line 67: | Line 48: |
| [[Include(BugSquad/Header)]] | <<Include(BugSquad/Header)>> |
| Line 69: | Line 50: |
| ||<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 71: | Line 52: |
| 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. | This week's Hug Day will focus on '''thunderbird'''! The goal of today's bug day will be to provide better desktop integration with one of the most popular mail clients. |
| Line 73: | Line 54: |
| 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. | 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 '''rowbgcolor='''. This will let people know that the bug in that row has been hugged. |
| Line 77: | Line 58: |
| 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: | |
| Line 78: | Line 60: |
| 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 |
* 5-a-day --add-tag hugday-20080828 |
| Line 82: | Line 62: |
| * And when done with hug day run: 5-a-day --remove-tag hugday-20080710 | * And when done with hug day run: 5-a-day --remove-tag hugday-20080828 |
| Line 86: | Line 66: |
| ## You should add any stock responses that might be useful on this page as well. | |
| Line 87: | Line 68: |
| '''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. |
For problem specific Stock Responses see: [[Bugs/Responses]] |
| Line 90: | Line 70: |
| 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. |
|
| Line 94: | Line 71: |
| Please attach the following information: * * * |
== 39 New Bugs == '''To mark it off the list you should:''' * Verify the bug is still not fixed * Request any needed info, Subscribe, Status to incomplete '''or''' * Set status to Confirmed |
| Line 99: | Line 77: |
| 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 |
||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || ||<rowbgcolor=lightgreen> [[https://launchpad.net/bugs/258849|258849]] || thunderbird-bin crashed with signal 5 in gdk_x_error() || Dereck || |
| Line 104: | Line 82: |
For '''other''' problem specific Stock Responses See: ["Bugs/Responses"] == 100 Bugs for '''Hug Target''' == |
== 36 Confirmed Bugs == |
| Line 112: | Line 85: |
| * Subscribe to the bug report * Comment with a stock reply or your own to get any needed info |
* Request any needed info, Subscribe, Status to incomplete '''or''' * Set status to Confirmed |
| Line 120: | Line 93: |
| ## example - http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png | |
| Line 124: | Line 96: |
| http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png | |
| Line 128: | Line 101: |
| This list is just a nibble of the [https://bugs.edge.launchpad.net/ubuntu/+expirable-bugs bigger picture]. | This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/grub|bigger picture]]. |
| Line 142: | Line 115: |
'''Due to an update in the wiki software, this is broken, please use the Open Office Method''' |
|
| Line 148: | Line 124: |
| 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 |
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 |
| Line 159: | Line 135: |
| =concatenate("||<rowstyle=\"background-color: ;\"> [https://launchpad.net/bugs/",A1," ",A1," ] || ",B1," || ||") | =CONCATENATE("||<rowbgcolor=none> [[https://launchpad.net/bugs/";A1;"|";A1;"]] || ";B1;" || ||" ) |
| Line 164: | Line 140: |
Please also e-mail [[BrianMurray|bdmurray]] to have you mail to ubuntu-devel-announce moderated in a timely fashion. |
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@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
Wiki Stuff
After you're ready to run, add your HugDay to the wiki!
https://wiki.ubuntu.com/UbuntuBugDay/Planning?action=edit
- Add your idea
Move past HugDays down to the 'past' section.
https://wiki.ubuntu.com/UbuntuBugDay/<Your Date Here>?action=edit
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
<<Include(BugSquad/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| This week's Hug Day will focus on '''thunderbird'''! The goal of today's bug day will be to provide better desktop integration with one of the most popular mail clients. 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 '''rowbgcolor='''. 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-20080828 * Add bugs to 5-a-day as usual * And when done with hug day run: 5-a-day --remove-tag hugday-20080828 == Stock Responses == ## You should add any stock responses that might be useful on this page as well. For problem specific Stock Responses see: [[Bugs/Responses]] == 39 New Bugs == '''To mark it off the list you should:''' * Verify the bug is still not fixed * Request any needed info, Subscribe, Status to incomplete '''or''' * Set status to Confirmed ||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' || ||<rowbgcolor=lightgreen> [[https://launchpad.net/bugs/258849|258849]] || thunderbird-bin crashed with signal 5 in gdk_x_error() || Dereck || == 36 Confirmed Bugs == '''To mark it off the list you should:''' * Verify the bug is still not fixed * Request any needed info, Subscribe, Status to incomplete '''or''' * Set status to Confirmed ||<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 ## 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 http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/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.launchpad.net/ubuntu/+source/grub|bigger picture]]. ---- CategoryBugSquad
Generate the bug list
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.
Bughelper
The first method is a command line utility designed just for this task.
Due to an update in the wiki software, this is broken, please use the Open Office Method
sudo apt-get install bughelper
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
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. 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.
=CONCATENATE("||<rowbgcolor=none> [[https://launchpad.net/bugs/";A1;"|";A1;"]] || ";B1;" || ||" )
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.
Please also e-mail bdmurray to have you mail to ubuntu-devel-announce moderated in a timely fashion.
ubuntu-bugsquad@lists.ubuntu.com, ubuntu-devel-announce@lists.ubuntu.com, ubuntu-users@lists.ubuntu.com, ubuntu-news-team@lists.ubuntu.com
Hug Day!!
Fellow Ubuntu Lovers! My name is YOUR NAME, hanging around IRC as HANDLE HERE. I'm helping organize this week's HUG DAY! 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 Have a nice day, YOUR NAME HERE (from the BugSquad)
What Now?
Thank you! That's a message from me to you.
UbuntuBugDay/Organizing (last edited 2017-10-10 05:01:07 by sbeattie)