From: Paul Louden <paulthenerd_at_gmail.com>
Date: Fri, 11 Jan 2008 00:40:15 -0600

1) Features should not be committed "until we can do it as a plugin". If
it's going to be done as a plugin, work on it as a plugin, don't clutter
the core with it just so that it has to be dug out later. Discuss the
idea, but make the decision before anything is committed.

2) Plugins should not be in the core language file. Not just for
archoses, but because it takes up more resources on non-Archos targets
too. It should be possible to come up with a method by which each plugin
has its own language file, and this seems a much more reasonable
methodology.

3) Please don't suggest dropping Archoses just because you don't use
one. They still offer features hard to come by in modern players. As
well "Microsoft doesn't support people wanting to use older stuff" is a
silly reason for us not to. It's not a democracy. Rockbox is written by
a select group of people to meet *their* needs. You aren't paying them
for it. As long as that group of people still has Archoses and wants to
run it on them, you're not going to convince them to give up on their
own players, just to support your features, especially when it's
theoretically possible to do it a way that meets both needs.

Rockbox's primary goal is *not* to be a speech interface for MP3
players. It needs to be taken into consideration, but you can't expect
significant sacrifices to be made just so it can speak non-essential
features like games.
Received on 2008-01-11