cvs commit: www/hints adoptahint.html archive-bottom.html hints-template.html list.html news-bottom.html submit.html whatarehints.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Sat Sep 6 07:10:41 PDT 2003


jeroen      03/09/06 08:10:41

  Modified:    .        sitemap.html
               hints    adoptahint.html archive-bottom.html
                        hints-template.html list.html news-bottom.html
                        submit.html whatarehints.html
  Log:
  Applied Tushar's patch to rewrite most of the text of the hints' pages. Reworked the hints menu a bit; removed the acknowledgments page and added a link to the hints attachments.
  
  Revision  Changes    Path
  1.35      +1 -1      www/sitemap.html
  
  Index: sitemap.html
  ===================================================================
  RCS file: /home/cvsroot/www/sitemap.html,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- sitemap.html	4 Sep 2003 19:03:50 -0000	1.34
  +++ sitemap.html	6 Sep 2003 14:10:40 -0000	1.35
  @@ -154,13 +154,13 @@
   					<li><a href="hints/submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   					<li><a href="hints/adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   					<li><a href="hints/list.html" title="A list of all hints to read online">Read hints</a></li>
  -					<li><a href="hints/acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   				</ul>
   			</li>
   			<li><h5>Download:</h5>
   				<ul>
   					<li><a href="hints/files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   					<li><a href="hints/files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +					<li><a href="hints/files/attachments/" title="For hints which require additional files">Attachments</a></li>
   				</ul>
   			</li>
   		</ul>
  
  
  
  1.30      +12 -6     www/hints/adoptahint.html
  
  Index: adoptahint.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/adoptahint.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- adoptahint.html	4 Sep 2003 19:40:52 -0000	1.29
  +++ adoptahint.html	6 Sep 2003 14:10:41 -0000	1.30
  @@ -39,14 +39,20 @@
   	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
   
   <h2>Adopt a hint</h2>
  -	<p>There are a lot of hints available here and not all of them are equally maintained. Some are abandonded by their author or are explicitly marked as adoptable. If you would like to adopt a hint, please contact its original author and CC <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">the hints mailinglist</a>. If the original author agrees to your maintainership, your updates will be included in the hint. In case the author does not respond, we will wait at least 1 month before requests to take over the hint are honored. The original hint is then placed in the <a href="list.html#abandoned">orphaned</a> hints section, and the updated hint takes its place.</p>
  -	<p>If you're a hint author and you're no longer able or willing to maintain your hint, please mail <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">the hints mailinglist</a> and set in your subject line "Up for adoption: (your hint)". Then it will be added to the list below.</p>
  +	<p>There are a lot of hints available here and not all of them are equally maintained. This page attempts to provide the current hint authors to offer their hint for adoption if they are not interested in maintaining the hint anymore. This page also attempts to provide a wish list for hints.</p>
  +	<p>If you are an hint author and are not interested in maintaining your hint anymore, we would appreciate you dropping a line to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">the hints mailinglist</a> stating that you are putting your hint for adoption.</p>
  +	<p>If you have a request for a hint, please drop a line to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">the hints mailinglist</a> and we will put the idea on this page for adoption.</p>
  +
   <h3>Adopters wanted</h3>
   	<p>These hints are explicitly marked as <em>orphaned</em>. This means that whomever is willing to do the job may take over the hint. The original author will still be credited, of course.</p>
   		<ul>
  -			<li>hint1</li>
  -			<li>hint2</li>
  -			<li>hint3</li>
  +			<li><em>No hints currently available.</em></li>
  +		</ul>
  +
  +<h3>Wish List</h3>
  +    <p>These are topics that other users have shown interest. If you feel confident on writing a hint on the this topic, drop a note to <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">the hints mailinglist</a>, get your pen and paper, err I mean start your workstation and start typing.</p>
  +		<ul>
  +			<li><em>No hints currently available.</em></li>
   		</ul>
   
   </div> <!-- end content -->
  @@ -72,11 +78,11 @@
   		<li><a href="submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint" class="currentpage">Adopt a hint</a></li>
   		<li><a href="list.html" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  
  1.5       +1 -1      www/hints/archive-bottom.html
  
  Index: archive-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/archive-bottom.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- archive-bottom.html	3 Sep 2003 16:20:28 -0000	1.4
  +++ archive-bottom.html	6 Sep 2003 14:10:41 -0000	1.5
  @@ -22,11 +22,11 @@
   		<li><a href="../../../hints/submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="../../../hints/adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="../../../hints/list.html" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="../../../hints/acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="../../../hints/files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="../../../hints/files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="../../../hints/downloads/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</ul>
   
  
  
  
  1.28      +2 -2      www/hints/hints-template.html
  
  Index: hints-template.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/hints-template.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- hints-template.html	4 Sep 2003 19:40:52 -0000	1.27
  +++ hints-template.html	6 Sep 2003 14:10:41 -0000	1.28
  @@ -1,4 +1,4 @@
  -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  +s<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   
   <head>
  @@ -65,11 +65,11 @@
   		<li><a href="submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="list.html" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  
  1.32      +4 -1      www/hints/list.html
  
  Index: list.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/list.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- list.html	4 Sep 2003 21:39:38 -0000	1.31
  +++ list.html	6 Sep 2003 14:10:41 -0000	1.32
  @@ -40,6 +40,8 @@
   
   <h2>Read hints</h2>
   
  +<em class="highlight">The hints list is currently out of date and will be replaced by a script. See <a href="../website.html#todo">the todo list</a> for the requirements of this script. Mail <a href="http://linuxfromscratch.org/mailman/listinfo/website" title="Subscription and archive of the website mailinglist">the website mailinglist</a> if you want to help with such a script.</em>
  +<!--
   <div id="pagenav">
   	<ul>
   		<li><a href="#booting">Booting</a></li>
  @@ -317,6 +319,7 @@
   		<li><a href="files/netscape.txt">Netscape 4.72+</a><br />How to fix the missing library problem while installing Netscape 4.72 (as of v. 4.74, the problem still hasn't been fixed, and therefore this hint is very useful (but the soname has to be changed to the name of the missing library)).</li>
   		<li><a href="files/w3m.txt">w3m hint</a><br />Installation of w3m, wich is a text only www browser supporting frames.</li>
   	</ul>
  +-->
   
   </div> <!-- end content -->
   
  @@ -341,11 +344,11 @@
   		<li><a href="submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="list.html" class="currentpage" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  
  1.11      +1 -1      www/hints/news-bottom.html
  
  Index: news-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/news-bottom.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- news-bottom.html	4 Sep 2003 19:44:14 -0000	1.10
  +++ news-bottom.html	6 Sep 2003 14:10:41 -0000	1.11
  @@ -24,11 +24,11 @@
   		<li><a href="submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="list.html" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  
  1.32      +20 -22    www/hints/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/submit.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- submit.html	4 Sep 2003 19:40:52 -0000	1.31
  +++ submit.html	6 Sep 2003 14:10:41 -0000	1.32
  @@ -40,13 +40,27 @@
   
   <h2>Hint style and submisson guide</h2>
   <h3 id="howtowrite">How to write a hint</h3>
  -	<p>Anyone can submit an lfs-hint. We'll list some general rules and guidelines for writing hints, and offer you some technical details on how to layout the hint.</p>
   	<p>A good hint provides information which is not otherwise easily obtainable. In general, we're not interested in hints which copy information already in LFS or BLFS and hints which simply list the steps needed for installing a package as explained in the INSTALL or README of a package.</p>
  -	<p>This leaves a broad scope of subjects. Hints can be about everything for which a non-obvious or non-trivial fix or hack is required. A hint can also explain a complicated package installation or a particular setup. Have a look at some <a href="list.html">other hints</a> to get an idea of what a hint may include.</p>
  -	<p>Once you have a good and original idea for a hint, you can start writing. Stick to the following style rules if you want to <a href="submit.html">submit</a> it for inclusion.</p>
  +	<p>This still leaves a broad scope of subjects. Hints can be about everything for which a non-obvious or non-trivial fix or hack is required. A hint can also explain a complicated package installation or a particular setup. Have a look at some <a href="list.html">other hints</a> to get an idea of what a hint may include. Also check out the <a href="adoptahint.html">Adopt a hint program</a> in case there is some cute little hint that you would like to nurture or if someone has suggested a topic for a hint.</p>
  +	<p>Once you have a good idea for a hint, you can start writing. Stick to the following style rules if you want to submit it for inclusion.</p>
  +
  +<h3>Submission guidelines</h3>
  +<ul>
  +	<li>Before submitting a hint, check if there is an already existing hint on the topic. If there is then contact the author if you have any updates. If the previous author is not interested in maintaining the hint, or if there is no response from the author for at least a month, then you may take over maintainence of the hint. Remember to CC hints-owner at linuxfromscratch.org  regarding all correspondence with the author so that the hint maintainers are aware of the changeover.<br />
  +		<em>Note that this does not mean that duplicate hints on the same topic are not allowed. If you feel that the current author has a different approach to a problem and you have one which does not match the current hint, feel free to submit a separate hint. We suggest communicating with the current author(s) before writing the hint. We suggest writing a short blurb on how the new hint differs from the existing one.</em></li>
  +	<li>Hints should be reserved for things that cannot be included into the book. Hints that relate to installation of packages and which would easily fit into the book (usually the BLFS book) should be submitted to the relevant development list.  If you are conversant with docbook and XML, then feel free to submit a patch to the current CVS Book version. If not, submit a text file matching the current format of the book and a book editor will do the neccessary modifications. </li>
  +	<li>If you are in the process of writing a hint on a topic, it would be good to drop a line to the relevant list in case someone else is working on something similar.</li>
  +	<li>A hint should not duplicate documentation that is already available elsewhere on a particular topic, it should complement it. Documentation available elsewhere includes <a href="http://www.tldp.org/">LDP documentation</a>, documentation available from the package website, documentation available by a simple <a href="http://www.google.com">google</a> search. Also, things that are already well documented in the book(s) or at the LDP should not be repeated in the hint unless the hint describes matters in more detail, in a different way, or from a different perspective. So things such as installation of db, freetype, zlib, etc can just be referenced by pointers to the book. </li>
  +	<li>Authors who are not interested in maintaining their hints any more should send a message to the hints mailing list specifying that the hint is <a href="adoptahint.html">up for adoption</a>. The author should also notify the hints list if the hint is not relevant anymore.</li>
  +	<li>Hints that have been integrated into the book will be retired after a stable version of the book is released.</li>
  +	<li>Keep the file name of the hint short, but descriptive. The extension for the hint should be .txt. The name should be all lowercase.</li>
  +	<li>The hint document is text based. The format for the hints is as explained at the end of this document.</li>
  +	<li>Avoid including scripts and patches in the hints. Keep these as separate files to avoid spoiling the beauty of the hint:) Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. For all attachments for the hint, create a tarball that will untar into a directory that has the same name as the name of your hint (without the .txt extension). This tarball will be hosted in the download section for users to download. Patches for packages will also be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. So be sure to mention the name of your hint in the patch description.</li>
  +	<li>To submit or update a hint, send an e-mail to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="http://linuxfromscratch.org/mailman/listinfo/hints">subscribe</a> to the hints mailinglist and check for the CVS commit message. Keep the hints list solely for <strong>submitting hints and updates to hints</strong>. If you want to discuss or announce a new hint.</li>
  +</ul>
   
   <h3 id="hintformat">Hint Format</h3>
  -	<p>Every hint should have the following sections, in the order specified here so as to have a consistent look and feel:) Check out the <a href="files/hint_sample.txt">example hint</a>.</p>
  +	<p>Every hint should have the following sections, <em>in the order specified here</em> so as to have a consistent look and feel:) Sections that are supposed to be single lines should be on the same line as the section header. Sections that are more than one line should begin from the line following the header. Check out the <a href="sample-hint.txt">example hint</a> to get an idea about the format.</p>
   	<dl>
   		<dt>AUTHOR:</dt>
   			<dd>This field can be repeated if there are multiple authors. Each author line should have name and contact details of the hint author.</dd>
  @@ -72,8 +86,7 @@
   				<li>[YYYY-MM-DD]</li>
   				<li> * Changed A</li>
   				<li> * Changed B</li>
  -			</ul>
  -			In addition, if the changes are based a user's comments to you, mention the name/e-mail in the ChangeLog.</dd>
  +			</ul></dd>
   	</dl>
   
   <div class="highlight">
  @@ -82,21 +95,6 @@
   	<p>If you have suggestions for improving this document, feel free to discuss it on the hints mailing list or drop a line to the hint maintainers at <a href="mailto:hints-owner at linuxfromscratch.org">hints-owner at linuxfromscratch.org</a>. The lfs-hints project is currently maintained by <a href="mailto:tushar at linuxfromscratch.org">Tushar Teredesai</a>.</p>
   </div>
   
  -<h3>Submission guidelines</h3>
  -<ul>
  -	<li>Before submitting a hint, check if there is an already existing hint on the topic. If there is then contact the author if you have any updates. If the previous author is not interested in maintaining the hint, or if there is no response from the author for at least a month, then you may <a href="adoptahint.html">take over maintainence of the hint</a>. Remember to CC hints-owner at linuxfromscratch.org  regarding all correspondence with the author so that the hint maintainers are aware of the changeover.<br />
  -		<em>Note that this does not mean that duplicate hints on the same topic are not allowed. If you feel that the current author has a different approach to a problem and you have one which does not match the current hint, feel free to submit a separate hint. We suggest writing a short blurb on how the new hint differs from the existing one. Remember, the more information users have related to your hint, the more the chances of someone using the hint.</em></li>
  -	<li>Hints should be reserved for things that cannot be included into the book. Hints that relate to installation of packages and which would easily fit into the book (usually the BLFS book) should be submitted to the relevant development list.  We reserve the instructions and basic configuration for the book and leave the additional stuff such as advanced configuration and detailed explanations in a hint. If you are conversant with docbook and XML, then feel free to submit a patch to the current CVS Book version. If not, submit a text file matching the current format of the book and a book editor will do the neccessary modifications. </li>
  -	<li>If you are in the process of writing a hint on a topic, it would be good to drop a line to the relevant list in case someone else is working on something similar.</li>
  -	<li>A hint should not duplicate documentation that is already available elsewhere on a particular topic, it should complement it. Documentation available elsewhere includes <a href="http://www.tldp.org/">LDP documentation</a>, documentation available from the package website, documentation available by a simple <a href="http://www.google.com">google</a> search. Also, things that are already well documented in the book(s) or at the LDP should not be repeated in the hint unless the hint describes matters in more detail, in a different way, or from a different perspective. So things such as installation of db, freetype, zlib, etc can just be referenced by pointers to the book. </li>
  -	<li>Authors who are not interested in maintaining their hints any more should send a message to the hints mailing list specifying that the hint is <a href="adoptahint.html">up for adoption</a>. The author should also notify the hints list if the hint is not relevant anymore.</li>
  -	<li>Hints that have been integrated into the book will be retired after a stable version of the book is released.</li>
  -	<li>Keep the file name of the hint short, but descriptive. The extension for the hint should be .txt. The name should be all lowercase.</li>
  -	<li>The hint document is text based. The format for the hints is as explained at the end of this document. Alternatively, if your hint contains patches or scripts, you may submit both a tarball (tar.gz) and a textfile of the hint. The tarball contains both the hint and the scripts/patches/whatever.</li>
  -	<li>Avoid including scripts and patches in the hints. Submit these as separate files along with the hint submission and they will be hosted on a separate location for download. Patches should follow the <a href="http://patches.linuxfromscratch.org">patches format</a>. Patches for packages will be hosted on Patches project website. For example, if your hint has a patch for gcc, that patch will be hosted under gcc directory. All other patches/scripts will be available for download from the hints website.</li>
  -</ul>
  -	<p>To submit or update a hint, send an e-mail to the <a href="http://linuxfromscratch.org/mailman/listinfo/hints" title="Archive and subscription information for the hints mailinglist">hint mailing list</a>. From there it will be picked up by the hint maintainer, who will update the hint index and the tarball. To check if your hint has already been included, you can <a href="http://linuxfromscratch.org/mailman/listinfo/hints">subscribe</a> to the hints mailinglist, check its <a href="http://linuxfromscratch.org/pipermail/hints/">archive</a> or use the <a href="../newsgroups.html">news group</a> gateway. As soon as it's added it's also viewable from the <a href="list.html">list</a> and the <a href="files/">files</a> sections on this website.</p>
  -	<p>Keep the hints list solely for <strong>submitting hints and updates to hints</strong>. If you want to discuss or announce a new hint, <a href="http://linuxfromscratch.org/mailman/listinfo/blfs-support" title="Archive and subscription information for the blfs-support mailinglist">blfs-support</a> is a good forum.</p>
   
   </div> <!-- end content -->
   
  @@ -120,12 +118,12 @@
   		<li><a href="whatarehints.html" title="What are LFS hints?">Project overview</a></li>
   		<li><a href="submit.html" class="currentpage" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><a href="list.html" title="A list of all hints to read online">Read hints</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  
  1.28      +14 -4     www/hints/whatarehints.html
  
  Index: whatarehints.html
  ===================================================================
  RCS file: /home/cvsroot/www/hints/whatarehints.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- whatarehints.html	4 Sep 2003 19:40:52 -0000	1.27
  +++ whatarehints.html	6 Sep 2003 14:10:41 -0000	1.28
  @@ -39,11 +39,21 @@
   	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
   
   	<h2>LFS Hints</h2>
  -	<p>The LFS-Hints are small documents that explain how to do things that are not in the LFS or BLFS books. They provide a variety of information such as alternative ways of building and configuring packages, information on new packages that haven't yet made it into the books, specialized techniques for specific hardware, and other areas that interest LFS users.</p>
  -	<p>If you have a specific problem which is not answered by LFS, BLFS or the FAQ, chances are there is a hint written about it, detailing everything you need to know. And if there isn't, you can <a href="howtowrite.html">write one yourself</a>!</p>
  -	<p>You can <a href="files/hints.tar.bz2">download</a> all the hints at once or read them <a href="list.html">online</a>.</p>
  +	<p>The LFS-Hints are small documents that explain how to do things that are not in the LFS or BLFS books. They provide a variety of information such as alternative ways of building and configuring packages, information on new/unstable packages that haven't yet made it into the books, specialized techniques for specific hardware, and other areas that interest LFS users.</p>
  +	<p>If you have a specific problem which is not answered by LFS, BLFS, the FAQ or the project documentation, chances are there is a hint written about it, detailing everything you need to know. And if there isn't, you can <a href="howtowrite.html">write one yourself</a>!</p>
   	<p>Have fun reading or writing!</p>
   
  +    <h2>Maintainer</h2>
  +	<p>The project is currently maintained by <a href="http://www.linuxfromscratch.org/~tushar/">Tushar Teredesai</a>.</p>
  +
  +    <h2>Past Maintainers</h2>
  +    <ul>
  +        <li><a href="mailto:timothy at linuxfromscratch.org">Timothy Bauscher</a> (June 2002 - August 2003)</li>
  +        <li><a href="mailto:ian at ichilton.co.uk">Ian Chilton</a> (June 2001 - June 2002)</li>
  +        <li><a href="mailto:nomis80 at videotron.ca">Simon Perreault</a> (August 2000 - June 2001)</li>
  +    </ul>
  +
  +
   </div> <!-- end content -->
   
   <div id="footer">
  @@ -67,11 +77,11 @@
   		<li><a href="submit.html" title="How to write and submit proper hint">Submission Guidelines</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="list.html" title="A list of all hints to read online">Read hints</a></li>
  -		<li><a href="acknowledgements.html" title="Maintainers and acknowledgements">Maintainers</a></li>
   		<li><h3>Download:</h3>
   			<ul>
   				<li><a href="files/hints.tar.bz2" title="A tarball of all hints, generated daily">Hints tarball</a></li>
   				<li><a href="files/" title="An unsorted list of the latest version of all hints">Individual hints</a></li>
  +				<li><a href="files/attachments/" title="For hints which require additional files">Attachments</a></li>
   			</ul>
   		</li>
   	</ul>
  
  
  



More information about the website mailing list