RFC: Let's make Amarok2 actually play music!

[Dan Meltzer]

On 9/1/07, Mark Kretschmann <kretschmann at kde.org> wrote:
> Hey all,
>
> on #amarok.dev we've just been discussing our development goals for
> the near future. Here's my suggestion:
>
> "Let's focus on making Amarok2 usable enough so that *we* can use it
> for our daily music needs!"
>
> I am convinced that the day we developers actually start using Amarok2
> daily for playing music (instead of just for testing purposes) will
> make a *big* difference. It's a whole different story whether you work
> on an application that might theoretically work some day, or if you
> use it yourself to actually do something useful. Once we achieve this
> goal, this will provide a huge motivation boost to us, and also to our
> users who are eager to beta-test Amarok2.
>
> Also it will help us to focus on the essential things. It's very easy
> to get lost in details. We can do the polishing later on, there will
> be plenty of time.
>
> Personally I need a collection, and a playlist, and I need the thing
> to actually play music without crashing. Then I would consider
> switching to Amarok2. What about you?

One thing that I think is important to get in place before expecting
non-us to test the application is the crash handling mechanism.  We
could just reenable kmail support and hope for it to use the kde3.5
version if the 4.0 version isn't installed, but I'm wondering if there
are better ways to deal with back traces all together.

I know ubuntu gutsy has added a global crash handler that allows one
to submit backtraces upstream... I'm wondering what kind of
application they use at the "other end" and if its something
accessible on lauchpad.  At the very least we should come up with
either a new list or a way of tagging 2.0 backtraces to separate from
1.4.x ones
>
> --
> Mark
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>