-
Notifications
You must be signed in to change notification settings - Fork 219
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
Short affiliation names in AUTHORS.md #897
Comments
I'm fine with short affiliations. Looking at the line wraps above, I appear to be the worst offender 😉 . |
I'm fine with short affiliations, too. However, since mine is currently the shortest I'd leave it to the others to decide. |
It seems more than half (5/9) of the "PyGMT Developers" agree with short affiliation names.
The table looks good, but making the plain markdown file more complicated. |
Could I help with this issue? It seems that it is a good first issue for me. Based on the above discussion, could we just keep the authors' full names, ORCID, and university/institute.
The second solution is to replace the authors' homepage with ORCID at the same time. Usually, we can find the authors' homepage on their ORCID websites. The maximum length is only 48 under preview and 91 in plaintext.
|
That's not always true. I'm in favor of the first solution. |
Me too, as pointed out not everybody has listed a homepage on the ORCID portal and some people don't even have a "real" homepage (execpt the linked GitHub profile). |
Cool, let's go with Solution 1 in #897 (comment) then, i.e.:
@core-man, feel free to open up a Pull Request for this, have a look at CONTRIBUTING.md to get started and don't hesitate to ask us if you need any help! |
Initial discussed in #857 (review):
The full affiliation names sometimes are longer than one line in GitHub web UI, and more than 200 characters in the plaintext markdown file (see the screenshot below).
And the full affiliation names won't be used unless when we write the first paper. So I prefer to have shorter affiliation names.
The text was updated successfully, but these errors were encountered: