Add new proprietary license or license rules

[pombredanne]

This is a somewhat arcane thing, but we better be able to either detect this as a license or a rule:

• https://github.com/search?q="ANTI-FASCIST-MIT+LICENSE%3A"&type=code
• https://github.com/VKEA/PrideCSS/blob/master/LICENSE
• https://github.com/jamiebuilds/anti-fascist-mit-license/blob/master/LICENSE
• https://app.unpkg.com/bgio-effects@0.7.1/files/README.md

To test before adding: is this detected by the unknown license detection?

[DennisClark]

I think that these should be handled by license rules and not new licenses.

[armijnhemel]

I think that these should be handled by license rules and not new licenses.

Why, if I may ask? When should something be done as a new license and when as a rule?

[pombredanne]

@armijnhemel the threshold is fuzzy, but roughly based on the number of occurrences. This is a set of old licenses, not even a single license. These are are several years old and seldom used. We can start with simple set of "proprietary license" rules, and if this later rise to be more common, we can give it its own record?

[armijnhemel]

@armijnhemel the threshold is fuzzy, but roughly based on the number of occurrences. This is a set of old licenses, not even a single license. These are are several years old and seldom used. We can start with simple set of "proprietary license" rules, and if this later rise to be more common, we can give it its own record?

As long as they are not tagged as MIT :-)