[Bug 530003] New: Review Request: pircbot - Java IRC bot framework

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Review Request: pircbot - Java IRC bot framework

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

           Summary: Review Request: pircbot - Java IRC bot framework
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: low
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: onekopaka at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: notting at redhat.com, fedora-package-review at redhat.com
   Estimated Hours: 0.0
    Classification: Fedora


Spec URL: http://theoks.net/~onekopaka/rpmsources/pircbot.spec
SRPM URL: http://theoks.net/~onekopaka/rpmsources/pircbot-1.4.6-1.fc11.src.rpm
Description:
After quite a bit of hassling around trying to make a specfile for PircBot, I
did it, and it's my very first package!

I'm terrible at making up descriptions, so here's the developer's description
of PircBot:

PircBot is a Java framework for writing IRC bots quickly and easily. Its
features include an event-driven architecture to handle common IRC events,
flood protection, DCC resuming support, ident support, and more. Its
comprehensive logfile format is suitable for use with pisg to generate channel
statistics.
(Taken from http://www.jibble.org/pircbot.php)

I packaged PircBot because my own IRC bot happens to use it, and I can't
include my own version of it!

rpmlint did scream on the binary about a lack of documentation and that the JAR
was not compressed. I don't know if that's a deal breaker (there's really poor
documentation on our Wiki about packaging IMO).

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.