Author: kwade
Update of /cvs/fedora/web/html/about/faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15400/web/html/about/faq
Modified Files:
index.php
Log Message:
Applying patch from bz#189069
Index: index.php
===================================================================
RCS file: /cvs/fedora/web/html/about/faq/index.php,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- index.php 30 Mar 2005 17:47:22 -0000 1.1.1.1
+++ index.php 13 Oct 2006 17:20:10 -0000 1.2
@@ -1,285 +1,10 @@
-<?
+<?php
+//
+// Easily-changeable template for redirection.
+//
-include("site.inc");
-$template = new Page;
-$template->initCommon();
-$template->displayHeader();
+$NEWURL="http://fedoraproject.org/wiki/FAQ";;
-?>
-
-<h1><a name="faq"></a>FAQs</h1>
-
-<div class="qandaset">
- <table border="0" summary="Q and A Set">
- <tbody>
-
-<!--
- <tr class="question"><td><strong>Q:</strong></td>
- <td></td>
- </tr>
-
- <tr class="answer"><td><p><strong>A:</strong></p></td>
- <td><p>
- </p></td>
- </tr>
--->
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Why a project instead of a product?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>
-A global steering committee at Red Hat decided that Red Hat Linux
-was suffering from too many compromises as a retail "product", and
-that we should redirect our efforts at creating a community-based
-project.
-Rather than being run through product management as
-something that has to appear on retail shelves on a certain date,
-<? print $RELEASE_NAME; ?> will be released based on schedules,
-set by a steering committee, that will be open and accessible to the
-community, as well as influenced by the community.
- </p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>What are the core benefits of this change?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>
-Changing the product to a project will:
-<ul>
-<li>Ensure that users can get the latest bits as quickly as possible.</li>
-<li>Create new opportunities for developers and users to participate in
-<? print $THE_PROJECT_NAME; ?> development by opening up the full development
-process for anyone to see and join if they'd like.</li>
-<li>Allow us to use <? print $THE_PROJECT_NAME; ?> to develop and mature
-the latest, greatest technologies that may be incorporated
-later into products like Red Hat Enterprise Linux.</li>
-<li>Speed up the development process, taking better advantage
-of the inherent strengths of the open source model.</li>
-</ul>
- </p>
- </td>
- </tr>
-
- <tr class="question"><td><strong>Q:</strong></td>
- <td>Who is this steering committee, anyway?</td>
- </tr>
-
- <tr class="answer"><td><p><strong>A:</strong></p></td>
- <td><p>The current membership of the steering committee will
- be maintained in the
- <a href="/about/leadership.php">leadership</a> section of
- the web site.</p>
- </p></td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
-
- <td>Can I make my own commercially-supported operating system
- based on <? print $RELEASE_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
-
- <td>
- <p>The open source licenses (such as the GPL) governing the
-source code allow you to do this, but any use must comply with the
-<a href="/about/trademarks/">trademark rules</a>.
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Can I redistribute <? print $THE_PROJECT_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>Yes, and we strongly encourage you to do so. You will need
-to comply with <? print $THE_PROJECT_NAME;
-?> <a href="/about/trademarks/">trademark rules</a>.
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Will Red Hat provide formal technical support for
- <? print $THE_PROJECT_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>No, no formal Web or phone support for <? print $THE_PROJECT_NAME;
-?> will be available from Red Hat. Red Hat's supported product line will be
-based in part on <? print $RELEASE_NAME; ?>, and our development will be done
-externally as part of <? print $THE_PROJECT_NAME; ?> as much as possible.
-Each new release of our supported products will be based in part on a recent
-release of <? print $RELEASE_NAME; ?>.</p>
-<p>Refer to the <a href="/about/" target="_top">About</a> for details.</p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Will Red Hat's supported products contain all the packages
- found in <? print $RELEASE_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>In order to focus our efforts and limit support costs, we
-will probably select a subset of packages found in <? print $RELEASE_NAME;
-?> to include in the supported product line. One of the goals of
-<? print $THE_PROJECT_NAME; ?> is to encourage a pool of high-quality add-on
-packages; if we're successful, there will be so many we won't be able
-to support all of them.</p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>What is the errata policy for <? print $THE_PROJECT_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
-<p>
-Security updates, bugfix updates, and new feature updates will all
-be available, through Red Hat and third parties. Updates may be staged
-(first made available for public qualification, then later for general
-consumption) when appropriate. In drastic cases, we may remove a package
-from <? print $THE_PROJECT_NAME; ?> if we judge that a necessary security
-update is too problematic/disruptive to the larger goals of the project.
-Availability of updates should not be misconstrued as support for anything
-other than continued development and innovation of the code base. Updates
-will be available for two to three months after the release of the subsequent
-version; that is, updates for <? print $RELEASE_NAME; ?> 1 will be provided
-for two to three months after the release of <? print $RELEASE_NAME; ?> 2,
-and so forth.
-</p>
-<p>
-Red Hat will not be providing an SLA (Service Level Agreement) for
-resolution times for updates for <? print $THE_PROJECT_NAME; ?>. Security
-updates will take priority. For packages maintained by external parties,
-Red Hat may respond to security holes by deprecating packages if the
-external maintainers do not provide updates in a reasonable time. Users
-who want support, or maintenance according to an SLA, may purchase the
-appropriate Red Hat Enterprise Linux product for their use.
-<p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Who will make global technical decisions about
- <? print $RELEASE_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>Red Hat will retain editorial control over
-<? print $RELEASE_NAME; ?> — but will explicitly include
-external developers in the process of making technical decisions
-that align with our <a href="/about/objectives.php">project objectives</a>.</p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>What architectures will be supported by
- <? print $THE_PROJECT_NAME; ?>?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
-
- <td>
- <p>Red Hat will initially focus on the x86 family of architectures.
-Red Hat may also choose to build <? print $RELEASE_NAME; ?> for other
-architectures, and in doing so will focus on architectures in which
-it has a business interest. This will make it easier to identify and
-fix bugs; the sooner they are found, the easier it is to isolate the
-change that caused the bug and therefore the easier it is to fix.
-Other community members are welcome to participate in building
-for other architectures. Mechanisms, policies, and procedures for
-supporting other architectures have not been created, but soon will be.
-To avoid duplication of effort, it is recommended that community members
-ask about builds for other architectures before doing their own builds.</p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>Will <? print $RELEASE_NAME; ?> be sold in retail?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>
-<? print $RELEASE_NAME; ?> will not be sold through the retail channel
-as a shrinkwrapped box. There is no list price for Fedora Core.
-</p></p>
-The rapid development pace we expect for <? print $RELEASE_NAME;
-?> doesn't suit retail distribution — it is a lot of work to get a
-box product in and out of the channel, and retail isn't set up to
-efficiently handle software that is updated as often as every six
-months. Also, the creation of packaging and other materials that are
-necessary for retail significantly slows down the time to market, which
-means that users can't get the freshest bits when they are still truly
-fresh.
-</p></p>
-Further information on Red Hat's retail product line is available at
-<a href="http://www.redhat.com/software/workstation/";>the Red Hat website</a>.
- </p>
- </td>
- </tr>
-
- <tr class="question">
- <td><strong>Q:</strong></td>
- <td>How will <? print $THE_PROJECT_NAME; ?> be made available to the
- public?</td>
- </tr>
-
- <tr class="answer">
- <td><p><strong>A:</strong></p></td>
- <td>
- <p>
-<? print $RELEASE_NAME; ?> releases will be available as ISO images for
-both CDs and DVDs, and will also be available through other channels such
-as third-party online sales of physical media; distribution at Linux User Groups,
-included in magazines and in books, and maybe even handed out at trade
-shows. The bits may be actively pushed into content sharing networks
-such as BitTorrent. (Not all mechanisms will be used for each release,
-except that ISOs will be freely available for each release.)
- </p>
- </td>
- </tr>
-
-
- </tbody>
- </table>
-</div>
-
-<?
-
-$template->displayFooter('$Date$');
+include("redirect.inc");
?>
