Skip to content

Conversation

@flarnie
Copy link

@flarnie flarnie commented Dec 5, 2017

In the past there was not info and support to add these docs to all Facebook Open Source projects. It's a useful measure that we can take now to create a healthy, welcoming open source community. :)

why make this change?:
Facebook Open Source provides a Code of Conduct statement for all
projects to follow, to promote a welcoming and safe open source community.

Exposing the COC via a separate markdown file is a standard being
promoted by Github via the Community Profile in order to meet their Open
Source Guide's recommended community standards.

As you can see, adding this file will improve the Mcrouter community profile
checklist and increase the visibility of our COC.

test plan:
Viewing it on my branch -
screen shot 2017-12-05 at 6 23 01 am
screen shot 2017-12-05 at 6 23 19 am

issue:
internal task t23481323

To foster an active and welcoming open source community, let's offer tips to first time contributors via the 'CONTRIBUTING.md' doc.

This links to a Code of Conduct doc - a follow up commit will add the Code of Conduct.
In the past there was not info and support to add these docs to all Facebook Open Source projects. It's a useful measure that we can take now to create a healthy, welcoming open source community. :)

**why make this change?:**
Facebook Open Source provides a Code of Conduct statement for all
projects to follow, to promote a welcoming and safe open source community.

Exposing the COC via a separate markdown file is a standard being
promoted by Github via the Community Profile in order to meet their Open
Source Guide's recommended community standards.

As you can see, adding this file will improve [the Mcrouter community profile](https://github.com/facebook/mcrouter/community)
checklist and increase the visibility of our COC.

**test plan:**
Viewing it on my branch -
(Flarnie will insert screenshots)

**issue:**
internal task t23481323
@thias
Copy link

thias commented Aug 13, 2020

This has been done as #313 so this could be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants