GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 #1083
Comments
|
@johndunne13 thanks, will get this change implemented. I note that we have no data published on ESGF for the |
|
I would defer to David Paynter (cc'd) on GFDL-GLOBAL-LBL, but he is on
paternity leave for the next few weeks.
…On Wed, Jun 8, 2022 at 11:52 AM Paul J. Durack ***@***.***> wrote:
@johndunne13 <https://github.com/johndunne13> thanks, will get this
change implemented.
I note that we have no data published on ESGF for the GFDL-GLOBAL-LBL
model <https://esgf-node.llnl.gov/search/cmip6/?source_id=GFDL-GLOBAL-LBL>,
is that an oversight, are we expecting data imminently, or should we
deregister this entry?
—
Reply to this email directly, view it on GitHub
<#1083 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGUJAMQTBD6ZVPNA5VHUIM3VOC6UFANCNFSM5YG76ECA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@johndunne13 thanks. I can get these licenses updated, and await an update from David on And a huge congrats to David and family too! |
|
@johndunne13 thanks for the update, all changes noted above are now in place. Please review CMIP6_source_id_licenses.html and let me know of any tweaks required. I will leave this issue open, awaiting the update from David RE: |
|
Hi David, first up congrats on welcoming the new family member! I do hope sleep is abundant in the Paynter household.
I am just circling around on the question regarding data submission of GFDL-GLOBAL-LBL. Did you have a plan to contribute data to RFMIP?
Cheers,
P
From: "Paul J. Durack" ***@***.***>
Reply-To: WCRP-CMIP/CMIP6_CVs ***@***.***>
Date: Wednesday, June 8, 2022 at 12:36 PM
To: WCRP-CMIP/CMIP6_CVs ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
@johndunne13<https://urldefense.us/v3/__https:/github.com/johndunne13__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTdASSaJI$> thanks for the update, all changes noted above are now in place. Please review CMIP6_source_id_licenses.html<https://urldefense.us/v3/__https:/wcrp-cmip.github.io/CMIP6_CVs/docs/CMIP6_source_id_licenses.html__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTmAk2QiU$> and let me know of any tweaks required.
I will leave this issue open, awaiting the update from David RE: GFDL-GLOBAL-LBL, after which we can update that final license (or deregister) and close the issue
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https:/github.com/WCRP-CMIP/CMIP6_CVs/issues/1083*issuecomment-1150322400__;Iw!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTTwauiIY$>, or unsubscribe<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/AE2HBKC2U4NTZ2BUY6F7ZXDVODY5LANCNFSM5YG76ECA__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTG6943ag$>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Hi David, just circling around on this query. Did you have plans to publish GFDL-GLOBAL-LBL output on ESGF, or should we rather deregister this source_id from the database?
Cheers,
P
From: "Durack, Paul J." ***@***.***>
Date: Friday, July 1, 2022 at 1:30 PM
To: ***@***.***" ***@***.***>
Cc: WCRP-CMIP/CMIP6_CVs ***@***.***>, WCRP-CMIP/CMIP6_CVs ***@***.***>, ***@***.***" ***@***.***>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
Hi David, first up congrats on welcoming the new family member! I do hope sleep is abundant in the Paynter household.
I am just circling around on the question regarding data submission of GFDL-GLOBAL-LBL. Did you have a plan to contribute data to RFMIP?
Cheers,
P
From: "Paul J. Durack" ***@***.***>
Reply-To: WCRP-CMIP/CMIP6_CVs ***@***.***>
Date: Wednesday, June 8, 2022 at 12:36 PM
To: WCRP-CMIP/CMIP6_CVs ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
@johndunne13<https://urldefense.us/v3/__https:/github.com/johndunne13__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTdASSaJI$> thanks for the update, all changes noted above are now in place. Please review CMIP6_source_id_licenses.html<https://urldefense.us/v3/__https:/wcrp-cmip.github.io/CMIP6_CVs/docs/CMIP6_source_id_licenses.html__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTmAk2QiU$> and let me know of any tweaks required.
I will leave this issue open, awaiting the update from David RE: GFDL-GLOBAL-LBL, after which we can update that final license (or deregister) and close the issue
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https:/github.com/WCRP-CMIP/CMIP6_CVs/issues/1083*issuecomment-1150322400__;Iw!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTTwauiIY$>, or unsubscribe<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/AE2HBKC2U4NTZ2BUY6F7ZXDVODY5LANCNFSM5YG76ECA__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTG6943ag$>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
Hi Paul,
So sorry for the slow reply, your request got a bit lost in my backlog of
tasks to catch up on. I think the source_id of GFDL-GLOBAL-LBL was created
in error, as we used GFDL-RFM-DISORT source_id for our LBL
calculations. Thanks
for the congratulations on our new family member. Unfortunately, sleep is
a commodity we are still in short supply of!
Best
David
…On Wed, Jul 27, 2022 at 6:43 PM Durack, Paul J. ***@***.***> wrote:
Hi David, just circling around on this query. Did you have plans to
publish GFDL-GLOBAL-LBL output on ESGF, or should we rather deregister this
source_id from the database?
Cheers,
P
*From: *"Durack, Paul J." ***@***.***>
*Date: *Friday, July 1, 2022 at 1:30 PM
*To: ***@***.***" ***@***.***>
*Cc: *WCRP-CMIP/CMIP6_CVs <
***@***.***>,
WCRP-CMIP/CMIP6_CVs ***@***.***>, ***@***.***"
***@***.***>
*Subject: *Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC
BY-SA 4.0 to CC BY 4.0 (Issue #1083)
Hi David, first up congrats on welcoming the new family member! I do hope
sleep is abundant in the Paynter household.
I am just circling around on the question regarding data submission of
GFDL-GLOBAL-LBL. Did you have a plan to contribute data to RFMIP?
Cheers,
P
*From: *"Paul J. Durack" ***@***.***>
*Reply-To: *WCRP-CMIP/CMIP6_CVs <
***@***.***>
*Date: *Wednesday, June 8, 2022 at 12:36 PM
*To: *WCRP-CMIP/CMIP6_CVs ***@***.***>
*Cc: *Subscribed ***@***.***>
*Subject: *Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC
BY-SA 4.0 to CC BY 4.0 (Issue #1083)
@johndunne13
<https://urldefense.us/v3/__https:/github.com/johndunne13__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTdASSaJI$>
thanks for the update, all changes noted above are now in place. Please
review CMIP6_source_id_licenses.html
<https://urldefense.us/v3/__https:/wcrp-cmip.github.io/CMIP6_CVs/docs/CMIP6_source_id_licenses.html__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTmAk2QiU$>
and let me know of any tweaks required.
I will leave this issue open, awaiting the update from David RE:
GFDL-GLOBAL-LBL, after which we can update that final license (or
deregister) and close the issue
—
Reply to this email directly, view it on GitHub
<https://urldefense.us/v3/__https:/github.com/WCRP-CMIP/CMIP6_CVs/issues/1083*issuecomment-1150322400__;Iw!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTTwauiIY$>,
or unsubscribe
<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/AE2HBKC2U4NTZ2BUY6F7ZXDVODY5LANCNFSM5YG76ECA__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTG6943ag$>
.
You are receiving this because you are subscribed to this thread.[image:
Image removed by sender.]Message ID: <WCRP-CMIP/CMIP6_CVs/issues/1083/
***@***.***>
|
|
Thanks for the update @david! If this is the case, I will deregister the erroneous registration of `GFDL-GLOBAL-LBL`.
And I do wish you well RE: sleep, we’re still running a decent debt with our not yet 2 yr old – I wish you good luck, and long, sweet dreams
From: David Paynter - NOAA Federal ***@***.***>
Date: Wednesday, July 27, 2022 at 5:44 PM
To: "Durack, Paul J." ***@***.***>
Cc: WCRP-CMIP/CMIP6_CVs ***@***.***>, ***@***.***" ***@***.***>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
Hi Paul,
So sorry for the slow reply, your request got a bit lost in my backlog of tasks to catch up on. I think the source_id of GFDL-GLOBAL-LBL was created in error, as we used GFDL-RFM-DISORT source_id for our LBL calculations. Thanks for the congratulations on our new family member. Unfortunately, sleep is a commodity we are still in short supply of!
Best
David
On Wed, Jul 27, 2022 at 6:43 PM Durack, Paul J. ***@***.******@***.***>> wrote:
Hi David, just circling around on this query. Did you have plans to publish GFDL-GLOBAL-LBL output on ESGF, or should we rather deregister this source_id from the database?
Cheers,
P
From: "Durack, Paul J." ***@***.******@***.***>>
Date: Friday, July 1, 2022 at 1:30 PM
To: ***@***.******@***.***>" ***@***.******@***.***>>
Cc: WCRP-CMIP/CMIP6_CVs ***@***.******@***.***>>, WCRP-CMIP/CMIP6_CVs ***@***.******@***.***>>, ***@***.******@***.***>" ***@***.******@***.***>>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
Hi David, first up congrats on welcoming the new family member! I do hope sleep is abundant in the Paynter household.
I am just circling around on the question regarding data submission of GFDL-GLOBAL-LBL. Did you have a plan to contribute data to RFMIP?
Cheers,
P
From: "Paul J. Durack" ***@***.******@***.***>>
Reply-To: WCRP-CMIP/CMIP6_CVs ***@***.******@***.***>>
Date: Wednesday, June 8, 2022 at 12:36 PM
To: WCRP-CMIP/CMIP6_CVs ***@***.******@***.***>>
Cc: Subscribed ***@***.******@***.***>>
Subject: Re: [WCRP-CMIP/CMIP6_CVs] GFDL CMIP6 licensing update from CC BY-SA 4.0 to CC BY 4.0 (Issue #1083)
@johndunne13<https://urldefense.us/v3/__https:/github.com/johndunne13__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTdASSaJI$> thanks for the update, all changes noted above are now in place. Please review CMIP6_source_id_licenses.html<https://urldefense.us/v3/__https:/wcrp-cmip.github.io/CMIP6_CVs/docs/CMIP6_source_id_licenses.html__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTmAk2QiU$> and let me know of any tweaks required.
I will leave this issue open, awaiting the update from David RE: GFDL-GLOBAL-LBL, after which we can update that final license (or deregister) and close the issue
—
Reply to this email directly, view it on GitHub<https://urldefense.us/v3/__https:/github.com/WCRP-CMIP/CMIP6_CVs/issues/1083*issuecomment-1150322400__;Iw!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTTwauiIY$>, or unsubscribe<https://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/AE2HBKC2U4NTZ2BUY6F7ZXDVODY5LANCNFSM5YG76ECA__;!!G2kpM7uM-TzIFchu!mU3QBcFjDX3ypbnY7ayQth2awkllEDvto5QhFswGrulqik_yjwTMDB_cXzpTG6943ag$>.
You are receiving this because you are subscribed to this thread.Error! Filename not specified.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
In accordance with Paul Durack's email of June 2, 2022 entitled "CMIP6 data licensing update" recommending all existing CC BY-SA 4.0 licenses be relaxed to CC BY 4.0, GFDL agrees to update this licensing to CC BY 4.0 for all its contributions, including: GFDL-ESM4, GFDL-CM4, GFDL-AM4, GFDL-ESM2M, GFDL-CM4C192, GFDL-GLOBAL-LBL, GFDL-GRTCODE, GFDL-OM4p5B, and GFDL-RFM-DISORTN. Please let me know if any additional action is necessary on GFDL's part.
Thanks, John Dunne
On behalf of NOAA/OAR/GFDL
The text was updated successfully, but these errors were encountered: