Thank you all for your advise, comments and suggestions.
To keep it simple and play it fair and save, I choose to take the
following actions:
Within DESCRIPTION
- the License now reads:
License: GPL (>= 2)
- the Authors are specified as
Authors@R: as.person(c(
"Peter Meissner [aut, cr
On 06/11/2014 10:05 AM, Peter Meissner wrote:
But how might I do that?
Writing GPL in DESCRIPTION and putting my name in every R-file?
You should probably choose a version to be unambiguous, e.g. use "GPL-2
| GPL-3". There's a section on this in "Writing R Extensions".
The files that you w
On Thu, Nov 6, 2014 at 10:05 AM, Peter Meissner
wrote:
> But how might I do that?
>
> Writing GPL in DESCRIPTION and putting my name in every R-file?
Maybe see http://www.gnu.org/licenses/gpl-howto.html
It has some example header that you can put in each source file.
Gabor
>
>
>
> Am 2014-11-06
> Yes, that's right. We often enter lines like
>
> Copyright (C) 1997--2014 The R Core Team
>
> into the sources, but I suspect that those don't legally imply a copyright
> transfer, at least where I live.
It's also not clear that R Core Team is a legal entity that can own copyright.
Hadley
--
On 06/11/2014 9:49 AM, Hadley Wickham wrote:
> Theoretically you could ask the copyright holder of that piece of code
> whether he/she/it allows you to use a different license. This brings up
> another question: who is formally the copyright holder of the R source code
> (and documentation)? The
But how might I do that?
Writing GPL in DESCRIPTION and putting my name in every R-file?
Am 2014-11-06 15:46, schrieb Hadley Wickham:
And if yes how to do it best? What is the standard procedure here?
Should I include base package authors as contributors in DESCRIPTION???
Am I allowed to us
On Thu, Nov 6, 2014 at 9:46 AM, Hadley Wickham wrote:
>>> And if yes how to do it best? What is the standard procedure here?
>>> Should I include base package authors as contributors in DESCRIPTION???
>>>
>>> Am I allowed to use MIT + file license with that or is it wrong to do so?
>>
>> No, you m
> Theoretically you could ask the copyright holder of that piece of code
> whether he/she/it allows you to use a different license. This brings up
> another question: who is formally the copyright holder of the R source code
> (and documentation)? The R Foundation, the individual who contributed th
>> And if yes how to do it best? What is the standard procedure here?
>> Should I include base package authors as contributors in DESCRIPTION???
>>
>> Am I allowed to use MIT + file license with that or is it wrong to do so?
>
> No, you must use the GPL, since the code you copied is licensed under
On Nov 6, 2014 3:36 AM, "Duncan Murdoch" wrote:
>
> On 06/11/2014, 5:57 AM, Peter Meissner wrote:
> > Dear Listeners,
> >
> > ... also I read the CRAN policies and tried to solve those questions
> > myself I feel very much in the need of good advise ...
> >
> >
> > I am currently finishing a packa
On 06/11/2014, 5:57 AM, Peter Meissner wrote:
> Dear Listeners,
>
> ... also I read the CRAN policies and tried to solve those questions
> myself I feel very much in the need of good advise ...
>
>
> I am currently finishing a package that -- to solve some nasty problems
> with dirty data -- u
Dear Listeners,
... also I read the CRAN policies and tried to solve those questions
myself I feel very much in the need of good advise ...
I am currently finishing a package that -- to solve some nasty problems
with dirty data -- uses its own as.Date() equivalent methods (i.e. its
own gene
12 matches
Mail list logo
