The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

_
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
Context English State
_ translator-credits
Writing FreeBSD Problem Reports
FreeBSD is a registered trademark of the FreeBSD Foundation.
IBM, AIX, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
Sun, Sun Microsystems, Java, Java Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, SunOS and VirtualBox are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the <quote>™</quote> or the <quote>®</quote> symbol.
$FreeBSD: head/en_US.ISO8859-1/articles/problem-reports/article.xml 53150 2019-06-14 09:41:35Z linimon $
This article describes how to best formulate and submit a problem report to the FreeBSD Project.
<personname> <firstname>Dag-Erling</firstname> <surname>Smørgrav</surname> </personname> <contrib>Contributed by </contrib>
<personname> <firstname>Mark</firstname> <surname>Linimon</surname> </personname>
<primary>problem reports</primary>
Introduction
One of the most frustrating experiences one can have as a software user is to submit a problem report only to have it summarily closed with a terse and unhelpful explanation like <quote>not a bug</quote> or <quote>bogus PR</quote>. Similarly, one of the most frustrating experiences as a software developer is to be flooded with problem reports that are not really problem reports but requests for support, or that contain little or no information about what the problem is and how to reproduce it.
This document attempts to describe how to write good problem reports. What, one asks, is a good problem report? Well, to go straight to the bottom line, a good problem report is one that can be analyzed and dealt with swiftly, to the mutual satisfaction of both user and developer.
Although the primary focus of this article is on FreeBSD problem reports, most of it should apply quite well to other software projects.

Showing only subset of the strings as there were too many matches.

Component Translation Difference to current string
The following strings have the same context and source.
Translated FreeBSD Doc (Archived)/articles_committers-guide
Translated FreeBSD Doc (Archived)/articles_bsdl-gpl
Translated FreeBSD Doc (Archived)/articles_contributing
Translated FreeBSD Doc (Archived)/books_arch-handbook
Translated FreeBSD Doc (Archived)/articles_remote-install
Translated FreeBSD Doc (Archived)/articles_explaining-bsd
Translated FreeBSD Doc (Archived)/articles_serial-uart
Translated FreeBSD Doc (Archived)/books_faq
Translated FreeBSD Doc (Archived)/articles_building-products
Translated FreeBSD Doc (Archived)/articles_freebsd-questions
Translated FreeBSD Doc (Archived)/articles_geom-class
Translated FreeBSD Doc (Archived)/articles_ipsec-must
Translated FreeBSD Doc (Archived)/articles_gjournal-desktop
Translated FreeBSD Doc (Archived)/articles_mailing-list-faq
Translated FreeBSD Doc (Archived)/books_developers-handbook
Translated FreeBSD Doc (Archived)/articles_pgpkeys
Translated FreeBSD Doc (Archived)/articles_leap-seconds
Translated FreeBSD Doc (Archived)/books_fdp-primer
Translated FreeBSD Doc (Archived)/articles_linux-users
Translated FreeBSD Doc (Archived)/articles_cups

Loading…

No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatching line breaks: Portuguese (Brazil), Spanish

Reset

Source information

Context
_
Source string comment
Put one translator per line, in the form NAME <EMAIL>, YEAR1, YEAR2
Flags
read-only
String age
a year ago
Source string age
a year ago
Translation file
articles/problem-reports.pot, string 1