Open Patches

[deckrider]

I would certainly like to see khc's patch get into the next release:

http://developer.pidgin.im/ticket/6604

On Thu, Nov 13, 2008 at 01:08:00AM -0500, John Bailey wrote:
> Hey, guys:
> 
> I've been slowly trying to make my way through the open tickets in Trac, and
> I've found something that surprised me--we have *93* open patches.
> 
> These 93 patches break down like so:
>   * Status:
>     * Pending - 1
>     * New - 92
>   * Milestones:
>     * "Patches Needing Improvement" - 16
>     * "3.0.0" - 2
>     * Not Milestoned - 75
>   * Components:
>     * AIM - 2
>     * Finch - 1
>     * Gadu-Gadu - 5
>     * Google Talk - 1
>     * ICQ - 10
>     * libpurple - 18
>     * MSN - 3
>     * MySpace - 1
>     * Pidgin - 27
>     * QQ - 1
>     * SIMPLE - 2
>     * WinPidgin - 2
>     * XMPP - 10
>     * Yahoo! - 3
>     * Zephyr - 2
>     * unclassified - 5
> 
> It's fairly obvious why the two patches on milestone 3.0.0 are waiting, but I
> need people to review the others!  If patches need work, PLEASE send them to the
> Patches Needing Improvement milestone.  If the patches aren't going to be
> acceptable no matter how much work the submitter puts into them, close the
> tickets.  Obviously, if a patch is good, test and apply it!  Don't be afraid to
> use im.pidgin.pidgin.next.minor for a patch that adds API--Richard and Gary are
> working on that branch, but it IS the correct place for new API.
> 
> Unfortunately, since our Gadu-Gadu and SIMPLE maintainers seem to be absent and
> we have no Zephyr maintainer, I think this means someone is going to need to
> just apply some patches and hope for the best.
> 
> I will be looking over some of these patches, particularly those for the
> libpurple and Pidgin components, and if needed I will assign them to a different
> component.  For my own convenience, I pretty much rewrote
> http://developer.pidgin.im/wiki/OpenPatches to break the patches down so I could
> get a better view of how the patches break down.  I'm still experimenting with
> some queries to try to get the exact results I want, but it's a good reference
> point even in its current state.
> 
> Let's get some of these patches taken care of for 2.5.3!
> 
> John
> 



> _______________________________________________
> Devel mailing list
> Devel at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/devel