Thoughts on QQ Situation

[ccpaging at foxmail.com]

I am one of the member of the pidgin qq plugin in http://groups.google.com/group/openq/

In fact, we have 5 patches now, and the 05-patch-reconnect should release at this weekend.

After 05-patch-reconnect, we have forward qq plugin to:
1. Test ok on qq 2005 protocol
2. Rewrite the network layer based on simple and yahoo plugin of purple
3. Test ok on tcp connect, and tcp connect over http/socks4/socks5 proxy
4. Test ok on udp connect
5. Test ok on arm-based embed device(pdaxrom for sharp zaurus, maemo for nokia), Freebsd on Mac book, ubuntu, arch linux

Since 06-patch-login, qq plugin will forword to qq 2006 protocol according to eva and lumaqq.

We are likely to maintain qq plugin if you want. 



2008-05-21



发件人： Daniel Atallah
发送时间： 2008-05-21 09:26:24
收件人： devel
抄送： 
主题： Thoughts on QQ Situation

It's pretty clear that at this point the QQ prpl is unmaintained.
Based on some bug reports and people in #pidgin, my impression is that
it doesn't work reliably.
There are 4 QQ patches in the tracker, 2 of them are quite large. 3 of
them are from the same person.
It doesn't look like these are likely to get evaluated any time soon
simply because nobody is capable of doing it.  I don't think that is
fair to the developer who has clearly put forward a lot effort on
these patches.
I see 3 options:
   1 - Find a new maintainer.  With the size of the apparent QQ
userbase, surely there is someone capable
plugin.and interested in stepping forward.  Perhaps the author of the
significant patches in the tracker is interested?
   2 - Do nothing.  Patches will continue sit in tracker, bugs reports
will continue to come in.
   3 - Remove the QQ prpl from the tree.  Perhaps someone will pick it
up and maintain it as a 3rd party
What are your thoughts?
My current opinion is that the options are listed in order of
preference, with the caveat that 2 and 3 are going to eventually
switch positions.
-D
_______________________________________________
Devel mailing list
Devel at pidgin.im
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20080521/db595583/attachment.html>