Zen

Translation

This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like GitHub or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click.
815/7420 · 742

Sign in to save the translation.

English Spanish Actions
<primary><command>hg</command></primary>
<primary><command>hg</command></primary>
<primary><command>cvs</command></primary>
<primary><command>cvs</command></primary>
<primary><command>fossil</command></primary>
<primary><command>fossil</command></primary>
It is beyond the scope of this book to provide a detailed explanation about Git. For that, you can refer to the <citetitle>Pro Git</citetitle> book. <ulink type="block" url="https://git-scm.com/book/" />
Está fuera del alcance de este libro proporcionar una explicación detallada sobre Git. Para ello, puedes consultar el libro <citetitle>Pro Git</citetitle>. <ulink type="block" url="https://git-scm.com/book/" />
While the output of <command>git diff</command> is a file that can be shared with other developers, there are usually better ways to submit changes. If the developers prefer to get patches by email, they usually want patches generated with <command>git format-patch</command> so that they can be directly integrated in the repository with <command>git am</command>. This preserves commits meta-information and makes it possible to share multiple commits at once.
Si bien la salida de <command>git diff</command> es un archivo que puede compartirse con otros desarrolladores, normalmente hay mejores formas de enviar cambios. Si los desarrolladores prefieren recibir parches por correo electrónico, normalmente quieren parches generados con <command>git format-patch</command> para que puedan ser integrados directamente en el repositorio con <command>git am</command>. Esto preserva la información de metadatos de los «commits» y permite compartir varios «commits» de golpe.
This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like GitHub or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click.
Este proceso de trabajo por correo electrónico es todavía popular, pero tiende a ser reemplazado por el uso de <emphasis>merge requests</emphasis> (o <emphasis>pull requests</emphasis>) cuando el software se aloja en una plataforma como GitHub o GitLab —y Debian usa GitLab en su servidor <literal>salsa.debian.org</literal>—. En estos sistemas, una vez creada una cuenta, bifurcas (<emphasis>fork</emphasis>) el repositorio, creando efectivamente una copia del repositorio en tu cuenta, y después puedes clonar ese repositorio y subir (<emphasis>push</emphasis>) tus propios cambios a este. Desde ahí, la interfaz web te sugerirá que envíes un <foreignphrase>merge request</foreignphrase>, notificando a los desarrolladores de tus cambios, facilitándoles la revisión y aceptación de tus cambios con un simple clic.
Other ways of contributing
Otras formas de colaborar
<primary>mailing lists</primary><secondary><email>debian-user@lists.debian.org</email></secondary>
<primary>listas de correos</primary><secondary><email>debian-user@lists.debian.org</email></secondary>
<primary>Debian Project</primary><secondary>users</secondary>
<primary>Proyecto Debian</primary><secondary>usuarios</secondary>
All of these contribution mechanisms are made more efficient by users' behavior. Far from being a collection of isolated persons, users are a true community within which numerous exchanges take place. We especially note the impressive activity on the user discussion mailing list, <email>debian-user@lists.debian.org</email> (<xref linkend="solving-problems" /> discusses this in greater detail). <ulink type="block" url="https://lists.debian.org/users.html" />
Todos estos mecanismos de colaboración son más eficientes con el comportamiento de los usuarios. Lejos de ser una colección de personas aisladas, los usuarios son una verdadera comunidad en la que ocurren numerosos intercambios. Notamos especialmente la impresionante actividad en la lista de correo para discusión de usuarios <email>debian-user@lists.debian.org</email> (el <xref linkend="solving-problems" /> discute esto en más detalle). <ulink type="block" url="https://lists.debian.org/users.html" />
Not only do users help themselves (and others) on technical issues that directly affect them, but they also discuss the best ways to contribute to the Debian project and help it move forward — discussions that frequently result in suggestions for improvements.
No sólo los usuarios se ayudan entre ellos (y a otros) con problemas técnicos que los afectan directamente sino que también discuten las mejores formas para contribuir con el proyecto Debian y ayudar moverlo adelante — discusiones que frecuentemente resultan en sugerencias para mejoras.

Loading…

User avatar jorgesumle

Translation changed

  1. Debian Handbook
  2. 01_the-debian-project
  3. Spanish
This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like GitHub or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click.
Este proceso de trabajo por correo electrónico es todavía popular, pero tiende a ser reemplazado por el uso de <emphasis>merge requests</emphasis> (o <emphasis>pull requests</emphasis>) cuando el software se aloja en una plataforma como GitHub o GitLab —y Debian usa GitLab en su servidor <literal>salsa.debian.org</literal>—. En estos sistemas, una vez creada una cuenta, bifurcas (<emphasis>fork</emphasis>) el repositorio, creando efectivamente una copia del repositorio en tu cuenta, y después puedes clonar ese repositorio y subir (<emphasis>push</emphasis>) tus propios cambios a este. Desde ahí, la interfaz web te sugerirá que envíes un <emforeignphrasise>merge request</emforeignphrasise>, notificando a los desarrolladores de tus cambios, facilitándoles la revisión y aceptación de tus cambios con un simple clic.
3 years ago
User avatar jorgesumle

Translation changed

  1. Debian Handbook
  2. 01_the-debian-project
  3. Spanish
This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like GitHub or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click.
Este proceso de trabajo por correo electrónico es todavía popular, pero tiende a ser reemplazado por el uso de <emphasis>merge requests</emphasis> (o <emphasis>pull requests</emphasis>) cuando el software se aloja en una plataforma como GitHub o GitLab —y Debian usa GitLab en su servidor <literal>salsa.debian.org</literal>—. En estos sistemas, una vez creada una cuenta, bifurcas (<emphasis>fork</emphasis>) el repositorio, creando efectivamente una copia del repositorio en tu cuenta, y después puedes clonar ese repositorio y subir (<emphasis>push</emphasis>) tus propios cambios a este. Desde ahí, la interfaz web te sugerirá que envíes un <emphasis>merge request</emphasis>, notificando a los desarrolladores de tus cambios, facilitándoles la revisión y aceptación de tus cambios con un simple clic.
3 years ago
User avatar None

Source string changed

  1. Debian Handbook
  2. 01_the-debian-project
  3. Spanish
This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like GithHub or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click.
3 years ago
Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English Spanish
click pulsar Debian Handbook
email email Debian Handbook
fork bifurcación Debian Handbook
request pedido Debian Handbook
software software Debian Handbook
workflow proceso de trabajo Debian Handbook

String information

Flags
xml-text
String age
3 years ago
Last updated
11 months ago
Source string age
3 years ago
Translation file
es-ES/01_the-debian-project.po, string 365