<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I guess it is reasonable that nobody expects a developer to stretch to manage his stuff across external forks. I am not maintaining MediaProxy in Kamailio project either, if there are volunteers there it is fine but if they are not, then end-users have indeed a problem with any such fork.</div><div><br></div><div>I guess Bogdan’s questions is very legitimate, who is going to maintain this new module?</div><div><br></div><div>Adrian </div><br><div><div>On 17 Jun 2014, at 13:05, Richard Fuchs <<a href="mailto:notifications@github.com">notifications@github.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Just to clear things up, I had no part in porting this module to opensips other than the original implementation from which it is derived.</p><p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/pull/152#issuecomment-46328088">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/5479561__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxODY0MDMyNCwiZGF0YSI6eyJpZCI6MjI0MzY3NDV9fQ==--dea44ed37e9f5774676ee43b49d21e8c29b6a87c.gif" width="1"></p>_______________________________________________<br>Devel mailing list<br><a href="mailto:Devel@lists.opensips.org">Devel@lists.opensips.org</a><br>http://lists.opensips.org/cgi-bin/mailman/listinfo/devel<br></blockquote></div><br></body></html>