Hi Andreas, Not sure if you are referring to me but in case you do. I am not demanding any apology. Personally, I have no issue with the name you have chosen. If you knowingly chose that name mediaproxy-ng which I was using since 2008 and expected me to complain about it, is really weird. I am not polling github every day just in case something like this happens.
The issue emerged now, in the context of OpenSIPS project where we have an obvious overlap of naming and purpose at the same time. As I mentioned, your software is a great addition and we just asked to eliminate any confusion by renaming it. If you can help with the name change is great, if not then so be it, I don’t really care about your choices and I don’t need any apologies from you or anybody else. Adrian On 06 Mar 2014, at 09:07, Andreas Granig <notificati...@github.com> wrote: > Speaking with my @sipwise hat on, there will be a name change of at least the > mediaproxy-ng back-end part soon, to clear things up for the future. I > understand the concerns of AG in regards to name clashing, and we don't like > the confusion either. No plans yet for the rtpproxy-ng module name though, > because as @rfuchs pointed out, it's really an evolution of the rtpproxy > module, and it can be used as rtpproxy drop-in replacement when switching the > back-end. > > Since only the module part (rtpproxy-ng) is going to be maintained by you > guys (we don't use opensips, so there are no plans to support the module for > opensips), you can name it however you like. > > However, I find it extremely offensive from this community to have a module > pulled into your project, then start accusing the author and demanding an > apology for the name, after he's kind enough to chime in and provide an > explanation for the naming clashes. The media proxy is available as open > source on github since nearly two years, and I would have expected some > feedback from AG if there were concerns about the name over this period (it's > not that the guys at AG don't know who we are and what we do). > > — > Reply to this email directly or view it on GitHub. > > _______________________________________________ > Devel mailing list > Devel@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
