[TangerineSDR] Tangerine licensing

Dave Larsen kv0s.dave at gmail.com
Thu Apr 2 12:28:52 EDT 2020


Are there preferences?

openhpsdr.org  used GPL2 and GPL3 depending on the time frame the software
was produced.

There are lots of choices.

Dave KV0S

On Thu, Apr 2, 2020 at 10:45 AM John Ackermann N8UR via TangerineSDR <
tangerinesdr at lists.tapr.org> wrote:

> This thought was prompted by my other message...
> We should formalize the requirements for licensing Tangerine hardware
> and software work product.
> For software, I would recommend simply requiring an OSF-approved open
> source license.  We should consider a copyright assignment from
> contributors, as discussed below.  While I'd personally prefer to use
> GPL, that could be an inhibiting factor for some organizations that
> might be involved so I'm comfortable with allowing any OSF license.
> For hardware, I think we've agreed that the TAPR OHL
> (http://tapr.org/OHL) should be used.
> But because of the economics of hardware design and manufacture, the
> implementation is not quite as straigh-forward as for software.  The
> problem is that immediately publishing the full design documentation
> with gerbers, etc., could bring on competitors who might undercut the
> market while TAPR is left holding inventory that required significant
> up-front investment (we had first-hand experience with this problem
> several years ago).
> The way TAPR has normally dealt with this issue is to ask each design
> contributor to sign an agreement that says a few things:
> 1.  The product will be licensed under OHL.
> 2.  TAPR has the exclusive right to produce an initial production run of
> the Product.  That right ends __ days after first product shipment.
> 3.  Developer may release descriptions, images, and schematics at any
> time, but may not provide Gerbers or other manufacturing documentation
> until after the exclusivity period ends.
> 4.  Once the exclusivity period is over, everyone has the right to
> publish full manufacturing documentation.
> 5.  Developer assigns his/her IP rights in the design to TAPR, and TAPR
> gives back a very broad license that pretty much allows the developer to
> do whatever they want except outright sell the IP.  This is similar to
> what the FSF does with individual contributors to its software projects;
> it gets the project rights in one place to make potential negotiations
> easier (e.g., offering products under a dual-license structure).
> A copy of an agreement to accomplish that is attached.  I'd welcome any
> thoughts about this approach, but it is something we should close on
> pretty soon.
> Thanks,
> John
> --
> TangerineSDR mailing list
> TangerineSDR at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/tangerinesdr_lists.tapr.org

KV0S - Dave Larsen
Columbia, MO, USA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20200402/fb29a315/attachment.html>

More information about the TangerineSDR mailing list