Nr-309883 migrate from opensource newrelic #18902
Conversation
|
Hi @ubanerjeeNR 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
ubanerjeeNR
added
content
|
| @@ -0,0 +1,35 @@ | |||
| --- | |||
| title: New Relic Open Source Community Code of Conduct - Reporting Guide | |||
There was a problem hiding this comment.
@ubanerjeeNR We use sentence case even in titles (https://docs.newrelic.com/docs/style-guide/capitalization/capitalization/#heading_caps)
I think this should be: "New Relic open source community code of conduct - reporting guide"
| @@ -0,0 +1,35 @@ | |||
| --- | |||
| title: New Relic Open Source Community Code of Conduct - Reporting Guide | |||
| metaDescription: Learn how to report violations of the New Relic code of conduct for open source community. | |||
There was a problem hiding this comment.
As a habit, I usually put quotation marks around the title and metadescription fields, because characters like apostrophes can break the build
| - Your contact info (so we can get in touch with you if we need to follow up). | ||
| - Names (real, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well. | ||
| - When and where the incident occurred. Please be as specific as possible. | ||
| - Your account of what occurred. If there is a publicly available record (e.g., a mailing list archive or Slack history) please include a link. |
There was a problem hiding this comment.
We don't typically use e.g. or i.e. https://docs.newrelic.com/docs/style-guide/word-choice/usage-dictionary/#eg
There was a problem hiding this comment.
But... license docs are where we make exceptions to a lot of these little rules :)
There was a problem hiding this comment.
My bad - fixed it.
| freshnessValidatedDate: never | ||
| --- | ||
|
|
||
| We believe in the power of Open Source to bring together developers and ideas to solve tricky problems and create the innovative software the world needs. |
There was a problem hiding this comment.
"Open Source" should be "open source"
| We respect all people in our community, regardless of their background or the extent of their contributions, and encourage participation from diverse sources. This Code of Conduct documents the principles we encourage in, and expect of, the Open Source community. | ||
|
|
||
| - Be friendly and patient. | ||
| - Be welcoming.<p/>We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to, members of any race, ethnicity, culture, national origin, colour, immigration status, social or economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability. |
There was a problem hiding this comment.
Let's remove things like these <p /> tags
There was a problem hiding this comment.
Sure - why though?
|
|
||
| <Collapser | ||
| id="one-catalog" | ||
| title="New Relic One Catalog" |
There was a problem hiding this comment.
We don't use the brand "New Relic One" anymore. It should just be "New Relic catalog"
|
|
No description provided.