Zen

Source string Source string

570/10000 · 570

The string is read only.

English Actions
If some useful software is not included in Fedora already, you can submit it as a new package. The package you are submitting can be of any Free and Open Source project.
Before creating your package, make sure that the software is not already in the Fedora repository:
Check if the package already exists by searching in https://packages.fedoraproject.org/[Fedora Packages].
Search in the https://fedoraproject.org/PackageReviewStatus/[Review Tracker] for packages under review.
Check the https://packager-dashboard.fedoraproject.org/user/orphan[orphaned or retired packages that need new maintainers].
Be aware of https://fedoraproject.org/wiki/Forbidden_items[forbidden items].
Make a Package
If you don't know how to create an RPM package, see the xref:Packaging_Tutorial.adoc[Packaging Tutorial].
Make sure that your package meets the xref:packaging-guidelines::index.adoc[Packaging Guidelines] and xref:packaging-guidelines::Naming.adoc[Package Naming Guidelines].
Be aware of the xref:packaging-guidelines::ReviewGuidelines.adoc[Package Review Guidelines] (they will be used during the package review).
Make sure your package builds. This is surprisingly important because a significant number of submissions don't.
Upload Your Package
Upload your SRPM and SPEC files onto the Internet somewhere so that others can retrieve them. This can be anywhere accessible by a URL, but it is important that the files be directly accessible, not hidden behind some service that makes people wait to download things or redirects through advertising pages.
Using https://copr.fedorainfracloud.org[Copr] is recommended. It allows creating repositories using the src.rpm or spec file, which can be then shared with the reviewers. It also can create automatic builds from these files and distribute the results.
First you need to log to https://copr.fedorainfracloud.org[Copr], you can use your Fedora account.
Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build the project. During the "New Build" step you need to upload your source, you can choose the one which works for you the best, but if you don't have the source uploaded somewhere else, you can select the _Upload_ option and then in the provide the step section, click on _Browse..._ button to select a file. Now in the next section you need to specify the Chroots and other built options, select at least one `fedora-rawhide` chroot and adjust other settings as necessary.
After the build is completed you can use the following links for the review process:
Link to Spec file: go to your copr packages, click the name of your package and then under general information look for your dist-git repositary. Find the *Spec* file in this repository tree and copy it's link, but replace the *tree* part of the URL with the string *plain*, then use it for the review submission.
Link to SRPM file: in your copr builds, click on the *id* of your last successful build and under general information look for link named directory. Here look in to the */srpm-build/your_build_id/* folder and copy the *src.rpm* file URL for your review submission.
Create Your Review Request
Fill out https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review[Bugzilla Fedora review form].
Before submitting your request, be sure there’s not a previous request for the same package. There is a convenient search box on the https://fedoraproject.org/PackageReviewStatus/[package review status page].
Make sure that you put the *name of the package* (excluding version and release numbers) in the `Review Summary` field, along with a very *brief summary* of what the package is.
Put a *description* of your package (usually, this can be the same thing as what you put in the spec `%description`) in the `Review Description` field. Include the *URLs* to your *SRPM* and *SPEC* files.
Explain in the ticket that this is your first package and you need a sponsor. Also, include any information that may help prospective sponsors. If you've been active in other review work, include links. If you're the upstream maintainer, be sure to say so.
For bonus points, include a link to a successful koji build so that everyone knows you did all of your homework.
The review process is described in detail on the xref:Package_Review_Process.adoc[Package Review Process] page.
Inform 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.
Watch for Feedback
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.

Loading…

User avatar None

String added in the repository
Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build the project. During the "New Build" step you need to upload your source, you can choose the one which works for you the best, but if you don't have the source uploaded somewhere else, you can select the _Upload_ option and then in the provide the step section, click on _Browse..._ button to select a file. Now in the next section you need to specify the Chroots and other built options, select at least one `fedora-rawhide` chroot and adjust other settings as necessary.
Then follow this https://docs.pagure.org/copr.copr/screenshots_tutorial.html[tutorial], to build the project. During the "New Build" step you need to upload your source, you can choose the one which works for you the best, but if you don't have the source uploaded somewhere else, you can select the _Upload_ option and then in the provide the step section, click on _Browse..._ button to select a file. Now in the next section you need to specify the Chroots and other built options, select at least one `fedora-rawhide` chroot and adjust other settings as necessary.
2 weeks ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

18651724 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/New_Package_Process_for_New_Contributors.adoc:81
String age
2 weeks ago
Last updated
2 weeks ago
Source string age
2 weeks ago
Translation file
pot/master/pages/New_Package_Process_for_New_Contributors.pot, string 21