Organizing

Differences between revisions 14 and 16 (spanning 2 versions)
Revision 14 as of 2008-08-27 21:48:06
Size: 8018
Editor: adsl-99-149-118-30
Comment:
Revision 16 as of 2008-10-13 17:56:20
Size: 7831
Editor: oscar
Comment: *sniff sniff* keepin' it fresh. :)
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
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! 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 44: Line 44:
  * 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
  * Paste the following into the new page and fill in the details 
  * <<<TARGET>>> should be replaced with your HugDay target
  *
Save and keep reading on how to make the list of bugs semi-automatically
Line 52: Line 53:
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. This week's Hug Day will focus on '''<<<TARGET>>>'''!
Line 60: Line 61:
 * 5-a-day --add-tag hugday-20080828  * 5-a-day --add-tag hugday-20081016
Line 62: Line 63:
 * And when done with hug day run: 5-a-day --remove-tag hugday-20080828  * And when done with hug day run: 5-a-day --remove-tag hugday-20081016
Line 71: Line 72:
== 39 New Bugs == == 112 New Bugs ==
Line 78: Line 79:
||<rowbgcolor=lightgreen> [[https://launchpad.net/bugs/258849|258849]] || thunderbird-bin crashed with signal 5 in gdk_x_error() || Dereck ||



== 36 Confirmed Bugs ==



== 37 Incomplete Bugs ==
Line 84: Line 84:
 * Change the bug's status to "Confirmed" or "Triaged" if the reporter replied with enough information '''or'''
 * Ask a secondary follow up question and subscribe to the bug report

||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||



== 40 Confirmed Bugs ==
'''To mark it off the list you should:'''
Line 85: Line 95:
 * Request any needed info, Subscribe, Status to incomplete '''or'''
 * Set status to Confirmed
 * Request any needed info, Subscribe, Status to incomplete or
 * Set status to triaged [[UbuntuBugControl]]
 
Line 89: Line 99:

Line 96: Line 108:
http://people.ubuntu.com/~brian/complete-graphs/compiz/plots/compiz-1day-new.png {{http://people.ubuntu.com/~brian/complete-graphs/gnome-power-manager/plots/<<<TARGET>>>-1day-triaging.png}}
Line 101: Line 113:
This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/grub|bigger picture]]. This list is just a nibble of the [[https://bugs.launchpad.net/ubuntu/+source/<<<TARGET>>>|bigger picture]].
Line 135: Line 147:
=CONCATENATE("||<rowbgcolor=> [[https://launchpad.net/bugs/";A1;"|";A1;"]] || ";B1;" || ||" ) =CONCATENATE("||<rowbgcolor=none> [[https://launchpad.net/bugs/";A1;"|";A1;"]] || ";B1;" || ||" )
Line 141: Line 153:
Please also e-mail [[BrianMurray|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
{{{
ubuntu-bugsquad@lists.ubuntu.com, ubuntu-devel-announce@lists.ubuntu.com, ubuntu-users@lists.ubuntu.com, ubuntu-news-team@lists.ubuntu.com brian@ubuntu.com
Line 150: Line 160:
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
Fellow Ubuntu Triagers!

This week's HugDay target is *drum roll please* <<<target>>>!
 * ### New bugs need a hug
 * ### Incomplete bugs need a status check
 * ### Confirmed bugs need a review

<<<What is the package being triaged and how is it important>>>

Bookmark it, add it to your calenders, turn over those egg-timers!
 * Thursday October 16th
 * http://wiki.ubuntu.com/UbuntuBugDay/20081016
Line 165: Line 176:
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.
Have some time? Triage boogz! I won't be upset if you get a headstart~ ;)
Have a blog? Blog about Hugday!
Have some screen space? Open #ubuntu-bugs and keep an eye out for
newcomers in need.
Have minions? Teach THEM to triage for you! :)


Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and
night, and will be ready to answer your questions about how to help.
Line 179: Line 187:
   http://wiki.ubuntu.com/HelpingWithBugs  http://wiki.ubuntu.com/HelpingWithBugs
Line 184: Line 192:
  (from the BugSquad) [From the BugSquad]

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. Smile :)

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!

<<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 '''<<<TARGET>>>'''! 

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-20081016
 * Add bugs to 5-a-day as usual
 * And when done with hug day run: 5-a-day --remove-tag hugday-20081016


== 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]]


== 112 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''' ||



== 37 Incomplete Bugs ==
'''To mark it off the list you should:'''
 * Change the bug's status to "Confirmed" or "Triaged" if the reporter replied with enough information '''or'''
 * Ask a secondary follow up question and subscribe to the bug report 

||<rowbgcolor="#FFEBBB"> '''Bug''' || '''Subject''' || '''Triager''' ||



== 40 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 triaged [[UbuntuBugControl]]
 
||<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/gnome-power-manager/plots/<<<TARGET>>>-1day-triaging.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/<<<TARGET>>>|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.

ubuntu-bugsquad@lists.ubuntu.com, ubuntu-devel-announce@lists.ubuntu.com, ubuntu-users@lists.ubuntu.com, ubuntu-news-team@lists.ubuntu.com brian@ubuntu.com

Hug Day!!

Fellow Ubuntu Triagers!

This week's HugDay target is *drum roll please* <<<target>>>!
 * ### New bugs need a hug
 * ### Incomplete bugs need a status check
 * ### Confirmed bugs need a review

<<<What is the package being triaged and how is it important>>>

Bookmark it, add it to your calenders, turn over those egg-timers!
 * Thursday October 16th
 * http://wiki.ubuntu.com/UbuntuBugDay/20081016


Can't stress it enough: everyone can help!

Have some time? Triage boogz! I won't be upset if you get a headstart~ ;)
Have a blog? Blog about Hugday!
Have some screen space? Open #ubuntu-bugs and keep an eye out for
newcomers in need.
Have minions? Teach THEM to triage for you! :)


Make a difference; 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.


CategoryBugSquad

UbuntuBugDay/Organizing (last edited 2017-10-10 05:01:07 by sbeattie)