Update all url's from the first commit that I did today to have
a space before the <link> and remove the space from within the link
so that it just looks good.
pointy hat: remko
noticed by: danger
- continue to add more information that is specific to the web-based
form as opposed to send-pr(1). In particular, mention problems that
are particular to that method.
- greatly expand the text sections about various fields such as
'categories' to try to adddress continuing misunderstanding on
the part of our users.
- discuss the fact that spammers will most likely find your email
address from a GNATS submission.
- demote kernel panics to 'serious' to represent commonly accepted
usage. Reserve 'critical' for data corruption issues or things that
would be considered 'showstoppers' for an upcoming release. (I am
using my bugmeister hat for this change.)
- reiterate that serious security problems should go to secteam, not
into GNATS.
- document the common problems seen when submitting PRs, including
our anti-spam measures and the 'lost PR' index problem.
- deprecate the use of HTML-only messages. Regression testing using
the spam filters shows that close to 100% of such messages are spam.
(The filters have been tuned to correctly pass HTML that is included
in patches but reject HTML that conforms to all the common abuse
patterns. I am using my bugmeister hat for this change).
which are problems with code that is merely incorporated into FreeBSD. In
particular, the original article was written from the standpoint of src/;
these changes put ports/ on an equal basis. Finally, cross-reference the
src/ versions that secteam supports.
the mailing-lists.ent file (though it's not really an mailinglist).
Also replace the current follow up addresses by it's entity name.
Submitted by: ceri
category and change the master list of categories to point the CVSweb
location, which should always have the latest list.
Spurred by email from: obrien
Currently we have articles.ent and books.ent, and
for example, articles.ent can be used by putting the
following lines in the doctype declaration:
<!ENTITY % articles.ent PUBLIC
"-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
This pulls all of the necessary entities via share/sgml/articles.ent.
The translation teams can customize these entities by redefining
the articles.ent file in <langcode>/share/sgml. See
ja_JP.eucJP/share/sgml for example.
a good Problem Report. Add pointers to the new files ports/CHANGES
and ports/UPDATING. Change some occurrences of FreeBSD to &os; if
they were in the affected lines (another commit will do the remaining
ones). Suggest guidelines for the often-abused Severity and Priority
fields. Add a pointer to the categories definition file. Add the
'threads' category. Add a warning to include the tracking number on
followups to save creating new, bogus, PRs.
PR: docs/67062
Reviewed by: ceri, keramida, others
Approved by: ceri (mentor)
- Add trademark tags as needed, generally on first use in each
article.
- Add an attribution to the legal section mentioning all trademarks
referenced.
- Always use correct case for trademarks.
writing a good problem report" section.
- Fix a few typos.
- Add a link to the searchable gnats database at FreeBSD.org.
- Point the users at /usr/src/UPDATING for more info before sending PRs.
- Be more verbose about patches and inline inclusion of diffs in a PR.
- Emphasize the importance of Class: maintainer-update and the use of
"[maintainer update]"
- Describe what "[patch]" in synopsis lines means now that it's
commonly used to help people who read PR indexes.
Submitted by: Mark Linimon <linimon@lonesome.com>
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
