1. Since Minto Joseph and you are both packaging Hiran's fonts, you should get together and interact with Hiran collectively (see bug #457709).
2. It's not a good idea to keep the versioning in the TTF filename, some apps refer fonts by filename and will get cross with you if it changes every version
3. You should discuss with Minto if you want to adopt a common prefix for your font packages names (for example hiranv-rufscript-fonts and perizia-rufscript-fonts). We've more or less started to do it for big foundries (gfs, sil) and some individual font authors (thibault), it's probably better to generalise the convention to have consistent naming
(please subscribe to the fonts SIG list if you haven't done so yet to get informed of packaging convention evolutions)
4. you can drop the -f in the fc-cache invocation for releases ≥ Fedora 9
→ http://fedoraproject.org/wiki/Packaging/FontsSpecTemplate
5. Some people want all Fedora-added source files in a package to be prefixed with the package name. You don't follow this convention for your fontconfig file. Please take inspiration from the general packaging guidelines or Minto's package to fix it.
→ http://fedoraproject.org/wiki/Packaging/FontsSpecTemplate
→ bug #457709
6. 69 is a bit low, for a latin font like rufscript something between 62 and 64 would be fine
→ http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Simple_priority_lists
7. Please have upstream publish rufscript in a proper versioned archive with a detached license file you can add in %doc
8. Please reformat your xml files with xmllint --format before submission so they are nicely indented
9. I would have declared rufscript as a cursive font, not a sans-serif one
10. Please add a "Generic name" rule in addition to the "Registering a font in default families" rule
→ http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Generic_names
This rule is used by fontconfig to complete your font with glyphs from other fonts when it encounters a codepoint your font is missing
→ http://fedoraproject.org/wiki/Fontconfig_packaging_tips#Registering_a_font_in_default_families
This rule is used by fontconfig to identify what fonts to use when an application requests a "cursive" font.
11. When you've written fontconfig rules you're happy with it's always a good idea to send them upstream to be included in the font next releases (in the versionned archive you're supposed to request)
Despite the long todo list your spec is in good shape overall and it should not take much to get it in a state that can be approved.

[This is a simplified version of the message sent to every package maintainer that ships TTF/OTF/Type1 fonts in Fedora.]
Our font packaging guidelines have now changed. New font package submissions must now be adapted to the new templates available in the fontpackages-devel
package:
– http://fedoraproject.org/wiki/fontpackages
– http://fedoraproject.org/wiki/Simple_fonts_spec_template
– http://fedoraproject.org/wiki/Fonts_spec_template_for_multiple_fonts
It is preferred to create a font package or subpackage per font family, though
it is not currently a hard guidelines requirement.
http://fedoraproject.org/wiki/PackagingDrafts/Font_package_splitting_rules_(2008-12-21)
has been submitted for FPC and FESCO approval today.
The new templates should make the creation of font packages easy and safe.
The following packages have already been converted by their packager in fedora-devel and can serve as examples:
❄ abyssinica-fonts
❄ andika-fonts
❄ apanov-heuristica-fonts
❄ bitstream-vera-fonts
❄ charis-fonts
❄ dejavu-fonts
❄ ecolier-court-fonts
❄ edrip-fonts
❄ gfs-ambrosia-fonts
❄ gfs-artemisia-fonts
❄ gfs-baskerville-fonts
❄ gfs-bodoni-classic-fonts
❄ gfs-bodoni-fonts
❄ gfs-complutum-fonts
❄ gfs-didot-classic-fonts
❄ gfs-didot-fonts
❄ gfs-eustace-fonts
❄ gfs-fleischman-fonts
❄ gfs-garaldus-fonts
❄ gfs-gazis-fonts
❄ gfs-jackson-fonts
❄ gfs-neohellenic-fonts
❄ gfs-nicefore-fonts
❄ gfs-olga-fonts
❄ gfs-porson-fonts
❄ gfs-solomos-fonts
❄ gfs-theokritos-fonts
❄ nafees-web-naskh-fonts
❄ stix-fonts
❄ yanone-kaffeesatz-fonts
The new spec templates have been designed to be easy to update to from the previous guidelines, and to remove complexity from font packages. To help new package creation the fontpackages-devel package has been made available in Fedora 9 and 10.
If you have any remaining questions about the new guidelines please ask them
on:
fedora-fonts-list at redhat.com

Hiran is promising a new release and an new website in October.
Meanwhile on the packaging side since he created multiple fonts it would be nice to use a common prefix on the packages (similar to the apanov- prefix we use in packaging Andrey Panov's fonts) to mark they have the same origin (as required by guidelines)

Is Rahul with you taking over this package? (The passage of time suggests yes, but you never know.)
1. The spec name must be the same as the package name.
2. The license in the source file is GPLv3+ with exceptions
3. The SFD contains the line "Version: 0.1.0" and this is consistent with Hiran's other font under review at the moment, Perizia, but version control of fonts is notoriously bad so 0.100, pulled from the name table, is OK.
4. The fontconfig is very wrong, as you've said that the font "Sans" is the same as the font "Rufscript". Please use the basic fontconfig template and declare this as a cursive font.
5. From Nicolas's previous comment #2, points 6 and 7 still apply.
Other than those, this is a simple package, and almost ready for approval.