sks-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sks-devel] wiki man-page link; readthedocs.org ?


From: Phil Pennock
Subject: [Sks-devel] wiki man-page link; readthedocs.org ?
Date: Sun, 1 Dec 2013 21:34:01 -0500

I received an off-list report that the man-page link at:
  https://bitbucket.org/skskeyserver/sks-keyserver/wiki/Documentation
was broken; it seems that registration of minskyprimus.net has lapsed
and the domain is now being squatted.

I've temporarily updated the page to point to an instance of the page
which I've shoved up on my server.  It's the result of pod2html using
the Mercurial source as of commit 4069c369eaaa, which is a tip commit by
John Clizbe on June 19th.  I see no commits since then to the master
repo.

I looked first for a documentation-server and didn't see anything
readily suitable, without repo commit access to configure it.  I think
that a better solution is probably to use <https://readthedocs.org/> and
point to the documentation there.

To that end, I've done preliminary setup, although build fails because
of a lack of "conf.py":

  https://readthedocs.org/projects/sks/

If anyone with commit access (to SKS itself, mine is just to the wiki)
thinks this is the right approach, let me know and I can continue with
setup based on a fork of the master repo, then merge back in, or give
other people maintainer access to the RTD project.

-Phil

----------------------------8< cut here >8------------------------------
% hg diff -c tip 
diff --git a/Documentation.wiki b/Documentation.wiki
--- a/Documentation.wiki
+++ b/Documentation.wiki
@@ -4,7 +4,7 @@
 
 The official documentation for SKS is:
 
-  * The [[http://minskyprimus.net/sks/sks-man.html|man page]]
+  * The [[http://sks.spodhuis.org/sks-man.html|man page]]
   * The 
[[https://bitbucket.org/skskeyserver/sks-keyserver/src/tip/README.md|README]] 
from the source distribution.
 
 Within this Wiki, you might start at the [[Peering]] page, for advice on setup 
and social issues.
----------------------------8< cut here >8------------------------------



reply via email to

[Prev in Thread] Current Thread [Next in Thread]