[MITgcm-support] Using the MIT name in a modified version of the MITgcm, and license questions

[Chris Hill]

Hi Roland,

(1) any name is fine, noting that this is based on MITgcm somewhere as
you suggest would be fine, but
whatever name makes sense to you is OK

(2) including the 2018 license and making your code available via
Github is a good plan if that works for you

(3) no prob putting output online

Thanks,

Chris
On Wed, Oct 17, 2018 at 6:13 AM Roland Young <ryoung at lmd.jussieu.fr> wrote:
>
> Hi,
>
> Shortly we will publish a couple of papers presenting work where we have modified the MITgcm to simulate Jupiter’s upper troposphere and lower stratosphere. I have a few questions that should be resolved before the papers are finalised.
>
> (1) Our Jupiter  / giant planet model does not yet have an official name, and we have referred to it by various names during its development. But as it will now appear in print, the name we refer to it by in this and future work should be finalised. Would you prefer this name to include a reference to MIT? Or as this modification of the model is not endorsed by MIT or the MITgcm development team, perhaps you would prefer this not to be included in the name (it will be obvious from the description that it uses the MITgcm).
>
> (2) I forked my version in 2014, before the MITgcm had a LICENSE.txt file in the source code. What license do you require that I include with the software, if any, if it is distributed to others or e.g. via Github? I am happy to include the current (2018) version of the LICENSE.txt file.
>
> (3) We plan to put some model output (netCDF) into a public repository hosted by our institution, as required by our funding body. Do you have any objection to this?
>
> Best wishes,
>
> Roland Young
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mailman.mitgcm.org/mailman/listinfo/mitgcm-support