upstream version. Whatever changes you need, always try not to fork from the
upstream sources.
</para>
+<para>
+If you find that the upstream developers are or become hostile towards Debian
+or the free software community, you may want to re-consider the need to
+include the software in Debian. Sometimes the social cost to the
+Debian community is not worth the benefits the software may bring.
+</para>
</section>
<section id="rc-bugs">
Generally you should deal with bug reports on your packages as described in
<xref linkend="bug-handling"/> . However, there's a special category of bugs
that you need to take care of — the so-called release-critical bugs (RC
-bugs). All bug reports that have severity <emphasis>critical</emphasis>,
-<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to
+bugs). All bug reports that have severity <literal>critical</literal>,
+<literal>grave</literal> or <literal>serious</literal> are considered to
have an impact on whether the package can be released in the next stable
release of Debian. These bugs can delay the Debian release and/or can justify
the removal of a package at freeze time. That's why these bugs need to be