1 <chapter id="chapter01">
2 <title>LFS Development</title>
3 <?dbhtml filename="chapter01.html" dir="chapter01"?>
5 <para>LFS development takes place using three main systems. Firstly,
6 the mailing lists <userinput>lfs-book</userinput>,
7 <userinput>lfs-dev</userinput> and (to a lesser extent)
8 <userinput>lfs-support</userinput>. Secondly the Bugzilla tracking
9 system, and thirdly the CVS server where the book itself is
10 stored. All of these services are provided by the server
11 <userinput>linuxfromscratch.org</userinput> also known as
12 <userinput>shadowfax.linuxfromscratch.org</userinput> or more usually,
13 <userinput>shadowfax</userinput>. This single server provides mailing
14 lists, web hosting, CVS hosting, ftp hosting, the Bugzilla system and
15 basically everything we use to work on the LFS project.</para>
17 <para>The actual LFS book itself is written using Docbook-XML and at
18 first can seem to be a daunting tangle of files. If you're confused, start
19 by looking at <filename>index.xml</filename>. At the bottom, you will
20 notice that it will reference the entity &book;. Look up the entity
21 &book; and you will see that it points to the file
22 <filename>book/book.xml</filename>. Continue in this way and you'll find
23 your way around the book soon enough.</para>
25 <para>The Bugzilla bug-tracking system for LFS can be found at <ulink
26 url="http://bugs.linuxfromscratch.org"/>. In order to be able to
27 add, remove and edit bugs, you need to add an account and make sure you
28 are logged in whenever you wish to perform such an action. You can
29 query and read the bug database without logging in or creating a user.
30 Note that all bugzilla messages are copied to the
31 <userinput>lfs-book</userinput> mailing list and that all editors
32 should be subscribed to this and the <userinput>lfs-dev</userinput>
33 list at a minimum.</para>
35 <para>Finally, there is the CVS server which will be discussed in the
36 following chapters.</para>