fedora-docs-l10n/package-maintainers/master/pages/New_Package_Process_for_New_Contributors — Spanish @ Fedora Weblate: `fedpkg request-repo` only creates a branch for Rawhide. To request …

Translation

Source change

English type: Plain text

Spanish

Needs editing

Skip

	English	Spanish	Actions
	For bonus points, include a link to a successful koji build so that everyone knows you did all of your homework.	Para obtener puntos de bonificación, incluya un enlace a una construcción koji exitosa para que todos sepan que hizo toda su tareas.
	The review process is described in detail on the xref:Package_Review_Process.adoc[Package Review Process] page.	El proceso de revisión se describe en detalle en la página xref:Package_Review_Process.adoc[Proceso de Revisión del Paquete].
	Inform Upstream	Informar al Upstream
	The Fedora Project prefers xref:Staying_Close_to_Upstream_Projects.adoc[Staying Close to Upstream Projects]. Inform the developers that you are packaging the software. You can do that by sending them an email introducing yourself and pointing out the review request. This sets up the stage for future conversations. They will usually advertise the fact that their software is now part of Fedora or might want to inform you of important bugs in the existing release, future roadmaps etc.	El Proyecto Fedora prefiere xref:Staying_Close_to_Upstream_Projects.adoc[Mantenerse Cerca de los Proyectos Upstream]. Informe a los desarrolladores que está empaquetando el software. Puede hacer esto enviándoles un correo electrónico presentándose y señalándoles la solicitud de revisión. Esto prepara el escenario para futuras conversaciones. Por lo general anunciarán el hecho de que su software es ahora parte de Fedora o querrán informarle sobre errores importantes en la versión existente, hoja de ruta futura, etc.
	Watch for Feedback	Esté Atento a los Comentarios
	Watch the Bugzilla report for your first package. You should get notifications of changes by email. Fix any blockers that the reviewer(s) point out.	Mire el informe Bugzilla para su primer paquete. Debería recibir notificaciones de cambios por correo electrónico. Corrija los obstáculos que los revisores señalen.
	Get Sponsored	Obtener Patrocinio
	When the package is APPROVED by the reviewer, you must separately obtain member sponsorship in order to check in and build your package. Sponsorship is not automatic and may require that you further participate in other ways in order to demonstrate your understanding of the packaging guidelines. The key to becoming sponsored is to convince an existing sponsor-level member that you understand and follow the project's guidelines and processes.	Cuando el paquete es APROBADO por el revisor, debe obtener patrocinio de miembros por separado para poder registrarse y crear su paquete. El patrocinio no es automático y puede requerir que usted participe de otras maneras para demostrar su comprensión de las directrices de empaquetamiento. La claves para llegar a ser patrocinado es que convenza a un miembro con nivel de patrocinador de que entiende y sigue las directrices y procesos del proyecto.
	See xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get Sponsored into the Packager Group] for more information on the process of becoming sponsored.	Vea xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[Como Obtener Patrocinio en el Grupo Empaquetador] para más información sobre el proceso para llegar a ser patrocinado.
	Your sponsor can add you to the packager group. You should receive an email confirmation of your sponsorship.	Su patrocinador le puede añadir al grupo empaquetador. Debería recibir un correo electrónico de confirmación de su patrocinio.
	Add Package to Source Code Management (SCM) system and Set Owner	Añadir un Paquete al sistema de Administración de Código Fuente (SCM) y Establecer el Propietario
	Before proceeding, please sync your account by login on https://src.fedoraproject.org/[Fedora Package Sources] using your FAS credentials.	Antes de proceder, sincronice su cuenta accediendo a las https://src.fedoraproject.org/[Fuentes de Paquetes Fedora] usando sus credenciales FAS.
	If you are becoming a maintainer for a new package, instead of being a co-maintainer, use https://pagure.io/fedpkg[fedpkg] to request a new git repository for your package. The sub-command is `fedpkg request-repo` which includes help text for setting up the Pagure API token the command requires. When creating your API-key choose toggle-all for the ACLs. You must specify the repository name and review bug number. For example:	Si se convierte en mantenedor de un nuevo paquete, en lugar de comantenedor, use https://pagure.io/fedpkg[fedpkg] para solicitar un nuevo repositorio git para su paquete. El subcomando es `fedpkg request-repo` que incluye texto de ayuda para configurar el token API de Pagure que el comando requiere. Al crear su clave API elija alternar todo para las ACLs. Debe especificar el nombre del repositorio y revisar el número de error. Por ejemplo:
	fedpkg request-repo python-prometheus_client 1590452	fedpkg request-repo python-prometheus_client 1590452
	The request will be reviewed and processed automatically. After processing, you will have access to commit and build the package. In case the automation does not work, you can report the problem to https://pagure.io/fedora-infra/toddlers/issues[Toddlers issue tracker].	La solicitud será revisada y procesada automáticamente. Después del procesamiento, tendrá acceso para confirmar y compilar el paquete. En el caso de que la automatización no funcione, puede reportar el problema al https://pagure.io/fedora-infra/toddlers/issues[rastreador de cuestiones Toddlers].
	`fedpkg request-repo` only creates a branch for Rawhide. To request branches for other Fedora releases, see xref:Package_Maintenance_Guide.adoc#requesting_branches[Requesting branches].	`fedpkg request-repo` solo crea una rama para Rawhide. Para solicitar ramas para otras versiones de Fedora, use `fedpkg request-branch`:
	[[check_out_the_module]] Check out the distgit repository	[[check_out_the_module]] Consultar el repositorio de distgit
	You _could_ check out your distgit repository now, but before doing that, consider doing `mkdir ~/fedora-scm ; cd ~/fedora-scm` — that way, all your files are inside a single directory. Also, run `ssh-add`, so that you won't have to keep typing in your key password.	Usted _podría_ consultar su repositorio distgit ahora, pero antes de hacer esto, considere hacer `mkdir ~/fedora-scm ; cd ~/fedora-scm` — de esta forma, todos sus archivos estarán dentro de un único directorio. También, ejecute `ssh-add`, para que no tenga que seguir escribiendo su clave contraseña.
	Now you are ready to checkout your distgit repository from the SCM:	Ahora está preparado para consultar su repositorio distgit desde el SCM:
	fedpkg clone your-package	fedpkg clone your-package
	Test Your Package	Probar Su Paquete
	Refer to https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Using Mock to test package builds] and xref:Using_the_Koji_Build_System.adoc#scratch_builds[Koji Scratch Builds] for more information on testing your package. Mock uses your local system while Koji command line tool uses the Fedora build system server.	Vea https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds[Usar Mock para probar las compilaciones de paquete] y xref:Using_the_Koji_Build_System.adoc#scratch_builds[Koji Scratch Builds] para más información sobre las pruebas de su paquete. Mock usa su sistema local, mientras que la herramienta en línea de comando Koji usar el servidor del sistema de compilación Fedora.
	Import, commit, and build your package	Importar, confirmar y crear su paquete
	Now that you've checked out your (empty) distgit repository with `fedpkg`, cd into the repository's main branch:	Ahora que ha comprobado su repositorio distgit (vacío) con `fedpkg`, acceda a la rama principal del repositorio:
	cd <packagename>	cd <packagename>
	Run fedpkg to import the contents of the SRPM into the SCM:	Ejecute fedpkg para importar los contenido del SRPM en el SCM:
	fedpkg import PATH_TO_SRPM	fedpkg import PATH_TO_SRPM
	# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD git commit -m "Initial import (fedora#XXXXXX)." git push fedpkg build	# Review Changes, press 'q' to stop; Revert with: git reset --hard HEAD git commit -m "Initial import (fedora#XXXXXX)." git push fedpkg build
	Obviously, replace `PATH_TO_SRPM` with the full path (not URL) to your approved SRPM, and `XXXXXX` with the package review bug number.	Obviamente, reemplazar `PATH_TO_SRPM` con la ruta completa (no URL) para su SRPM aprobado y `XXXXXX` con el número de error del paquete revisado.
	If your package is using _autochangelog_, writing the bug number as specified will make the Fedora update system automatically close the bug when your package is submitted to Rawhide stable repository.	Si su paquete está usando _autochangelog_, escribiendo el número de error como se ha especificado hará que el sistema de actualización de Fedora cierre automáticamente el error cuando su paquete se envíe al repositorio Rawhide estable.
	This imports into, commits, and builds only the main (xref:releases::rawhide.adoc[Rawhide]) branch.	Esto importa, confirma y construye solo la rama https://fedoraproject.org/wiki/Releases/Rawhide[(Rawhide)] principal.

Loading…

None

String added in the repository

English

Spanish 136 characters edited Current translation Needs editing

3 months ago

None

Source string changed

English 62 characters edited Needs editing

3 months ago

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Placeholders

The following format strings are missing: xref:Package_Maintenance_Guide.adoc#requesting_branches
The following format strings are extra: `fedpkg request-branch`

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string description

type: Plain text

Flags

placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"

Source string location

pages/New_Package_Process_for_New_Contributors.adoc:170

String age

3 months ago

Last updated

3 months ago

Source string age

3 months ago

Translation file

po/es/master/pages/New_Package_Process_for_New_Contributors.po, string 41

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.