LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

sid rendered, ispelled, ready to publish

This commit is contained in:
appaji 2004-04-14 15:46:07 +00:00
parent be006aefd5
commit 3c5a003cce
1 changed files with 50 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

93
LDP/ldpwn/20040414.xml
View File

@ -17,10 +17,7 @@
<itemizedlist> <itemizedlist>
<listitem><para>Emma Jane was still not happy with the Author Guide and after some discussion submitted a <ulink url="http://cvsview.tldp.org/index.cgi/LDP/guide/docbook/LDP-Author-Guide/">new update</ulink>, merging the contribution section into the TLDP publishing process section.</para></listitem> <listitem><para>Emma Jane was still not happy with the Author Guide and after some discussion submitted a <ulink url="http://cvsview.tldp.org/index.cgi/LDP/guide/docbook/LDP-Author-Guide/">new update</ulink>, merging the contribution section into The LDP publishing process section.</para></listitem>
<listitem><para>Christine Lorenz submitted v2.3.0 of the <ulink url="http://tldp.org/LDP/EVMSUG/html/index.html">EVMS User Guide</ulink>. She is co-author of this document with Joy Goodreau and Kylie Smith.</para></listitem>
</itemizedlist> </itemizedlist>
@ -32,7 +29,12 @@
<itemizedlist> <itemizedlist>
<listitem><para>Nico Schottelius wrote a <ulink url="http://lists.tldp.org/index.cgi?5:mss:9046:200404:gkahgfjmoglaokcaaepk">mini-HOWTO about Cryptoloop partial security</ulink> and awaits your comments.</para></listitem> <listitem><para>Nico Schottelius wrote a <ulink
url="http://lists.tldp.org/index.cgi?5:mss:9046:200404:gkahgfjmoglaokcaaepk">mini-HOWTO
about Cryptoloop partial security</ulink> and awaits your comments. The
document explains what Cryptoloop is, what it is used for and why it is
only partially secure. A section also discusses solutions to the
problem. </para></listitem>
</itemizedlist> </itemizedlist>
@ -43,11 +45,13 @@
<itemizedlist> <itemizedlist>
<listitem><para>David Hinds provides us with v2.118 of his <ulink url="http://tldp.org/HOWTO/PCMCIA-HOWTO.html">Linux PCMCIA HOWTO</ulink>. This version features updated lists of supported hardware, updated program version numbers of the discussed software and a whole new section about the kernel PCMCIA support in 2.4 kernels and higher.</para></listitem> <listitem><para>David Hinds submitted the v2.118 of his <ulink url="http://tldp.org/HOWTO/PCMCIA-HOWTO.html">Linux PCMCIA HOWTO</ulink>. This version features updated lists of supported hardware, updated program version numbers of the discussed software and a whole new section about the kernel PCMCIA support in 2.4 kernels and higher.</para></listitem>
<listitem><para>.</para></listitem> <listitem><para>Christine Lorenz submitted v2.3.0 of the <ulink url="http://tldp.org/LDP/EVMSUG/html/index.html">EVMS User Guide</ulink>. She is co-author of this document with Joy Goodreau and Kylie Smith.</para></listitem>
<listitem><para>.</para></listitem> <listitem><para>Walt Penningtons <ulink url="http://tldp.org/HOWTO/Medicine-HOWTO/">Linux
Medicine-HOWTO</ulink> is now at v2.3. This new release has few minor
updates. </para></listitem>
</itemizedlist> </itemizedlist>
@ -60,25 +64,29 @@
<listitem> <listitem>
<para>News item title 1:</para> <para>The LDP Feedback</para>
<para>News item 1 body.</para> <para>It has been close to an year since The LDP weekly news was
re-started. The <ulink url="http://tldp.org/ldpwn/latest.html">latest
LDPWN</ulink> is available on the web, mailed to the
<email>news@en.tldp.org</email> mailing list and several important news
sources. There is also an <ulink
url="http://www.karakas-online.de/myServices/rssify.php?url=http://tldp.org/ldpwn/latest.html">RSS
feed</ulink> in case you would like to track us with your favorite
aggregator. We take this opportunity to request you for comments and
suggestions for improvement. Please send in your feedback to
<email>feedback@en.tldp.org</email></para>
</listitem> </listitem>
<listitem> <listitem>
<para>News item title 2:</para> <para>IRC: Freenode Server #tldp room</para>
<para>News item 2 body.</para> <para>The Freenode servers we have a #tldp room for IRC. Connect to one
of the servers at <ulink
</listitem> url="http://freenode.net/irc_servers.shtml">http://freenode.net/irc_servers.shtml</ulink>
and join #tldp.</para>
<listitem>
<para>News item title 3:</para>
<para>News item 3 body.</para>
</listitem> </listitem>
@ -93,25 +101,25 @@
<listitem> <listitem>
<para>Discussion topic title 1:</para> <para>Document Licensing Discussion</para>
<para>Discussion topic 1 body.</para> <para>Rahul Sundaram was <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6964:200404:ihpahginmljdgbhooeje">unhappy</ulink>
</listitem> that he might be volunteering his work to document authors that restrict
their documentation with a non-free license and indicated what he
<listitem> thought would be acceptable licenses. Rick Moen <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6965:200404:pkdleajpekbbaookkgbd">described</ulink>
<para>Discussion topic title 2:</para> what those licenses were and their problems (like the <ulink
url="http://people.debian.org/~srivasta/Position_Statement.xhtml">DFSG-freeness
<para>Discussion topic 2 body.</para> of GNU FDL 1.2</ulink>). Rodolfo J. Paiz was of the <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6968:200404:ehngfbpnepphojhokgdn">opinion</ulink>
</listitem> that license of a document is an individual choice and volunteering for
a work with a license that one does not like is not obligatory. David
<listitem> Lawyer and Greg Ferguson <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6979:200404:claiepedajakajhoajgg">explained</ulink>
<para>Discussion topic title 3:</para> the <ulink
url="http://lists.tldp.org/index.cgi?1:mss:6982:200404:ifhbolfhjihbhnkaanhb">recommendations</ulink>
<para>Discussion topic 3 body.</para> of The LDP. </para>
</listitem> </listitem>
@ -122,7 +130,6 @@
<sect1 id="interview"> <sect1 id="interview">
<title>Interview with Emma Jane Hogbin</title> <title>Interview with Emma Jane Hogbin</title>
<figure> <figure>
<title>Emma Jane Hogbin</title> <title>Emma Jane Hogbin</title>
<mediaobject> <mediaobject>
@ -130,7 +137,7 @@
<imagedata fileref="emma.eps" format="EPS"/> <imagedata fileref="emma.eps" format="EPS"/>
</imageobject> </imageobject>
<imageobject> <imageobject>
<imagedata fileref="emma.png" format="PNG"/> <imagedata fileref="emma.jpg" format="JPG"/>
</imageobject> </imageobject>
<textobject> <textobject>
<phrase>Emma Jane Hogbin</phrase> <phrase>Emma Jane Hogbin</phrase>
@ -140,7 +147,7 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>Emma Jane Hogbin, probably the most talkative TLDP volunteer, was very <para>Emma Jane Hogbin, probably the most talkative TLDP volunteer, was very
enthousiastic when we asked her if she would grant us an interview. <ulink url="http://tldp.org/ldpwn/20040414.html#interview">Get to know enthusiastic when we asked her if she would grant us an interview. <ulink url="http://tldp.org/ldpwn/20040414.html#interview">Get to know
Emma Jane:</ulink></para> Emma Jane:</ulink></para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -157,7 +164,7 @@ Linux on my laptop I had to re-install the system about half a dozen times.
(Yes, I'm as shocked as you are.) Each time my notes improved and I got a (Yes, I'm as shocked as you are.) Each time my notes improved and I got a
little faster at performing each of the required steps.</para> little faster at performing each of the required steps.</para>
<para>The first publically available documentation I wrote for a specific <para>The first publicly available documentation I wrote for a specific
application was for <ulink url="http://www.htdig.org">ht://dig</ulink> (a great little search engine). application was for <ulink url="http://www.htdig.org">ht://dig</ulink> (a great little search engine).
The document was very well received by my client at the time, The document was very well received by my client at the time,
and by the ht://dig community. Although my documentation had always been and by the ht://dig community. Although my documentation had always been
@ -262,7 +269,7 @@ The review date would be based on the document's anniversary, not based on
the <quote>last updated</quote> date.</para> the <quote>last updated</quote> date.</para>
<para>That and having mugs for sale. The <ulink <para>That and having mugs for sale. The <ulink
url="http://www.hackerthreads.com/?page=shop/browse&category_id=ae255697973840ae34ac3dcd028e55ce">t-shirts</ulink> are nice, but what I really url="http://www.hackerthreads.com/?page=shop/browse&amp;category_id=ae255697973840ae34ac3dcd028e55ce">t-shirts</ulink> are nice, but what I really
want is a mug.</para> want is a mug.</para>
</sect1> </sect1>