From S.Ellison at LGCGroup.com  Thu Oct  8 14:56:37 2015
From: S.Ellison at LGCGroup.com (S Ellison)
Date: Thu, 8 Oct 2015 13:56:37 +0100
Subject: [Rd] authorship and citation
In-Reply-To: <CABdHhvEgKF85d0vk2XDNVYDtPr-r10OCxxn+Rdm=FSijQLFa4g@mail.gmail.com>
References: <CAJ=0CtAKRSjo9yeVtN6ye4kHWZs3Yrf2DJMBscUbWTZRDCDvtg@mail.gmail.com>
	<5612EA11.7080805@statistik.tu-dortmund.de>
	<CAHyGmd7M_OZ3vtJzHBV_1AsHrB34tXD6-a8+wB87S8QpUhPRvw@mail.gmail.com>
	<5612FA28.2090607@statistik.tu-dortmund.de>
	<8B5956DE-4D87-4444-BC9D-AF96C04C4F7A@r-project.org>
	<CAJ=0CtAkV0uyeRjgRbOAdFzp4dfM9b_Q1+PqS2MfLBS492W94Q@mail.gmail.com>
	<CADwqtCPV3cFqSzXH5Wr-uWaSN0PZg_7cFddk-xyqrn5_SNpvSw@mail.gmail.com>
	<CAJ=0CtAF--akTCjUocARtURD5GGxuUX55R+WXxyq=D2Tfn3HNg@mail.gmail.com>
	<CABdHhvEgKF85d0vk2XDNVYDtPr-r10OCxxn+Rdm=FSijQLFa4g@mail.gmail.com>
Message-ID: <1A8C1289955EF649A09086A153E2672403B485CBD8@GBTEDVPEXCMB04.corp.lgc-group.com>


> > I read the CRAN policies twice, and there
> > is no official guideline on how to compile the citation.

The policies are about copyright and IP, not credited authorship. There's overlap but they are not the same thing. 

You can see whether someone is a copyright holder by referring to the license you had and whether there is any of their content remaining. But that might not mean they are package 'authors'. If you reuse code verbatim from another package's function, you _must_ note the copyright - but that does not necessarily make the original author of the code a co-author of your package (though I would expect to see at least an acknowledgement in the particular function's help page). And not all 'authors' need necessarily provide code - they could, for example, have developed the core maths the code implements. Of itself, that does not confer copyright in any part of the package code or help text, but it's very likely they'd deserve credit as co-authors. 

Common sense would suggest to me that if you are in doubt about whether someone should be on your author list (as opposed to copyright owner list) in a package's citation, you should probably ask them. And if you are considering removing an author, you should very definitely be in doubt because there was a reason they were there.

The answers you get from different contributors might be different so it would not be surprising if packages differed in the extent to which they cited contributions or added acknowledgements. In essence, though, if everybody feels fairly treated by the citations within a package, there's no reason for anyone else to complain about it, and if someone feels they have not been properly credited they can - and should - contact the maintainer and say so.

So ask before removing someone from your citation. If they say 'no', don?t remove them.

S Ellison


*******************************************************************
This email and any attachments are confidential. Any use, copying or
disclosure other than by the intended recipient is unauthorised. If 
you have received this message in error, please notify the sender 
immediately via +44(0)20 8943 7000 or notify postmaster at lgcgroup.com 
and delete this message and any copies from your computer and network. 
LGC Limited. Registered in England 2991879. 
Registered office: Queens Road, Teddington, Middlesex, TW11 0LY, UK


[Rd] authorship and citation
S Ellison