my git branches: acoustic fingerprinting and playlist generator

[Seb Ruiz]

2009/1/16 Ian Monroe <ian.monroe at gmail.com>:
> On Thu, Jan 15, 2009 at 10:01 AM, Soren Harward <stharward at gmail.com> wrote:
>> Hiya Amarok Developers:
>>
>> I haven't been able to do much Amarok work for about six weeks now
>> because of my work situation.  After about six months of unemployment
>> (which gave me lots of Amarok coding time), I just started a part-time
>> teaching job, so I spent most of December going through certification
>> and putting together lesson plans.  And I've just been offered a
>> full-time job which starts at the beginning of February, so it doesn't
>> look like I'll be getting much Amarok work done then, either.  I have
>> a brief lull over the next couple of days, and at the request of Lydia
>> and Teo, I'm going to polish up the stuff I've had sitting in my
>> personal git branch and get it committed to trunk some time this
>> weekend.  I'm sending out this email as much to give myself a deadline
>> as I am to warn you that some new things are incoming.
>>
>> More thorough descriptions of what's in the code, and more
>> importantly, what's still missing from it, will be in the commit
>> messages.  In the meantime, I would appreciate it if those of you who
>> are inclined could download GTACFeat from SourceForge and play around
>> with it; Amarok's acoustic fingerprinting code depends on this
>> library.  It's the first piece of software I've written and packaged
>> from the ground up, and there are bound to be quirks in it that need
>> to be addressed before it's ready for major consumption when A2.1
>> comes out.  Please email me bug reports (patches are especially
>> appreciated!).
>>
>> Thanks.  I'm sorry that my involvement has been very limited for the
>> last couple of months, and will likely continue to be so until the
>> summer.  But on the other hand, it is really nice to be working for a
>> paycheck again.
>>
>
> Do you have your git repo published somewhere so we could do a little
> pre-commit code reviewing?

Agreed. We might want to consider using Crucible for this, which is
used exactly for code reviews.

http://amarok.be/fisheye


-- 
Seb Ruiz

http://www.sebruiz.net/
http://amarok.kde.org/