[Psi-devel] unifying libjingle

[Rafael Espíndola]

> Honestly, i'm not very keen on forking a moving target library like
> libjingle. It introduces quite some overhead to track changes, find
> out who's to blame for bugs, ... For example, there will probably be
> a next release of libjingle next week with some new features, and so
> how long will it take before all these forks find out which patches
> have been integrated or are obsolete, how they will integrate the
> conflicting patches, ...
True. The ideal scenario would be if the real upstream libjingle would
include bug fixes and updates. Currently this is not happening.

Psi has a copy of libjingle already, so the mentioned problems already
exist. But using an external version will share the effort of
maintaining it among kopete and tapioca developers.

> Just my 2 cents.
>
> cheers,
> Remko

Best Regards,
Rafael