Re: Proper Copyright Year in PHP files now an automated QA tasks

Marcel van der Boom wrote:
> 
>> But I think we do need to recognize why we have what is there now
> Agreed, but not for many more messages I hope :D The thread is getting
> mighty long.

I've seen it written that any project which does not document not only the
results of decisions made, but the reasoning behind those decisions, is going to
spend all its time going over old ground.

That said, this thread would be very useful to direct people to when this topic
comes up again, but is there any way to do this? Should it go into some kind of
project blog? The RFC contains the what and how, but does not (and should not)
contain the background to how it came about.

So, is there a permanent place where the background behind decisions can be
documented?

-- Jason