Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jspwiki-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Janne.Jalkanen@ecyrd.com
 designates 193.64.5.122 as permitted sender)
In-Reply-To: <176632746.20080508193924@holeczek.de>
References: <1210113506.29334.869.camel@netframe>
 <8F4CF652-FE32-44A9-8A10-45E805633CFE@mac.com>
 <1210125116.29334.884.camel@netframe>
 <43C8A522-7D13-4DEB-B9B5-0C9A4335D75C@mac.com>
 <1210168961.29856.25.camel@netframe>
 <B377347E-01D6-4D74-8701-A5B460CDAF33@mac.com>
 <1210176068.29856.78.camel@netframe>
 <9E1E32DC-9C3A-49DD-9C37-470E0E1353AB@ecyrd.com>
 <176632746.20080508193924@holeczek.de>
Mime-Version: 1.0 (Apple Message framework v753)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DE2C255D-C842-40B3-8F44-418512E4A21D@ecyrd.com>
Content-Transfer-Encoding: 7bit
From: Janne Jalkanen <Janne.Jalkanen@ecyrd.com>
Subject: Re: Higher level project documentation, Was: Re: Other 2.6.2 changes
Date: Thu, 8 May 2008 22:43:22 +0300
To: jspwiki-dev@incubator.apache.org

> Aren't there any tools which could analyze a code base and generate a
> project map / graphical class overview with dependencies a.s.o.?

Yes, there are, but these are in general useless, since they don't  
really describe how the software works.  Process diagrams and  
tutorials are far more useful.

> Well I think, the big picture documentation can only be done by people
> who at least have enough overview on the project and its history.

True, but we still need someone who is willing to take overall  
responsibility of the documentation and find the bits that need to be  
documented.  Also clean it up once someone writes some documentation,  
and makes sure it is organized well and is up to date.  I'm happy to  
contribute when someone says that "this bit here, that needs  
contribution from YOU since you understand it", but I can't take on  
the entire project management of the documentation, too...

/Janne