From Fedora Project Wiki

MUST requirements

[      ] MUST: rpmlint must be run on the source rpm and all binary rpms the
         build produces. The output should be posted in the review.(refer to
[      ] MUST: The package must be named according to the
[      ] MUST: The spec file name must match the base package
         <code>%{name}</code>, in the format <code>%{name}.spec</code> unless your
         package has an exemption. (refer to
[      ] MUST: The package must meet the
[      ] MUST: The package must be licensed with a Fedora approved license and
         meet the
[      ] MUST: The License field in the package spec file must match the actual
         license. (refer to
[      ] MUST: If (and only if) the source package includes the text of the
         license(s) in its own file, then that file, containing the text of the
         license(s) for the package must be included in <code>%doc</code>.(refer to Text)
[      ] MUST: The spec file must be written in American English. (refer to
[      ] MUST: The spec file for the package '''MUST''' be legible. (refer to
[      ] MUST: The sources used to build the package must match the upstream
         source, as provided in the spec URL. Reviewers should use md5sum for this task.
         If no upstream URL can be specified for this package, please see the for how to deal with
[      ] MUST: The package '''MUST''' successfully compile and build into
         binary rpms on at least one primary architecture. (refer to
[      ] MUST: If the package does not successfully compile, build or work on
         an architecture, then those architectures should be listed in the spec in
         <code>ExcludeArch</code>. Each architecture listed in <code>ExcludeArch</code>
         '''MUST''' have a bug filed in bugzilla, describing the reason that the package
         does not compile/build/work on that architecture. The bug number '''MUST''' be
         placed in a comment, next to the corresponding <code>ExcludeArch</code> line.
         (refer to
[      ] MUST: All build dependencies must be listed in
         <code>BuildRequires</code>, except for any that are listed in the section of the
         Packaging Guidelines ; inclusion of those as <code>BuildRequires</code> is
         optional. Apply common sense.
[      ] MUST: The spec file MUST handle locales properly. This is done by
         using the <code>%find_lang</code> macro. Using
         <code>%{_datadir}/locale/*</code> is strictly forbidden.(refer to
[      ] MUST: Every binary RPM package (or subpackage) which stores shared
         library files (not just symlinks) in any of the dynamic linker's default paths,
         must call ldconfig in <code>%post</code> and <code>%postun</code>. (refer to
[      ] MUST: Packages must NOT bundle copies of system libraries.(refer to
[      ] MUST: If the package is designed to be relocatable, the packager must
         state this fact in the request for review, along with the rationalization for
         relocation of that specific package. Without this, use of Prefix: /usr is
         considered a blocker. (refer to
[      ] MUST: A package must own all directories that it creates. If it does
         not create a directory that it uses, then it should require a package which
         does create that directory.  (refer to
[      ] MUST: A Fedora package must not list a file more than once in the spec
         file's %files listings. (Notable exception: license texts in specific
         situations)(refer to
[      ] MUST: Permissions on files must be set properly. Executables should be
         set with executable permissions, for example. (refer to
[      ] MUST: Each package must consistently use macros. (refer to
[      ] MUST: The package must contain code, or permissable content. (refer to
[      ] MUST: Large documentation files must go in a -doc subpackage. (The
         definition of large is left up to the packager's best judgement, but is not
         restricted to size. Large can refer to either size or quantity). (refer to
[      ] MUST: If a package includes something as %doc, it must not affect the
         runtime of the application. To summarize: If it is in %doc, the program must
         run properly if it is not present. (refer to
[      ] MUST: Header files must be in a -devel package. (refer to
[      ] MUST: Static libraries must be in a -static package. (refer to
[      ] MUST: If a package contains library files with a suffix (e.g., then library files that end in .so (without suffix) must go in
         a -devel package. (refer to
[      ] MUST: In the vast majority of cases, devel packages must require the
         base package using a fully versioned dependency: <code>Requires:
         %{name}%{?_isa} = %{version}-%{release} </code> (refer to
[      ] MUST: Packages must NOT contain any .la libtool archives, these must
         be removed in the spec if they are built.(refer to
[      ] MUST: Packages containing GUI applications must include a
         %{name}.desktop file, and that file must be properly installed with
         desktop-file-install in the %install section. If you feel that your packaged
         GUI application does not need a .desktop file, you must put a comment in the
         spec file with your explanation. (refer to
[      ] MUST: Packages must not own files or directories already owned by
         other packages. The rule of thumb here is that the first package to be
         installed should own the files or directories that other packages may rely
         upon. This means, for example, that no package in Fedora should ever share
         ownership with any of the files or directories owned by the
         <code>filesystem</code> or <code>man</code> package. If you feel that you have
         a good reason to own a file or directory that another package owns, then please
         present that at package review time. (refer to
[      ] MUST: All filenames in rpm packages must be valid UTF-8. (refer to

SHOULD requirements

[      ] SHOULD: If the source package does not include license text(s) as a
         separate file from upstream, the packager SHOULD query upstream to include it.
         (refer to
[      ] SHOULD: The description and summary sections in the package spec file
         should contain translations for supported Non-English languages, if available.
         (refer to
[      ] SHOULD: The reviewer should test that the package builds in mock.
         (refer to
[      ] SHOULD: The package should compile and build into binary rpms on all
         supported architectures. (refer to
[      ] SHOULD: The reviewer should test that the package functions as
         described. A package should not segfault instead of running, for example.
[      ] SHOULD: If scriptlets are used, those scriptlets must be sane. This is
         vague, and left up to the reviewers judgement to determine sanity. (refer to
[      ] SHOULD: Usually, subpackages other than devel should require the base
         package using a fully versioned dependency. (refer to
[      ] SHOULD: The placement of pkgconfig(.pc) files depends on their
         usecase, and this is usually for development purposes, so should be placed in a
         -devel pkg.  A reasonable exception is that the main pkg itself is a devel tool
         not installed in a user runtime, e.g. gcc or gdb. (refer to
[      ] SHOULD: If the package has file dependencies outside of /etc, /bin,
         /sbin, /usr/bin, or /usr/sbin consider requiring the package which provides the
         file instead of the file itself. (refer to
[      ] SHOULD: your package should contain man pages for binaries/scripts. If
         it doesn't, work with upstream to add them where they make sense.(refer to