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

iready for publish

This commit is contained in:
tille 2003-08-13 17:38:36 +00:00
parent 811ff2d196
commit 945b362ef6
1 changed files with 4 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
LDP/ldpwn/20030810.xml
View File

@ -51,7 +51,7 @@
<listitem><para>The <ulink url="http://tldp.org/HOWTO/Kernel-HOWTO/">Linux Kernel HOWTO</ulink>, v6.5 was sent in by Alavoor Vasudevan.</para></listitem>
<listitem><para>David Lawyer is still updating the <ulink url="http://tldp.org/HOWTO/Modem-HOWTO.html">Modem HOWTO</ulink>, in order to help all those who can't have fast access yet; it's now at v0.29.</para></listitem>
<listitem><para>Rick Moen sent in v1.6.3 of the <ulink url="http://tldp.org/HOWTO/User-Group-HOWTO.html">Linux User Group HOWTO.</para></listitem>
<listitem><para>And Håvard Stranden's <ulink url="http://tldp.org/HOWTO/XFree86-R200/">ATI R200 + XFree86 4.x mini-HOWTO</ulink> is now availabl in v1.3.</para></listitem>
<listitem><para>And Håvard Stranden's <ulink url="http://tldp.org/HOWTO/XFree86-R200/">ATI R200 + XFree86 4.x mini-HOWTO</ulink> is now available in v1.3.</para></listitem>
<listitem><para>Miroslav Skoric updated his <ulink url="http://tldp.org/HOWTO/FBB.html">FBB mini-HOWTO.</para></listitem>
<listitem><para>Eric S. Raymond sent in an update for the <ulink url="http://tldp.org/HOWTO/Linksys-Blue-Box-Router-HOWTO/">Linksys Blue Box Router HOWTO</ulink>.</para></listitem>
<listitem><para>Gerardo Arnaez presented v2.2 of the <ulink url="http://tldp.org/HOWTO/Medicine-HOWTO/">Linux Medicine HOWTO</ulink>.</para></listitem>
@ -121,7 +121,7 @@ wholeheartedly that I'm a stronger writer for it, so why stop now? :D
<para>Q: What do you think is the single most needed improvement for TLDP?</para>
<para>A: <quote>I'll stand my ground and say it would have to be an online editor for
authors. It should provide a simple way for authors to choose the
version of markup they wish to use, and help them progess through
version of markup they wish to use, and help them progress through
creation of their document in a logical format, based on the LDP
documentation templates. Ideally, this system would parse and validate,
provide suggestions for errors, and allow for a browser preview no
@ -148,28 +148,13 @@ valuable to everyone. Dream big!</quote></para>
<sect1>
<title>Happenings in the LDP world</title>
<para>.</para>
<sect2>
<title>Title1</title>
<title>We make free documentation</title>
<para>.</para>
<para>A very long and at times tiresome discussion about who can or can not use TLDP documents dominated the past two weeks. You can read the entire thread <ulink url="http://lists.tldp.org/index.cgi?1:mss:4905:200308:nndilkkmnocimdnhjmkm">here</ulink>. Summarized, it comes down to this: everybody can read our docs and store them on their servers, in accordance with the GPL. This includes also people we don't like.</para>
</sect2>
<sect2>
<title>Title2</title>
<para>.</para>
</sect2>
<sect2>
<title>Title3</title>
<para>.</para>
</sect2>
</sect1>
<sect1 id="feedback">