Direction of Pidgin development

[Dale Worley]

I'm in no position to make a recommendation as to how to deal with this,
but I do know that it is an example of what happens when projects
approach *real* success -- All sorts of user interaction issues become
more important, and "bringing the software to market" includes an
increasing amount of work which isn't "getting the code to work".  The
usual estimate is that 1/3 of the work is getting the code to work, and
2/3 is needed to polish up the software to the point that
non-specialists can use it conveniently.

Dale