Bug#668076: reSIProcate packages RFS

[Daniel Pocock]

On 09/04/12 10:41, Tzafrir Cohen wrote:
> Hi,
> 
> On Sun, Apr 08, 2012 at 09:07:49PM +0200, Daniel Pocock wrote:
>>
>>
>> Hi,
>>
>> I've recently filed an RFS for reSIProcate
>>
>> http://lists.debian.org/debian-mentors/2012/04/msg00168.html
> 
> I didn't yet try to build it, but at first glance the packaging looks
> good.
> 
> One minor nit: The license is a 4-cluase BSD-like license. Is this
> intended to be a used as a library? Clause (3) from the license makes it
> *GPL incompatible. Any hope of fixing that?

I believe you are referring to this clause:

 "3. The names "VOCAL", "Vovida Open Communication Application Library",
     and "Vovida Open Communication Application Library (VOCAL)" must
     not be used to endorse or promote products derived from this
     software without prior written permission. For written
     permission, please contact vocal at vovida.org."

http://www.resiprocate.org/License

Here is some background info about VOCAL:

   http://www.voip-info.org/wiki/view/VOCAL

I'm not sure if Vovida or VOCAL still exists in some formal sense, and
if so, I don't know whether the clause is still valid or even relevant

reSIProcate broke away from SIPfoundry and some of the other projects
some years ago too, so it is quite independent

Can you comment more on the relationship of this clause with the GPL?

Does it just prevent linking with *GPL apps, or does it prevent
inclusion in Debian outright?  As it is now, could it go in contrib or
non-free rather than main?

>>
>> If anyone is interested in reviewing or collaborating on this, please
>> get in touch.  I'd also be interested to know if pkg-voip-maintainers
>> should be registered as the maintainer for this work.
>>
>> In particular, the packages provide a working instance of the repro SIP
>> proxy and the reTurn TURN server
> 
> Looks interesting. I see you've already merged your autotool fixes in
> upstream trunk.
> 
> Also note that if you switch to dpkg v.3, there's nothing wrong with
> having a debian/ directory upstream (if it helps them). It just gets
> deleted at packaging time.

It may be better to manage it separately on alioth/collab-maint (Gregor
already started a Git repo there), so that people who are not members of
the reSIProcate project can make changes if needed.

Having two versions (one in upstream and another on alioth) may also
lead to confusion, even though it is technically permitted now.

However, I don't mind either way.