The Free Software Foundation maintains a list of free and GPL-compatible
software licenses here:
https://www.gnu.org/licenses/license-list.en.html#Unlicense
It appears that Unlicense is considered a free and GPL-compatible license;
however, the page does suggest using CC0 instead (which is indeed
Unfortunately, our lawyers say that they can't give legal advice in
this context.
My question would be, what are people looking for that the MIT or
2-clause BSD license don't provide? They're short, clear, widely
accepted and very permissive. Another possibility might be to
dual-license packages
On 18.01.2017 00:13, Karl Millar wrote:
Please don't use 'Unlimited' or 'Unlimited + ...'.
Google's lawyers don't recognize 'Unlimited' as being open-source, so
our policy doesn't allow us to use such packages due to lack of an
acceptable license. To our lawyers, 'Unlimited + file LICENSE' me
Please don't use 'Unlimited' or 'Unlimited + ...'.
Google's lawyers don't recognize 'Unlimited' as being open-source, so
our policy doesn't allow us to use such packages due to lack of an
acceptable license. To our lawyers, 'Unlimited + file LICENSE' means
something very different than it presuma
On 10/12/16 00:22, Paul Gilbert wrote:
In R 3.3.2 detectCores() in package parallel reports 2 rather than 1 on
Raspberry Pi B+ running Raspbian. (This report is just 'for the record'.
The model is superseded and I think no longer produced.) The problem
seems to be caused by
grep processor /pro
Hi Frederik,
On Mon, 2017-01-16 at 18:20 -0800, frede...@ofb.net wrote:
> Hi R Devel,
>
> I wrote some code which depends on 'strptime' being able to parse an
> incomplete date, like this:
>
> >
> > base::strptime("2016","%Y")
> [1] "2016-01-14 PST"
>
> The above works - although it's odd that
Hi Robert,
I've run more experiments (and yes, the code is probably too long for
the list). The tradeoffs are platform dependent. The "nobreak" version
is slower than "break" on a corei7 (i7-3610QM), it is faster on opteron
(6282) and it is about the same on Xeon (E5-2640, E5-2670 even though
