[License-discuss] Pritunl "open source"

[Antoine Thomas]

At OW2 Con a few years ago, someone from the Talend company introduced in a
talk the concept of "open core". And he explained the difference with "open
source".

This was really similar.



[image: PrestaShop]
<https://www.prestashop.com/?utm_source=signature&utm_medium=e-mail&utm_campaign=emails-signatures>

Antoine Thomas aka ttoine

Developer Advocate

t: +33 (0)6 63 13 79 06

antoine.thomas at prestashop.com



On Thu, Jun 21, 2018 at 9:15 AM, Rick Moen <rick at linuxmafia.com> wrote:

> Quoting B Galliart (bgallia at gmail.com):
>
> > A couple months ago, I evaluated Pritunl, the "Open Source Enterprise
> > Distributed OpenVPN and IPsec Server"
> [...]
>
> > (1) What advocacy information does the Open Source Initiative provide
> which
> > indicates it is possible to protect the commercial viability of a product
> > when honoring the Open Source Definition?
>
> I am not a spokesman of any kind for OSI, just a member of the open
> source community.  Perhaps someone with official status will get around
> to contributing to this thread, too.
>
> However, a quick check on OSI's site found entries on the FAQ that are
> helpful, and include pointers to further resources, e.g.,
>
>   Q; How do I make money if anybody can sell my code?
>
>   A: You can sell services based on the code (i.e., sell your time), sell
>   warranties and other assurances, sell customization and maintenance
>   work, license the trademark, etc. The only kind of profit strategy that
>   is incompatible with Open Source is monopoly-based sales, also known as
>   "royalties". See this article [link] for how to think about business
>   strategies that make money from Open Source. Also, this 2015 survey of
>   open source leaders (including many OSI Directors) provides several
>   business models for Free and Open Source software [link].
>
> https://opensource.org/faq#profit
>
> > (2) If someone still is not convinced the OSD is right for their product
> > but still wants to market their limited license code as Open Source, what
> > is the downside in doing so?
>
> Ignominy.  The accurate perception that the claim is fraudulent and
> deceptive.
>
>
> _______________________________________________
> License-discuss mailing list
> License-discuss at lists.opensource.org
> http://lists.opensource.org/mailman/listinfo/license-
> discuss_lists.opensource.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-discuss_lists.opensource.org/attachments/20180621/bafb9da9/attachment-0001.html>