similar to: Authorship and Attribution

Displaying 20 results from an estimated 1100 matches similar to: "Authorship and Attribution"

2015 Oct 06
5
authorship and citation
> The former co-author contributed, so he is still author and probably copyright > holder and has to be listed among the authors, otherwise it would be a CRAN > policy violation ... It's a bit of a philosophical question right now, but at some point in a developing package's life - particularly one that starts small but is subsequently refactored in growth - there may be no code
2015 Oct 07
4
authorship and citation
On Tue, Oct 6, 2015 at 4:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Gabriel, > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >> At the very least, this is seems to be a flagrant violation of the >> *spirit* of the CRAN policy, which AFAIK is intended to enforce >>
2015 Oct 06
4
authorship and citation
Adrian, I am not on the CRAN or R-core teams, so the following is my own view, but... > library(QCA) > > Users are encouraged to cite this package as: > > Dusa, Adrian (2015). QCA: Qualitative Comparative Analysis. R Package > Version 1.2-0, > URL: http://cran.r-project.org/package=QCA > > This is just an encouragement, not a requirement, and the official citation
2015 Oct 06
0
authorship and citation
On 06/10/2015 12:58, S Ellison wrote: (quoting without attribution to the author, who would appear to be Uwe Liggges). >> The former co-author contributed, so he is still author and probably copyright >> holder and has to be listed among the authors, otherwise it would be a CRAN >> policy violation ... > > It's a bit of a philosophical question right now, but at some
2015 Oct 06
1
authorship and citation
On Tue, Oct 6, 2015 at 2:52 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Dear Gabriel, > > On Wed, Oct 7, 2015 at 12:39 AM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >>> >>> I apologize for pushing this topic to the limit, but I haven't got an >>> answer to this question yet... >>> >>
2015 Oct 06
3
authorship and citation
On Oct 5, 2015, at 6:31 PM, Uwe Ligges <ligges at statistik.tu-dortmund.de> wrote: > > > On 05.10.2015 23:47, Andrew Robinson wrote: >> As a fourth option, I wonder if the first author could fork the package? >> >> Presumably, appropriately cited, a fork is permitted by the license under >> which it was released. Then the original package, by both
2015 Oct 06
2
authorship and citation
Adrian, Responses inline On Tue, Oct 6, 2015 at 1:58 PM, Adrian Du?a <dusa.adrian at unibuc.ro> wrote: > Hi Gabriel, > > On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> > wrote: > >> [...] >> >> At the very least, this is seems to be a flagrant violation of the >> *spirit* of the CRAN policy, which AFAIK is intended to
2015 Oct 08
0
authorship and citation
> > 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
2015 Oct 05
2
authorship and citation
As a fourth option, I wonder if the first author could fork the package? Presumably, appropriately cited, a fork is permitted by the license under which it was released. Then the original package, by both authors, still exists (and a final version could point to the new one) and the new package, citing the previous version appropriately, is by a single author. The page of CRAN's policies
2015 Jan 16
3
[LLVMdev] git-svn authorship (was: Howdy + GIT)
Erik> I am surprised noone has mentioned the one of the biggest Erik> advantages of Git which is proper author attribution for Erik> non-core and drive-by patch contributors. >From what I can make of the git-svn docs, that LLVM committers should be adding a "From: <email>" field to commit messages instead of "Patch by <name>". If the original author is
2006 May 22
4
LAN games no longer working in Starcraft
My nephew was home last night and I couldn't play Starcraft with him because selecting UDP or IPX LAN games no longer works. When they're selected, a message box appears saying: Unable to initialize network provider I had the same issue in 0.9.11, 0.9.12, 0.9.13. I was able to play multiplayer LAN games previously, but I'm unable to say what version I was using at that time. I first
2015 Oct 06
0
authorship and citation
On Tue, Oct 6, 2015 at 3:06 AM, Simon Urbanek <simon.urbanek at r-project.org> wrote: > > [...] > > To clarify, legally, you can fork a standard GPL package and make any > changes you want, including changing authors fields etc. If you don't own > copyright for the entire work then you cannot change the license without > consent from the other copyright holders,
2015 Oct 06
0
authorship and citation
Hi Gabriel, On Tue, Oct 6, 2015 at 10:59 PM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > [...] > > At the very least, this is seems to be a flagrant violation of the > *spirit* of the CRAN policy, which AFAIK is intended to enforce > acknowledgement of the contributions of all copyright holders in the > package. The fact that you are trying to bypass the policy by
2015 Oct 07
0
authorship and citation
Hadley, With all due respect, I'm not sure what exactly your deliniation between author and contributor is, but from what I can tell I don't agree with it. >From the blogpost regarding your new purrr package: "Purrr wouldn?t be possible without Lionel Henry <https://github.com/lionel->. He wrote a lot of the package and his insightful comments ..." And yet he is
2015 Oct 05
0
authorship and citation
Simply advice: The former co-author contributed, so he is still author and probably copyright holder and has to be listed among the authors, otherwise it would be a CRAN policy violation since even if he does not develop further on, he developed parts of the so far existing package (if you talk about a CRAN package). I am not a lawyer, hence I cannot speak for copyright/license stuff in
2015 Oct 06
0
authorship and citation
Dear Gabriel, On Wed, Oct 7, 2015 at 12:39 AM, Gabriel Becker <gmbecker at ucdavis.edu> wrote: > [...] > >> >> I apologize for pushing this topic to the limit, but I haven't got an >> answer to this question yet... >> > > With respect, not receiving the answer you wanted isn't the same as not > receiving an answer. > I very much appreciate
2009 May 31
1
R Solves Shakespeare Authorship Question
Those of you who track applications of R may be interested in the following: "The purpose of this paper is then to apply modern text analysis techniques using the R statistical packege [sic] to compare the works attributed to Shakespeare to those of leading alternate candidates such as Sir Frances Bacon, Christopher Marlow, and Edward de Vere...".
2015 Oct 05
0
authorship and citation
On 05.10.2015 23:47, Andrew Robinson wrote: > As a fourth option, I wonder if the first author could fork the package? > > Presumably, appropriately cited, a fork is permitted by the license under > which it was released. Then the original package, by both authors, still > exists (and a final version could point to the new one) and the new > package, citing the previous version
2015 Oct 07
2
authorship and citation
On 07/10/2015 1:39 PM, Tim Keitt wrote: > On Wed, Oct 7, 2015 at 11:29 AM, Spencer Graves <spencer.graves at prodsyse.com >> wrote: > >> Another example: The "Author" of the Ecdat package is Yves Croissant < >> yves.croissant at let.ish-lyon.cnrs.fr>. I'm the Maintainer. At some >> point, I may add my name to the list of Authors but I
2003 Jan 24
4
Problems for 13 year old
I would like to teach some scientific/statistical computing to my 13 year old nephew and was considering using R for this. He has a Mac G3 OS 9.1. I am looking for ideas for problems that would be interesting and motivating for someone that age. I recently taught him the basics of HTML and noticed that he particularly was intrigued by the ability to change colors; thus, perhaps problems