Zachary Grafton writes:
On Thursday, February 12, 2015 08:24:02 AM Sam Varshavchik wrote: > At some point, something will probably have to be done with DNSSEC. But > things haven't been sufficiently stabilized to the point that it's clear > where things are going. Courier's internal resolver already knows how to > handle DNSSEC replies, just need to wait until it's clear what needs to be > done with them.That makes complete sense. I thought there might be some clean up work that needed to be done or something along those lines. Would anyone entertain the possibility of updating the web site with a new design?
That anyone would be me. In general, I'm happy to look at proposals for tweaks to the web site's appearance. However, two things need to be kept in mind:
1) I'm naturally resistant to radical, inside-out rewrites. I'll be more receptive to many, smaller changes, in steps.
2) Most of the web site's content actually gets generated from Docbook XML documentation. This is a major timesaver. For example, both the man pages in the source code tarball, and their versions on the web side, come from a single source file. Docbook XML imposes some limitations on what kinds of things can be done without dumping everything down the drain. See #1.
pgp0hTROHSPqr.pgp
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
