Hi Jon.
> We've been the benificiaries of using Linux for our Web server
> for more than 3 years. Used to do all our email on Linux, too,
> before the IS folks got involved and went to NT :-(
> So I think it's only fair if in return I offer to host a Linux
> ham-radio section on www.arrl.org. That should provide a good
> means of exposing Linux ham-radio topics to hams in general,
> which I think is one of the principal issues here.
> How does that sound?
Brilliant...
>>> 3> The idea of the HAM-HOWTO was that it would be a community
>>> generated document. That is, people would volunteer
>>> information about new software as it is developed and/or
>>> found. To their credit, some people have contributed, but I
>>> don't think enough have to call it a successful collaborative
>>> exercise.
>> It is not obvious that it is a community generated document and
>> in order to make it so one must provide an easy mechanism to do
>> the updating. There is no formal or easy to use mechanism to do
>> this in place (e-mail by itself doesn't count).
> Email is just the delivery mechanism. But the conversion to a
> structure of Web documents would provide an opportunity to make
> its collaborative nature more obvious.
I've written a few things like that, and have a 24/7 site with cgi and
forms abilities available, so could probably set up a trial version
thereof if you'd like that.
In addition, for those sites interested in putting up suchlike pages,
but without CGI facilities of your own, I can arrange to home the cgi
side thereof for you, but ONLY if I can proofread the cgi source. The
server runs under RedHat Linux 5.0 with an upgraded kernel, so don't
ask me to host cgi scripts written for M$ OS's...
>>> 2> Provide a web site, like Joops, and extend it such that it is
>>> able to automatically produce textual catalogs that could be
>>> posted periodically on usenet/mailing lists etc. for those
>>> that don't have interactive net access, and all else could use
>>> the web site when they're looking for software.
>> Yes.
> Cool. We could also make the text-based material available via
> our automated email responder ([EMAIL PROTECTED]).
That would be extremely useful in my opinion...
>> But this isn't sufficient. There needs to be a place where
>> people can obtain step by step information on how to setup the
>> software, that you are cataloging so dilligently.
>> So this website (good idea) must contain the instructional parts
>> of the HOW-TO and have a form based, moderated, response page
>> that either allows people to add stuff to the 'HOW-TO' or
>> generates an FAQ or both.
> I'm all for that, but if we do it, we will need outside
> moderators (meaning: not me) to vet the input.
I'd be willing, but wouldnae have the time before October, and can't
guarantee anything then - we're moving into exam season at the moment,
and those have to come first...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
