-
Notifications
You must be signed in to change notification settings - Fork 235
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 roxygen2 #1163
Comments
I agree |
8 similar comments
I agree |
I agree |
I agree |
I agree |
I agree |
I agree |
I agree |
I agree |
As you well know by now I think it's a shame you're moving away from GPL. Since my contributions are minimal I don't oppose the license change on the basis of my contributions (I agree). One question though: on what basis do you believe that R being GPL doesn't require packages run on it to also be GPL? Is it because of the "interpreted code" FAQ "exemption". Or because you don't consider "R + package" to be the "modified work as a whole". I realize many folks believe that R's license doesn't apply to packages (including CRAN), but presumably you've had some extensive discussions on this before making these changes, so probably have specific reasons for believing so. Would you mind sharing those? |
I agree |
2 similar comments
I agree |
I agree |
@brodieG can you please keep the discussion on the ggplot2 issue? |
Sure. For those interested it is this one: |
Just noticed @klutometis is not in the list and AFAICT he is not Rstudio (maybe he provided approval separately?)? Also, is it a given the Rstudio employees automatically consent to this type of license change, even if contributions precede employment, or is that done on a case by case basis? I think some contributions would fall in this category. |
@brodieG, |
Great, thanks @batpigandme, this does help. I didn't think Rstudio would be automatically taking copyright ownership of prior contributions (or requiring it as condition for employment), but it's nice to see it confirmed. |
I agree |
1 similar comment
I agree |
I agree |
2 similar comments
I agree |
I agree |
I agree. |
1 similar comment
I agree. |
I agree |
1 similar comment
I agree |
I agree |
I agree.
…On Fri, Oct 30, 2020 at 3:42 PM Geoff99 ***@***.***> wrote:
I agree
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1163 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2QEAIZTFXY3R44OPSSGGLSNM6ONANCNFSM4TFA3CBA>
.
--
Best wishes,
Michael
Cell: (917) 808 6508
|
I agree. |
I agree |
2 similar comments
I agree |
I agree |
I agree. |
2 similar comments
I agree. |
I agree. |
I agree |
Hi @HenrikBengtsson, @jefferis, @martin-mfg, and @mikefc, |
I agree (sorry @batpigandme, there were slew of similar requests at the same time and I thought I had responded to all of them) |
I agreed: #1163 (comment) |
No need to apologize, @jefferis, I know all too well how easily notifications get lost on GH. |
Sorry, @martin-mfg, thanks for agreeing, and sorry for the re-ping! |
Actually #1163 (comment) also, so I'm doubly agreed! ;-) All the best, Greg. |
I agree |
I agree. |
Apologies, lost track of whether I've responded to this already or not, but just in case I haven't, I agree |
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. @briandk, @brodieG, @dougmitarotonda, @dpritchLibre, @egnha, @eibanez, @flying-sheep, @fmichonneau, @Geoff99, @gustavdelius, @halldc, @HenrikBengtsson, @jakob-r, @jameslamb, @jefferis, @jhchou, @jonthegeek, @JoshOBrien, @jranke, @klmr, @lindbrook, @LiNk-NY, @Lucaweihs, @maelle, @martin-mfg, @michaelquinn32, @mikefc, @mikemahoney218, @mikldk, @mikmart, @mjskay, @sgibb, @shrektan, @tobiaskley, @wibeasley, would you permit us to re-license roxygen2 with the MIT license? If so, please comment "I agree" below.
The text was updated successfully, but these errors were encountered: