dev builds
themes manual
device status forums
mailing lists
IRC bugs
dev guide

Rockbox mail archive

Subject: Handling NoDo features

Handling NoDo features

From: Frank Gevaerts <>
Date: Tue, 23 Mar 2010 20:58:16 +0100


We currently have some features that tend to be rejected without much
discussion because they are in some way or other on a list of features
that We Do Not Want. Part of this list is at
but a significant part is not recorded anywhere, except in the
collective memories of the developers. I get the impression that for
most of the items on the unwritten list, nearly nobody actually
remembers when or why the feature was banned, there's just the vague
memory that it was, and possibly some a posteriori reasoning of what the
reason likely was. Discussions about the bans tends to quickly turn into
flamewars, so it's almost impossible to ever reverse them, even in case
a majority (or maybe even all) developers would agree to that.

I think this situation is intolerable. We *have* to find a solution.

My proposal is:
* Every single NoDo item *must* appear on
* All NoDo items must have a proper rationale
* All NoDo items must be reconfirmed once a year, possibly at DevCon

Thoughts? Proposals?


"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
Received on 2010-03-23

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy