pecan icon indicating copy to clipboard operation
pecan copied to clipboard

PEcAn license change

Open infotroph opened this issue 1 year ago • 24 comments

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

  • [x] @aabaris
  • [ ] @UncleWeeds
  • [ ] @abhinav52000
  • [x] @helge22a
  • [ ] @Amanskywalker
  • [x] @andydawson
  • [ ] @TonyCohen
  • [x] @bailsofhay
  • [x] @bcow
  • [x] @braczka
  • [x] @djaiswal
  • [x] @ecamo19
  • [ ] @gbromley
  • [x] @Snafkin547
  • [ ] @hmb1
  • [x] @jbowers20
  • [ ] @jingxia
  • [x] @JoshuaPloshay
  • [x] @jsimkins2
  • [x] @julianpistorius
  • [x] @kzarada
  • [ ] @kragosta
  • [x] @kimberlyh66
  • [ ] @lovelilyinfall
  • [x] @hangyakuzero
  • [x] @marissakivi
  • [ ] @mtmarsh2
  • [ ] @MukulMaheshwari
  • [ ] @Parthmadan-1
  • [x] @rahul799
  • [x] @rykelly
  • [ ] @Sarthakaga15
  • [x] @gsrohde
  • [x] @shubhamagarwal92
  • [ ] @Yiyiyimu
  • [ ] @sl4397
  • [x] @Viskari
  • [ ] @zhangwenx
  • [ ] @yan130

infotroph avatar Aug 26 '24 22:08 infotroph

Text of the email we sent to all contributors whose addresses we could find:

Dear PEcAn contributor,

May we please have your permission to change the PEcAn license from “NCSA Open Source” to “BSD 3-clause”? Please respond and tell us yes or no!

We’re sending this message because you wrote some of the code or documentation in one or more PEcAn packages and therefore you hold* a piece of the PEcAn copyright, so we want your explicit consent before we change the license it is distributed under.

*(Well, probably. Determining who holds copyright is complicated and this is not legal advice. But it does for sure mean you get a say in this decision!)

Timeline: Please answer now! If you agree, replying with the word “yes” is enough.

If you disagree, please tell us and we’ll do our best to address your concerns and find a resolution. We will resolve all contributor concerns before changing the license.

If we haven’t heard from you in a week, we’ll assume the email address we had for you is out of date and move on to hounding you in a different channel... ;)

FAQ:

  • To what specifically am I agreeing? If you respond “yes, I agree”, you are giving us permission to change the license of all your contributions to PEcAn from the NCSA Open Source license to the BSD 3-clause license. We will ask you once and keep your answer on file, then refer to it to relicense each individual PEcAn package when all its contributors have signed off on the change. It may take some time for all the packages to update — we need to track down some contributors who have not been in regular touch for some time.

  • What’s the difference between the old and new licenses? Both licenses are very similar — see the links above for their exact text. NCSA is more explicit about what parts (software and documentation) it covers and what rights the user has, but both licenses are identical in the uses they allow.

  • If they’re so similar, why change? We initially used the NCSA license because we liked the more explicit user rights, but few other projects have adopted it and the BSD3 license is now more widely recognized. One big motivation for this change is that we would like the option of submitting the PEcAn R packages to CRAN, which will require us to choose from a list of standard licenses that includes BSD3 but not NCSA.

  • How did you decide to ask me? We ran git shortlog -se —all in the PEcAn Git repository and found your name there. Even if your involvement was just one commit long ago, we still consider you a PEcAn contributor and we want your agreement for this change.

  • Didn’t you just hassle me about this in Slack? Yes. Sorry for the repeated messages, but if you’re reading this it means we haven't yet seen an answer from you in any medium.

Thank you again for being part of PEcAn, and we look forward to your response.

For the whole team,

Rob Kooper, Mike Dietze, David LeBauer, Chris Black

infotroph avatar Aug 26 '24 22:08 infotroph

@ecamo19 had answered by email already! Sorry for re-pinging you, Erick.

infotroph avatar Aug 26 '24 22:08 infotroph

Tagging @sbs2019 as well -- Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? See thread above.

infotroph avatar Aug 26 '24 22:08 infotroph

Yes, I agree. Joshua PloshayOn Aug 26, 2024, at 6:20 PM, Chris Black @.***> wrote: If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below. Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in. Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

@aabaris @UncleWeeds @abhinav52000 @helge22a @Amanskywalker @andydawson @TonyCohen @bailsofhay @bcow @braczka @djaiswal @ecamo19 @gbromley @Snafkin547 @hmb1 @jbowers20 @jingxia @JoshuaPloshay @jsimkins2 @julianpistorius @kzarada @kragosta @kimberlyh66 @lovelilyinfall @hangyakuzero @marissakivi @mtmarsh2 @MukulMaheshwari @Parthmadan-1 @rahul799 @rykelly @Sarthakaga15 @gsrohde @shubhamagarwal92 @Yiyiyimu @sl4397 @Viskari @zhangwenx @yan130

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

JoshuaPloshay avatar Aug 27 '24 01:08 JoshuaPloshay

Yes! Thanks!

shubhamagarwal92 avatar Aug 27 '24 05:08 shubhamagarwal92

Yes

On Tue, 27 Aug, 2024, 3:50 am Chris Black, @.***> wrote:

Text of the email we sent to all contributors whose addresses we could find:

Dear PEcAn contributor,

May we please have your permission to change the PEcAn license from “NCSA Open Source” to “BSD 3-clause”? Please respond and tell us yes or no!

We’re sending this message because you wrote some of the code or documentation in one or more PEcAn packages and therefore you hold* a piece of the PEcAn copyright, so we want your explicit consent before we change the license it is distributed under.

*(Well, probably. Determining who holds copyright is complicated and this is not legal advice. But it does for sure mean you get a say in this decision!)

Timeline: Please answer now! If you agree, replying with the word “yes” is enough.

If you disagree, please tell us and we’ll do our best to address your concerns and find a resolution. We will resolve all contributor concerns before changing the license.

If we haven’t heard from you in a week, we’ll assume the email address we had for you is out of date and move on to hounding you in a different channel... ;)

FAQ:

To what specifically am I agreeing? If you respond “yes, I agree”, you are giving us permission to change the license of all your contributions to PEcAn from the NCSA Open Source license to the BSD 3-clause license. We will ask you once and keep your answer on file, then refer to it to relicense each individual PEcAn package when all its contributors have signed off on the change. It may take some time for all the packages to update — we need to track down some contributors who have not been in regular touch for some time.

What’s the difference between the old and new licenses? Both licenses are very similar — see the links above for their exact text. NCSA is more explicit about what parts (software and documentation) it covers and what rights the user has, but both licenses are identical in the uses they allow.

If they’re so similar, why change? We initially used the NCSA license because we liked the more explicit user rights, but few other projects have adopted it and the BSD3 license is now more widely recognized. One big motivation for this change is that we would like the option of submitting the PEcAn R packages to CRAN, which will require us to choose from a list of standard licenses that includes BSD3 but not NCSA.

How did you decide to ask me? We ran git shortlog -se —all in the PEcAn Git repository and found your name there. Even if your involvement was just one commit long ago, we still consider you a PEcAn contributor and we want your agreement for this change.

Didn’t you just hassle me about this in Slack? Yes. Sorry for the repeated messages, but if you’re reading this it means we haven't yet seen an answer from you in any medium.

Thank you again for being part of PEcAn, and we look forward to your response.

For the whole team,

Rob Kooper, Mike Dietze, David LeBauer, Chris Black

— Reply to this email directly, view it on GitHub https://github.com/PecanProject/pecan/issues/3364#issuecomment-2311206067, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK7ZBT5U72V3V3C2LJ5XWJLZTOS4VAVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJRGIYDMMBWG4 . You are receiving this because you were mentioned.Message ID: @.***>

hangyakuzero avatar Aug 27 '24 08:08 hangyakuzero

Yes

kzarada avatar Aug 27 '24 10:08 kzarada

@rahul799 says yes via email

infotroph avatar Aug 27 '24 11:08 infotroph

Yes (I have contributed literally 1 character to your project, so I don't really feel like I should have a say, but I'll provide my consent lest hold anyone up.)

aabaris avatar Aug 27 '24 13:08 aabaris

Yes! Sent from my iPhoneOn Aug 27, 2024, at 8:48 AM, aabaris @.***> wrote: Yes (I have contributed literally 1 character to your project, so I don't really feel like I should have a say, but I'll provide my consent lest hold anyone up.)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

marissakivi avatar Aug 27 '24 18:08 marissakivi

yes

[https://emailsignature.ucmerced.edu.672elmp01.blackmesh.com/ucm_new-logo.png] DR. BAILEY MORRISON she/her/hers

ASSISTANT PROJECT SCIENTIST

CIVIL AND ENVIRONMENTAL ENGINEERING

5200 Lake Road | Merced, California 95343 @.*** I only check and respond to emails twice a day. If you need to reach me for an emergency and have my phone number please call me.


From: Chris Black @.> Sent: Monday, August 26, 2024 3:20 PM To: PecanProject/pecan @.> Cc: Bailey Morrison @.>; Mention @.> Subject: [PecanProject/pecan] PEcAn license change (Issue #3364)

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

— Reply to this email directly, view it on GitHubhttps://github.com/PecanProject/pecan/issues/3364, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIIOOOULFFC7CAYHZSX4LPTZTOSZFAVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DOOBYGY2DAMI. You are receiving this because you were mentioned.Message ID: @.***>

bailsofhay avatar Aug 27 '24 20:08 bailsofhay

Yes.

On Mon, 26 Aug 2024 at 16:20, Chris Black @.***> wrote:

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

— Reply to this email directly, view it on GitHub https://github.com/PecanProject/pecan/issues/3364, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3N3QZMG3O54ZFSM3ZDX2LZTOSZBAVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DOOBYGY2DAMI . You are receiving this because you were mentioned.Message ID: @.***>

-- Andria Dawson (she / her) Associate Professor of Mathematics | Mount Royal University Adjunct Professor of Biology | University of Calgary @.*** (403) 440-7085

The place we call Calgary is on the beautiful Treaty 7 land, where the Bow River meets the Elbow River; the traditional Blackfoot name for this place of meeting is “Moh’kins’tsis”.

andydawson avatar Aug 27 '24 20:08 andydawson

Yes, I agree

On Aug 26, 2024, at 18:20, Chris Black @.***> wrote:

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

@aabaris https://github.com/aabaris @UncleWeeds https://github.com/UncleWeeds @abhinav52000 https://github.com/abhinav52000 @helge22a https://github.com/helge22a @Amanskywalker https://github.com/Amanskywalker @andydawson https://github.com/andydawson @TonyCohen https://github.com/TonyCohen @bailsofhay https://github.com/bailsofhay @bcow https://github.com/bcow @braczka https://github.com/braczka @djaiswal https://github.com/djaiswal @ecamo19 https://github.com/ecamo19 @gbromley https://github.com/gbromley @Snafkin547 https://github.com/Snafkin547 @hmb1 https://github.com/hmb1 @jbowers20 https://github.com/jbowers20 @jingxia https://github.com/jingxia @JoshuaPloshay https://github.com/JoshuaPloshay @jsimkins2 https://github.com/jsimkins2 @julianpistorius https://github.com/julianpistorius @kzarada https://github.com/kzarada @kragosta https://github.com/kragosta @kimberlyh66 https://github.com/kimberlyh66 @lovelilyinfall https://github.com/lovelilyinfall @hangyakuzero https://github.com/hangyakuzero @marissakivi https://github.com/marissakivi @mtmarsh2 https://github.com/mtmarsh2 @MukulMaheshwari https://github.com/MukulMaheshwari @Parthmadan-1 https://github.com/Parthmadan-1 @rahul799 https://github.com/rahul799 @rykelly https://github.com/rykelly @Sarthakaga15 https://github.com/Sarthakaga15 @gsrohde https://github.com/gsrohde @shubhamagarwal92 https://github.com/shubhamagarwal92 @Yiyiyimu https://github.com/Yiyiyimu @sl4397 https://github.com/sl4397 @Viskari https://github.com/Viskari @zhangwenx https://github.com/zhangwenx @yan130 https://github.com/yan130 — Reply to this email directly, view it on GitHub https://github.com/PecanProject/pecan/issues/3364, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUBEDSXGFY456ZUUWW2MX3ZTOSZDAVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DOOBYGY2DAMI. You are receiving this because you were mentioned.

rykelly avatar Aug 29 '24 13:08 rykelly

Yes.

jsimkins2 avatar Aug 29 '24 14:08 jsimkins2

@braczka says 👍 by email

infotroph avatar Aug 29 '24 14:08 infotroph

Yes. @.***)


Scott Rohde Scientific Web Programmer Carl R. Woese Institute for Genomic Biology University of Illinois at Urbana-Champaign

From: Chris Black @.> Date: Monday, August 26, 2024 at 5:20 PM To: PecanProject/pecan @.> Cc: Rohde, Scott @.>, Mention @.> Subject: [PecanProject/pecan] PEcAn license change (Issue #3364)

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

· @aabarishttps://urldefense.com/v3/__https:/github.com/aabaris__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnhyrKGlw$

· @UncleWeedshttps://urldefense.com/v3/__https:/github.com/UncleWeeds__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnQZGp9sg$

· @abhinav52000https://urldefense.com/v3/__https:/github.com/abhinav52000__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkvWKw4aw$

· @helge22ahttps://urldefense.com/v3/__https:/github.com/helge22a__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkjA3M2ww$

· @Amanskywalkerhttps://urldefense.com/v3/__https:/github.com/Amanskywalker__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnk1y0STA$

· @andydawsonhttps://urldefense.com/v3/__https:/github.com/andydawson__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkhB-VWLw$

· @TonyCohenhttps://urldefense.com/v3/__https:/github.com/TonyCohen__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlMRQZEew$

· @bailsofhayhttps://urldefense.com/v3/__https:/github.com/bailsofhay__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnM6_Mbiw$

· @bcowhttps://urldefense.com/v3/__https:/github.com/bcow__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvn_-GPyLg$

· @braczkahttps://urldefense.com/v3/__https:/github.com/braczka__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkY8g136A$

· @djaiswalhttps://urldefense.com/v3/__https:/github.com/djaiswal__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlMaewibA$

· @ecamo19https://urldefense.com/v3/__https:/github.com/ecamo19__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvny_AWy5g$

· @gbromleyhttps://urldefense.com/v3/__https:/github.com/gbromley__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvk2sFL-8w$

· @Snafkin547https://urldefense.com/v3/__https:/github.com/Snafkin547__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlaSmZ0pg$

· @hmb1https://urldefense.com/v3/__https:/github.com/hmb1__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvk4wEQ_ZQ$

· @jbowers20https://urldefense.com/v3/__https:/github.com/jbowers20__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkLFMI1MA$

· @jingxiahttps://urldefense.com/v3/__https:/github.com/jingxia__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkPuj08nw$

· @JoshuaPloshayhttps://urldefense.com/v3/__https:/github.com/JoshuaPloshay__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvm2VE-QiQ$

· @jsimkins2https://urldefense.com/v3/__https:/github.com/jsimkins2__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkpCxyZNw$

· @julianpistoriushttps://urldefense.com/v3/__https:/github.com/julianpistorius__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvmT4Hb3uQ$

· @kzaradahttps://urldefense.com/v3/__https:/github.com/kzarada__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlMDmwN7Q$

· @kragostahttps://urldefense.com/v3/__https:/github.com/kragosta__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlVwQ4USw$

· @kimberlyh66https://urldefense.com/v3/__https:/github.com/kimberlyh66__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvm8m4WqHA$

· @lovelilyinfallhttps://urldefense.com/v3/__https:/github.com/lovelilyinfall__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvl6aMx6Yg$

· @hangyakuzerohttps://urldefense.com/v3/__https:/github.com/hangyakuzero__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnMXGetkg$

· @marissakivihttps://urldefense.com/v3/__https:/github.com/marissakivi__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvmLsjYS6g$

· @mtmarsh2https://urldefense.com/v3/__https:/github.com/mtmarsh2__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvksoZ_mjA$

· @MukulMaheshwarihttps://urldefense.com/v3/__https:/github.com/MukulMaheshwari__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvndmEpW4A$

· @Parthmadan-1https://urldefense.com/v3/__https:/github.com/Parthmadan-1__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvn0N8EEPw$

· @rahul799https://urldefense.com/v3/__https:/github.com/rahul799__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvl2iNEnnA$

· @rykellyhttps://urldefense.com/v3/__https:/github.com/rykelly__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlXB942rQ$

· @Sarthakaga15https://urldefense.com/v3/__https:/github.com/Sarthakaga15__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvmBe1Ehqw$

· @gsrohdehttps://urldefense.com/v3/__https:/github.com/gsrohde__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvlltcQfvg$

· @shubhamagarwal92https://urldefense.com/v3/__https:/github.com/shubhamagarwal92__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnPTkRF8w$

· @Yiyiyimuhttps://urldefense.com/v3/__https:/github.com/Yiyiyimu__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnxDKVooA$

· @sl4397https://urldefense.com/v3/__https:/github.com/sl4397__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvl__zMcWA$

· @Viskarihttps://urldefense.com/v3/__https:/github.com/Viskari__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvm0TnXgeA$

· @zhangwenxhttps://urldefense.com/v3/__https:/github.com/zhangwenx__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvnaatimhg$

· @yan130https://urldefense.com/v3/__https:/github.com/yan130__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvl10DdFWw$

— Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/PecanProject/pecan/issues/3364__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvkJhHVqHQ$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AANAXEGQG2GXXBG5S43HSN3ZTOSY7AVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DOOBYGY2DAMI__;!!DZ3fjg!__kIvCTFvv1G9DtT3zxYFKZCI1e94ODPIho8HezfYfa6Vd4UphI1pZmbYazqb4BdwiAE_v0B_m1DJJ5NFvmVrH17qw$. You are receiving this because you were mentioned.Message ID: @.***>

gsrohde avatar Aug 30 '24 17:08 gsrohde

Yes!

On Mon, Aug 26, 2024 at 3:20 PM Chris Black @.***> wrote:

If you are tagged below: Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? If so, please comment "yes" below.

Both licenses are very similar, but BSD 3-clause is more widely recognized, importantly including being on the list of licenses CRAN will accept. We assume by default that every PEcAn contributor retains copyright on their contributions, so we want consent for this change from ALL PEcAn contributors. You can agree once here and we will use it for each PEcAn package you have code in.

Many, many authors are not tagged here because they have already given their consent by Slack or email -- thank you for your responses thus far!

— Reply to this email directly, view it on GitHub https://github.com/PecanProject/pecan/issues/3364, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVU7NXB6R4VGEUMHNJVF7TZTOSZHAVCNFSM6AAAAABNE4DUL2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4DOOBYGY2DAMI . You are receiving this because you were mentioned.Message ID: @.***>

helge22a avatar Sep 03 '24 19:09 helge22a

@bcow says yes by email 👍

infotroph avatar Sep 04 '24 00:09 infotroph

Approved by email, linkedIn, and/or text message: @djaiswal @kimberlyh66 @julianpistorius Andrew Shirk 👍

infotroph avatar Sep 23 '24 22:09 infotroph

@Snafkin547 says yes by email 👍

infotroph avatar Sep 25 '24 18:09 infotroph

Tagging @sbs2019 as well -- Do we have your permission to switch PEcAn's open source license from NCSA to BSD-3? See thread above.

@sbs2019 says yes by email 👍

infotroph avatar Nov 25 '24 17:11 infotroph

Carl Davidson (not tagged above, couldn't find his handle) says yes via LinkedIn) 👍

infotroph avatar Dec 16 '24 22:12 infotroph

@Viskari says yes by email 👍

infotroph avatar Nov 18 '25 17:11 infotroph

@jbowers20 said yes by email

mdietze avatar Nov 18 '25 19:11 mdietze