cvs commit: www/hints adoptahint.html submit.html

jeroen at jeroen at
Thu Oct 30 02:26:50 PST 2003

jeroen      03/10/30 03:26:50

  Modified:    hints    adoptahint.html submit.html
  Applies Tushars patch for the hints website.
  Revision  Changes    Path
  1.48      +0 -1      www/hints/adoptahint.html
  Index: adoptahint.html
  RCS file: /home/cvsroot/www/hints/adoptahint.html,v
  retrieving revision 1.47
  retrieving revision 1.48
  diff -u -r1.47 -r1.48
  --- adoptahint.html	12 Oct 2003 19:13:56 -0000	1.47
  +++ adoptahint.html	30 Oct 2003 10:26:49 -0000	1.48
  @@ -55,7 +55,6 @@
   			<li><a href="downloads/files/PREVIOUS_FORMAT/lowspace.txt">lowspace.txt</a> and <a href="downloads/files/PREVIOUS_FORMAT/stripped-down.txt">stripped-down.txt</a> - should be merged into one hint</li>
   			<li><a href="downloads/files/PREVIOUS_FORMAT/security.txt">security.txt</a></li>
   			<li><a href="downloads/files/PREVIOUS_FORMAT/optimization.txt">optimization.txt</a></li>
  -			<li><a href="downloads/files/PREVIOUS_FORMAT/lfsbackup.txt">lfsbackup.txt</a></li>
   <h3>Wish List</h3>
  1.44      +1 -1      www/hints/submit.html
  Index: submit.html
  RCS file: /home/cvsroot/www/hints/submit.html,v
  retrieving revision 1.43
  retrieving revision 1.44
  diff -u -r1.43 -r1.44
  --- submit.html	17 Oct 2003 13:07:53 -0000	1.43
  +++ submit.html	30 Oct 2003 10:26:49 -0000	1.44
  @@ -55,7 +55,7 @@
   	<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="">patches format</a>. For all attachments for the hint, created a tarball with the same name as your hint and that will untar into a directory that has the same name as the name of your hint (without the .txt extension). For example, if your hint is foo.txt, then the tarball would be named foo.tar.bz2 (replace compression extension by the one that you use) and it would untar into foo directory. 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>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="">patches format</a>. The patches that you submit will be comitted to the patches repository (so be sure to mention the hint in the patch description) under the appropriate package name. The scripts or patches that don't fit into the patches project will be available from the <a href="downloads/attachments">Attachments</a> link in the left menu. If you need to reference any patches in your hint, point to the patches subproject (e.g.<package_name>/<patch_name>). If you need to reference to any attachments, point to the attachments directory (e.g.<hint_name>/) Don't worry if the URIs are incorrect, the maintainer will modify the URIs before submitting. Since maintainers are sometimes lazy, you may need to give them a bit of a push/shove to "do the right thing".</li>
   	<li>To submit or update a hint, send an e-mail to the <a href="" 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="">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>.</li>
   	<li><strong>Note that by submitting a hint, you agree to the conditions mentioned on this page with respect to the hint. In particular, you allow other users to take over the maintainership of the hint if another user contacts you with a request (for taking over the maintainership or integrating his/her work in your hint) and you fail to respond to the request for a month. If you would not like someone to take over the maintainership of the hint, please state so clearly in the hint. Authors should also keep the contact information updated.</strong></li>

More information about the website mailing list