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

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Aug 18 17:10:18 PDT 2003


jeroen      03/08/18 18:10:17

  Modified:    test     generalnews.txt
               test/blfs news-top.html
               test/hints news.html
               test/lfs news-top.html
  Log:
  Added most of last weeks lfs-dev news to the general news section.
  
  Revision  Changes    Path
  1.5       +57 -6     www/test/generalnews.txt
  
  Index: generalnews.txt
  ===================================================================
  RCS file: /home/cvsroot/www/test/generalnews.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- generalnews.txt	10 Aug 2003 10:36:30 -0000	1.4
  +++ generalnews.txt	19 Aug 2003 00:10:15 -0000	1.5
  @@ -2,6 +2,58 @@
   <h2 id="generalnews">General news</h2>
   
   <!-- 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>
  +		<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>
  +		<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>
  +			<li>LFS - Gerard
  +			<ul>
  +				<li>Testing Team - Vacant</li>
  +				<li>Quality Control Team - Vacant</li>
  +				<li>Editorial Team - Vacant</li>
  +			</ul></li>
  +			<li>BLFS  - Larry
  +			<ul>
  +				<li>Testing Team - Vacant</li>
  +				<li>Quality Control - Vacant</li>
  +				<li>Editorial Team - Vacant</li>
  +			</ul></li>
  +			<li>ALFS	- Special case, no real management going on here</li>
  +			<li>Hints	- Tushar</li>
  +			<li>Patches - Tushar</li>
  +			<li>FAQ	- Jeroen</li>
  +			<li>Websites - Jeroen</li>
  +			<li>Bugzilla Database Maintainer - Vacant</li>
  +			<li>System Adminstration Team - Gerard</li>
  +		</ul>
  +		<p>I've called the toplevel LFS.org rather than LFS so we don't confuse it with the LFS beneath it which relates to LFS as a sub-project, not the entire project that encompasses everything.</p>
  +		<p>You see my name a few times in places where it probably shouldn't. And there are some vacancies. Don't worry or get hung up on names. I'm just looking for a finalized structure. We can figure out the "who does what" part afterwards. This is basically how things stand today, be it good or bad, or non-existing, that's all.</p>
  +		<p>We've talked about a Leadership Team, which is not evident here. I couldn't figure out how to properly place that, so I left it out. In a way LFS.org is the Leadership Team. The people who are part of this team take care of the entire LFS project, making sure all the sub-projects (LFS, BLFS, Hints, etc) are functioning properly.</p>
  +		<p>As to who belongs to that team, we can go two ways:</p>
  +		<p>1) Leadership team consists of its own group of people. I suppose it can be compared to a Board of Directors within a real company.</p>
  +		<p>However, I don't think that extra level of people/separation is necessary, so I propose:</p>
  +		<p>2) Leadershipo team consists of people who run a sub-project. This means, that me, Tushar, Larry and Jeroen would currenctly be part of this team, as well as a number of other people like Richard for instance. The only "bad" thing about this setup is a possible conflict of interests as it's put so nicely in the corporate world. I don't think that is something we have to worry about, it just saves that extra level of abstraction. </p> 
  +		<p>So, think it through for a while and comment on it, point out missing teams or bring up new ones that would be beneficial. Sometime tomorrow this will be copied into the wiki too. I thought about starting in the wiki, but I prefer a discussion on this list, rather than a string of comments on the web page.</p>
  +		<p>And while you're thinking, give some thought as to who you think would be a good person to fill vacancies.</p>
  +		<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>
  +		<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>
  +		<p>So, is anybody interested in helping out at all and wants to take on one of the things mentioned above?</p>
  +		<p>Even if you don't want to take on a role like this being in charge, if you still want to contribute by testing CVS stuff, testing proposed bug fixes and then submitting your ideas/proposals and all that other stuff also let me know. You'd be a regular contributor as opposed to the occasional report when you happen to come across something. A regular contributor could be asked upon to help out doing a test run of something. I guess contributor isn't a good term, but it'll do, lacking a better one.</p>
  +		<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>
   		<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>
  @@ -18,13 +70,12 @@
   		<p>Do I have to write down and explain all the reasons why this is so?  I don't think so, because you're quite aware of this.. but up untill now, nothing's been done about it.</p>
   		<p>Gerard, i'm not looking for an apology-I never was.  I am however looking for a solution to the problem, because i'm sick and tired of watching this project continue to grumble apart from the inside.</p>
   		<p>My only hope is that everyone that reads this, takes the time to properly <strong>think</strong> about it, before jumping to anything or responding, because this is a very important issues, and should be treated as such.  (:</p>
  -		<p>In either case, these are my honest feelings and opinions, and I don't mean any disrespect, this just
  -seemed the most straight-forward way of getting something <strong>done</strong>.</p> 
  +		<p>In either case, these are my honest feelings and opinions, and I don't mean any disrespect, this just seemed the most straight-forward way of getting something <strong>done</strong>.</p> 
   		<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>
  -		<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>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>
   		<p>I wouldn't recommend doing an xml2latex conversion the way I did for LFS. We had better get that new XML we've been talking on lfs-dev started soon. Then it's a simple matter of creating a stylesheet that converts XML to LaTeX using the previous lfs-book-latex template I have here.</p>
  @@ -46,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/7/2003</h4>
  +		<h4>Gerard Beekmans - 24/07/2003</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>
  @@ -56,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/6/2003</h4>
  +		<h4>Gerard Beekmans - 25/06/2003</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>
  @@ -67,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/6/2003</h4>
  +		<h4>Nicholas Leippe - 21/06/2003</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.3       +1 -1      www/test/blfs/news-top.html
  
  Index: news-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/blfs/news-top.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- news-top.html	5 Aug 2003 16:38:32 -0000	1.2
  +++ news-top.html	19 Aug 2003 00:10:16 -0000	1.3
  @@ -51,7 +51,7 @@
   
   <h2 id="blfsnews">BLFS-specific news</h2>
   	<h3 id="thispage">Page now updated</h3>
  -		<h4>Jeroen Coumans - 1/8/2003</h4>
  +		<h4>Jeroen Coumans - 01/08/2003</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>
  
  
  
  1.22      +5 -5      www/test/hints/news.html
  
  Index: news.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/hints/news.html,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- news.html	8 Aug 2003 16:11:08 -0000	1.21
  +++ news.html	19 Aug 2003 00:10:17 -0000	1.22
  @@ -54,7 +54,7 @@
   <h2 id="news">Hints-specific news</h2>
   	<p><em>This page should be automatically generated from CVS commit messages. For more details see <a href="../website.html#todo">the todo page</a>. My hacks to cvs2cl.pl don't work with this page since it strips out filename information. That information is vital for this page, as can be seen from below's sample changelog. So please <a href="mailto:jeroen at linuxfromscratch.org">contact me</a> if you're familiar with XML and XSLT.</em></p>
   	<h3 id="newmaintainer">New hints maintainer</h3>
  -		<h4>Timothy Bauscher - 8/8/2003</h4>
  +		<h4>Timothy Bauscher - 08/08/2003</h4>
   		<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>
  @@ -68,7 +68,7 @@
   <!-- 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="newwebsitedesign">New website design</h3>
  -		<h4>Jeroen Coumans - 25/7/2003</h4>
  +		<h4>Jeroen Coumans - 25/07/2003</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>
  @@ -81,7 +81,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/7/2003</h4>
  +		<h4>Gerard Beekmans - 24/07/2003</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>
  @@ -91,7 +91,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/6/2003</h4>
  +		<h4>Gerard Beekmans - 25/06/2003</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>
  @@ -102,7 +102,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/6/2003</h4>
  +		<h4>Nicholas Leippe - 21/06/2003</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.6       +3 -3      www/test/lfs/news-top.html
  
  Index: news-top.html
  ===================================================================
  RCS file: /home/cvsroot/www/test/lfs/news-top.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- news-top.html	8 Aug 2003 16:11:08 -0000	1.5
  +++ news-top.html	19 Aug 2003 00:10:17 -0000	1.6
  @@ -53,14 +53,14 @@
   
   <h2 id="lfsnews">LFS-specific news</h2>
   	<h3 id="neweditor">New editor</h3>
  -		<h4>Gerard Beekmans - 8/8/2003</h4>
  +		<h4>Gerard Beekmans - 08/08/2003</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 - 1/8/2003</h4>
  +		<h4>Jeroen Coumans - 01/08/2003</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>
  @@ -68,7 +68,7 @@
   		<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/7/2003</h4>
  +		<h4>Alex Groenewoud - 29/07/2003</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