[asterisk-dev] Recommendations for using a SIP stack with Asterisk

Faidon Liambotis paravoid at debian.org
Tue Nov 13 11:28:08 CST 2012


On 11/13/12 18:40, Matthew Jordan wrote:
> 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.

No. I know you all would love to call this a distributions' problem but
you'd be completely missing the point. This "rule" against embedding
wouldn't be common to all distributions if there wasn't a very good reason.

Forking & embedding libraries within your project hurts free software
and hurts the community. It's a very uncathedral (and uncommon in this
world) way of running a project and shows that the project cares more
about retaining control than contributing back to the community and its
work that is based upon.

And besides this giving you a bad community karma, I do believe it
results in a technically inferior solution, for the same reasons a
closed source development model results in inferior results than an open
source one.

Regards,
Faidon



More information about the asterisk-dev mailing list