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

[Saúl Ibarra Corretgé]

Hi @rfuchs, thanks for chiming in.

Disclaimer: speaking for myself here.

I know you guys mean well and that the naming was an evolution of an internal name, but the current situation is unfortunate, as those names are bad for public project names. They create confusion not only amongst users but also amongst other developers as you just witnessed.

Moreover, the fact that Sipwise's "rtpproxy-ng" works with "mediaproxy-ng" makes the matters worse. Imagine you are new to the industry and are trying to find a suitable RTP relaying solution. You can use RTPProxy, MediaProxy (which both use modules under the same name on both SIP proxy projects), or MediaProzy-NG, which needs to be used in conjunction with the RTPProxy-NG module.

The MediaProxy-NG project has nothing to do with MediaProxy, as you mentioned in your note, so it would be ideal if a new name could be found for it. Then, if the project would be called "fooRTP", the module could be called "foortp", following the convention used throughout the years. Users wouldn't be confused and now there would be a new kid in town they can play with :-)

Thanks,


---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/152#issuecomment-35752800
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/devel/attachments/20140221/a8125773/attachment.htm>