fedora-docs-l10n/package-maintainers/master/pages/Package_Review_Process — English @ Fedora Weblate: Put your spec file and SRPM somewhere on the Internet …

Zen

Source string Source string

English

Put your spec file and SRPM somewhere on the Internet where it can be directly downloaded (just http(s), no registration pages or special download methods, please).  If you have no place to put your spec and SRPM, use https://copr.fedorainfracloud.org/[copr].

Needs editing

The string is read only.

Skip

	English	Actions
	Package Review Process
	In order for a new package to be added to Fedora, the package must first undertake a formal review. The process is governed by the FESCo approved xref:fesco::Package_review_policy.adoc[Package Review Policy].
	Review Process
	There are two roles in the review process, that of the contributor and that of the reviewer. This document presents both perspectives.
	Exemptions
	Certain packages are exempted from the review process as described in the xref:fesco::Package_review_policy.adoc#what[Applicability section of Package Review Policy]. If an exemption is warranted, the contributor can directly request a repository for the package. The request to create a repo should include the `--exception` flag instead of a bug number:
	fedpkg request-repo --exception <package-name>
	Contributor
	A Contributor is defined as someone who wants to submit (and maintain) a new package in Fedora. To become a contributor, you must follow the detailed instructions to xref:Joining_the_Package_Maintainers.adoc[Joining the Package Maintainers].
	As a Contributor, you should have already made a package which adheres to the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and does not contain any https://fedoraproject.org/wiki/Forbidden_items[Forbidden Items].
	When you're happy with your spec file, you should then submit that SRPM to a package review. Currently, this is done by following these steps:
	Put your spec file and SRPM somewhere on the Internet where it can be directly downloaded (just http(s), no registration pages or special download methods, please). If you have no place to put your spec and SRPM, use https://copr.fedorainfracloud.org/[copr].
	Fill out a https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[request for review in bugzilla]. Make absolutely certain to file this bug with an account tied to your FAS email address, otherwise your followup requests will be closed as invalid.
	If nobody comments on your review request, you might want to mail to a mailing list (for example, devel) or the https://discussion.fedoraproject.org/c/workflows/pkg-review-swap/91[Package Review Swaps category] on Fedora Discussion to ask for a "review swap". This is an offer to do a review of someone else's package in exchange for them reviewing your package. This is usually one-for-one, or can be some other private arrangement depending on the difficulty of the respective packages.
	If you are not member of the https://accounts.fedoraproject.org/group/packager/[packager] group, you need a sponsor. Add https://bugzilla.redhat.com/show_bug.cgi?id=FE-NEEDSPONSOR[FE-NEEDSPONSOR] to the bugs being blocked by your review request. For more information read xref:How_to_Get_Sponsored_into_the_Packager_Group.adoc[How to Get Sponsored into the Packager Group].
	If this is a "re-review" request needed to xref:Package_Retirement_Process.adoc#claiming[claim ownership] of a retired package, add `Unretirement` to the _Whiteboard_ field.
	Wait for someone to review your package! At this point in the process, the `fedora-review` flag is blank, meaning that no reviewer is assigned.
	There may be comments from people that are not formally reviewing the package, they may add `NotReady` to the _Whiteboard_ field, indication that the review request is not yet ready, because of some issues they report. After you have addressed them, please post the URLs to the updated SPEC and SRPM file and clear the Whiteboard. It is expected that you will respond to commentary, including updating your submission to address it; if you do not, your ticket will be closed.
	A reviewer takes on the task of reviewing your package. They will set the `fedora-review` flag to `?`.
	The reviewer will review your package. You should fix any blockers that the reviewer identifies. Once the reviewer is happy with the package, the `fedora-review` flag will be set to `+`, indicating that the package has passed review.
	If you have not yet been sponsored, request sponsorship by https://pagure.io/packager-sponsors/issues[raising an issue at packager-sponsors].
	When your package passes the review you should use `fedpkg` to request a Git repository for it. Before you can request a Git repository for the package, you will need a https://pagure.io/settings/token/new[pagure.io api token] with _Create a new ticket_ ACL added into `~/.config/rpkg/fedpkg.conf`:
	[fedpkg.pagure] token = <generated-code>
	Request a Git repository for the package. For example, if the package name is `my-package` and the bugzilla review ticket is 12345, :
	fedpkg request-repo my-package 12345
	Check that your review bug is valid. It must have the `fedora-review` set to `+`, and it must be assigned to your reviewer. Otherwise your repository request will be closed as invalid.
	If you want to add your package to more Fedora releases and not just Rawhide, see xref:Package_Maintenance_Guide.adoc#requesting_branches[Requesting branches].

Loading…

None

String updated in the repository

English

English 259 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English	English
No related strings found in the glossary.

16731542 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\-_/]*)?", read-only

Source string location

./pages/Package_Review_Process.adoc:50

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

pot/master/pages/Package_Review_Process.pot, string 12

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.