I don't have all the answers, but here are a few comments (in the same order as the points in the blog): * Sofia SIP - now that FreeSWITCH maintains the continuation of this project, distributions like Debian would probably be willing to carry the FreeSWITCH version of Sofia SIP as long as it has a new version number to distinguish it from the past releases * SpanDSP - as your comments suggest FreeSWITCH is now the main repository for new work on SpanDSP, it is the FreeSWITCH version of this code that distributions should be packaging up and other projects relying on SpanDSP should keep up with it. * SQLite - if your code is significantly different, why not fork under a different name? * Obsolete libraries: aim for distributions like Debian unstable and Fedora rawhide first - if FreeSWITCH is pushed into the distribution in that place, it can be co-ordinated with the selection and updating of the related libraries for the next major release of the distribution. This means that future releases of the distributions will enable many successful FreeSWITCH projects for long into the future. I realize this doesn't solve all the problems but it would provide a good start even doing just one library at a time. SofiaSIP and SpanDSP seem like less complicated choices to start with. In reSIProcate, we keep copies of certain libraries for the convenience of Windows users