r828 - in trunk: . templates templates/alfs templates/blfs templates/hints templates/lfs templates/patches

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Mon Aug 9 23:18:59 PDT 2004


Author: jeroen
Date: 2004-08-10 00:18:57 -0600 (Tue, 10 Aug 2004)
New Revision: 828

Modified:
   trunk/acknowledgements.html
   trunk/mail.html
   trunk/organization.html
   trunk/people.html
   trunk/sitemap.html
   trunk/templates/alfs/news-top.html
   trunk/templates/blfs/news-top.html
   trunk/templates/hints/news-top.html
   trunk/templates/lfs/news-top.html
   trunk/templates/patches/news-top.html
   trunk/templates/website-bottom.html
   trunk/templates/website-top.html
   trunk/website-manifesto.html
Log:
Removed all occurences of CVS, it's not used anymore

Modified: trunk/acknowledgements.html
===================================================================
--- trunk/acknowledgements.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/acknowledgements.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -58,7 +58,7 @@
 
 <h3>Current Project Team Members</h3>
 <ul>
-    <li><a href="mailto:gerardATlinuxfromscratch.org">Gerard Beekmans</a> | Linux-From-Scratch initiator, LFS Project organizer.</li>
    <li><a href="mailto:matthewATlinuxfromscratch.org">Matthew Burgess</a> | LFS Project Co-Leader, LFS General Package maintainer, LFS Book editor.</li>
    <li><a href="mailto:meerkatsATbellsouth.net">Craig Colton</a> | LFS, ALFS, BLFS & Hints Project logo creator.</li>
    <li><a href="mailto:nathanATlinuxfromscratch.org">Nathan Coulson</a> | LFS-Bootscripts maintainer.</li>
    <li><a href="mailto:jeroenATlinuxfromscratch.org">Jeroen Coumans</a> | Website developer, FAQ maintainer.</li>
    <li><a href="mailto:bdubbsATlinuxfromscratch.org">Bruce Dubbs</a> | LFS Quality Assurance Team leader, BLFS Book editor.</li>
    <li>Vassili Dzuba | ALFS Project editor.</li>
    <li><a href="mailto:manuelATlinuxfromscratch.org">Manuel Canales Esparcia</a> | LFS Book Editor (XML).</li>
    <li><a href="mailto:lfsATjg555.com">Jim Gifford</a> Patches Project</li>
    <li><a href="mailto:alexATlinuxfromscratch.org">Alex Groenewoud</a> | LFS Book editor.</li>
    <li><a href="mailto:kpflemingATlinuxfromscratch.org">Kevin Fleming</a> | ALFS Project leader.</li>
    <li>Neven Has | ALFS Project editor.</li>
    <li><a href="mailto:markhATlinuxfromscratch.org">Mark Hymers</a> | CVS maintainer, BLFS Book creator, former LFS Book editor.</li>
    <li><a href="mailto:iwanekATlinuxfromscratch.org">James Iwanek</a> | System Administration Team member.</li>
    <li><a href="mailto:larryATlinuxfromscratch.org">Larry Lawrence</a> | BLFS Book Editor.</li>
    <li><a href="mailto:nicholasATlinuxfromscratch.org">Nicholas Leippe</a> | Wiki maintainer.</li>
    <li><a href="mailto:lizardoATlinuxfromscratch.org">Anderson Lizardo</a> | Website backend scripts creator & maintainer.</li>
    <li><a href="mailto:djATlucasit.com">DJ Lucas</a> | BLFS Book editor.</li>
    <li><a href="mailto:billATlinuxfromscratch.org">Bill Maltby</a> | LFS Project organizer.</li>
    <li><a href="mailto:spyroATfs2.com">Ian Molton</a> | LFS Book editor.</li>
    <li><a href="mailto:geryonATgaosu.rave.org">Roel Neefs</a> | FTP Mirror maintainer.</li>
    <li><a href="mailto:billyocATgnuyork.org">Billy O'Connor</a> | BLFS Book editor.</li>
    <li><a href="mailto:alexanderATlinuxfromscratch.org">Alexander Patrakov</a> | LFS Book Editor (internationalization/localization).</li>
    <li><a href="mailto:thomaspATlinuxfromscratch.org">Thomas Pegg</a> | LFS Testing Team, ALFS Project editor.</li>
    <li><a href="mailto:scotATlinuxfromscratch.org">Scot McPherson</a> | LFS NNTP gateway maintainer.</li>
    <li><a href="mailto:ryanATlinuxfromscratch.org">Ryan Oliver</a> | LFS Testing Team leader, Toolchain maintainer, co-creator of PLFS.</li>
    <li><a href="mailto:jwroberATlinuxfromscratch.org">James Robertson</a> | Bugzilla maintainer, Wiki developer, LFS Book editor.</li>
    <li><a href="mailto:gregATlinuxfromscratch.org">Greg Schafer</a> | Toolchain maintainer, Former LFS Book editor, co-creator of PLFS.</li>
    <li><a href="mailto:tusharATlinuxfromscratch.org">Tushar Teredesai</a> | BLFS Book editor, Bugzilla maintainer, LFS-Bootscripts Maintainer, Patches Project, LFS Server co-admin.</li>
    <li><a href="mailto:jeremyATlinuxfromscratch.org">Jeremy Utley</a> | LFS Book editor, LFS Testing Team, Bugzilla maintainer, LFS-Bootscripts Maintainer, LFS Server co-admin.</li>
    <li><a href="mailto:winkieATlinuxfromscratch.org">Zack Winkles</a> | LFS Book editor (Emerging Technologies), LFS-Bootscripts co-maintainer.</li>
    <li>Igor Zivkovic | BLFS Book editor</li>
    <li>Countless other people on the various LFS and BLFS mailing lists who are making this book happen by giving their suggestions, testing the book and submitting bug reports, instructions and their experiences with installing various packages.</li>
</ul>
+    <li><a href="mailto:gerardATlinuxfromscratch.org">Gerard Beekmans</a> | Linux-From-Scratch initiator, LFS Project organizer.</li>
    <li><a href="mailto:matthewATlinuxfromscratch.org">Matthew Burgess</a> | LFS Project Co-Leader, LFS General Package maintainer, LFS Book editor.</li>
    <li><a href="mailto:meerkatsATbellsouth.net">Craig Colton</a> | LFS, ALFS, BLFS & Hints Project logo creator.</li>
    <li><a href="mailto:nathanATlinuxfromscratch.org">Nathan Coulson</a> | LFS-Bootscripts maintainer.</li>
    <li><a href="mailto:jeroenATlinuxfromscratch.org">Jeroen Coumans</a> | Website developer, FAQ maintainer.</li>
    <li><a href="mailto:bdubbsATlinuxfromscratch.org">Bruce Dubbs</a> | LFS Quality Assurance Team leader, BLFS Book editor.</li>
    <li>Vassili Dzuba | ALFS Project editor.</li>
    <li><a href="mailto:manuelATlinuxfromscratch.org">Manuel Canales Esparcia</a> | LFS Book Editor (XML).</li>
    <li><a href="mailto:lfsATjg555.com">Jim Gifford</a> Patches Project</li>
    <li><a href="mailto:alexATlinuxfromscratch.org">Alex Groenewoud</a> | LFS Book editor.</li>
    <li><a href="mailto:kpflemingATlinuxfromscratch.org">Kevin Fleming</a> | ALFS Project leader.</li>
    <li>Neven Has | ALFS Project editor.</li>
    <li><a href="mailto:markhATlinuxfromscratch.org">Mark Hymers</a> | Book creator, former LFS Book editor.</li>
    <li><a href="mailto:iwanekATlinuxfromscratch.org">James Iwanek</a> | System Administration Team member.</li>
    <li><a href="mailto:larryATlinuxfromscratch.org">Larry Lawrence</a> | BLFS Book Editor.</li>
    <li><a href="mailto:nicholasATlinuxfromscratch.org">Nicholas Leippe</a> | Wiki maintainer.</li>
    <li><a href="mailto:lizardoATlinuxfromscratch.org">Anderson Lizardo</a> | Website backend scripts creator & maintainer.</li>
    <li><a href="mailto:djATlucasit.com">DJ Lucas</a> | BLFS Book editor.</li>
    <li><a href="mailto:billATlinuxfromscratch.org">Bill Maltby</a> | LFS Project organizer.</li>
    <li><a href="mailto:spyroATfs2.com">Ian Molton</a> | LFS Book editor.</li>
    <li><a href="mailto:geryonATgaosu.rave.org">Roel Neefs</a> | FTP Mirror maintainer.</li>
    <li><a href="mailto:billyocATgnuyork.org">Billy O'Connor</a> | BLFS Book editor.</li>
    <li><a href="mailto:alexanderATlinuxfromscratch.org">Alexander Patrakov</a> | LFS Book Editor (internationalization/localization).</li>
    <li><a href="mailto:thomaspATlinuxfromscratch.org">Thomas Pegg</a> | LFS Testing Team, ALFS Project editor.</li>
    <li><a href="mailto:scotATlinuxfromscratch.org">Scot McPherson</a> | LFS NNTP gateway maintainer.</li>
    <li><a href="mailto:ryanATlinuxfromscratch.org">Ryan Oliver</a> | LFS Testing Team leader, Toolchain maintainer, co-creator of PLFS.</li>
    <li><a href="mailto:jwroberATlinuxfromscratch.org">James Robertson</a> | Bugzilla maintainer, Wiki developer, LFS Book editor.</li>
    <li><a href="mailto:gregATlinuxfromscratch.org">Greg Schafer</a> | Toolchain maintainer, Former LFS Book editor, co-creator of PLFS.</li>
    <li><a href="mailto:tusharATlinuxfromscratch.org">Tushar Teredesai</a> | BLFS Book editor, Bugzilla maintainer, LFS-Bootscripts Maintainer, Patches Project, LFS Server co-admin.</li>
    <li><a href="mailto:jeremyATlinuxfromscratch.org">Jeremy Utley</a> | LFS Book editor, LFS Testing Team, Bugzilla maintainer, LFS-Bootscripts Maintainer, LFS Server co-admin.</li>
    <li><a href="mailto:winkieATlinuxfromscratch.org">Zack Winkles</a> | LFS Book editor (Emerging Technologies), LFS-Bootscripts co-maintainer.</li>
    <li>Igor Zivkovic | BLFS Book editor</li>
    <li>Countless other people on the various LFS and BLFS mailing lists who are making this book happen by giving their suggestions, testing the book and submitting bug reports, instructions and their experiences with installing various packages.</li>
</ul>
 
 <h3>Translators</h3>
 <ul>

Modified: trunk/mail.html
===================================================================
--- trunk/mail.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/mail.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -74,11 +74,11 @@
 		<dt>lfs-support</dt>
 			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-support">lfs-support</a> list is the place to get help following the instructions in the stable release of LFS Book itself. If you're finished with the LFS Book, use blfs-support instead. Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
 		<dt>lfs-book</dt>
-			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-book">lfs-book</a> list is used for coordinating the LFS Book's maintenance. Traffic on it is mostly Bugzilla and CVS commit messages. It is important that all development discussion of interest to the Book's users take place on lfs-dev, not here.</dd>
+			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-book">lfs-book</a> list is used for coordinating the LFS Book's maintenance. Traffic on it is mostly Bugzilla and SVN commit messages. It is important that all development discussion of interest to the Book's users take place on lfs-dev, not here.</dd>
 		<dt>lfs-dev</dt>
 			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-dev">lfs-dev</a> list is for discussion of LFS Book development and tracks the testing branch. Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
 		<dt>lfs-hackers</dt>
-			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-hackers">lfs-hackers</a> list is for people working with bleeding-edge (CVS, alpha and beta) software and use the unstable LFS branch. This is the future of LFS...  Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
+			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-hackers">lfs-hackers</a> list is for people working with bleeding-edge (SVN, alpha and beta) software and use the unstable LFS branch. This is the future of LFS...  Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
 		<dt>lfs-chat</dt>
 			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/lfs-chat">lfs-chat</a> list is the place for community chatter. It's a place where anything goes, nothing is off-topic. You can discuss the price of beer or what hardware to buy. Even GNU versus BSD and Microsoft versus Linux flamewars are okay in lfs-chat.</dd>
 		<dt>lfs-security</dt>
@@ -86,7 +86,7 @@
 		<dt>blfs-support</dt>
 			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/blfs-support">blfs-support</a> list for the BLFS Book and beyond. It includes requests for help following the BLFS Book, requests for help with packages not (yet) in either the LFS Book or the BLFS Book, and other requests and discussion concerning software that might be installed on an LFS system. It does not include topics such as the price of beer, what hardware to buy, or GNU versus BSD or Microsoft versus Linux flamewars. These belong on lfs-chat, and since blfs-support is high traffic, please follow this rule strictly. Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
 		<dt>blfs-book</dt>
-			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/blfs-book">blfs-book</a> list is used for coordinating the BLFS Book's maintenance. Traffic on it is mostly Bugzilla and CVS commit messages. It is important that all development discussion of interest to the Book's users take place on blfs-dev, not here.</dd>
+			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/blfs-book">blfs-book</a> list is used for coordinating the BLFS Book's maintenance. Traffic on it is mostly Bugzilla and SVN commit messages. It is important that all development discussion of interest to the Book's users take place on blfs-dev, not here.</dd>
 		<dt>blfs-dev</dt>
 			<dd>The <a href="http://linuxfromscratch.org/mailman/listinfo/blfs-dev">blfs-dev</a> list is for discussion of BLFS Book development. Please read <a href="/faq/#netiquette">the netiquette rules</a> before posting!</dd>
 		<dt>hlfs-dev</dt>

Modified: trunk/organization.html
===================================================================
--- trunk/organization.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/organization.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -141,7 +141,7 @@
 
 	<p>An ideal implementation of the strategy is a dynamic thing, evolving as the environment changes. Maximum use of available tools will be needed to stay current in this rapidly changing environment.</p>
 
-	<p>The core delivery system for educating the user is an on-line and downloadable "book" and, recently instituted, a traditional printed version. Auxiliary delivery, to allow aggressive users to stay 100% current, is provided via CVS access that delivers the latest updates.</p>
+	<p>The core delivery system for educating the user is an on-line and downloadable "book" and, recently instituted, a traditional printed version. Auxiliary delivery, to allow aggressive users to stay 100% current, is provided via Subversion access that delivers the latest updates.</p>
 
 	<p>A vital adjunct to these core products are various support services. Implemented using mailing lists, forums, "chat", dynamically built web pages and a "wiki", these services will help users resolve problems they experience while progressing through the process of constructing the system the book defines. A side-effect is increased knowledge in areas that are precluded by the "Scope" and "Bounds" of the project proper, but it is encouraged if it does not detract from the primary goal.</p>
 

Modified: trunk/people.html
===================================================================
--- trunk/people.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/people.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -150,8 +150,6 @@
 		<dd>Nicholas Leippe, James Robertson</dd>
 	<dt>Bugzilla Maintainers</dt>
 		<dd>James Robertson, Jeremy Utley</dd>
-	<dt>CVS Maintainer</dt>
-		<dd>Mark Hymers</dd>
 	<dt>FTP Mirror maintainer</dt>
 		<dd>Roel Neefs</dd>
 	<dt>SVN Maintainers</dt>

Modified: trunk/sitemap.html
===================================================================
--- trunk/sitemap.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/sitemap.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -105,7 +105,7 @@
 <ul>
     <li><a href="blfs/downloads/stable/" title="The latest stable BLFS version">Current stable</a></li>
     <li><a href="blfs/downloads/test/" title="Test the next stable version">Test version</a></li>
-    <li><a href="blfs/downloads/cvs/" title="The latest CVS BLFS version">Current CVS</a></li>
+    <li><a href="blfs/downloads/cvs/" title="The latest unstable BLFS version">Current unstable</a></li>
     <li><a href="http://archive.linuxfromscratch.org/blfs-museum/" title="Download older versions">Previous Releases</a></li>
     <li><a href="blfs/packages.html" title="How to download all packages required by BLFS">Packages</a></li>
     <li><a href="blfs/artwork/" title="Desktop backgrounds, bootup logo's etc">Artwork</a></li>
@@ -113,7 +113,7 @@
 <h5>Read:</h5>
 <ul>
     <li><a href="blfs/stable.html" title="Release information and translations of BLFS">Stable and translation</a></li>
-    <li><a href="blfs/cvs.html" title="Get the bleeding-edge development version">Development (CVS)</a></li>
+    <li><a href="blfs/cvs.html" title="Get the bleeding-edge development version">Development (Unstable)</a></li>
 </ul>
 <h5>Write:</h5>
 <ul>
@@ -183,7 +183,7 @@
 <h5>Project:</h5>
 <ul>
     <li><a href="patches/index.html">Patches Mirrors</a></li>
-    <li><a href="patches/news.html">Patches CVS Changelog</a></li>
+    <li><a href="patches/news.html">Patches SVN Changelog</a></li>
     <li><a href="patches/about.html" title="About the patches project">About the patches project</a></li>
     <li><a href="patches/submit.html">Submit patches</a></li>
 </ul>

Modified: trunk/templates/alfs/news-top.html
===================================================================
--- trunk/templates/alfs/news-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/alfs/news-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -56,7 +56,7 @@
 	<ul>
 		<li><a href="#projectnews">ALFS-specific news</a></li>
 		<li><a href="#generalnews">General news</a></li>
-		<li><a href="#changelog">CVS Changelog</a></li>
+		<li><a href="#changelog">Development Changelog</a></li>
 	</ul>
 	</div>
 

Modified: trunk/templates/blfs/news-top.html
===================================================================
--- trunk/templates/blfs/news-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/blfs/news-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -55,7 +55,7 @@
 	<ul>
 		<li><a href="#projectnews">BLFS-specific news</a></li>
 		<li><a href="#generalnews">General news</a></li>
-		<li><a href="#changelog">CVS Changelog</a></li>
+		<li><a href="#changelog">Development Changelog</a></li>
 	</ul>
 	</div>
 

Modified: trunk/templates/hints/news-top.html
===================================================================
--- trunk/templates/hints/news-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/hints/news-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -50,4 +50,4 @@
 	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
 
 <div id="changelog">
-<h1>Hints CVS Changelog</h1>
+<h1>Hints Changelog</h1>

Modified: trunk/templates/lfs/news-top.html
===================================================================
--- trunk/templates/lfs/news-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/lfs/news-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -56,7 +56,7 @@
 	<ul>
 		<li><a href="#projectnews">LFS-specific news</a></li>
 		<li><a href="#generalnews">General news</a></li>
-		<li><a href="#changelog">CVS Changelog</a></li>
+		<li><a href="#changelog">Development Changelog</a></li>
 	</ul>
 	</div>
 

Modified: trunk/templates/patches/news-top.html
===================================================================
--- trunk/templates/patches/news-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/patches/news-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -50,5 +50,5 @@
 	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
 
 <div id="changelog">
-<h2>Patches CVS Changelog</h2>
+<h2>Patches Changelog</h2>
 	<p>The following changelog is automatically generated from CVS log messages and fed into this file. These changes are from last month.</p>

Modified: trunk/templates/website-bottom.html
===================================================================
--- trunk/templates/website-bottom.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/website-bottom.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -1,11 +1,10 @@
-		<p><a href="http://cvs.linuxfromscratch.org/index.cgi/www/?sortby=rev#dirlist">All CVS entries.</a></p>
 		<p><a href="#header">Back to the top.</a></p>
 	</div>
 
 	<h3 id="todo">Todo</h3>
 
 	<h4>Dynamic newspages</h4>
-		<p>Each section of lfs, blfs and alfs have a news page. These should reflect the most current state of development, which includes Bugzilla status, CVS commit logs and important maillinglist discussions. The result is useful as a development overview and reference point, both for the LFS team and for outside users. Currently the only things missing are the Bugzilla messages:</p>
+		<p>Each section of lfs, blfs and alfs have a news page. These should reflect the most current state of development, which includes Bugzilla status, commit logs and important maillinglist discussions. The result is useful as a development overview and reference point, both for the LFS team and for outside users. Currently the only things missing are the Bugzilla messages:</p>
 		<h5>Bugzilla script</h5>
 		<p>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>Got some useful replies from the Bugzilla developers; it seems that <a href="http://bugzilla.mozilla.org/attachment.cgi?id=109161&action=view">fine_whine.pl</a> is usually used for this (described in <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=185090">bug 185090</a>). This script should at least be edited so it spits out content which we can use, similar to the solution we've devised for cvs2cl.pl.</p>

Modified: trunk/templates/website-top.html
===================================================================
--- trunk/templates/website-top.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/templates/website-top.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -68,7 +68,7 @@
 			<li>We've tried to reduce the burden on the main LFS server. First of all, <a href="becomemirror.html" title="Learn how to become a mirror">mirror usage</a> is now enforced from the main section pages. Thanks to the use of relative links, mirrors can keep a copy of the entire site. A new initiative is the use of <a href="lfs/packages.html">P2P network links</a> for downloading the LFS tarballs. Right now this is a volunteer effort, but is well on its way to becoming the most reliable method of getting the packages.</li>
 			<li>Together with the fresh look comes a fresh navigation system. In graphical browsers you can navigate quickly to each LFS project with the top links. On the right column you'll always see the site-wide navigation links, while the left column is reserved for project-specific links. Be sure to check out the <a href="accesskeys.html">accessibility statement</a>, which tells you how to use keyboard shortcuts to navigate the website. In text browsers you'll see a number of skip-links have been added so you can quickly navigate through the website. You'll also be pleasantly surprised when printing the website.</li>
 			<li>As you can see, there are lots of additional goodies hidden on the website. The best thing to do is to start surfing! Please send all comments, positive and negative, to <a href="http://linuxfromscratch.org/mailman/listinfo/website">the website mailing list</a>. Also use that list if you find any bugs in this site, wether it's a browser not displaying pages properly or an orphaned link. Please include some information about your browser and the resolution you're surfing in.</li>
-			<li>The website's focus has shifted towards being more of a central portal for LFS and the community. The most visible change towards this goal is the inclusion of a news page for each section. These will inform you of new hints, recent changes in the books and, of course, book releases. The pages contain entries which are created by scripts which parse LFS and BLFS CVS changelogs. To stay informed of all website changes, you can view <a href="#changelog">the dynamically generated changelog.</a></li>
+			<li>The website's focus has shifted towards being more of a central portal for LFS and the community. The most visible change towards this goal is the inclusion of a news page for each section. These will inform you of new hints, recent changes in the books and, of course, book releases. The pages contain entries which are created by scripts which parse LFS and BLFS Subversion changelogs. To stay informed of all website changes, you can view <a href="#changelog">the dynamically generated changelog.</a></li>
 			<li>Some sections have rewritten or new content. For example, the <a href="hints/news.html">hints section</a> now has additional instructions on <a href="hints/submit.html">how to write and submit</a> hints and even <a href="hints/adoptahint.html">how to take over other people's hints</a>! The <a href="alfs/news.html">ALFS</a> section now also lists other people's build scripts next to the official Automated LFS system. </li>
 		</ul>
 		<p><a href="#header">Back to the top.</a></p>
@@ -130,4 +130,3 @@
 
 	<div id="changelog">
 	<h2>Changelog</h2>
-		<p>The following changelog is automatically generated from CVS log messages and fed into this file.</p>

Modified: trunk/website-manifesto.html
===================================================================
--- trunk/website-manifesto.html	2004-08-10 05:46:47 UTC (rev 827)
+++ trunk/website-manifesto.html	2004-08-10 06:18:57 UTC (rev 828)
@@ -71,10 +71,10 @@
 <li>provide LFS users and developers information about relevant LFS activities and releases ("news");</li>
 
 <li>direct LFS users needing support to relevant information channels;</li>
-<li>provide LFS developers with information needed to fulfill their tasks (e.g.. Bugzilla, CVS and mailing lists).</li>
+<li>provide LFS developers with information needed to fulfill their tasks (e.g.. Bugzilla, Subversion and mailing lists).</li>
 </ul>
 <h3>STRATEGY and LOGISTICS</h3>
-<p>The team will use the same tools as other LFS-related projects to manage the website. This includes, among other things, mailing-list-based communication, CVS and Bugzilla. Additionally, a variety of scripts and other tools may be used to enhance or automate the website. These should be open source.</p>
+<p>The team will use the same tools as other LFS-related projects to manage the website. This includes, among other things, mailing-list-based communication, Subversion and Bugzilla. Additionally, a variety of scripts and other tools may be used to enhance or automate the website. These should be open source.</p>
 <p>Content will be marked up semantically and will follow the spirit of the recommendations of the WWW Consortium.</p>
 <h3>POLICIES</h3>
 <p>Larger structural changes (e.g. a different CMS or the modification of the global navigation) must be announced and discussed on the website mailinglist first.</p>




More information about the website mailing list