Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-licensing usethis (1/2) #1252

Closed
49 of 50 tasks
hadley opened this issue Oct 16, 2020 · 60 comments · Fixed by #1277
Closed
49 of 50 tasks

Re-licensing usethis (1/2) #1252

hadley opened this issue Oct 16, 2020 · 60 comments · Fixed by #1277

Comments

@hadley
Copy link
Member

hadley commented Oct 16, 2020

We are systematically re-licensing tidyverse and r-lib packages to use the MIT license, to make our package licenses as clear and permissive as possible. To do so, we need the approval of all copyright holders, which I have found by reviewing contributions from all all non-RStudio contributors. @davidchall, @dchiu911, @dpprdan, @EmilHvitfeldt, @fmichonneau, @friep, @gadenbuie, @GegznaV, @Geoff99, @haozhu233, @hmalmedal, @ijlyttle, @jayhesselberth, @jdblischak, @jmgirard, @jonthegeek, @jules32, @karaesmen, @khailper, @kiernann, @KOSHKE, @lbusett, @llrs, @lorenzwalthert, @maelle, @malcolmbarrett, @Maschette, @maurolepore, @MichaelChirico, @mitchelloharawild, @muschellij2, @ncarchedi, @njtierney, @noamross, @overmar, @pachamaltese, @pat-s, @riccardoporreca, @rmflight, @rorynolan, @rundel, @ryapric, @salim-b, @smwindecker, @statwonk, @strboul, @stufield, @uribo, @VincentGuyader, @yoni, would you permit us to re-license usethis with the MIT license? If so, please comment "I agree" below.

@haozhu233
Copy link
Contributor

I agree

@lorenzwalthert
Copy link
Contributor

I agree.

@fmichonneau
Copy link
Contributor

I agree

3 similar comments
@rundel
Copy link
Contributor

rundel commented Oct 16, 2020

I agree

@hmalmedal
Copy link
Contributor

I agree

@malcolmbarrett
Copy link
Collaborator

I agree

@MichaelChirico
Copy link
Contributor

MichaelChirico commented Oct 16, 2020 via email

@maurolepore
Copy link
Contributor

I agree

2 similar comments
@EmilHvitfeldt
Copy link
Member

I agree

@k5cents
Copy link
Contributor

k5cents commented Oct 16, 2020

I agree

@jonthegeek
Copy link
Contributor

I agree.

@jules32
Copy link
Contributor

jules32 commented Oct 16, 2020 via email

@gadenbuie
Copy link
Contributor

I agree

@salim-b
Copy link
Contributor

salim-b commented Oct 16, 2020

to use the MIT license, to make our package licenses as clear and permissive as possible

The only additional freedom a so called "permissive" license provides compared to a copyleft license like GPL is the freedom to not cooperate, i.e. to act in your own interest instead of a common interest. I would therefore consider it as a typical "neoliberal" freedom, i.e. one whose use always puts someone else in a worse position and can therefore never be pareto-efficient.


But anyway, I'm in no position to decide about the licensing of this package since my contributions are marginal. Therefore I agree.

@pachadotdev
Copy link
Contributor

I agree with repairs. I prefer to have a restriction such as "share your contributions and improvements with the community".

@rmflight
Copy link
Contributor

I agree.

@salim-b
Copy link
Contributor

salim-b commented Oct 16, 2020

I prefer to have a restriction such as "share your contributions and improvements with the community".

It's called copyleft, something a "permissive" license like MIT explicitly wants to avoid.

@khailper
Copy link
Contributor

khailper commented Oct 16, 2020 via email

@riccardoporreca
Copy link
Contributor

I agree

2 similar comments
@pat-s
Copy link
Contributor

pat-s commented Oct 16, 2020

I agree

@davidchall
Copy link
Contributor

I agree

@muschellij2
Copy link
Contributor

muschellij2 commented Oct 16, 2020 via email

@ncarchedi
Copy link
Contributor

I agree

2 similar comments
@jayhesselberth
Copy link
Contributor

I agree

@dchiu911
Copy link
Contributor

I agree

@VincentGuyader
Copy link
Contributor

VincentGuyader commented Oct 16, 2020 via email

@stufield
Copy link
Contributor

I agree

3 similar comments
@jdblischak
Copy link
Contributor

I agree

@jmgirard
Copy link
Contributor

I agree

@Geoff99
Copy link
Contributor

Geoff99 commented Oct 16, 2020

I agree

@njtierney
Copy link
Contributor

I agree

2 similar comments
@maelle
Copy link
Contributor

maelle commented Oct 17, 2020

I agree

@llrs
Copy link
Contributor

llrs commented Oct 17, 2020

I agree

@GegznaV
Copy link
Contributor

GegznaV commented Oct 17, 2020

I agree.
Very good initiative to use MIT.

@pr130
Copy link
Contributor

pr130 commented Oct 17, 2020

I agree

2 similar comments
@rorynolan
Copy link
Contributor

I agree

@strboul
Copy link
Contributor

strboul commented Oct 17, 2020

I agree

@ryapric
Copy link
Contributor

ryapric commented Oct 18, 2020 via email

@smwindecker
Copy link
Contributor

I agree.

@dpprdan
Copy link
Contributor

dpprdan commented Oct 20, 2020

We are systematically re-licensing tidyverse and r-lib packages to use the MIT license, to make our package licenses as clear and permissive as possible.

@hadley Could you elaborate on why you want to make this change, please? In particular, what exactly prompted you to choose GPL in the first place and what makes you want to change to MIT now? I am more interested in the "systematically" than in the particular usethis case (which, I assume, is GPL due to devtools and the base R code used therein). This is a substantial change and I suppose the community would be interested in your rationale (well, at least I am).

Anyway, I agree with this change here, because I would not have not contributed at the time, had usethis already been MIT-licensed then.

@hadley
Copy link
Member Author

hadley commented Oct 20, 2020

@dpprdan you can see some discussion at tidyverse/ggplot2#4236

@karaesmen
Copy link
Contributor

I agree.

@batpigandme
Copy link
Contributor

Hi @KOSHKE, @lbusett, @noamross, @overmar, and @statwonk,
We'd love to get your agreement please, if you could take a look when you have a chance. 🙂
Thanks!

@noamross
Copy link
Contributor

I agree

@statwonk
Copy link
Contributor

I agree.

@jennybc
Copy link
Member

jennybc commented Nov 18, 2020

@hadley @batpigandme The 3 remaining appear to be essentially inactive on GitHub, so I believe this issue has served its purpose.

@jennybc jennybc added this to the v2.0.0 milestone Nov 18, 2020
@overmar
Copy link
Contributor

overmar commented Nov 18, 2020 via email

@jennybc
Copy link
Member

jennybc commented Nov 18, 2020

I stand corrected! Thanks @overmar.

@hadley
Copy link
Member Author

hadley commented Nov 18, 2020

We have made a good-faith attempt to get consent from all contributor to the package under the previous license. This has included reviewing contributions to the package for non-trivial changes, seeking agreement to re-license with GitHub issues, sending a reminding after two weeks, and reaching out by e-mail (where possible).

Unfortunately, we have not received a response from @lbusett. We have carefully reviewed their contributions. Given that the contributions are relatively small, and no one has objected to re-licensing across all tidyverse and r-lib repos, we are going to move ahead with the re-licensing. Of course, if we later discover that contributors are not happy with the re-licensing, we'll re-implement their changes.

batpigandme added a commit that referenced this issue Nov 18, 2020
hadley pushed a commit that referenced this issue Nov 18, 2020
@llrs
Copy link
Contributor

llrs commented Nov 18, 2020

If you needed our consent to change the license don't we also hold the copyright?
I propose to change on LICENSE

-COPYRIGHT HOLDER: usethis authors
+COPYRIGHT HOLDER: usethis contributors

@hadley
Copy link
Member Author

hadley commented Nov 18, 2020

@llrs yes, we'd consider you to be an author of usethis.

@llrs
Copy link
Contributor

llrs commented Nov 19, 2020

Many thanks @hadley glad to contribute to the package 🥳 but that is not reflected on the Description of the package. We are not listed there as authors or contributors. I'm fine with not appearing on the Description, just hope there is a balance between this issue, where we are authors and you need our approval for re-licensing, and the usual practice 😅 .

@salim-b
Copy link
Contributor

salim-b commented Nov 19, 2020

(...) this issue, where we are authors and you need our approval for re-licensing, and the usual practice.

I guess legal prudence and social status are not the same thing. 😜

@hadley
Copy link
Member Author

hadley commented Nov 19, 2020

@llrs our policy is to only use Authors@R for significant and sustained contributions to the package, and acknowledge other contributions in blog posts. This allows us to clearly recognise those folks who have put in a lot of effort over a long period, while still thanking everyone who's made the package better, no matter how small their contribution is. If you want to discuss this policy, I'd suggest opening a new issue, so all 50+ folks on this issue aren't notified every time you comment.

@jennybc
Copy link
Member

jennybc commented Dec 1, 2020

I have learned that @lbusett recently passed away, which explains the lack of response.

https://docs.ropensci.org/MODIStsp/articles/lorenzo.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.