[asterisk-dev] 13 November, 2012 New SIP stack update

[Daniel Pocock]

On 14/11/12 00:27, Mark Michelson wrote:
> Hi folks,
> 
> This is just a periodic update on the current planned work for the new
> SIP channel driver for the next couple of weeks. I had meant to send
> this out yesterday, but I didn't because I suck and am a terrible person :)
> 
> The hot topic on the mailing list at the moment is the proposed method
> for Asterisk's use of a SIP stack. On that front, we've opened up
> dialogs with the PJSIP and ReSIProcate developers to find out what our
> role can be in their development and find out the reality of being able
> to provide or use packaged versions of their SIP stacks.

Just an update... we're doing a trial of git.  It is just a trial for
now, but if we do commit to git (if you'll excuse the pun), then it
would be much easier for you to maintain a fork and/or independent
branches, if that is the development approach that you prefer.

http://list.resiprocate.org/archive/resiprocate-devel/msg08113.html

(also, can someone clarify whether Asterisk is going to git?  I notice
you have some projects at git.asterisk.org already, but the main
Asterisk page still refers to SVN)

> Things you can expect to see on the wiki soon:
> 

I may be able to add some details to the wiki to help, but I don't seem
to have write access.  My login is daniel.pocock - can somebody check
the permissions?

One thing I notice on the wiki is the licensing.  reSIProcate started
with VOCAL (4-clause BSD) but recent commits are made with a more
standard 3-clause BSD license.  If the Asterisk team makes
contributions, then:

a) you would contribute them under 3-clause BSD terms (not VOCAL terms)

b) the author would retain their name in the copyright, you don't have
to grant copyright to Vovida/VOCAL or any third party.

Here is an example of the license block in a contribution I made
recently on that basis:

https://svn.resiprocate.org/viewsvn/resiprocate/main/resip/dum/TlsPeerAuthManager.cxx?revision=9845&view=markup#l197