cvs commit: www/test/hints news-2003.txt

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Sep 1 10:05:35 PDT 2003


jeroen      03/09/01 11:05:35

  Added:       test/lfs news-2003.txt
               test/blfs news-2003.txt
               test/hints news-2003.txt
  Log:
  Added the news files for LFS, BLFS and the hints.
  
  Revision  Changes    Path
  1.1                  www/test/lfs/news-2003.txt
  
  Index: news-2003.txt
  ===================================================================
  Content-Type: multipart/mixed;
      boundary="NEWS_ITEM_BOUNDARY"
  MIME-Version: 1.0
  Section: lfs
  
  --NEWS_ITEM_BOUNDARY
  Title: Roadmap
  Author: James Robertson
  Date: 2003/08/28
  Id: roadmap
  
  		<p>I see the "Possible interim release?" thread turning more into a roadmap discussion.  I think that the leadership team needs to come to some agreement as to what path we want to take from here with regard to stable releases.  A  roadmap does not have to include dates, it is just a list of major talking points (milestones) with regard to the project and in what version we see them showing up in.  From the last thread, I see one possible roadmap.</p>
  		<p>(Note - the roadmap was removed since it has changed significantly from the original. The current version is found in the wiki.</p>
  		<p>Please understand that this is a PROPOSED roadmap.  I have placed a copy of this in the <a href="http://lfs.sourceforge.net/wiki/Roadmap">wiki</a>. Hopefully we can to some agreement as to the path we want to take and move on from discussion to action.</p>
  		<p>Read reactions to this roadmap on <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/037056.html">lfs-dev</a>.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: Possible interim release?
  Author: Jeremy Utley
  Date: 2003/08/27
  Id: possibleinterumrelease
  
  		<p>I was doing some thinking about the current state of LFS.  As it stands right now, we have CVS making a pretty stable build, very few truly outstanding issues in the building itself.  But, coming soon, we have a LOT of things to get ready for - namely 2.6.0, gcc 3.3.1, the new XML, and probably lots of other things I haven't thought of (including NPTL when it's ready).</p>
  		<p>I think now might be the time to get the text in line with the commands again, and put out an interim LFS 4.2 with the current packages and build process.  Then, take CVS into a heavy development stage, trying to get ready for some of the above mentioned things.</p>
  		<p>Lets face it...after the wait in releasing 4.1 to coincide with the printed book, 4.1 has become pretty stale.  Most of the distros are now beyond that.  If we could spend the next couple of weeks cleaning up the text between commands, we could put out a 4.2 release.  Then, we can go with 2.6.0 and gcc 3.3.1 into CVS, and start the conversion to the new XML, and once NPTL is ready for prime time, bring that in as well. </p>
  		<p>Read everybody's comments on the <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/037006.html">lfs-dev mailinglist</a>.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: More new editors
  Author: Gerard Beekmans
  Date: 2003/08/26
  Id: moreneweditors
  
  		<p>Matthew Burgess joined the editorial team. He's expressed interest in helping out with keeping the packages up-to-date. I'm sure we can get more work out of him as time goes by :-)</p>
  		<p>When it rains it pours (good thing in this case)</p>
  		<p>Jeremy Utley joined the editorial team as well. Lots of fresh meat, this will be good for development. </p>
  		<p>Now all that's left is sort out bugs in Bugzilla so we can get started fixing things again, updating the text, getting PLFS fully into the book and all those good things.</p>
  		<p>Congrats are in <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036936.html">this</a> and <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036938.html">this</a> thread on lfs-dev.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: New editor
  Author: Gerard Beekmans
  Date: 2003/08/08
  Id: neweditor
  
  		<p>Just to inform you all, Alex Groenewoud is setup as the latest addition to the editorial team and will be helping out effective right now.</p>
  		<p>Alex is well known for his excellent contributions in the past to LFS in the form of grammatical patches. His most recent work is a <a href="#bookredone">rewriting of the book</a> with a new structure. This led to some recent changes in the LFS book, of which we're bound to see more now.</p>
  		<p>We wish Alex good luck with editing LFS and we are confident that he will continue to make useful contributions to the book and the project.</p>
  		<p><a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036114.html">See lfs-dev for a discussion of this post</a></p>
  
  --NEWS_ITEM_BOUNDARY
  Title: Page now updated
  Author: Jeroen Coumans
  Date: 2003/08/01
  Id: thispage
  
  		<p>The LFS news page will now be properly updated with recent CVS changelogs and general LFS-project news. It also has an <a href="feed.rss">RSS newsfeed</a> which contains the latest headlines of LFS-specific and general news.</p>
  		<p>It still lacks Bugzilla messages, which are needed to give a proper view of the current LFS development status. </p>
  		<p>Allthough there is no mechanism yet to phase out old news, it's fairly easy to add new news. This file is actually divided in two parts, of which the top part should be adjusted with news. A look at the source shows that it is fairly trivial to add news, as long as the structure remains intact. Use <h3> for the news title (or e-mail subject), and <h4> for the who - when. Use <p>'s for the e-mail or message. </p>
  		<p>Since the pages are all XHTML, please ensure that the page is still well-formed. If the page is not well-formed, the <a href="http://linuxfromscratch.org/pipermail/lfs-chat/2003-July/016028.html">lfs2rss.pl</a> script which Rob Park contributed won't work and the pages won't validate.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: The book redone
  Author: Alex Groenewoud
  Date: 2003/07/29
  Id: bookredone
  
  		<p>Impatient with the chaotic state of the book, irked by a comment from Gerard, and reminded of something by Jeroen, I went and rewrote the entire book.</p>
  		<p>I changed the structure, moved things around, threw some things out, and rewrote just about all of the text.  And moved it from Lilo to Grub to boot.</p>
  		<p>You can <a href="http://home.wanadoo.nl/krisp/betterbook/index.html">browse</a> the result. You can also download the html in a <a href="http://home.wanadoo.nl/krisp/betterbook/boos-in-html.tar.bz2">tarball</a> (61 kB). And you can download the docbook xml in a <a href="http://home.wanadoo.nl/krisp/betterbook/boos-in-xml.tar.bz2.">tarball</a> too.</p>
  		<p>(This may come at an awkward time, with the move to custom xml just about to begin, but... maybe it's not too late.)</p>
  		<p>Comments are very welcome.</p>
  		<p>Alex</p>
  		<p><a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-July/035797.html">See lfs-dev for discussion of this post.</a></p>
  
  --NEWS_ITEM_BOUNDARY--
  
  
  
  1.1                  www/test/blfs/news-2003.txt
  
  Index: news-2003.txt
  ===================================================================
  Content-Type: multipart/mixed;
      boundary="NEWS_ITEM_BOUNDARY"
  MIME-Version: 1.0
  Section: blfs
  
  --NEWS_ITEM_BOUNDARY
  Title: LFS Reorganization [please read if you do not read lfs-dev]
  Author: Larry Lawrence
  Date: 2003/08/15
  Id: lfsreorganization
  
  		<p>Gerard is conducting a reorganization which is under heavy discussion on lfs-dev.  There is some concern that not every involved in BLFS is aware of this.  This will impact all LFS projects, so you may want to temporaily subscribe to lfs-dev, review the archives and contribute to the changes.</p>
  		<p>The obvious benefit to BLFS is the testing teams and QA will be an assigned responsibility.</p>
  		<p>Any BLFS specific questions can be discussed here are emailed to me privately.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: Page now updated
  Author: Jeroen Coumans
  Date: 2003/08/01
  Id: thispage
  
  		<p>The BLFS news page will now be properly updated with recent CVS changelogs and general LFS-project news. It also has an <a href="feed.rss">RSS newsfeed</a> which contains the latest headlines of BLFS-specific and general news.</p>
  		<p>It still lacks Bugzilla messages, which are needed to give a proper view of the current BLFS development status. </p>
  		<p>Allthough there is no mechanism yet to phase out old news, it's fairly easy to add new news. This file is actually divided in two parts, of which the top part should be adjusted with news. A look at the source shows that it is fairly trivial to add news, as long as the structure remains intact. Use <h3> for the news title (or e-mail subject), and <h4> for the who - when. Use <p>'s for the e-mail or message. </p>
  		<p>Since the pages are all XHTML, please ensure that the page is still well-formed. If the page is not well-formed, the <a href="http://linuxfromscratch.org/pipermail/lfs-chat/2003-July/016028.html">lfs2rss.pl</a> script which Rob Park contributed won't work and the pages won't validate.</p>
  
  --NEWS_ITEM_BOUNDARY--
  
  
  
  1.1                  www/test/hints/news-2003.txt
  
  Index: news-2003.txt
  ===================================================================
  Content-Type: multipart/mixed;
      boundary="NEWS_ITEM_BOUNDARY"
  MIME-Version: 1.0
  Section: hints
  
  --NEWS_ITEM_BOUNDARY
  Title: New hint format
  Author: Tushar Teredesai
  Date: 2003/08/24
  Id: newhintformat
  
  		<p>I will move the currently relevant hints to a new directory old_fomat and all the hints that are not relevant to the old directory. My analysis for the current hints is at the end of this mail. Feel free to suggest changes. Since I don't personally use all the hints, my recommendation may be flawed.<p>
  		<p>On the website, I will also need to create hints.linuxfromscratch.org/downloads directory which will contain the downloads for hints that cannot fit on patches website. Since Jeroen is alreay in the process of moving to the new website, I will leave this task and other tasks related to creating webpages for him:)</p>
  		<p>Some suggestions which did not go into the current format:</p>
  		<ul>
  			<li>Categories: IMO, it is very difficult to categorize something and will always create problems. There was a discussion in the past on categorization of packages in LFS, which resulted in "Its not feasible".</p>
  			<li>Target LFS Version: This is covered by the Pre-requsites section where the author can be as descriptive and as restrictive as needed.</li>
  		</ul>
  		<p>Analysis of current hints (Note, Remove just means it is moved to old). Note that I went thru the list in alphabetical order, so when I indicate merging Y with X, even the vice versa is true.</p>
  		<p>The complete list and the new format is available in the <a href="http://www.linuxfromscratch.org/pipermail/hints/2003-August/001860.html">original
  mail,</a>, where you can also follow the discussion.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: Page now updated
  Author: Jeroen Coumans
  Date: 2003/08/18
  Id: thispage
  
  		<p>The hints news page will now be properly updated with recent CVS changelogs and general hints news. </p>
  		<p>Allthough there is no mechanism yet to phase out old news, it's fairly easy to add new news. This file is actually divided in two parts, of which the top part should be adjusted with news. A look at the source shows that it is fairly trivial to add news, as long as the structure remains intact. Use <h3> for the news title (or e-mail subject), and <h4> for the who - when. Use <p>'s for the e-mail or message. </p>
  		<p>Since the pages are all XHTML, please ensure that the page is still well-formed. If the page is not well-formed, the <a href="http://linuxfromscratch.org/pipermail/lfs-chat/2003-July/016028.html">lfs2rss.pl</a> script which Rob Park contributed won't work and the pages won't validate.</p>
  
  --NEWS_ITEM_BOUNDARY
  Title: Reorganization of hints
  Author: Tushar Teredesai
  Date: 2003/08/18
  Id: reorganizationofhints
  
  		<p>Now that the patches project details have been finalized, I would like to start on reogranizing the hints. I would like to start with a new format which would make it easy for Jeroen to automatically add it to a hints index. An added bonus is that since all hints would require resubmission with the new format, the unmaintained hints will automatically get moved to old.</p>
  		<p>Each hint would have the following sections:</p>
  		<ul>
  			<li>Author(s): Who wrote the hint along with contact e-mail.</li>
  			<li>Date: YYYY-MM-DD format date.</li>
  			<li>Category: One of the predefined categories. I am not sure whether this should be included coz there will always be some hint that will break this segregation (remember the discussion on lfs-dev on this topic?).</li>
  			<li>Synopsis: One line description.</li>
  			<li>Primary URL: (Optional) If there is a different primary location.</li>
  			<li>Description: A short description on why the hint was written and who it is targetted towards.</li>
  			<li>Hint: The contents of the hint. (The patches for the hint can be hosted on <a href="http://patches.linuxfromscratch.org">the patches section</a>).</li>
  			<li>ChangeLog: ChangeLog sorted by date. For an example, see the mozilla hint.</li>
  		</ul>
  		<p>I plan to do some quality control with the hints. A hint is not there to replace the documentation that comes with the package, it should go beyond the documentation available elsewhere. Also, if there is an already existing hint on a topic, instead of creating a seperate hint, it should probably be added to the existing hint (unless the objectives/modus operandi are different). Before writing a hint on the same topic, the original author should be contacted and if the author does not respond within a reasonable time, the new author can modify an existing hint. Also hints that deal with different ways of doing things should be seperate. (e.g. there are three devfs related hints, but all of them have a different target audience.)</p>
  		<p>In addition, hints that are more appropriate for inclusion in the book should be directed to lfs-dev or blfs-dev (though they can be hosted on hints till they are incorporated), where a book editor can incorporate them into the book.</p>
  		<p><a href="http://linuxfromscratch.org/pipermail/hints/2003-August/001828.html">Thoughts?</a></p>
  
  --NEWS_ITEM_BOUNDARY
  Title: New hints maintainer
  Author: Timothy Bauscher
  Date: 2003/08/08
  Id: newmaintainer
  
  		<p>Congratulations to Tushar Teredesai, the new Hint Maintainer. </p>
  		<p>Tushar is a long-time contributor of LFS, BLFS, and the hints. The hints he has written are a joy to read. He was the first to <a href="files/javafromscratch.txt">build java</a> and <a href="files/openoffice.txt">Open Office</a> from scratch, and documented the painful process of building <a href="files/mozilla.txt">mozilla from scratch</a>. He has also contributed these procedures to BLFS and earned himself an editor's position this way.</p>
  		<p>Thank you, Tushar, for your labors, and for accepting this position.</p>
  		<p><em>Editor note: </em>Thanks to Timothy for having maintained the hints untill now. You've done a great job and we hope that you'll continue to contribute to LFS.</p>
  		<p>Discussion of this announcement can be read on <a href="http://linuxfromscratch.org/pipermail/hints/2003-August/001819.html">the hints mailinglist</a>.</p>
  
  --NEWS_ITEM_BOUNDARY--
  
  
  



More information about the website mailing list