-
Notifications
You must be signed in to change notification settings - Fork 114
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 covr as MIT #454
Comments
I agree |
I agree
Le ven. 30 oct. 2020 à 15:09, Robert M Flight <notifications@github.com> a
écrit :
… I agree
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA566FVHBETVKBAIBBP2S3SNLCIDANCNFSM4TFAOUBQ>
.
|
I agree |
Agree!
…On Fri, 30 Oct 2020 at 15:13, Jouni Helske ***@***.***> wrote:
I agree
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKAUFKYUIN4P65ASKK4WAP3SNLC2FANCNFSM4TFAOUBQ>
.
|
I agree |
I agreee |
agreed
…On Fri, Oct 30, 2020, 10:26 AM Kun Ren ***@***.***> wrote:
I agreee
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2BA5KL7UBIO5TDA4ZEEB3SNLEIBANCNFSM4TFAOUBQ>
.
|
I agree |
2 similar comments
I agree |
I agree |
I give permission. But I think GPL 2/3 remain the correct licenses for the R community. |
I agree |
I also think GPL is the better license for the R community, but given my contributions are minor I agree. For those interested in more discussion please see: tidyverse/ggplot2#4236 |
I agree |
1 similar comment
I agree |
I agree. |
I agree |
2 similar comments
I agree |
I agree |
I agree. |
Administrivia: my name is left out in the checklist, but present in the paragraph. |
Same here - and for a few other folks as well. |
I agree. |
1 similar comment
I agree. |
I agree |
I agree
…On Sat, Oct 31, 2020 at 6:53 AM David Hugh-Jones ***@***.***> wrote:
I agree
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4HYM6UYKIAXI3GF3G2FATSNM7V7ANCNFSM4TFAOUBQ>
.
|
Hi, @chen-liang-oracle, @chinqw, @jpritikin, @katrinleinweber, @MishaCivey, and @surmann, |
Hi, sorry I still haven't had time to get to any of these requests (I got lots of them). I don't object to changes as long as the main maintainer and the original author(s) are ok with it. But I'd like to take the opportunity to ask for some clarifications, and I don't know another place to ask than here: Q1. Who are "we" in: "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. ..."? Is that RStudio, or something or somebody else? Q2. Related to the above, and maybe this is already explained somewhere that I'm not aware of. How is the 'r-lib' organization/group/entity (https://github.com/r-lib/) related to RStudio (https://github.com/rstudio)? Is 'r-lib' some type of entity with some ownership or just an online location to share code? Regarding the move of 'covr' back to the MIT license. I recall the MIT -> GPL3 transition that was "forced" upon 'covr' (#256). Is that no longer an issue? |
Q1. We is mostly me, Hadley (in conjunction with discussions with my team and other folks (e.g. JJ) within RStudio). Q2. r-lib is roughly equivalent to tidyverse but for packages that provide low level infrastructure (processx, gert, pillar, ...) or support package development (roxygen2, devtools, ...). Most of the maintainers are RStudio employees (mostly on my team). There are a few repos that are owned by others, but live in r-lib to indicate that my team would take over maintenance if the original creator is no longer interested Q3. It was forced mostly because we didn't understand licensing as well then as we do now. |
I agree |
As I replied earlier, I agree (chen liang Ex-Oracle)
…On Fri, Nov 20, 2020 at 10:04 AM Henrik Bengtsson ***@***.***> wrote:
I agree
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4HYMYG57LZERDTMCD6NIDSQXFDPANCNFSM4TFAOUBQ>
.
|
I agreed. Thank you for moving to MIT :-) |
@jpritikin agreed over email. |
I don't see my name in the checklist above (but was cc'd), but if its necessary, I agree. |
I agree |
I agree. |
I agree.
…On Wed, Feb 2, 2022 at 2:28 PM Jim Hester ***@***.***> wrote:
Closed #454 <#454> via #498
<#498>.
—
Reply to this email directly, view it on GitHub
<#454 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMQAXGINWBABEWAOLS56K3UZGHX5ANCNFSM4TFAOUBQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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. @brodieG, @chen-liang-oracle, @chinqw, @daattali, @daroczig, @Delfic, @enbrown, @helske, @HenrikBengtsson, @hughjonesd, @jameslamb, @JohnMount, @jonclayden, @jpritikin, @karl-forner-quartz-bio, @katrinleinweber, @kenahoo, @kforner, @kirillseva, @kiwiroy, @maodunzhe, @MichaelChirico, @MishaCivey, @nibant, @patperry, @renkun-ken, @rmflight, @robertzk, @RolandASc, @siddharthab, @stevepeak, @surmann, @wamserma, @wligtenberg, would you permit us to re-license covr with the MIT license? If so, please comment "I agree" below.
(You may recall that we've been through this process once before in #256. We now understand the licensing landscape much better and are moving to make our policies consistent across the tidyverse)
The text was updated successfully, but these errors were encountered: