https://bugzilla.redhat.com/show_bug.cgi?id=827730

            Bug ID: 827730
        QA Contact: extras...@fedoraproject.org
          Severity: medium
           Version: rawhide
          Priority: medium
                CC: nott...@redhat.com,
                    package-review@lists.fedoraproject.org
          Assignee: nob...@fedoraproject.org
           Summary: Review Request: trac-code-comments-plugin - Trac
                    plugin for code comments and sending them to tickets
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Linux
          Reporter: codebl...@elrod.me
              Type: ---
     Documentation: ---
          Hardware: All
        Mount Type: ---
            Status: NEW
         Component: Package Review
           Product: Fedora

Spec URL:
http://codeblock.fedorapeople.org/packages/trac-code-comments-plugin/trac-code-comments-plugin.spec
SRPM URL:
http://codeblock.fedorapeople.org/packages/trac-code-comments-plugin/trac-code-comments-plugin-1.2.0-alpha2.20120601gitb260714.fc18.src.rpm
Description:
This plugin allows you to leave comments on top of files, change sets, and
attachments. Once you've added all of your comments, you can send them to
tickets. These include links to these comments and their description.
Fedora Account System Username: codeblock

Clean rpmlint, minus one warning because of how the source was obtained
(upstream is a tarball downloaded from github).

[ricky@t520 rpmbuild]$ rpmlint
SRPMS/trac-code-comments-plugin-1.2.0-alpha2.20120601gitb260714.fc18.src.rpm 
trac-code-comments-plugin.src: W: invalid-url Source0:
Automattic-trac-code-comments-plugin-v1.0.1-52-gb260714.tar.gz
1 packages and 0 specfiles checked; 0 errors, 1 warnings.

[ricky@t520 rpmbuild]$ rpmlint
RPMS/noarch/trac-code-comments-plugin-1.2.0-alpha2.20120601gitb260714.fc18.noarch.rpm
 
1 packages and 0 specfiles checked; 0 errors, 0 warnings.

Note that this does have several javascript libraries bundled with it with
varying licenses. I've included (in %doc) a LICENSING_BREAKDOWN file which
shows what is licensed differently from the plugin itself, as instructed here:
http://fedoraproject.org/wiki/Packaging:LicensingGuidelines#Multiple_Licensing_Scenarios

Happy to clarify any of the licensing related things if I need to (or
communicate with upstream to do so).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/package-review

Reply via email to