From h.wickham at gmail.com  Mon Aug 26 20:12:55 2013
From: h.wickham at gmail.com (Hadley Wickham)
Date: Mon, 26 Aug 2013 13:12:55 -0500
Subject: [Rd] legitimate use of :::
In-Reply-To: <CAMigB8Gf4tdrpeOBU88T=UE-hVySJgh3etgELKs2C1GmWzyxyA@mail.gmail.com>
References: <mailman.25.1377252007.21998.r-devel@r-project.org>
	<521B4F6C.3090101@imbe.med.uni-erlangen.de>
	<521B6A8A.7040307@gmail.com> <521B722A.5050702@fau.de>
	<CAMigB8Gf4tdrpeOBU88T=UE-hVySJgh3etgELKs2C1GmWzyxyA@mail.gmail.com>
Message-ID: <CABdHhvELKs7V=eOVD4P3jD6KxMqDYwXR6BWLVemi+RicobaWcQ@mail.gmail.com>

On Mon, Aug 26, 2013 at 1:06 PM, Trevor Davis <trevor.l.davis at gmail.com> wrote:
>> This is a good solution. Do I need to specify the original License etc? And
>> what about a helper function such as stats:::n.knots? This will not appear
>> in the manual of my package. Is it sufficient in this case to document the
>> authorship in the source (and perhaps a README as you suggested)?
>
> If the license is the same as your projects you just need the proper
> copyright notice.
> As Hadley suggests it is a good idea to also document the appropriate authorship
> in the Authors field in the DESCRIPTION as well.
>
> If the license is different but permissive than then it typically doesn't need
> go into DESCRIPTION or a separate LICENSE file but the permissive
> license text does usually need to either go
> into inst/COPYRIGHT or at the top of the relevant code file:
>
>   https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
>   https://www.softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html

That may be true for other open source projects, but that is not the
interpretation that cran maintainers have used in the past.

Hadley

-- 
Chief Scientist, RStudio
http://had.co.nz/



[Rd] legitimate use of :::
Hadley Wickham