Translation

(itstool) path: legalnotice/para
English
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.
207/2070
Context English Spanish State
_ translator-credits Juan F. Rodriguez jrh@it.uc3m.es, 2007
Sergio Carlavilla carlavilla@mailbox.org, 2019
Writing FreeBSD Problem Reports Escribiendo informes de problemas de FreeBSD
FreeBSD is a registered trademark of the FreeBSD Foundation. 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. 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. 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. 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. 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 $ $FreeBSD$
This article describes how to best formulate and submit a problem report to the FreeBSD Project. Este artículo describe cómo realizar y enviar informes de problemas para el proyecto FreeBSD de la mejor forma posible.
<personname> <firstname>Dag-Erling</firstname> <surname>Smørgrav</surname> </personname> <contrib>Contributed by </contrib> <personname> <firstname>Dag-Erling</firstname> <surname>Smørgrav</surname> </personname> <contrib>Contributed by </contrib>
<personname> <firstname>Mark</firstname> <surname>Linimon</surname> </personname> <personname> <firstname>Mark</firstname> <surname>Linimon</surname> </personname>
<primary>problem reports</primary> <primary>problem reports</primary>
Introduction Introducción
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. Una de las experiencias más frustrantes que uno puede tener como usuario de software es enviar un informe de problemas solo para que se cierre sumariamente con una explicación breve e inútil como <quote>no es un error</quote> o <quote>PR erróneo</quote>. De manera similar, una de las experiencias más frustrantes que puede experimentar un desarrollador de aplicaciones consiste en verse inundado por una cantidad ingente de informes de problemas que en realidad vienen a ser solicitudes de soporte o ayuda, o que contienen poca o ninguna información sobre cúal es el problema y cómo reproducirlo.
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. Este documento intenta describir cómo escribir buenos informes de problemas. ¿Qué, se preguntará, es un buen informe de problemas? Bien, para ir directos al grano, un buen informe de problemas es aquél que se puede analizar y tratar rápidamente, para mutua satisfacción del usuario y del desarrollador.
Although the primary focus of this article is on FreeBSD problem reports, most of it should apply quite well to other software projects. Aunque el objetivo principal de este artículo se centra en los informes de problemas de FreeBSD, la mayoría de los conceptos se pueden aplicar bastante bien en otros proyectos de software.
Note that this article is organized thematically, not chronologically. Read the entire document before submitting a problem report, rather than treating it as a step-by-step tutorial. Tenga en cuenta que este artículo está organizado temáticamente, no cronológicamente. Lea todo el documento antes de enviar un informe de problemas, en lugar de tratarlo como un tutorial paso a paso.
When to Submit a Problem Report Cuándo enviar informes de problemas
There are many types of problems, and not all of them should engender a problem report. Of course, nobody is perfect, and there will be times when what seems to be a bug in a program is, in fact, a misunderstanding of the syntax for a command or a typographical error in a configuration file (though that in itself may sometimes be indicative of poor documentation or poor error handling in the application). There are still many cases where submitting a problem report is clearly <emphasis>not</emphasis> the right course of action, and will only serve to frustrate both the submitter and the developers. Conversely, there are cases where it might be appropriate to submit a problem report about something else than a bug—an enhancement or a new feature, for instance. Hay muchos tipos de problemas y no todos ellos merecen la creación de un informe de problemas. Por supuesto, nadie es perfecto, y habrá ocasiones en que lo que parece ser un error en un programa es, de hecho, un malentendido de la sintaxis de un comando o un error tipográfico en un archivo de configuración (aunque en este último caso podría tratarse de un indicador de documentación escasa o que la aplicación peca de una gestión de errores defectuosa). Incluso teniendo estos aspectos en cuenta existen varios casos en los cuales el envío de un informe de problemas resulta claramente <emphasis>no ser</emphasis> la mejor forma de proceder, y solo servirá para frustrar tanto al remitente como a los desarrolladores. Por el contrario, hay casos en los que podría ser apropiado enviar un informe de problemas sobre algo más que un error: una mejora o una nueva característica, por ejemplo.
So how does one determine what is a bug and what is not? As a simple rule of thumb, the problem is <emphasis>not</emphasis> a bug if it can be expressed as a question (usually of the form <quote>How do I do X?</quote> or <quote>Where can I find Y?</quote>). It is not always quite so black and white, but the question rule covers a large majority of cases. When looking for an answer, consider posing the question to the <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions">FreeBSD general questions mailing list</link>. Entonces, ¿cómo se determina qué es un error y qué no? Como regla general, el problema <emphasis>no</emphasis> es un error si puede expresarse como una pregunta (normalmente del estilo de <quote>¿Cómo hago X?</quote> o <quote>¿Dónde puedo encontrar Y?</quote>). Las cosas no son siempre blancas o negras, pero la regla de la pregunta cubre la gran mayoría de los casos. Al buscar una respuesta, considere plantear la pregunta a la <link xlink:href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-questions">lista de correo de preguntas generales de FreeBSD</link>.
Component Translation Difference to current string
This translation Translated FreeBSD Doc/articles_problem-reports
The following strings have the same context and source.
Translated FreeBSD Doc/articles_explaining-bsd Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and y Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.
Translated FreeBSD Doc/articles_committers-guide
Translated FreeBSD Doc/articles_geom-class
Translated FreeBSD Doc/articles_linux-users Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and y Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.
Translated FreeBSD Doc/articles_freebsd-releng Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, andy Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.
Translated FreeBSD Doc/articles_filtering-bridge
Translated FreeBSD Doc/articles_freebsd-update-server
Translated FreeBSD Doc/articles_releng
Translated FreeBSD Doc/books_faq
Translated FreeBSD Doc/books_developers-handbook Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and y Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.
Translated FreeBSD Doc/books_handbook Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and y Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.
Translated FreeBSD Doc/articles_bsdl-gpl Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and y Xeon are trademarks or registered trademarks ofson marcas comerciales o marcas comerciales registradas de Intel Corporation or it sus subsidiarieas ien the United States and other countrilos Estados Unidos y otros países.

Loading…

User avatar None

New source string

FreeBSD Doc / articles_problem-reports — Spanish

New source string a year ago
Browse all component changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Spanish
trademark marca comercial FreeBSD Doc

Source information

Source string comment
(itstool) path: legalnotice/para
Source string location
article.translate.xml:15
String age
a year ago
Source string age
a year ago
Translation file
articles/es_ES/problem-reports.po, string 5