gSoC Implement a better database schema

[Caleb Cushing]

2009/3/27 Tim Bocek <tim.bocek at gmail.com>:
> onsidering how you were *already* planning to fix it yourself as a GSoC
> project, I don't think that quote really applies, actually.
>
> All people are saying is that to fix the problem you've identified would
> require a week of work, not twelve.  Since you obviously feel strong enough
> to devote twelve weeks, why not one?  Or, to get to the *real* point of the
> post you linked too, put your money where your mouth is instead (aside from
> the fact that Amarok doesn't have an official sponsorship program...)
>

It'd take you a week, it might take me a month if I started today.
Why? I'm a student, actually my second C++ class is about to start and
I haven't done any C++ in 2 years, I'm not familiar with the amarok
code base, and I don't know kde or qt libraries. I offered to do this
as part of gsoc, because as you'll notice that bug has been there for
quite a while, 2 prior discussions on this  (before the release of
amarok 2.0 )and the developer list suggest it wasn't a simple issue.
Now I'm told it is. This bug has been in amarok as long as I have used
it, which has been a few years now, maybe 3, 4?

now I'm told it's a simple bug to fix, and I ask myself, then why does
it still exist, I find the answer to be, simply amarok's devs don't
care.

anyways when reading that post today it made me think of this whole thing.

and no I'm not going to pay you to fix it. I may fix it myself when I
have the knowledge to, but that day has not yet come.
-- 
Caleb Cushing

http://xenoterracide.blogspot.com