GlobalBugJam

Differences between revisions 81 and 82
Revision 81 as of 2008-12-18 08:40:31
Size: 4407
Editor: i59F755EC
Comment:
Revision 82 as of 2008-12-24 00:26:42
Size: 4493
Editor: cpe-72-230-147-165
Comment:
Deletions are marked like this. Additions are marked like this.
Line 35: Line 35:
|| || USA || New York State || NewYorkTeam || TBD || Desktop and Server || TBD || ||

http://farm4.static.flickr.com/3265/2550528941_5677fdf41e_o.png

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!

Digg It!

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

ChicagoTeam

TBD

Desktop and Server

Location and times will be announced shortly - Talk to RichardJohnson (nixternal) for more information

USA

New York State

NewYorkTeam

TBD

Desktop and Server

TBD

USA

TBD

MichiganTeam

TBD

Desktop

Chile

TBD

ChileanTeam

TBD

TBD

Asia

Australia

Europe

Germany

Berlin

UbuntuBerlin

http://c-base.org

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

New bugs without a package assigned to them

315973 - Find the Right Package

Bugs without a package and tagged apport-bug so contain lots of information

Find the Right Package

Bugs marked for expiration

32443

Bugs without a package with more than 5 comments

Find the Right Package

Bugs that need to be forwarded to an upstream bug tracker

Downstream Report - Upstream Report

Unlinked upstream bugs

Ensure that the bugs are the same before linking

Patch available! Please package and test.

Bugs with Patches to be reviewed

Oldest bugs with a New status - updated every 24 hours

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

Least recently changed bugs with a New status

Least recently changed bugs with an Incomplete status

Least recently changed bugs with a Confirmed status

Least recently changed bugs with a Fix Committed status

Bitesize bug reports

How to fix bugs

Kernel bugs with patches attached: linux, linux-fsl-imx51, linux-ec2, linux-mvl-dove

How to handle Kernel bugs with patches

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

  • 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)


CategoryBugSquad

GlobalBugJam (last edited 2009-08-20 18:43:07 by c-76-112-233-201)