8000 Docs: CoC violation correspondants by DirtyF · Pull Request #6429 · jekyll/jekyll · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Docs: CoC violation correspondants #6429

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

Merged
merged 1 commit into from
Oct 16, 2017
Merged

Conversation

DirtyF
Copy link
Member
@DirtyF DirtyF commented Oct 15, 2017

fix #6428

@pup you seem to be the right person to handle this, maybe we should add another team mate to second you?

8000 @DirtyF DirtyF added the documentation label Oct 15, 2017
@DirtyF DirtyF requested a review from a user October 15, 2017 20:02
@ghost
Copy link
ghost commented Oct 15, 2017

yeah, definitely don't single me out. at least two people would be perfect. does anyone want to volunteer?

README.markdown Outdated
@@ -45,7 +45,7 @@ conduct.
Please adhere to this code of conduct in any interactions you have in the
Jekyll community. It is strictly enforced on all official Jekyll
repositories, websites, and resources. If you encounter someone violating
these terms, please let a [team captain](https://github.com/orgs/jekyll/teams/affinity-team-captains/members) know and we will address it as soon as possible.
these terms, please let our [correspondant](https://github.com/pup) know and we will address it as soon as possible.
Copy link

Choose a reason for hiding this comment

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

oh, preferably we could put my email address in here (olivia@fastmail.com)

@pathawks
Copy link
Member

Feel free to include me as a contact for CoC violations.

@DirtyF DirtyF requested a review from pathawks October 15, 2017 20:26
README.markdown Outdated
@@ -45,7 +45,7 @@ conduct.
Please adhere to this code of conduct in any interactions you have in the
Jekyll community. It is strictly enforced on all official Jekyll
repositories, websites, and resources. If you encounter someone violating
these terms, please let our [correspondant](https://github.com/pup) know and we will address it as soon as possible.
these terms, please let one of our core team members [Oliva](mailto:olivia@fastmail.com?subject=Jekyll%20CoC%20Violation) or Pat(mailto:pat@pathawks.com?subject=Jekyll%20CoC%20Violation) know and we will address it as soon as possible.
Copy link

Choose a reason for hiding this comment

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

Oliva -> Olivia 😄

Copy link
Member Author

Choose a reason for hiding this comment

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

Oops 😕

@DirtyF DirtyF changed the title Docs: Contact @pup for CoC violation Docs: CoC violation correspondants Oct 15, 2017
@DirtyF DirtyF requested a review from mattr- October 15, 2017 21:02
@DirtyF
Copy link
Member Author
DirtyF commented Oct 15, 2017

I think we're good with three contacts for any CoC violation.
Jekyll has now its own League of Justice ✊

@DirtyF DirtyF force-pushed the docs-coc-correspondant branch 2 times, most recently from 8d33d09 to f219a20 Compare October 15, 2017 21:27
@DirtyF DirtyF force-pushed the docs-coc-correspondant branch from f219a20 to 71a7e9f Compare October 15, 2017 21:28
@@ -45,7 +45,7 @@ conduct.
Please adhere to this code of conduct in any interactions you have in the
Jekyll community. It is strictly enforced on all official Jekyll
repositories, websites, and resources. If you encounter someone violating
these terms, please let a [team captain](https://github.com/orgs/jekyll/teams/affinity-team-captains/members) know and we will address it as soon as possible.
these terms, please let one of our core team members [Olivia](mailto:olivia@jekyllrb.com?subject=Jekyll%20CoC%20Violation), [Pat](mailto:pat@jekyllrb.com?subject=Jekyll%20CoC%20Violation), [Matt](mailto:matt@jekyllrb.com?subject=Jekyll%20CoC%20Violation) or [Parker](mailto:parker@jekyllrb.com?subject=Jekyll%20CoC%20Violation) know and we will address it as soon as possible.
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure that jekyllrb.com email addresses are set up or are they forwarded to our other emails?

Copy link
Member Author

Choose a reason for hiding this comment

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

@mattr- @parkr kindly offered to configure this. 📫

Copy link
Member

Choose a reason for hiding this comment

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

oh, excellent. i missed that comment in the other issue.

Copy link
Member

Choose a reason for hiding this comment

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

All set up! You too, @DirtyF 😄 I went with first names – if you'd prefer something else, please let me know!

Copy link
Member Author

Choose a reason for hiding this comment

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

@parkr 🍷 cheers mate!

Copy link
Member
@mattr- mattr- left a comment

Choose a reason for hiding this comment

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

:shipit:

@mattr-
Copy link
Member
mattr- commented Oct 16, 2017

@jekyllbot: merge +dev

@jekyllbot jekyllbot merged commit a5f8cb7 into master Oct 16, 2017
@jekyllbot jekyllbot deleted the docs-coc-correspondant branch October 16, 2017 00:51
jekyllbot added a commit that referenced this pull request Oct 16, 2017
@jekyll jekyll locked and limited conversation to collaborators Jul 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

code of conduct enforcement contacts are not publicly visible
5 participants
0