sb_core

what is it?

sb_core is our designation for the core developers, the people building and hacking on the Songbird player/platform code itself.  Since Songbird is GPL'd, we have a quite a few developers pulling from Subversion, hacking on the code, getting code review and making patches.  We wanted to recognise these guys for all their hard work and dedication to making Songbird a better player, so we've created the sb_core program.

If you're new to Songbird core development, you can read our Getting Started Guide for a quick intro on how to get started with pulling the source, building it, and making patches.  And fear not - we've gone through and flagged a whole bunch of good starter bugs for people to ease their way into Songbird development.

howzit work?

It's pretty simple.  If you look at bugs in our Bugzilla, you'll see every bug has a cost associated with it.  For every bug you fix, you accumulate points. Because we're geeks, we're going by a power of 2 scale, so if a bug is cost 0, you'll get 2⁰=1 point.  If a bug is cost 3, you'll get 8 points (2³=8).

The easiest rule of the program is that every developer who fixes at least 1 point gets:

1. Some schwag (t-shirt, stickers, pins, and if you're lucky - a fart in a bag ;-))
2. Credit in Songbird's "about:" page as a Songbird core contributor

Beyond that, we'll also be giving away stuff to our most productive contributors.  We'll be doing this two ways:

1. Every two months we'll give away smaller Songbird related stuff to the two devs who have fixed the most points worth of bugs (these will typically be things like MP3 players, Songbird hoodies, and other exclusive schwag)
2. As the total number of points you accumulate cross certain thresholds, we'll be giving away higher-end stuff.  We can't say what until after we give it out... but trust us, it's some h0t stuff.
   

who's contributing, and how do i join?

If you're fixing bugs, implementing features, and making patches - then you're already participating.

The scores are taken from bugs which have both the "3rdppatch" (third party patch attached) and "fixed-external" (patches from this bug were committed to the Subversion repo) keywords.

If you think you have a bug that isn't being reflected in the table above, please let stevel know and he can correct it.