cvs commit: www/test/lfs news-top.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Aug 18 19:12:58 PDT 2003


jeroen      03/08/18 20:12:58

  Modified:    test     generalnews.txt website-bottom.html
                        website-top.html
               test/blfs news-top.html
               test/hints news-top.html
               test/lfs news-top.html
  Log:
  News pages now have a correct item about their status. Also converted all (?) dates to YYYY/MM/DD format.
  
  Revision  Changes    Path
  1.6       +9 -9      www/test/generalnews.txt
  
  Index: generalnews.txt
  ===================================================================
  RCS file: /home/cvsroot/www/test/generalnews.txt,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- generalnews.txt	19 Aug 2003 00:10:15 -0000	1.5
  +++ generalnews.txt	19 Aug 2003 02:12:57 -0000	1.6
  @@ -4,13 +4,13 @@
   <!-- 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="nominations">Nominations again</h3>
  -		<h4>Gerard Beekmans - 19/12/2003</h4>
  +		<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>
   		<p>For the record I'd like to tell you guys that I don't want to hear complaints about the fact that the community was not involved in selecting the coordinators and that I'm being selfish, still want to do things on my own and can't let go, etc (yes these are all things I've heard before in recent weeks and I'm anticipating hearing them again. I'd rather not though, it doesn't serve a purpose anymore).</p>
   		<p>If you want your opinion to count, get your emails in by tomorrow morning.</p>
   
   	<h3 id="organisationstructure">Organisation structure</h3>
  -		<h4>Gerard Beekmans - 14/12/2003</h4>
  +		<h4>Gerard Beekmans - 2003/08/12</h4>
   		<p>I have that list of teams and inter-relationships drawn out. When you look at it, it's not much yet. Let me show the chart, then some comments I have about it.</p>
   		<h5>LFS.org</h5>
   		<ul>
  @@ -46,7 +46,7 @@
   		<p>This mail is archived in the <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036565.html">lfs-dev mailing list</a>.</p>
   
   	<h3 id="whosin">Let's come right out - who wants in, who wants out</h3>
  -		<h4>Gerard Beekmans - 12/08/2003</h4>
  +		<h4>Gerard Beekmans - 2003/08/12</h4>
   		<p>Instead of bickering about the past and whether or not I'm an incapable leader, maybe we can be more productive instead. We can argue until we're blue in the face, the only way for me to prove myself that I think I can be a capable leader is just to show it and see if the plan I had in mind works, or not. If not, that proves enough. If it does work, it also proves enough. Also how badly past contributors have been treated isn't productive, really, other than keep rubbing it in my face. It's not that I can't stand criticism, but there comes a point all has been said and further talk serves no purpose. Time to move on. I think we've arived at that time.</p>
   		<p>The plan as I quickly outlined it was that I envision people being in charge of their sections of LFS and have control over it, without my supervision and don't need to wait for me to make a decision. There are a number of cut-n-dry sections: toolchain, bootable system, the real core programs and the not-so-core-but-nice-to-have programs. This last category consists of the most packages so it probably a good candidate to be split up into smaller chunks.</p>
   		<p>Other than packages there are areas such as the general structure of the book (that what Alex is <a href="http://home.wanadoo.nl/krisp/proposedlfs/">currently working on</a>).</p>
  @@ -55,7 +55,7 @@
   		<p>Discussion starts at <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036233.html">lfs-dev</a>.</p>
   
   	<h3 id="canofworms">Let's open a can of worms, shall we?</h3>
  -		<h4>Jessie Tie-Ten-Quee - 10/08/2003</h4>
  +		<h4>Jessie Tie-Ten-Quee - 2003/08/10</h4>
   		<p>This project has <strong>always</strong> been about the community; at least for me, and a very large portion of us.  Hence, I want to open a can of worms, and let everyone in on it.  Sounds fun, eh?</p>
   		<p><strong>puts on his asbestos suit for good measure, woohoo!</strong></p>
   		<p>I've been spending alot of time talking to everyone i've had a chance too about LFS in it's current state and it's future.  And everyone seems to say the same thing, except nobody has ever acted upon it... soooooo;</p>
  @@ -74,7 +74,7 @@
   		<p>Discuss this at <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036144.html">lfs-dev</a></p>
   
   	<h3 id="printedblfsbook">Printed BLFS Book</h3>
  -		<h4> Gerard Beekmans - 06/08/2003</h4>
  +		<h4> Gerard Beekmans - 2003/08/06</h4>
   		<p>The publisher who printed & published the LFS book has shown interested in doing the same thing for the BLFS book and he's interested, if at all possible. publishing it around October.</p>
   		<p>I know it's not a lot of notice I realize. Also seeing they also want to see if the next LFS book (5.0) can be published around the same time (possible a bundle, LFS+BLFS combined in one book). I'm not sure what's special about October, but it has something to do with that time of year being statistically a good time in the year to release these kind of books. The wheather gets colder, people tend to stay at home more and generally have more time to take on an extended project such as LFS+BLFS would be.</p>
   		<p>So guys, how long do you anticipate needing to whip the BLFS book into shape for publishing? Submission format is PDF and our current XML2PDF generations don't create a good enoug PDF. For the LFS book I converted the XML to LaTeX and used the latex2pdf conversion which does a much better job, also seeing we're going to need to specify custom paper sizes, margins and all that fun stuff.</p>
  @@ -84,7 +84,7 @@
   		<p>You can read the discussion at <a href="http://linuxfromscratch.org/pipermail/blfs-dev/2003-August/003219.html">blfs-dev</a> and <a href="http://linuxfromscratch.org/pipermail/lfs-dev/2003-August/036072.html">lfs-dev</a>.</p>
   
   	<h3 id="newwebsitedesign">New website design</h3>
  -		<h4>Jeroen Coumans - 25/07/2003</h4>
  +		<h4>Jeroen Coumans - 2003/07/25</h4>
   		<p>The LFS team is proud to present the new website! There were some disadvantages with the old site which are adressed in this new design.</p>
   		<ul>
   			<li>The website now uses semantically correct and valid XHTML-1.1 and CSS-2 throughout the entire site (check it for yourself with the button's at the bottom). A new look is simply a matter of adjusting the stylesheet. The site is optimized for Unix browsers, such as <a href="http://www.mozilla.org">Mozilla</a> and <a href="http://www.konqueror.org">Konqueror</a>, and is more friendly for text browsers, such as <a href="http://lynx.browser.org/">lynx</a>.</li>
  @@ -97,7 +97,7 @@
   		<p>There's more information available at the <a href="../website.html">website information page</a></p>
   
   	<h3 id="mail_change">Mailing list software changes</h3>
  -		<h4>Gerard Beekmans - 24/07/2003</h4>
  +		<h4>Gerard Beekmans - 2003/07/24</h4>
   		<p>Tomorrow I'm going to start the process of moving all the mailinglists to Mailman management. When a list is being moved I need to disable it in Postfix and change the aliases, as well as move the archive over to Mailman. This will take some time, especially the initial archiving (Mailman keeps archives (html and mbox) up-to-date as emails arrive, so before the list is opened again, the archives have to be in place first).</p>
   		<p>I'll send a message to the list I'm working on so you don't have to bother trying to email it. It'll bounce.</p>
   		<p>Then there's the matter of filtering on you guys' end. I don't see a way to make Mailman use the X-List: header so I'm afraid you're going to have to change your email filters. Instead of filtering by X-List, you'll need to filter by List-Id. Here's a regex example for procmail which will filter all messages from lfs-book:</p>
  @@ -107,7 +107,7 @@
   		<p><em>Update:</em> the <a href="../mail.html">mail instructions page</a> has been updated.</p>
   
   	<h3 id="logocontest">Logo contest</h3>
  -		<h4>Gerard Beekmans - 25/06/2003</h4>
  +		<h4>Gerard Beekmans - 2003/06/25</h4>
   		<p>Together with the website facelift we'll be holding an LFS Logo contest. I thought it'd be nice to throw in a small prize as an extra incentive and "thank you" to the winner.</p>
   		<p>The prize is going to be a brand new book called "UNIX Systems Programming" which is the anticipated update of the mid-1990's UNIX programming classic "Practical UNIX Programming" by Kay and Steven Robins (same authors who wrote this new book).</p>
   		<p>This completely updated book demonstrates how to design complex software to get the most from the UNIX operating system, whether using Linux. Solaris, Mac OS X or another POSIX-based system. This new edition features all-new chapters on the Web, UPD and server performance. The book thoroughly explores communication, concurrency and multi-threading. It also deals with UNIX process files/special files, signal/timers, POSIX threads, semaphores, IPC, TCP/UDP/multicast and more.</p>
  @@ -118,7 +118,7 @@
   		<p>I only have one book to give away, so the winner of the LFS logo will get the book. But it would still be nice to have (slightly) different logo's for ALFS, BLFS and Hints that will be more in line with that project's 'theme'.</p>
   
   	<h3 id="wiki_opened">Developers wiki opened</h3>
  -		<h4>Nicholas Leippe - 21/06/2003</h4>
  +		<h4>Nicholas Leippe - 2003/06/21</h4>
   		<p>I've set up the wiki on the sf account, and seeded it with some entries from recent issues on the list.  This should be enough to give an idea of what can be done.</p>
   		<p>Since there wasn't much enthusiasm when this was first mentioned a while back, I don't expect everyone to rush to it.  (/me hears groans, "yet another place to look!")</p>
   		<p>Please, at least read the introduction and purpose on the homepage and give it a chance.  I really do think a wiki can help LFS be that much better.</p>
  
  
  
  1.4       +1 -2      www/test/website-bottom.html
  
  Index: website-bottom.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-bottom.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- website-bottom.html	7 Aug 2003 01:51:13 -0000	1.3
  +++ website-bottom.html	19 Aug 2003 02:12:57 -0000	1.4
  @@ -28,8 +28,7 @@
   			</ol>
   		<p>The script should thus extract this from the CVS logs and <em>add</em> it to an intermediate file. By only adding information to an intermediate file, the content of this page should thus be manually adjustable in case we want to add news ourselves. That should account for the body. The whole page can be cat'ed together with a seperate header and footer which I can provide.</p>
   		<p>Also, it might be nice if we could archive news pages each month. This would have the advantage that no news is lost and that the news pages are bookmarkable. Therefore, it should be a symlink to news/year/month.html (where year and month are numerical values of course). This can be done from a crontab. The old news pages are kept on archives.linuxfromscratch.org so there's no additional burden for the mirrors.</p>
  -		<p>Allthough I lack the skills to write such a script myself, I've <a href="http://www.linuxfromscratch.org/~jeroen/">hacked</a> <a href="http://www.red-bean.com/cvs2cl/">cvs2cl.pl</a> and managed to get <a href="#changelog">this output</a>. <em>This method is nowhere near suitable for the requirements set above, so if you're familiar with Perl, XML and/or XSL, please <a href="mailto:website at linuxfromscratch.org">e-mail the website list</a>!</em></p>
  -		<p><em>Status: <strong>functional</strong>. The current solution is functional but technically very ugly. We have a volunteer who will cook up a better solution.</em></p>
  +		<p><em>Status: <strong>done (except for news archiving)</strong>. See <a href="http://www.linuxfromscratch.org/pipermail/website/2003-August/000374.html">Anderson Lizardo's perl script</a>.</em></p>
   		<h5>Bugzilla script</h5>
   		<p>Similar to the above CVS scripts we should also get or write a script which feeds Bugzilla messages into the project's newspages. The information which needs to be extracted is the same (who, when and what bug is reported). Additionally, it should contain a link to the bug page. This script should be triggered whenever Bugzilla changes (a bug is added, resolved, commented etc.). This way, active LFS'ers can read the website daily, be aware of the current state of LFS and be able to directly comment on bugs. </p>
   		<p><em>Status: <strong>no solution yet</strong>. I haven't found a script yet which can extract this information. Again, please <a href="mailto:website at linuxfromscratch.org">e-mail the website list</a> if you're able to help.</em></p>
  
  
  
  1.2       +1 -1      www/test/website-top.html
  
  Index: website-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/website-top.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- website-top.html	2 Aug 2003 16:37:11 -0000	1.1
  +++ website-top.html	19 Aug 2003 02:12:57 -0000	1.2
  @@ -87,4 +87,4 @@
   		<p><a href="#header">Back to the top.</a></p>
   
   	<h3 id="changelog">Changelog</h3>
  -		<p>The following changelog is automatically generated from CVS log messages and fed into this file. We only list the changes from the last week.</p>
  +		<p>The following changelog is automatically generated from CVS log messages and fed into this file. These changes are from last month.</p>
  
  
  
  1.4       +8 -4      www/test/blfs/news-top.html
  
  Index: news-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/blfs/news-top.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- news-top.html	19 Aug 2003 00:10:16 -0000	1.3
  +++ news-top.html	19 Aug 2003 02:12:58 -0000	1.4
  @@ -50,12 +50,16 @@
   	</div>
   
   <h2 id="blfsnews">BLFS-specific news</h2>
  +	<h3 id="lfsreorganization">LFS Reorganization [please read if you do not read lfs-dev]</h3>
  +		<h4>Larry Lawrence - 2003/08/15</h4>
  +		<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>
  +
   	<h3 id="thispage">Page now updated</h3>
  -		<h4>Jeroen Coumans - 01/08/2003</h4>
  +		<h4>Jeroen Coumans - 2003/08/01</h4>
   		<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>Note that this is still based on <a href="http://www.linuxfromscratch.org/~jeroen/cvs2xhtml.pl">my hack</a> of <a href="http://www.red-bean.com/cvs2cl/">cvs2cl.pl</a>, which should be <a href="../website.html#todo">rewritten</a>.</p>
  -		<p>It also lacks Bugzilla messages, which are needed to give a proper view of the current BLFS development status. </p>
  -		<p>There are no news-worthy developments announced on the BLFS mailinglists, but when they are, they should be included in this page. For now, I'll maintain this section. In the future, this should probably also be edited by the BLFS editors. They monitor the lists and are aware of significant BLFS developments. </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>
   
  
  
  
  1.2       +6 -0      www/test/hints/news-top.html
  
  Index: news-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/news-top.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- news-top.html	19 Aug 2003 01:45:40 -0000	1.1
  +++ news-top.html	19 Aug 2003 02:12:58 -0000	1.2
  @@ -70,6 +70,12 @@
   		<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>
   
  +	<h3 id="thispage">Page now updated</h3>
  +		<h4>Jeroen Coumans - 2003/08/18</h4>
  +		<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>
  +
   	<h3 id="newmaintainer">New hints maintainer</h3>
   		<h4>Timothy Bauscher - 2003/08/08</h4>
   		<p>Congratulations to Tushar Teredesai, the new Hint Maintainer. </p>
  
  
  
  1.7       +4 -5      www/test/lfs/news-top.html
  
  Index: news-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/lfs/news-top.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- news-top.html	19 Aug 2003 00:10:17 -0000	1.6
  +++ news-top.html	19 Aug 2003 02:12:58 -0000	1.7
  @@ -53,22 +53,21 @@
   
   <h2 id="lfsnews">LFS-specific news</h2>
   	<h3 id="neweditor">New editor</h3>
  -		<h4>Gerard Beekmans - 08/08/2003</h4>
  +		<h4>Gerard Beekmans - 2003/08/08</h4>
   		<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>
   
   	<h3 id="thispage">Page now updated</h3>
  -		<h4>Jeroen Coumans - 01/08/2003</h4>
  +		<h4>Jeroen Coumans - 2003/08/01</h4>
   		<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>Note that this is still based on <a href="http://www.linuxfromscratch.org/~jeroen/cvs2xhtml.pl">my hack</a> of <a href="http://www.red-bean.com/cvs2cl/">cvs2cl.pl</a>, which should be <a href="../website.html#todo">rewritten</a>.</p>
  -		<p>It also lacks Bugzilla messages, which are needed to give a proper view of the current LFS development status. </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>
   
   	<h3 id="bookredone">The book redone</h3>
  -		<h4>Alex Groenewoud - 29/07/2003</h4>
  +		<h4>Alex Groenewoud - 2003/07/29</h4>
   		<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>
  
  
  



More information about the website mailing list