Overview

Project website docs.freebsd.org/en
Translation license BSD 2-Clause "Simplified" License
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Only chosen users can contribute.
  • The translation uses bilingual files.
File mask documentation/content/*/articles/freebsd-status-report-process/_index.po
Translation file Download documentation/content/es/articles/freebsd-status-report-process/_index.po
Last change Jan. 24, 2025, 1:39 p.m.
Last author None

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 122 1,867 12,836
Translated 99% 121 95% 1,790 96% 12,412
Needs editing 1% 1 4% 77 3% 424
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 124 changes 0 changes 1 change 0 changes 0 changes 0 changes 143 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 4 changes
Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan

Quick numbers

1,867
Hosted words
122
Hosted strings
99%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
−1%
Translated
+100%
+100%
Contributors
—
User avatar None

New string to translate

Documentation / articles/freebsd-status-report-process/_index — Spanish

1 new string to translate appeared in the translation. 2 weeks ago
User avatar None

Resource update

Documentation / articles/freebsd-status-report-process/_index — Spanish

The "documentation/content/es/articles/freebsd-status-report-process/_index.po" file was changed. 2 weeks ago
User avatar None

String updated in the repository

Documentation / articles/freebsd-status-report-process/_index — Spanish

And then they stop. Maybe the reader is an avid Cyberdyne fan and knows what exciting new features the T800 brings. This is unlikely. It is far more likely that they have vaguely heard of whatever you have imported (especially into the ports tree: remember that there are over 35,000 other things there too...). List some of the new features, or bug fixes. Tell them why it is a good thing that we have the new version.
Y luego paran. A lo mejor el lector es un ávido fan de Cyberdyne y conoce todas las características excitantes del nuevo T800. Es improbable. Es mucho más probable que haya oído hablar vagamente de lo que quiera que hayas importado (especialmente en el árbol de ports: recuerda que hay cerca de 30,000 cosas ahí también...). Proporciona una lista de nuevas características, o fallos corregidos. Diles por qué es bueno que tengamos una nueva versión.
2 weeks ago
User avatar None

Source string changed

Documentation / articles/freebsd-status-report-process/_index — Spanish

And then they stop. Maybe the reader is an avid Cyberdyne fan and knows what exciting new features the T800 brings. This is unlikely. It is far more likely that they have vaguely heard of whatever you have imported (especially into the ports tree: remember that there are over 305,000 other things there too...). List some of the new features, or bug fixes. Tell them why it is a good thing that we have the new version.
2 weeks ago
User avatar None

Committed changes

Documentation / articles/freebsd-status-report-process/_index — Spanish

Committed changes a year ago
User avatar fernape

Translation changed

Documentation / articles/freebsd-status-report-process/_index — Spanish

Reports are always accepted by the status team, but the main collection process happens the last month of each quarter, hence in March, June, September and December. Explicit calls for status reports will be sent in those months. The months of January, April, July and October are dedicated to putting together the reports submitted during the precedent quarter; this can include waiting for late submissions. Status reports publication is done during the same months as soon as the report are ready.
Los informes siempre son aceptado por el _status team_, pero el proceso de recolección principal sucede en el último mes de cada trimestre, esto es en Marzo, Junio, Septiembre y Diciembre. Se enviarán llamadas para los informes de estado en esos meses. Los meses de Enero, Abril, Julio y Octubre se dedican a organizar los informes enviados durante el trimestre anterior; esto puede inclurir esperar por envíos tardíos. La publicación de los informes de estado se realiza durante los mismos meses en cuanto el informe está listo.
a year ago
User avatar fernape

Translation changed

Documentation / articles/freebsd-status-report-process/_index — Spanish

submit a pull request to the doc repository through link:https://github.com/freebsd/freebsd-doc[its GitHub mirror] . You should put your reports in the appropriate subdirectory of `doc/website/content/en/status` (create it if it is missing);
envía una pull request al repositorio doc mediante link:https://github.com/freebsd/freebsd-doc[su réplica en GitHub]. Deberías poner tus informes en el subdirectorio apropiado de `doc/website/content/en/status` (créalo si no existe);
a year ago
User avatar fernape

Translation changed

Documentation / articles/freebsd-status-report-process/_index — Spanish

Bear in mind that status reports are not just reports on the status of the project, they are reports on the change of status of the project. If there is an ongoing project, spend a couple of sentences introducing it, but then spend the rest of the report talking about the new work. What progress has been made since the last report? What is left to do? When is it likely to be finished (or, if "finished" does not really apply, when is it likely to be ready for wider use, for testing, for deployment in production, and so on)?
Ten en cuenta que los informes de estado no son sólo informes de estado del proyecto, son informes sobre el cambio de estado del proyecto. Si hay un proyecto en curso, utiliza un par de frases para presentarlo, pero utiliza el resto del informe hablando acerca del trabajo nuevo ¿Qué progresos se han hecho desde el último informe? ¿Qué queda por hacer? ¿Cuándo es probable que termine (o, isi "terminado" no se puede aplicar, cuando está previsto que esté listo para un uso más amplio, para pruebas, para desplegarlo en producción, etc)?
a year ago
User avatar fernape

Search and replace

Documentation / articles/freebsd-status-report-process/_index — Spanish

First [.filename]#doc/website/content/en/status/_index.adoc# is edited: the next due date is updated and a link to the new report is added. The change is then pushed on the repository and the status team checks that everythings works as expected.
Primero se edita [.filename]#doc/website/content/en/status/_index.adoc#: se actualiza la siguiente fecha de entra y se añade un enlace al nuevo informe. Después se empuja el cambio al repositorio y el equipo de estado_status team_ comprueba que todo funciona como se espera.
a year ago
User avatar fernape

Search and replace

Documentation / articles/freebsd-status-report-process/_index — Spanish

Submitted reports are reviewed and merged in the proper subdirectory of [.filename]#doc/website/content/en/status/# as they come in. While the reports are being updated, people outside the status team may also review the individual entries and propose fixes.
Los informes enviados son revisados e integrados en el subdirectorio apropiado de [.filename]#doc/website/content/en/status/# conforme van llegado. Mientras los informes están siendo actualizados, gente fuera del equipo de estado_status team_ también puede revisar las entradas individuales y proponer arreglos.
a year ago
Browse all translation changes