[asterisk-dev] Recommendations for using a SIP stack with Asterisk
Russell Bryant
russell at russellbryant.net
Tue Nov 13 11:15:02 CST 2012
On Tue, Nov 13, 2012 at 11:40 AM, Matthew Jordan <mjordan at digium.com> wrote:
> On 11/13/2012 09:47 AM, Russell Bryant wrote:
> >
> > One of the biggest takeaways from the discussion so far is that the
> > health of the SIP stack's community and how well it plays with the rest
> > of the open source ecosystem is very important to people. Ignoring all
> > of that and just embedding something is unacceptable. The path to *not*
> > doing that must be taken into account when figuring out how much work it
> > will be to consume a given library. All of that is in addition to the
> > technical merits of any given choice.
> >
>
> Let's be careful with the word 'unacceptable' :-)
>
> There are certainly trade-offs to any decision that gets made. Given
> the number of variables involved, I can guarantee that regardless of the
> final decision reached, some subset of the Asterisk community will be
> unhappy. I'd like to pretend that's not the case, but this is too
> contentious of an issue for that not to happen.
>
> So let's just say that having the SIP stack as a separate package is a
> highly desirable attribute for package maintainers, and that should
> receive sufficient weight when making a decision.
I was careful when writing it. I know what it means. In my opinion, it is
in fact unacceptable.
--
Russell Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20121113/6a8360f6/attachment.htm>
More information about the asterisk-dev
mailing list