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

Fill placeholder in new "Code of Conduct" template #1269

Closed
krlmlr opened this issue Nov 11, 2020 · 3 comments · Fixed by #1374
Closed

Fill placeholder in new "Code of Conduct" template #1269

krlmlr opened this issue Nov 11, 2020 · 3 comments · Fixed by #1374

Comments

@krlmlr
Copy link
Member

krlmlr commented Nov 11, 2020

See 3b2998d#diff-b2396aff8b9801c5504d37c25f47f8614ff68ad547f8993ca66c333310c8ee4dR62-R63.

What's a good value for the "INSERT CONTACT METHOD" placeholder?

CC @batpigandme.

@batpigandme
Copy link
Contributor

Like a default value, or the name for the placeholder? If the latter, I like INSERT CONTACT METHOD.

@jennybc
Copy link
Member

jennybc commented Nov 17, 2020

At the very least, for all of our repos, we should be populating that placeholder. Should we say "contact the maintainer"? Then we'd also need some sort of fall back if the complaint involves the maintainer.

In general, we should either expose an argument in use_code_of_conduct() to populate this or I should be messaging, alerting people to the fact that the template requires some manual modification.

So I'm seeking your advice about:

  1. Is the maintainer the best blanket recommendation?
  2. For tidyverse/r-lib org-owned packages, at least, what's the fall back beyond maintainer? Is there an RStudio email appropriate for this?

@hadley
Copy link
Member

hadley commented Nov 19, 2020

I think we should add an argument, and for our repos make it an email address (maybe me + Mara?).

hadley added a commit that referenced this issue Feb 24, 2021
hadley added a commit that referenced this issue Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants