cvs commit: www/test/hints howtowrite.html submit.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Aug 25 09:26:40 PDT 2003


jeroen      03/08/25 10:26:40

  Modified:    test     generalnews.txt
               test/hints howtowrite.html submit.html
  Log:
  Added GB's Team Coordinators mail to the general news
  
  Revision  Changes    Path
  1.7       +15 -0     www/test/generalnews.txt
  
  Index: generalnews.txt
  ===================================================================
  RCS file: /home/cvsroot/www/test/generalnews.txt,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- generalnews.txt	19 Aug 2003 02:12:57 -0000	1.6
  +++ generalnews.txt	25 Aug 2003 16:26:39 -0000	1.7
  @@ -3,6 +3,21 @@
   
   <!-- insert new news here. Keep the existing semantic structure, eg. h3 for news title, h4 for who - what and p's for the actual news. -->
   
  +	<h3 id="teamcoordinators">Team Coordinators</h3>
  +		<h4>Gerard Beekmans - 2003/08/25</h4>
  +		<p>I've had the chance to talk to everybody I wanted to and here's the outcome of who will be doing what. I imagine this will be in a state of flux as more people decide to jump on board later down the road. That's all good of course, so don't see this as set in stone, just a place to start off from with people who are interested right now.</p>
  +		<ul>
  +			<li>LFS.org (Organizational team): Gerard Beekmans, Bill Maltby</li>
  +			<li>LFS Testing Team: Ryan Oliver</li>
  +			<li>LFS Quality Assurance: Bruce Dubbs</li>
  +			<li>LFS Editorial Team: Gerard Beekmans</li>
  +			<li>Bugzilla Maintainers: James Robertson, Jeremy Utley</li>
  +			<li>CVS Maintainer: Vacant. I'll fill the role for now</li>
  +		</ul>
  +		<p>I've also gotten quite a few emails from people who like to join these teams. It'll be up to the team coordinators to start writen some rudimentary documentation asap that quickly outlines what will be done under the banner of a team, how it's done and more of that. These guidelines will also be in a state of flux I imagine, so I don't expect any long essays. Let that stuff evolve over time and concentrate on the actual work to be done, not on documenting everything. Others can do that for you (there's the LFS.org team who can help out there and other people like Richard Downing who can help out with such documentation needs).</p>
  +		<p>Anything I've forgotten that should be dealt with (team wise)?</p>
  +		<p><a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036920.html">Follow or discuss this item</a></p>
  +
   	<h3 id="nominations">Nominations again</h3>
   		<h4>Gerard Beekmans - 2003/08/19</h4>
   		<p>Okay, I know some of you don't like the way I'm doing the nominations. Maybe foolishly I thought since it worked very well for Seth with regards to the FAQ that it might work for LFS as a whole as well. Seeing the fact I've only gotten nominations from 9 people so far, I'm beginning to think people don't care about who will be chosen, or nobody is nominating because they don't like the way I'm doing it and are trying to make a point. Whatever the cause might be, I will of course take those 9 people into consideration, but will probably have to pick a team of people by myself. People who have been away and haven't had the chance to do anything yet, I'm not speaking to you, so don't take offense.</p>
  
  
  
  1.23      +1 -1      www/test/hints/howtowrite.html
  
  Index: howtowrite.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/howtowrite.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- howtowrite.html	25 Aug 2003 13:05:55 -0000	1.22
  +++ howtowrite.html	25 Aug 2003 16:26:40 -0000	1.23
  @@ -102,7 +102,7 @@
   		<ul>
   		<li><a href="news.html">Hints News</a></li>
   		<li><a href="whatarehints.html" title="What are these hints for?">What are LFS hints?</a></li>
  -		<li><a href="howtowrite.html" title="Style and format of hints" class="currentpage">How do I write LFS hints?</a></li>
  +		<li><a href="howtowrite.html" class="currentpage" title="Style and format guidelines of hints">Write a hint</a></li>
   		<li><a href="adoptahint.html" title="Edit an existing hint">Adopt a hint</a></li>
   		<li><a href="submit.html" title="If you want to submit a new hint">Submit new hint</a></li>
   		<li><a href="acknowledgements.html" title="People who earned credits for their contributions">Acknowledgements</a></li>
  
  
  
  1.23      +1 -1      www/test/hints/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/submit.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- submit.html	25 Aug 2003 13:05:55 -0000	1.22
  +++ submit.html	25 Aug 2003 16:26:40 -0000	1.23
  @@ -48,7 +48,7 @@
   <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 explainations 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>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>
  
  
  



More information about the website mailing list