guix/documentation-manual — Spanish @ Fedora Weblate: Important

Zen

Translation

English type: quotation

Spanish

Needs editing

Skip

	English	Spanish	Actions
	A contributor (who may or may not have commit access) wishing to block a proposal bears a special responsibility for finding alternatives, proposing ideas/code or explain the rationale for the status quo to resolve the deadlock. To learn what consensus decision making means and understand its finer details, you are encouraged to read @url{https://www.seedsforchange.org.uk/consensus}.
	commit access, for developers	acceso al repositorio, para desarrolladoras
	Everyone can contribute to Guix without having commit access (@pxref{Submitting Patches}). However, for frequent contributors, having write access to the repository can be convenient. As a rule of thumb, a contributor should have accumulated fifty (50) reviewed commits to be considered as a committer and have sustained their activity in the project for at least 6 months. This ensures enough interactions with the contributor, which is essential for mentoring and assessing whether they are ready to become a committer. Commit access should not be thought of as a ``badge of honor'' but rather as a responsibility a contributor is willing to take to help the project.
	Committers are in a position where they enact technical decisions. Such decisions must be made by @emph{actively building consensus} among interested parties and stakeholders. @xref{Making Decisions}, for more on that.
	The following sections explain how to get commit access, how to be ready to push commits, and the policies and community expectations for commits pushed upstream.
	Applying for Commit Access	Acceso al repositorio
	When you deem it necessary, consider applying for commit access by following these steps:	El acceso de escritura al repositorio es conveniente para personas que contribuyen frecuentemente. Cuando lo crea necesario, considere solicitar acceso al repositorio siguiendo estos pasos:
	Find three committers who would vouch for you. You can view the list of committers at @url{https://savannah.gnu.org/project/memberlist.php?group=guix}. Each of them should email a statement to @email{guix-maintainers@@gnu.org} (a private alias for the collective of maintainers), signed with their OpenPGP key.	Encuentre tres personas que contribuyan al proyecto que puedan respaldarle. Puede ver la lista de personas que contribuyen en @url{https://savannah.gnu.org/project/memberlist.php?group=guix}. Cada una de ellas deberá enviar un correo confirmando el respaldo a @email{guix-maintainers@@gnu.org} (un alias privado para el colectivo de personas que mantienen el proyecto), firmado con su clave OpenPGP.
	Committers are expected to have had some interactions with you as a contributor and to be able to judge whether you are sufficiently familiar with the project's practices. It is @emph{not} a judgment on the value of your work, so a refusal should rather be interpreted as ``let's try again later''.	Se espera que dichas personas hayan tenido algunas interacciones con usted en sus contribuciones y sean capaces de juzgar si es suficientemente familiar con las prácticas del proyecto. @emph{No} es un juicio sobre el valor de su trabajo, por lo que un rechazo debe ser interpretado más bien como un ``habrá que probar de nuevo más adelante''.
	Send @email{guix-maintainers@@gnu.org} a message stating your intent, listing the three committers who support your application, signed with the OpenPGP key you will use to sign commits, and giving its fingerprint (see below). See @uref{https://emailselfdefense.fsf.org/en/}, for an introduction to public-key cryptography with GnuPG.	Envíe un correo a @email{guix-maintainers@@gnu.org} expresando su intención, enumerando a las tres contribuidoras que respaldan su petición, firmado con su clave OpenPGP que usará para firmar las revisiones, y proporcionando su huella dactilar (véase a continuación). Véase @uref{https://emailselfdefense.fsf.org/es/} para una introducción a la criptografía de clave pública con GnuPG.
	Set up GnuPG such that it never uses the SHA1 hash algorithm for digital signatures, which is known to be unsafe since 2019, for instance by adding the following line to @file{~/.gnupg/gpg.conf} (@pxref{GPG Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}):	Configure GnuPG de modo que no use el algorítmo de hash SHA1 nunca para las firmas digitales, el cual se sabe que no es seguro desde 2019, añadiendo, por ejemplo, la siguiente línea en @file{~/.gnupg/gpg.conf} (@pxref{GPG Esoteric Options,,, gnupg, The GNU Privacy Guard Manual}):
	digest-algo sha512	digest-algo sha512
	Maintainers ultimately decide whether to grant you commit access, usually following your referrals' recommendation.	Las personas que mantienen el proyecto decidirán en última instancia si conceder o no el acceso de escritura, habitualmente siguiendo las recomendaciones de las personas de referencia proporcionadas.
	OpenPGP, signed commits	OpenPGP, revisiones firmadas
	If and once you've been given access, please send a message to @email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key you will use to sign commits (do that before pushing your first commit). That way, everyone can notice and ensure you control that OpenPGP key.	Una vez haya conseguido acceso, en caso de hacerlo, por favor envíe un mensaje a @email{guix-devel@@gnu.org} para notificarlo, de nuevo firmado con la clave OpenPGP que vaya a usar para firmar las revisiones (hágalo antes de subir su primera revisión). De esta manera todo el mundo puede enterarse y asegurarse de que controla su clave OpenPGP.
	Important	Importante
	Before you can push for the first time, maintainers must:	Antes de que suba alguna revisión por primera vez, quienes mantienen Guix deben:
	add your OpenPGP key to the @code{keyring} branch;	añadir su clave OpenPGP a la rama @code{keyring};
	add your OpenPGP fingerprint to the @file{.guix-authorizations} file of the branch(es) you will commit to.	añadir su firma OpenPGP al archivo @file{.guix-authorizations} de la(s) rama(s) a las que vaya a subir código.
	Make sure to read the rest of this section and... profit!	Asegúrese de leer el resto de esta sección y... ¡a disfrutar!
	Maintainers are happy to give commit access to people who have been contributing for some time and have a track record---don't be shy and don't underestimate your work!	Quienes mantienen el proyecto están encantadas de proporcionar acceso al repositorio a personas que han contribuido durante algún tiempo y tienen buen registro---¡no sea tímida y no subestime su trabajo!
	However, note that the project is working towards a more automated patch review and merging system, which, as a consequence, may lead us to have fewer people with commit access to the main repository. Stay tuned!	No obstante, tenga en cuenta que el proyecto está trabajando hacia la automatización de la revisión de parches y el sistema de mezclas, lo que, como consecuencia, puede hacer necesario que menos gente tenga acceso de escritura al repositorio principal. ¡Seguiremos informando!
	All commits that are pushed to the central repository on Savannah must be signed with an OpenPGP key, and the public key should be uploaded to your user account on Savannah and to public key servers, such as @code{keys.openpgp.org}. To configure Git to automatically sign commits, run:	Todas las revisiones que se suban al repositorio central de Savannah deben estar firmadas por una clave OpenPGP, y la clave pública debe subirse a su cuenta de usuaria en Savannah y a servidores públicos de claves, como @code{keys.openpgp.org}. Para configurar que Git firme automáticamente las revisiones ejecute:
	git config commit.gpgsign true
	# Substitute the fingerprint of your public PGP key. git config user.signingkey CABBA6EA1DC0FF33	git config commit.gpgsign true git config user.signingkey CABBA6EA1DC0FF33
	To check that commits are signed with correct key, use:
	@xref{Building from Git} for running the first authentication of a Guix checkout.
	To avoid accidentally pushing unsigned or signed with the wrong key commits to Savannah, make sure to configure Git according to @xref{Configuring Git}.	Puede evitar la subida accidental de revisiones sin firma a Savannah mediante el uso del hook pre-push de Git que se encuentra en @file{etc/git/pre-push}:
	Commit Policy	Acceso al repositorio
	If you get commit access, please make sure to follow the policy below (discussions of the policy can take place on @email{guix-devel@@gnu.org}).	Si obtiene acceso, por favor asegúrese de seguir la política descrita a continuación (el debate sobre dicha política puede llevarse a cabo en @email{guix-devel@@gnu.org}).
	Ensure you're aware of how the changes should be handled (@pxref{Managing Patches and Branches}) prior to being pushed to the repository, especially for the @code{master} branch.

Loading…

No matching activity found.

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Spanish
No related strings found in the glossary.

6471287 String information

Source string description

type: quotation

Flags

ignore-same, no-wrap

Source string location

guix-git/doc/contributing.texi:2827 • guix-git/doc/guix.texi:722 • guix-git/doc/guix.texi:754 • guix-git/doc/guix.texi:22676 • guix-git/doc/guix.texi:36626 • guix-git/doc/guix.texi:37661

String age

4 years ago

Last updated

a week ago

Source string age

4 years ago

Translation file

po/doc/guix-manual.es.po, string 755

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.