<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 22, 2014 at 7:35 AM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hey everyone,<br>
<br>
While I was writing the documentation for the options framework, I<br>
thought up of a way to better organize the code documentation we are<br>
creating now. I've posted a patch for review that implements this<br>
organization. [1]<br>
<br>
Copying the description from the patch I've posted for review,<br>
```<br>
A new directory hierarchy has been created in doc/code for the code<br>
documentation, which follows the general GlusterFS source hierarchy.<br>
Each GlusterFS module has an entry in this tree. The source directory of<br>
every GlusterFS module has a symlink, 'doc', to its corresponding<br>
directory in the doc/code tree.<br>
<br>
Taking glusterd for example. With this scheme, there will be<br>
doc/code/xlators/mgmg/glusterd directory which will contain the relevant<br>
documentation to glusterd. This directory will be symlinked to<br>
xlators/mgmt/glusterd/src/doc .<br>
<br>
This organization should allow for easy reference by developers when<br>
developing on GlusterFS and also allow for easy hosting of the documents<br>
when we set it up.<br>
```<br></blockquote><div><br></div><div><br></div><div>I haven't read the previous thread, but having doc dir co-exist with src in each module would encourage (or at least remind) keeping doc updated along with src changes. Generally recommended not to store symlinks in the source repo (though git supports it I think). You could create symlinks from top level doc/code to per module (or vice versa) in autogen.sh.</div>
<div><br></div><div>Thanks</div></div></div></div>