old-www/pub/Linux/docs/ldp-archived/mail_archives/ldp-discuss/msg01186.html

272 lines
12 KiB
HTML

<!-- MHonArc v2.5.0b2 -->
<!--X-Subject: Re: Processing HOWTOs -->
<!--X-From-R13: Egrva Uwbra <ftwbraNznvy.alk.arg> -->
<!--X-Date: Thu, 27 Jan 2000 15:28:34 &#45;0500 (EST) -->
<!--X-Message-Id: 3890AA41.5A554C53@mail.nyx.net -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 20000124233050.A22764@morgana.systemy.it -->
<!--X-Reference: 388CDAB8.579A83E3@cu&#45;portland.edu -->
<!--X-Reference: m3vh4hlubm.fsf@maya.linux.ca -->
<!--X-Reference: 388EBCB2.95774F2@mail.nyx.net -->
<!--X-Reference: 10001261119.ZM11214@hoop.timonium.sgi.com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML//EN">
<html>
<head>
<title>Re: Processing HOWTOs</title>
<link rev="made" href="mailto:sgjoen@mail.nyx.net">
</head>
<body>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->
<hr>
[<a href="msg01185.html">Date Prev</a>][<a href="msg01187.html">Date Next</a>][<a href="msg01154.html">Thread Prev</a>][<a href="msg01156.html">Thread Next</a>][<a href="maillist.html#01186">Date Index</a>][<a href="threads.html#01186">Thread Index</a>]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<h1>Re: Processing HOWTOs</h1>
<hr>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<ul>
<li><em>To</em>: <A HREF="mailto:ldp-discuss@lists.debian.org">ldp-discuss@lists.debian.org</A></li>
<li><em>Subject</em>: Re: Processing HOWTOs</li>
<li><em>From</em>: Stein Gjoen &lt;<A HREF="mailto:sgjoen@mail.nyx.net">sgjoen@mail.nyx.net</A>&gt;</li>
<li><em>Date</em>: Thu, 27 Jan 2000 21:27:45 +0100</li>
<li><em>Cc</em>: <A HREF="mailto:ldp-discuss@lists.debian.org">ldp-discuss@lists.debian.org</A></li>
<li><em>References</em>: &lt;20000124233050.A22764@morgana.systemy.it&gt; &lt;<a href="msg01137.html">388CDAB8.579A83E3@cu-portland.edu</a>&gt; &lt;<a href="msg01149.html">m3vh4hlubm.fsf@maya.linux.ca</a>&gt; &lt;<a href="msg01150.html">388EBCB2.95774F2@mail.nyx.net</a>&gt; &lt;<a href="msg01153.html">10001261119.ZM11214@hoop.timonium.sgi.com</a>&gt;</li>
<li><em>Resent-cc</em>: recipient list not shown: ;</li>
<li><em>Resent-date</em>: 27 Jan 2000 20:28:23 -0000</li>
<li><em>Resent-from</em>: <A HREF="mailto:ldp-discuss@lists.debian.org">ldp-discuss@lists.debian.org</A></li>
<li><em>Resent-message-id</em>: &lt;ngxX.A.KdB.npKk4@murphy&gt;</li>
<li><em>Resent-sender</em>: <A HREF="mailto:ldp-discuss-request@lists.debian.org">ldp-discuss-request@lists.debian.org</A></li>
</ul>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<hr>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<pre>
Due to fringertrouble at my end this went to Greg Ferguson alone, I
intended it to go to the list, sorry about that.
This is getting big, I have trimmed quite a bit...
Greg Ferguson wrote:
&gt;
&gt; On Jan 26, 10:21am, Stein Gjoen wrote:
&gt; &gt; Subject: Processing HOWTOs
&gt; &gt;
&gt; &gt; &gt; IMHO, while the LDP is amazing, let's not kid ourselves about quality.
&gt; &gt; Sadly true. So when is the core team going to post a request
&gt; &gt; for new authors or maintainers on <A HREF="news:comp.os.linux.announce">news:comp.os.linux.announce</A> ?
&gt; &gt; It wouldn't cost to try.
&gt;
&gt; There is no longer a core team; there are volunteers. If you would
&gt; like to take on that task, I think everyone involved with the LDP
&gt; would be most appreciative!
I'll be happy to do the web promotion and I hope to finish a
NetHelp framework to demonstrate a potentialy more userfriendly
format for HOWTOs.
Having been remarkably unsuccessful in getting feedback from
Slashdot poll system, I'll leave the people-to-people promotion
to someone more successful.
&gt; &gt; &gt; &gt;&gt; To this aim, we need a charismatic leader or group of leaders,
&gt; &gt; &gt; &gt;&gt; who can accept and refuse works without offending anybody.
&gt; &gt; &gt;
&gt; &gt; &gt; No, we need a process whereby docs can be rated and comments attached
&gt; &gt; &gt; by the user base. We need stats to show which docs are actually read,
&gt; &gt; &gt; and a followup process which asks the reader if the doc was actually
&gt; &gt; &gt; helpful. This is basic Customer Support 101.
See note later on about the Freshmeat mechanism...
&gt; &gt; To get proper stats we also need to promote. I did some automated
&gt; &gt; web promotion of my HOWTO and raised the hit counts from
&gt; &gt; about 50 a day to 300-500 a day. What has the core team done in
&gt; &gt; this respect? This is hardly the firt time I ask/suggest but I
&gt; &gt; have yet to see an answer. Some actual hit stats from the LDP
&gt; &gt; site would tell us how we are doing.
&gt;
&gt; Again, anyone part of this mailing list, anyone that has used
&gt; the LDP, anyone that likes what they see can assist in promoting
&gt; the LDP. Posting to the ng's is no doubt a good place to start.
&gt; Placing links to the TPL on individual websites is another.
Agreed, very much.
&gt; &gt; &gt; Maybe we should treat authors like software authors: When someone is
&gt; &gt; &gt; the maintainer of a software package, they put their email address on
&gt; &gt; &gt; it. They _expect_ to receive bug reports and gripes which are then
&gt; &gt; &gt; folded back into the software to improve it. When it gets to be too
&gt; &gt; &gt; much for them, they hand the reigns to someone else.
&gt; &gt; &gt;
&gt; &gt; &gt; How about this: A new display engine on the website which lists the
&gt; &gt; &gt; requested doc in the right frame, but down the left margin lists
&gt; &gt; &gt; the title, the date, author contact info and the version numbers of
&gt; &gt; &gt; mentioned software. Below this is a survey form that says &quot;How
&gt; &gt; &gt; useful is this doc?&quot; Then, once we have a significant database of
&gt; &gt; &gt; reviews, when someone searches for a doc, the search results page
&gt; &gt; &gt; shows the title of the document followed by its review metrics, its
&gt; &gt; &gt; age and the version numbers.
&gt; &gt;
&gt; &gt; Good idea, I second this.
&gt;
&gt; I *like* the idea, but I'm worried about us modifying the display
&gt; in any way, shape or form...especially using frames. Call it
&gt; paranoia.
Sorry, I was too quick, I dislike the frame mechanism but the
table tags can be put to good use here. Take the HOWTO
index page, run it through a script to add on the survey,
comments field etc. or use the Freshmeat method.
&gt; How about, for a start, just a simple way to provide feedback - a
&gt; page linked to from the other &quot;main&quot; pages we have on the LDP? It
&gt; may at least help to garner some form of feedback. I realize it isn't
&gt; quite the fine-grained functionality we'd like to have/need, but it
&gt; is a start.
&gt;
&gt; I can put together a form and then collect and/or email the
&gt; results from each inquiry; if this is an approach we decide
&gt; upon. Like I said, it's a starting point; it might remove the
&gt; intimidation factor some people might feel wrt emailing an
&gt; author directly.
A user writable web log would lessen the burden of maintaining
the system, something I feel is important given the limited
resources.
&gt; &gt; &gt; Part of this is also proper dating of material. All LDP docs should
&gt; &gt; &gt; say right at the top the date of last revision, and the search engine
&gt; &gt; &gt; results must tell me this. What good is it to find a ppp-2.1 or a
&gt; &gt; &gt; kernel-2.0 doc? Maybe I really am looking for help with old
&gt; &gt; &gt; technology, but I will bet real money most queries against the LDP
&gt; &gt; &gt; search engine are looking for help with the most recent Linux
&gt; &gt; &gt; distributions --- the vast majority of the Linux users out there today
&gt; &gt; &gt; have been using Linux for less than a year.
Perhaps the HOWTO HOWTO should have a few notes about
obligatory parts such as
- date
- version number
- email address
- document homepage
&gt; &gt; Again this is not the first time this topic comes up and many
&gt; &gt; authors were approached by a 3.rd party willing to take up that
&gt; &gt; job. Nothing has been heard of since.
&gt; &gt;
&gt; &gt; I proposed an automated cooperation with Freshmeat, another idea
&gt; &gt; that sunk mostly without a trace. Yet when I check the place
&gt; &gt; <A HREF="http://freshmeat.net/search.php3?query=HOWTO">http://freshmeat.net/search.php3?query=HOWTO</A>
&gt; &gt; I find 17 HOWTOs have quietly been registered, and tracking
&gt; &gt; numbers and dating is done, an example:
&gt; &gt; <A HREF="http://freshmeat.net/appindex/1999/06/26/930410556.html">http://freshmeat.net/appindex/1999/06/26/930410556.html</A>
&gt; &gt; Looking closer I notice it is possible for users to make
&gt; &gt; comments directly to those web pages. It does look like
&gt; &gt; Freshmeat ALREADY has done what we have talked about.
I would like to add that you also get click-though statistics
for each document, that could save us a lot of work.
&gt; &gt; I suggest we get a TODO list of good ideas up. Many ideas come
&gt; &gt; up again and again and sink without trace. I think even a TODO
&gt; &gt; list was mentioned some time ago but funnily enough nothing
&gt; &gt; happened.
&gt;
&gt; Start sending me items, I'll put one together.
OK, a few points:
- Add META tags to the LDP homepage, that can improve ranking
on many search engines
- Ask the maintainer of the Pedia to join LDP, if not we should
add a link to his page
- Many have links to LDP, it is only polite to return the favour,
also there are many links to zines we could add
- add a link to FAQs
- An idea from IMDB, add links to &quot;related topics&quot;, for instance
for the Multi Disk HOWTO the Partitioning- , Partition Rescue- ,
Large Disk HOWTO are relevant. Again links to Usenet News FAQs
could be relevant
- Consider a link to OSWG; while politically sensitive here we
should not forget the end users might benefit here
- Get the rest of the HOWTOs registered with Freshmeat
- Ask Linux Weekly News to get a small section on LDP news,
perhaps best place is their Development section
- run an automated robot to look for broken links in documents;
many like me don't have the net access to do this well
- Approach the various distribution compilers to join this
mailing list, and persuade them to keep fresh LDP HOWTO archives
in their errata section
- Make an intro.ldp manpage to point out to users where to find
the HOWTOs on their disks, not all know of /usr/doc/HOWTO
- Make the TODO list, with dates on submission and completion
-
(have to stop, machine about to crash...)
Regards,
Stein Gjoen
--
To UNSUBSCRIBE, email to ldp-discuss-request@lists.debian.org
with a subject of &quot;unsubscribe&quot;. Trouble? Contact listmaster@lists.debian.org
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="01137" href="msg01137.html">Re: mini-HOWTO</a></strong>
<ul><li><em>From:</em> Gregory Leblanc &lt;gleblanc@cu-portland.edu&gt;</li></ul></li>
<li><strong><a name="01149" href="msg01149.html">Re: mini-HOWTO</a></strong>
<ul><li><em>From:</em> Gary Lawrence Murphy &lt;garym@canada.com&gt;</li></ul></li>
<li><strong><a name="01150" href="msg01150.html">Processing HOWTOs</a></strong>
<ul><li><em>From:</em> Stein Gjoen &lt;sgjoen@mail.nyx.net&gt;</li></ul></li>
<li><strong><a name="01153" href="msg01153.html">Re: Processing HOWTOs</a></strong>
<ul><li><em>From:</em> &quot;Greg Ferguson&quot; &lt;gferg@hoop.timonium.sgi.com&gt;</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg01185.html">Re: mailing list archives</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01187.html">Re: mailing list archives</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01154.html">Re: Processing HOWTOs</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01156.html">Re: Processing HOWTOs</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01186"><strong>Date</strong></a></li>
<li><a href="threads.html#01186"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>