<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>- So I guess we are all for asciidoc or any other "developer" oriented documentation system. Sounds good. When you folks pick one Just let us know.</div><div><br></div><div>- Point us to the repo and we can all start contributing .</div><div><br></div><div>This Probably will simplify things for all of us because we won't have the wiki-rot problem anymore. </div><div><br></div><div>Again I really like how this worked in the hbase community: hbase is a big program like gluster with similar need for diverse and ever evolving docs... And the code integrated docs really work well, and I think gluster is definetly ready for the same doc integration.</div><div><br></div><div><br></div><div><br></div><div>On Jan 7, 2014, at 10:14 PM, Anand Babu Periasamy <<a href="mailto:abperiasamy@gmail.com">abperiasamy@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jan 7, 2014 at 5:40 PM, Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</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"><div class="im"><br>
On 01/07/2014 05:37 PM, Emmanuel Dreyfus 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">
Joe Julian <<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>> wrote:<br>
<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">
docbook didn't work last time it was used. Perhaps asciidoc would be<br>
more open to collaboration.<br>
</blockquote>
I do not know abot asciidoc, but I have an experience of docbook +<br>
docbook to latex XSL transformation which worked great. Here is the<br>
result:<br>
<a href="http://www.editions-eyrolles.com/Livre/?ouv_ean13=9782212114638" target="_blank">http://www.editions-eyrolles.<u></u>com/Livre/?ouv_ean13=<u></u>9782212114638</a><br>
<br>
</blockquote></div>
To be more specific, when I say it didn't work last time I'm not referring to the technology, but rather the suggestion that programmers would be willing to keep it current. Gluster hired a documentation writer. He wrote the documentation in docbook. Gluster was acquired and nobody ever updated the documentation ever again.<br>
<br>
I've personally tried and it was so cumbersome that I ran out of my available time.<div class=""><div class="h5"><br></div></div></blockquote><div><br></div><div>Asciidoc sounds cool. I always used texinfo and publican. I would go with Asciidoc here. It looks like Asciidoc has pretty good PDF and HTML conversion. </div>
</div><div><br></div><div>We tried and failed with professional documentation writers. Doc should be maintained by developers. Like code, doc changes all the time. I think we should commit doc along with source repository. This way we can enforce doc updates at the time of patch submission. We will always have have updated doc for any version of code we pull out.</div>
<div><br></div><div>-ab</div><div dir="ltr"><div><pre style="color:rgb(0,0,0)">[[[ To any NSA and FBI agents reading my email: please consider eating more bacon!! ]]]</pre></div></div>
</div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Gluster-devel mailing list</span><br><span><a href="mailto:Gluster-devel@nongnu.org">Gluster-devel@nongnu.org</a></span><br><span><a href="https://lists.nongnu.org/mailman/listinfo/gluster-devel">https://lists.nongnu.org/mailman/listinfo/gluster-devel</a></span><br></div></blockquote></body></html>