main TODO file ?

[Ralf Habacker]

Am Samstag, 15. Oktober 2005 16:17 schrieb tnagyemail-ml at yahoo.fr:
> > But for users, who will take a fast look what to do
> > and where they can perhaps
> > help , without reading any platform related doc.
>
> As you wish, my last email was only a suggestion.
I think, were it is it no so important, the import thing is that we should 
have a rule where to places bugs and todos to keep in mind. May be that the 
recent core developers have all this stuff in mind, but it seems recently 
that there will be more developers in future. 

I would add  the following lines to 

BUGS
see BUGS.TXT

TODO
see TODO.TXT and python sources for TODO's  


see RULES.TXT for some project rules 
-> this file contains source code style and documenting rules 

Any problem with this  ? 

> > TODO and BUGS  have a general sections and a
> > platform specific  section and
> > anybody  who fixes a bug/todo can see if there are
> > platform related bugs in
> > one view.
> >
> > Additional in the past there were some questions
> > raised up like a generic
> > solution for '#', which had to be noted anywhere.
>
> When possible, use relative paths ('../kdecore/' etc).
> To specify a directory that lies in the original
> source directory use '#'.
>
>
> Scons does not duplicate all files directly, it only
> makes symlinks or copies of nodes that have been
> declared ( SCons.Node.FS.File('something') )
>
> Since we need both folders to be added and most of the
> time we do not want to bother adding both build and
> source dirs to the scripts, i suggest to use '#' paths
> only and to silently add the builddir equivalent.
>
> There is already a scons feature to do this, but in
> the opposite way:
> SCons.Node.FS.Dir('somepath').srcnode()
>
>
> Thomas
>
>
> /* Thomas Nagy */
>
>
>
>
>
>
> ___________________________________________________________________________
> Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
> Téléchargez cette version sur http://fr.messenger.yahoo.com