New FAQ: define POLA
This commit is contained in:
parent
73c5147228
commit
31289252fe
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12980
1 changed files with 16 additions and 0 deletions
|
@ -11404,6 +11404,22 @@ raisechar=^^</programlisting>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="define-pola">
|
||||
<para>What does <acronym>POLA</acronym> mean?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Principle of Least Astonishment. It means that as
|
||||
FreeBSD evolves, changes visible to the user should be
|
||||
kept as unsurprising as possible. For example,
|
||||
arbitrarily rearranging system startup variables in
|
||||
<filename>/etc/rc.conf</filename> violates POLA.
|
||||
Developers consider POLA when contemplating user-visible
|
||||
system changes.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="define-repocopy">
|
||||
<para>What is a repo-copy?</para>
|
||||
|
|
Loading…
Reference in a new issue