[OpenSIPS-Devel] [opensips] [RFC] An initial attempt of porting rtpproxy-ng module from your twin project to OpenSIPS. (#152)

[ag at ag-projects.com]

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.

I guess Bogdan’s questions is very legitimate, who is going to maintain this new module?

Adrian  

On 17 Jun 2014, at 13:05, Richard Fuchs <notifications at github.com> wrote:

> 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.
> 
> —
> Reply to this email directly or view it on GitHub.
> 
> _______________________________________________
> Devel mailing list
> Devel at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20140617/850585fd/attachment.htm>