os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Based on some verbal feedback from colleagues;

Browse source 
De-emphasise the fact that we use GNATS.  Some people have assumed that
GNATS is something they have a problem with, not a tool that we use.

Add some additional information about what a PR is, and why it's not
necessarily a bad thing.

Include an additional link to send-pr.html where it seemed appropriate.
This commit is contained in:
Nik Clayton 2002-06-11 20:53:42 +00:00
parent 252e0942ad
commit f52778b85b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=13367
2 changed files with 44 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
en/support.sgml
View file

@ -1,5 +1,5 @@
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY date "$FreeBSD: www/en/support.sgml,v 1.259 2002/04/20 18:08:58 phantom Exp $">
<!ENTITY date "$FreeBSD: www/en/support.sgml,v 1.260 2002/04/27 12:31:12 gioria Exp $">
<!ENTITY title "Support">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
@ -12,7 +12,7 @@
<li><a href="#newsgroups">Newsgroups</a></li>
<li><a href="#irc">IRC</a></li>
<li><a href="#web">WEB Resources</a></li>
<li><a href="#gnats">GNATS Problem Report Database</a></li>
<li><a href="#gnats">Problem Report Database</a></li>
<li><a href="#cvs">CVS Repository</a></li>
<li><a href="#user">User Groups</a></li>
<li><a href="#development">FreeBSD Development Projects</a></li>
@ -197,11 +197,24 @@
<a href="news/newsflash.html">Newsflash</a> page.</p></li>
</ul>
<h2><a name="gnats"
href="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">GNATS</a>
Problem Report Database</h2>
<h2><a name="gnats">Problem Report Database</a></h2>
<p>Current FreeBSD problem reports are tracked using the GNATS database.</p>
<p>Current FreeBSD problem reports are tracked using the <a
href="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">GNATS</a>
database.</p>
<p>A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD
itself. In some cases it may be reporting a mistake in the
documentation (which could be a simple typo). In other cases it may
be a 'wishlist' item that the submitter would like to see incorporated
in to FreeBSD. In many cases a PR contains a port which has been
prepared for inclusion in the FreeBSD
<a href="../ports/index.html">Ports and Packages</a> collection.</p>
<p>Problem reports start 'open', and are closed as the issue they report
is resolved. In addition, each PR is assigned a unique tracking ID
to ensure that it is not lost. Many FreeBSD changes include the
tracking ID of the PR that prompted the change.</p>
<ul>
<li><a href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">View the
@ -219,12 +232,13 @@
</ul>
<p>Problem reports may also be submitted to the development team using the
<a href="send-pr.html">send-pr(1)</a> command on a FreeBSD system or
<a href="send-pr.html">send-pr(1)</a> command on a FreeBSD system,
using this web based <a href="send-pr.html">submission form</a>, or
by sending an email message to <a
href="mailto:freebsd-bugs@FreeBSD.ORG">freebsd-bugs@FreeBSD.ORG</a>.
Please note that <a href="send-pr.html">send-pr</a> is preferred
since messages sent to the mailing list are <em>not</em> tracked as
official problem reports!</p>
official problem reports, and may get lost in the noise!</p>
<p>Before submitting a problem report, you might find it useful to
read the <a

30
en/usergroups.sgml
View file

@ -1,5 +1,5 @@
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY date "$FreeBSD: www/en/support.sgml,v 1.259 2002/04/20 18:08:58 phantom Exp $">
<!ENTITY date "$FreeBSD: www/en/support.sgml,v 1.260 2002/04/27 12:31:12 gioria Exp $">
<!ENTITY title "Support">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
@ -12,7 +12,7 @@
<li><a href="#newsgroups">Newsgroups</a></li>
<li><a href="#irc">IRC</a></li>
<li><a href="#web">WEB Resources</a></li>
<li><a href="#gnats">GNATS Problem Report Database</a></li>
<li><a href="#gnats">Problem Report Database</a></li>
<li><a href="#cvs">CVS Repository</a></li>
<li><a href="#user">User Groups</a></li>
<li><a href="#development">FreeBSD Development Projects</a></li>
@ -197,11 +197,24 @@
<a href="news/newsflash.html">Newsflash</a> page.</p></li>
</ul>
<h2><a name="gnats"
href="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">GNATS</a>
Problem Report Database</h2>
<h2><a name="gnats">Problem Report Database</a></h2>
<p>Current FreeBSD problem reports are tracked using the GNATS database.</p>
<p>Current FreeBSD problem reports are tracked using the <a
href="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">GNATS</a>
database.</p>
<p>A FreeBSD problem report (PR) is not necessarily a bug with FreeBSD
itself. In some cases it may be reporting a mistake in the
documentation (which could be a simple typo). In other cases it may
be a 'wishlist' item that the submitter would like to see incorporated
in to FreeBSD. In many cases a PR contains a port which has been
prepared for inclusion in the FreeBSD
<a href="../ports/index.html">Ports and Packages</a> collection.</p>
<p>Problem reports start 'open', and are closed as the issue they report
is resolved. In addition, each PR is assigned a unique tracking ID
to ensure that it is not lost. Many FreeBSD changes include the
tracking ID of the PR that prompted the change.</p>
<ul>
<li><a href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">View the
@ -219,12 +232,13 @@
</ul>
<p>Problem reports may also be submitted to the development team using the
<a href="send-pr.html">send-pr(1)</a> command on a FreeBSD system or
<a href="send-pr.html">send-pr(1)</a> command on a FreeBSD system,
using this web based <a href="send-pr.html">submission form</a>, or
by sending an email message to <a
href="mailto:freebsd-bugs@FreeBSD.ORG">freebsd-bugs@FreeBSD.ORG</a>.
Please note that <a href="send-pr.html">send-pr</a> is preferred
since messages sent to the mailing list are <em>not</em> tracked as
official problem reports!</p>
official problem reports, and may get lost in the noise!</p>
<p>Before submitting a problem report, you might find it useful to
read the <a