Hello Kai,
Thursday May 13 2021, Kai Richter wrote to Michael Dukelsky:
TK>>>>>> How about http://download.huskyproject.org/docs/ ?
MD>>>> Is it better to remove it from wiki?
KR> Maybe i misunderstood. Did you talked about the docs itself or the
KR> link to huskyproject?
My reply about wiki was to Oli who said that wiki was an inappropriate place for the documentation if I understood him correctly. The wiki is here:
https://github.com/huskyproject/hpt/wiki
KR>>> To provide a fast and easy access to latest documentation i'd
KR>>> like to suggest to place a prebuild .txt ascii version for each
KR>>> module to the github.
MD>> First of all I want to say that the documentation in the wiki was
MD>> made partly manually, I did not manage to make it automatically,
MD>> so it cannot be the latest version.
So here I talked about wiki and not about download.huskyproject.org.
KR> Date shows 2018 and that's the reason why i was looking for a more
KR> recent version. Could it become a yearly update event?
Here you talk about download.huskyproject.org. There is no sense to publish the documentation yearly, it is much better to publish it when it changes as it is now.
MD>> As to the latest documentation it can be made in several forms.
MD>> Those who run a UNIX-like OS may clone the GitHub repo and using
MD>> a simple command get info- and/or man-pages. From my point of
MD>> view this is better than plain ascii.
KR> Yes, i do agree. I have to admit that i'm not on the latest version
KR> and that i'm to lazy to pull the git and do a compilation of the docs
KR> for the purpose of a check for the actual keywords when i tried to
KR> support the route configuration. I copied the text from the texi and
KR> edited it to ascii manually. Lazy as i am the idea was to have quickly
KR> accessable file for reference.
You are lazy? Oh, no! You spent much more time for editing texi, you could get the info-pages of the docs within a minute.
KR> Is it possible to use other mechanisms of github? I noticed that
KR> github could handle releases too.
Yes, it is possible to publish the docs in GitHub releases.
Michael
... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Moscow, Russia (2:5020/1042)
|