GlobalBugJam
|
Size: 1184
Comment:
|
Size: 4407
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ||<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 3: | Line 3: |
| {{{ __ _____ ____ \ \ / /_ _| _ \ \ \ /\ / / | || |_) | \ V V / | || __/ \_/\_/ |___|_| }}} |
{{http://farm4.static.flickr.com/3265/2550528941_5677fdf41e_o.png}} |
| Line 15: | Line 9: |
| On the weekend of the '''27th June''' to '''29th June''' we'll do the same, globally! | On the weekend of the '''20 February''' to '''22 February''' we'll do the same, globally! [[http://digg.com/linux_unix/Announcing_the_next_Ubuntu_Global_Bug_Jam|Digg It!]] |
| Line 20: | Line 16: |
| * Make sure you read RunningBugJam - it has a lot of information on | * Make sure you read '''RunningBugJam''' - it has a lot of information on |
| Line 23: | Line 19: |
| * running the jam and * soliciting the right of feedback afterwards |
* running the jam and * soliciting the right feedback afterwards * Check out [[attachment:GlobalBugJam.pdf]] - it's a one-page cheatsheet document, print out a few and have a small stack of them at the venue (also check out our [[RunningBugJam#Material|Bug Jam Material]] section). |
| Line 27: | Line 24: |
| * Ask around early who's interested in the event and | * Ask locals early who's interested in the event * '''Ask what packages/kind of bugs your participants are interested in''' * We will try to organise specialists for the event who can assist and help out via IRC |
| Line 32: | Line 31: |
| || '''Continent''' || '''Country''' || '''City''' || '''Team''' || '''Where''' || '''Interests''' || '''Comments''' || || '''Africa''' || || || || || || || || '''Americas''' || || || || || || || || || USA || Chicago, IL || ChicagoTeam || TBD || Desktop and Server || Location and times will be announced shortly - Talk to RichardJohnson (nixternal) for more information || || || USA || TBD || MichiganTeam || TBD || Desktop || || || || Chile || TBD || ChileanTeam || TBD || TBD || || || '''Asia''' || || || || || || || || '''Australia''' || || || || || || || || '''Europe''' || || || || || || || || || Germany || Berlin || UbuntuBerlin || http://c-base.org || TBD || TBD || || '''International'''|| || || || || || || |
|
| Line 33: | Line 43: |
| * Africa * The Americas * Asia * Australia * Europe * Germany * Berlin, details yet to come ([:UbuntuBerlin] |
== Potential bug targets == |
| Line 41: | Line 45: |
| Here are some interesting bug lists to work from for the Global Bug Jam! <<Include(Bugs/EasyTasks/List)>> == During the Event == * Have somebody of the team there who can answer Bug Triage specific questions. * Ask a few people to forward questions to `#ubuntu-bugs` if necessary. * '''Share your interesting and fun stories on [[GlobalBugJam/Stories]] along with pictures, videos and what else you can think of.''' * Use the flickr tag `global-bugjam-february-09`. * Blog and Twitter about your success. * Make use of [[5-A-Day]]. :-) * Use the [[https://wiki.ubuntu.com/5-A-Day/Reporting#Tagging%205-A-Day%20Bugs|5-a-day Tag]] `global-february-09-<city>`. * Play [[GlobalBugJam/Bingo|Bug Jam Bingo]]! == Upstream Participation == We encourage upstream projects to ''piggyback'' on the Global Bug Jam and use this as an opportunity to work with Ubuntu and participate. Please list your project here and a point of contact and run your own jam along with us! If you're an Ubuntu participant and interested in working with a specific upstream project, add your name (or LoCo) to the last column. Ubuntu bugsquad volunteers can help upstreams by triaging bugs for a specific project, file bugs upstream and link them to launchpad, and help upstreams triage their own bugs. Upstream point of contacts should be in #ubuntu-bugs as well to help coordinate/triage volunteers as the Jam takes place. || '''Project''' || '''Upstream Point of Contact Name/Nick''' || '''IRC Channel''' || '''Ubuntu Point of Contact Name/Nick''' || || KDE || RichardJohnson (nixternal) || #kde | #kde-devel | #kubuntu-devel | #ubuntu-chicago || RichardJohnson (nixternal) || |
Global Bug Jam
Everybody knows what a great success our institution the UbuntuBugDay is. Some LoCo teams even took this further: instead of just meeting on IRC, they made a party out of it and met locally to work on bugs together.
On the weekend of the 20 February to 22 February we'll do the same, globally!
How to do it
So you're interested and want to make the event ROCK in your LoCo?
Make sure you read RunningBugJam - it has a lot of information on
- organising the venue
- promoting the event
- running the jam and
- soliciting the right feedback afterwards
Check out GlobalBugJam.pdf - it's a one-page cheatsheet document, print out a few and have a small stack of them at the venue (also check out our Bug Jam Material section).
Special planning:
- Ask locals early who's interested in the event
Ask what packages/kind of bugs your participants are interested in
- We will try to organise specialists for the event who can assist and help out via IRC
The List
Continent |
Country |
City |
Team |
Where |
Interests |
Comments |
Africa |
|
|
|
|
|
|
Americas |
|
|
|
|
|
|
|
USA |
Chicago, IL |
TBD |
Desktop and Server |
Location and times will be announced shortly - Talk to RichardJohnson (nixternal) for more information |
|
|
USA |
TBD |
TBD |
Desktop |
|
|
|
Chile |
TBD |
TBD |
TBD |
|
|
Asia |
|
|
|
|
|
|
Australia |
|
|
|
|
|
|
Europe |
|
|
|
|
|
|
|
Germany |
Berlin |
TBD |
TBD |
||
International |
|
|
|
|
|
|
Potential bug targets
Here are some interesting bug lists to work from for the Global Bug Jam!
The Level column indicate the difficulty of the bugs on the list for being Triaged, those are divided into three levels:
Easy |
Medium |
Hard |
Level |
Type of bugs |
Triage Example |
|
||
|
Bugs without a package and tagged apport-bug so contain lots of information |
|
|
||
|
||
|
Ensure that the bugs are the same before linking |
|
|
|
|
|
|
|
|
|
|
|
Oldest bugs with a Incomplete status - updated every 24 hours |
|
|
Oldest bugs with a Confirmed status - updated every 24 hours |
|
|
Least recently changed bugs without a package and with a New status |
|
|
Least recently changed bugs without a package and with an Incomplete status |
|
|
Least recently changed bugs without a package and with a Confirmed status |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
Kernel bugs with patches attached: linux, linux-fsl-imx51, linux-ec2, linux-mvl-dove |
Paper Cuts
New to paper cuts? Start here.
During the Event
- Have somebody of the team there who can answer Bug Triage specific questions.
Ask a few people to forward questions to #ubuntu-bugs if necessary.
Share your interesting and fun stories on GlobalBugJam/Stories along with pictures, videos and what else you can think of.
Use the flickr tag global-bugjam-february-09.
- Blog and Twitter about your success.
Make use of 5-A-Day.
Use the 5-a-day Tag global-february-09-<city>.
Play Bug Jam Bingo!
Upstream Participation
We encourage upstream projects to piggyback on the Global Bug Jam and use this as an opportunity to work with Ubuntu and participate. Please list your project here and a point of contact and run your own jam along with us! If you're an Ubuntu participant and interested in working with a specific upstream project, add your name (or LoCo) to the last column.
Ubuntu bugsquad volunteers can help upstreams by triaging bugs for a specific project, file bugs upstream and link them to launchpad, and help upstreams triage their own bugs. Upstream point of contacts should be in #ubuntu-bugs as well to help coordinate/triage volunteers as the Jam takes place.
Project |
Upstream Point of Contact Name/Nick |
IRC Channel |
Ubuntu Point of Contact Name/Nick |
KDE |
RichardJohnson (nixternal) |
#kde | #kde-devel | #kubuntu-devel | #ubuntu-chicago |
RichardJohnson (nixternal) |
GlobalBugJam (last edited 2009-08-20 18:43:07 by c-76-112-233-201)