[lsb-discuss] LSB Bug Day on Fridays

Wichmann, Mats D mats.d.wichmann at intel.com
Thu Nov 4 16:29:58 PST 2004

This is a one-time note sent to a bunch of LSB mailing lists.
I won't repeat this blast but there are resources on it on the
LSB Wiki or you can find this message in the list archive if 
you forget the details and want them later.

During the LSB 2.0.1 we found it useful to have a "bug day"
session via IRC. For the time being, let's continue that 
practice indefinitely.

LSB bug days are every Friday.

What's a bug day?

Participants meet in an IRC channel (or in real life) and 
collaboratively go through the LSB bug database, triaging as well
as fixing and closing bugs as they go. Bugs may be filed against
any of the LSB "products" (i.e. toplevel category in bugzilla);
if there's a specific focus for a bug day it will be in the bug
channel topic for that day - if that's not an interesting topic,
just join on a different bug day. Join any time you like, and
stick around as you can.

Triage (from wikipedia.org):
The word triage comes from the French word trier, which means "to sort".
Much of the credit for modern day triage has been attributed to 
Baron Dominique Jean Larrey, a famous French surgeon in Napoleon's 
army who devised a method to quickly evaluate and categorize the 
wounded in battle and then evacuate those requiring the most urgent
medical attention. He instituted these practises while battle was 
in progress and triaged patients with no regard to rank.

You don't need to have previous experience with LSB internals to
participate; in fact bug days offer a good opportunity to learn
the basics by asking questions and working on relatively simple bugs.
Fresh eyes on topics sometimes bring clarity of vision that the 
battle-scarred veterans are missing.

Bug day participation also helps the developers and makes LSB better
by reducing the backlog of bugs and patches. Plus, it's fun!

The LSB irc channel is at: irc://irc.freestandards.org/#bugs

The irc channel has a bot listening which can be asked to put up
a summary of the bug under consideration; anyone is free to
propose a fresh bug in this way.  The syntax is:

bugbot: bug lsb XXX

where XXX is the bug number.  These are references to the bugs
in the LSB bugzilla at: http://bugs.linuxbase.org
The bugbot will provide a link to the specific bug as well
as a brief summary.

Some notes on the bug policies and procedures, and a page 
covering these notes may be found on the LSB wiki at:


And a quickstart or refresher for folks who haven't been around 
the LSB a lot recently (or ever) is at:


Hope to see you there this week, and/or in the future!

More information about the lsb-discuss mailing list