Rockbox mail archiveSubject: Re: Handling NoDo features
Re: Handling NoDo features
From: Frank Gevaerts <frank_at_gevaerts.be>
Date: Mon, 29 Mar 2010 22:21:50 +0200
Ok, I think the discussion is mostly over, so I'll summarise what I
On Tue, Mar 23, 2010 at 08:58:16PM +0100, Frank Gevaerts wrote:
Everyone seems to agree on this.
> * All NoDo items must have a proper rationale
I think everyone agreed that NoDo items without a stated reason are bad.
Personally I don't think this matters much. The stated reason isn't the
> * All NoDo items must be reconfirmed once a year, possibly at DevCon
This was I think the least clear, but the good news is that we don't
I think we can move to the next step, which is to actually document all
I've added a new section to the NoDo page listing some of the unwritten
Please shout if I've added things that shouldn't be there.
I'd suggest that anything that is not on the list by the time DevCon
-- "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. KernighanReceived on 2010-03-29
Page was last modified "Jan 10 2012" The Rockbox Crew