Re: [directory-discuss] Game plan for 'bait and surrender' and 'freedom betrayed' packages in the directory

[Ian Kelling]

On Fri, Nov 18, 2016, at 01:31 PM, David Hedlund wrote:
> The term that are already in use to describe this scenario is
>        called "open core". We don't use the term "open", at least not
>        in a positive meaning, but situation is different. Here we
>        actually have the chance to put "open" in negative light.
>
>
> MySQL is an example: 
> Oracle[https://en.wikipedia.org/wiki/Oracle_Corporation]'s 
> MySQL[https://en.wikipedia.org/wiki/MySQL] database software is dual-licensed 
> under a proprietary license,
>        and the GNU GPL[https://en.wikipedia.org/wiki/GNU_GPL]; proprietary
>        versions offer additional features and enterprise support plans.
>        - https://en.wikipedia.org/wiki/Open_core#Examples
>
>
> Do you think we should use the term "open core" to describe
>        partially proprietary software?


I thought about this a bit more, and remembered this blog post:
http://ebb.org/bkuhn/blog/2011/03/05/open-core-slur.html, which can be
summed up that people say open core for a lot of different situations,
and different people have different ideas of what you mean when you say
it, so it's better not to use it. Also, when you explain it, it really
leads you to say open source. Also, people tend to think of it as
referencing a business model of selling proprietary software, but
I don't think the category should really reference that specific
business model, there could be other reasons something fits in this 
category.

I think our other term "Bait and Surrender" is fine, but it looks like
it's going to be essentially the same definition as the f-droid category
"Non free Addons: the application promotes other non-Free apps or
plugins," and that one seems find too, so I think it will be better for
our users to use the same one as F-droid, so that they can use both fsd
and F-droid and understand the label faster and easier since it is
common to both.