Hi Eric,<br><br><div class="gmail_quote">2009/3/16 Eric S. Raymond <span dir="ltr"><<a href="mailto:esr@snark.thyrsus.com">esr@snark.thyrsus.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Arnaud, my UPS arrived yesterday; thanks for your generosity.</blockquote><div><br>pleased to hear that it arrived ;-)<br>Eaton is the new player here, and we have had some recent proof of its dedication to FLOSS...<br>so if we can help, it's a pleasure ^_^<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'm<br>
using it to power the computer I'm typing on. This moves NUT up a few<br>
places on my priority list.<br>
<br>
In our last email exchange, I believe we agreed on a couple of major<br>
points. I want to confirm these before I start modifying the<br>
documentation heavily.<br>
<br>
1. asciidoc is a good master format for the in-tree documentation.<br>
</blockquote><div><br>right<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2. We're going to go with making the website a branch of the<br>
Subversion repo, with the pages mainly pointing to HTMLized copies<br>
of the in-tree repo.<br>
</blockquote><div><br>right, though I'm still unsure about the exact details of the html generation and location.<br>we'll discuss these kind of details later on.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
3. The exception is that we may retain the new wiki for the<br>
protocol library, since that is an area where we can expect substantial<br>
user contributions.<br>
</blockquote><div><br>well, the wiki is interesting for the protocols (though I don't expect many contribs there), i18n and website mastering delegation.<br><br>btw, if you have a better solution that fits the above criteria, I'm opened and it's the right time.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are there any more decisions we need to make or cautions you want to<br>
utter before I dive in and start work?<br>
</blockquote><div><br>I don't think. just beware of the docs/bits present on one side and not the other (aknowledgements, ...).<br>though I'll however jump in there when you've laid up the base system to make sure we don't miss anything.<br>
I'll also have to check for the generation / integration of the HW compat list.<br>don't hesitate to hit me regurlarly to check that we're on the right track.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Further note: I'll need shell access to the host for the SVN repo.<br>
One of my first tasks will be to write a hook that automatically<br>
publishes a web page when its repo master gets a commit.<font color="#888888"></font></blockquote><div><br>private followup with Charles...<br></div></div><br>thanks again for your help there.<br><br>cheers,<br clear="all">
Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>