Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Authorship best practices #107

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dlebauer
Copy link
Contributor

@dlebauer dlebauer commented Jan 22, 2025

Drafted best practices for offering co-authorship and otherwise revised authorship section.

Motivated by unfortunate experiences.

Comment on lines +45 to +62
- **Template letter to collaborators**

```
**Subject:** Request for Contributions and Feedback on [Product Name]

Dear [Collaborator Name(s)],

I hope this message finds you well. As part of the [Project Title], we are currently drafting [Product Name]. I am reaching out to ensure that all collaborators have the opportunity to contribute and review the manuscript.

Here are the key details:
- **Scope of Work:**
- **Target Journal/Outlet:**
- **Current Timeline:**

We would appreciate your input at this stage. Contributions can include [specific examples].

Thank you for your time and collaboration!
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are not typically going to be lead authors, so unlikely that we will be writing this email. Still, it could be a useful template for lead authors we collaborate with or getting feedback on, say, a part of the methods section.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was indeed motivated by a 'we are submitting this tomorrow with your name on it' email that came out of the blue.

So the audience really is more external. But that also brings up the question - how to set expectations so that they will get to those who need to hear it?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants