<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Tue, 2010-11-23 at 12:11 -0500, Trevor Woerner wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">So I can predict Gaetan replying to my previous email saying: "let's</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">use 'install-docs'" since not all projects have a "specs" directory</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">and we want to use the same target across all projects :-D</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
Yes, he said that, and more :-)<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">Sorry, I have no idea if this can or should be cleaned up.</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
There isn't really anything to "clean-up", not that a new organization principle<BR>
could not be used, provided the benefits are tangible.<BR>
<BR>
The man directory is used for man pages in legacy troff format. A couple of exceptions<BR>
where the man pages are generated from DocBook/XML or ASCIIDOC<BR>
<BR>
The /specs directory contains functional specifications which is a "type of" document.<BR>
<A HREF="http://en.wikipedia.org/wiki/Functional_spec.">http://en.wikipedia.org/wiki/Functional_spec.</A><BR>
<BR>
The /doc is for user's and developer's documentation. It would probably be hard to distinguished<BR>
between the two. Sometimes both are in the same logical document.<BR>
<BR>
In the server, there is no central location for docs or specs, there are close to the code.<BR>
<BR>
</BODY>
</HTML>