|
Lines 1572-1578
Link Here
|
| 1572 |
request a review of the decision after 30 days and every 30 days |
1572 |
request a review of the decision after 30 days and every 30 days |
| 1573 |
thereafter (unless the total suspension period is less than 30 |
1573 |
thereafter (unless the total suspension period is less than 30 |
| 1574 |
days). A committer whose privileges have been revoked entirely |
1574 |
days). A committer whose privileges have been revoked entirely |
| 1575 |
may request a review after a period of 6 months have elapsed. |
1575 |
may request a review after a period of 6 months has elapsed. |
| 1576 |
This review policy is <emphasis>strictly informal</emphasis> |
1576 |
This review policy is <emphasis>strictly informal</emphasis> |
| 1577 |
and, in all cases, core reserves the right to either act on or |
1577 |
and, in all cases, core reserves the right to either act on or |
| 1578 |
disregard requests for review if they feel their original |
1578 |
disregard requests for review if they feel their original |
|
Lines 1998-2004
Link Here
|
| 1998 |
<para>FreeBSD is a highly portable operating system intended to |
1998 |
<para>FreeBSD is a highly portable operating system intended to |
| 1999 |
function on many different types of hardware architectures. |
1999 |
function on many different types of hardware architectures. |
| 2000 |
Maintaining clean separation of Machine Dependent (MD) and Machine |
2000 |
Maintaining clean separation of Machine Dependent (MD) and Machine |
| 2001 |
Independent (MI) code, as well as minimizing MD code is an important |
2001 |
Independent (MI) code, as well as minimizing MD code, is an important |
| 2002 |
part of our strategy to remain agile with regards to current |
2002 |
part of our strategy to remain agile with regards to current |
| 2003 |
hardware trends. Each new hardware architecture supported by |
2003 |
hardware trends. Each new hardware architecture supported by |
| 2004 |
FreeBSD adds substantially to the cost of code maintenance, |
2004 |
FreeBSD adds substantially to the cost of code maintenance, |
|
Lines 2018-2029
Link Here
|
| 2018 |
of interest in these environments, the FreeBSD Project is able |
2018 |
of interest in these environments, the FreeBSD Project is able |
| 2019 |
to maintain high levels of quality, stability, and performance, |
2019 |
to maintain high levels of quality, stability, and performance, |
| 2020 |
as well as minimize the load on various support teams on the |
2020 |
as well as minimize the load on various support teams on the |
| 2021 |
project, such as the ports team, documentation team, as well as |
2021 |
project, such as the ports team, documentation team, |
| 2022 |
security officer and release engineering teams. Diversity in |
2022 |
security officer, and release engineering teams. Diversity in |
| 2023 |
hardware support broadens the options for FreeBSD consumers by |
2023 |
hardware support broadens the options for FreeBSD consumers by |
| 2024 |
offering new features and usage opportunities (such as support |
2024 |
offering new features and usage opportunities (such as support |
| 2025 |
for 64-bit CPUs, use in embedded environments), but these |
2025 |
for 64-bit CPUs, use in embedded environments, etc.), but these |
| 2026 |
benefits always be carefully considered in terms of the real-world |
2026 |
benefits must always be carefully considered in terms of the real-world |
| 2027 |
maintenance cost associated with additional platform support. |
2027 |
maintenance cost associated with additional platform support. |
| 2028 |
</para> |
2028 |
</para> |
| 2029 |
|
2029 |
|
|
Lines 2032-2038
Link Here
|
| 2032 |
requirements for an architecture to be in that tier, |
2032 |
requirements for an architecture to be in that tier, |
| 2033 |
as well as specifying the obligations of developers with |
2033 |
as well as specifying the obligations of developers with |
| 2034 |
regards to the platform. In addition, a policy is defined |
2034 |
regards to the platform. In addition, a policy is defined |
| 2035 |
regarding under the circumstances required to change the tier |
2035 |
regarding the circumstances required to change the tier |
| 2036 |
of an architecture.</para> |
2036 |
of an architecture.</para> |
| 2037 |
</sect2> |
2037 |
</sect2> |
| 2038 |
|
2038 |
|
|
Lines 2082-2088
Link Here
|
| 2082 |
2 status as the availability of resources to continue to maintain |
2082 |
2 status as the availability of resources to continue to maintain |
| 2083 |
the system in a Production Quality state diminishes.</para> |
2083 |
the system in a Production Quality state diminishes.</para> |
| 2084 |
|
2084 |
|
| 2085 |
<para>Current Tier 2 platforms are PowerPC, and ia64.</para> |
2085 |
<para>Current Tier 2 platforms are PowerPC and ia64.</para> |
| 2086 |
</sect2> |
2086 |
</sect2> |
| 2087 |
|
2087 |
|
| 2088 |
<sect2> |
2088 |
<sect2> |
|
Lines 2094-2100
Link Here
|
| 2094 |
platforms are architectures for which hardware is not or will not |
2094 |
platforms are architectures for which hardware is not or will not |
| 2095 |
be available to the project in the foreseeable future, for which |
2095 |
be available to the project in the foreseeable future, for which |
| 2096 |
there are two or fewer active developers, that can not boot to at |
2096 |
there are two or fewer active developers, that can not boot to at |
| 2097 |
least single-user mode on real hardware (or simulator for new |
2097 |
least single-user mode on real hardware (or a simulator for new |
| 2098 |
hardware platforms), or which are considered legacy systems |
2098 |
hardware platforms), or which are considered legacy systems |
| 2099 |
unlikely to see broad future use. Tier 3 systems will not be |
2099 |
unlikely to see broad future use. Tier 3 systems will not be |
| 2100 |
committed to the base source tree, although support for Tier 3 |
2100 |
committed to the base source tree, although support for Tier 3 |
|
Lines 2118-2124
Link Here
|
| 2118 |
<sect2> |
2118 |
<sect2> |
| 2119 |
<title>Policy on Changing the Tier of an Architecture</title> |
2119 |
<title>Policy on Changing the Tier of an Architecture</title> |
| 2120 |
|
2120 |
|
| 2121 |
<para>Systems may only be moved from one tier to another tier by |
2121 |
<para>Systems may only be moved from one tier to another by |
| 2122 |
approval of the FreeBSD Core Team, which shall make that |
2122 |
approval of the FreeBSD Core Team, which shall make that |
| 2123 |
decision in collaboration with the Security Officer, Release |
2123 |
decision in collaboration with the Security Officer, Release |
| 2124 |
Engineering, and toolchain maintenance teams.</para> |
2124 |
Engineering, and toolchain maintenance teams.</para> |
|
Lines 2668-2674
Link Here
|
| 2668 |
well.</para> |
2668 |
well.</para> |
| 2669 |
|
2669 |
|
| 2670 |
<para>This information consists of one or more lines containing the |
2670 |
<para>This information consists of one or more lines containing the |
| 2671 |
the key word or phrase, a colon, tabs for formatting, and then the |
2671 |
key word or phrase, a colon, tabs for formatting, and then the |
| 2672 |
additional information.</para> |
2672 |
additional information.</para> |
| 2673 |
|
2673 |
|
| 2674 |
<para>The key words or phrases are:</para> |
2674 |
<para>The key words or phrases are:</para> |