Skip to content
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

Set up rules how to use/cite Mistra #12

Open
3 tasks
pb866 opened this issue Apr 5, 2019 · 3 comments
Open
3 tasks

Set up rules how to use/cite Mistra #12

pb866 opened this issue Apr 5, 2019 · 3 comments
Labels
decision A decision is needed to progress documentation Issues related with the manual or documentation in the source code. license Issues related to licensing, citing, co-authorships and other contributions strategy Discussions about development strategies and promoting Mistra

Comments

@pb866
Copy link

pb866 commented Apr 5, 2019

We need to decide on rules and state them in the README concerning:

  • citing Mistra, when using the model
  • decide, whether we want to be informed about publications
  • do we request co-authorships under certain circumstances?

This should probably be discussed together with @Mistra-UEA.

@pb866 pb866 added documentation Issues related with the manual or documentation in the source code. decision A decision is needed to progress license Issues related to licensing, citing, co-authorships and other contributions strategy Discussions about development strategies and promoting Mistra labels Apr 5, 2019
@pb866 pb866 added this to the High Priority milestone Apr 5, 2019
@pb866 pb866 added this to Strategy and Discussions in Development Plan Apr 5, 2019
@rs028
Copy link
Collaborator

rs028 commented Apr 6, 2019

Yes, it should be discussed with the UEA group. It would be good to put this information in a text file in the main directory.

IMHO:

  1. For the moment, probably cite the 2002 JGR papers by Roland, which are the initial description of the model, and maybe the 2012 EST paper, which contains the updated chemical mechanism (until your paper supersedes it). It also depends whether Josue is still working on his paper, which would be the description of the current version.
  2. It would be nice if people let us know. We could have a page in the wiki with the list of publications.
  3. This is a bit tricky. My opinion is that co-authorship should be requested when run the model is run for somebody else and/or significant contribution is given. What constitutes significant is a bit debatable and probably should be agreed with the main authors. If somebody can take the model and use it on their own, I am happy with just a citation and maybe acknowledgements.

@pb866
Copy link
Author

pb866 commented Apr 6, 2019

I, again (scary!), absolutely agree with you.
For 1. That can be a living and breathing statement, so we can always update it, if new papers become available.
But, to have at least a slightly different opinion on a minor point. I think this information is best stored in a separate section in the README. There, the info is prominent as soon as you look at the repo. In a text file in the main folder it can get lost and never looked at. Or, we could have a markdown file and link that in the README, but I would prefer the first option.

@rs028
Copy link
Collaborator

rs028 commented Apr 6, 2019

Just common sense man, don't be alarmed :D
I am okay to have this in the README. We should draft a "protocol" and then send it to @Mistra-UEA people for comments before including it in the repo.

rs028 pushed a commit that referenced this issue Feb 24, 2021
Minor improvements, bugfix, and manual update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision A decision is needed to progress documentation Issues related with the manual or documentation in the source code. license Issues related to licensing, citing, co-authorships and other contributions strategy Discussions about development strategies and promoting Mistra
Projects
No open projects
Development Plan
Strategy and Discussions
Development

No branches or pull requests

2 participants