From: KOSAKI Motohiro <kosaki.motohiro@...>
Date: 2011-01-21T14:36:48+09:00
Subject: [ruby-core:34699] Re: MRI file architecture doc

>> ------- README.FILES ------
>> Explains the ruby project's file structure
>> (snip)
>
> This list includes generated files during build process.
> Such files should be separated.
>
> Additional to say, this list should be on Redmine wiki.
> On wiki, people who notice a new file or want more detail can add
> description.
> Fell free to ask the meaning of each files.
> We understand such document must be provided.

Hmm..

I think svn is the best place. Why? Source files will be created and removed
with our development. So, the same time updating significantly keep to
consistency
with source. Especially, It can be easily maintained on multiple
version and/or branch.

In other words, README.FILES is for extension developer. Not usualy
ruby programmer.
Then, we can assume they can extract source tarball and read included documents.
If false, Why do we include README.EXT in tarball?

Thanks.