On Thu, Apr 3, 2008 at 10:46 PM, Jay R. Ashworth <jra@baylink.com> wrote:
On Wed, Apr 02, 2008 at 10:30:29PM +0200, Trixter aka Bret McDanel wrote:
> dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> that usually are only "big carrier types" that do not properly deal with
> what asterisk sends. I gave oej specifics as he was doing something
> relating to a filed bug on this issue. I even wrote a patch, but until
> asterisk is no longer released gpl I cant contribute it (personal thing
> just as some wont contribute unless its gpl I wont contribute if it is).
Just curious why you look at it that way, Bret.
The only reason I could see why someone would decline to contribute
to a GPLd project would seem to be handily dealt with merely by
dual-licensing your code GPL and BSD.
On the other hand, it may be that you're complaining about *having to
assign your copyright to Digium*, which would be an entirely different
issue: you would be unhappy that they could then themselves dual-license
it commercially.
Is that the situation that troubles you?
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra@baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com '87 e24
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
Those who cast the vote decide nothing.
Those who count the vote decide everything.
-- (Joseph Stalin)
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-biz mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-biz
No comments:
Post a Comment