From: Austin Ziegler <halostatue@...>
Date: 2005-05-15T05:05:01+09:00
Subject: Re: [SOURCES] - Hierarchical/Modular Directory Structure

On 5/14/05, Ilias Lazaridis <ilias@lazaridis.com> wrote:
> Ilias Lazaridis wrote:
>> The source-code structure should be simplified, lowering barriers for
>> developers which would like to start looking at the ruby-core.
>> the goal would be a self-documenting directory-structure /content.
> "Do it or not" should not be the topic of discussion.

Do it or not is of course the first topic of discussion. Like it or
not. At this point, the proper answer is "do not do it." There's a
perfectly legitimate reason not to do it, too.

When it is time to consider doing this, then the "how" is able to be
discussed -- but Matz being a benevolent dictator will make the
decision that is best after hearing from interested and informed
parties with interesting and informed opinions.

> > place all 'sources' withing the directory "src"
> I take back the above suggestion.
> 
> I suggest the simplest step, which would require only a few changes:
> 
> * add a directory "core"
> * move *.c and *.h files from root to /core
> * update makefiles
> 
> low effort, cleaner structure.

...with 100% loss of source code revision history for those files that
are moved. If and when Matz decides to change the source code
repository for Ruby, then I think that a discussion on the
reorganisation of the sources is appropriate. Until then, it is most
inappropriate, because it will result in a loss of source code
revision history under CVS.

-austin
-- 
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca