You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR was automatically generated by the
update-native-provider-workflows workflow in the pulumi/ci-mgmt repo,
from commit a5ca43f7b3bbfe7daa9717a5e6e9d86eb3d6202b.
Copy file name to clipboardExpand all lines: CODE-OF-CONDUCT.md
+17-10Lines changed: 17 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@ include:
19
19
* Gracefully accepting constructive criticism
20
20
* Focusing on what is best for the community
21
21
* Showing empathy towards other community members
22
+
* Contribute in a positive and constructive way
22
23
23
24
Examples of unacceptable behavior by participants include:
24
25
@@ -30,6 +31,12 @@ Examples of unacceptable behavior by participants include:
30
31
address, without explicit permission
31
32
* Other conduct which could reasonably be considered inappropriate in a
32
33
professional setting
34
+
35
+
## Our Community Guidelines
36
+
* Be clear and stay on topic. Communicating with strangers on the Internet can make it hard to convey or read tone, and sarcasm is frequently misunderstood. Try to use clear language, and think about how the other person will receive it.
37
+
* Don’t cross-post the same thing in multiple GitHub Discussion topics or multiple Slack channels. This can make it difficult for people answering your questions and creates "scrollback spam".
38
+
* Public discussion is preferred to private. Avoid using Slack DMs for questions, and instead share them in public Slack channels or GitHub Discussion threads. This allows a larger audience to both share their knowledge as well as learn from your question or issue. If you're having a problem, chances are someone else is having a similar problem. Learning in public is a community contribution.
39
+
* Minimize notifications to other community members. Avoid tagging other community members in Slack messages or Discussion threads, unless you are replying to something specific. Community members are here to help each other, but are not "on call" for support, and we expect everyone to try to minimize "notification fatigue". If your issue is time-sensitive or critical, use methods like [email protected] instead.
33
40
34
41
## Our Responsibilities
35
42
@@ -38,19 +45,19 @@ behavior and are expected to take appropriate and fair corrective action in
38
45
response to any instances of unacceptable behavior.
39
46
40
47
Project maintainers have the right and responsibility to remove, edit, or
41
-
reject comments, commits, code, wiki edits, issues, and other contributions
42
-
that are not aligned to this Code of Conduct, or to ban temporarily or
43
-
permanently any contributor for other behaviors that they deem inappropriate,
44
-
threatening, offensive, or harmful.
48
+
reject comments, commits, code, wiki edits, issues, GitHub Discussions posts,
49
+
and other contributions that are not aligned to this Code of Conduct, or to ban
50
+
temporarily or permanently any contributor for other behaviors that they deem
51
+
inappropriate, threatening, offensive, or harmful.
45
52
46
53
## Scope
47
54
48
-
This Code of Conduct applies both within project spaces and in public spaces
49
-
when an individual is representing the project or its community. Examples of
50
-
representing a project or community include using an official project e-mail
51
-
address, posting via an official social media account, or acting as an appointed
52
-
representative at an online or offline event. Representation of a project may be
53
-
further defined and clarified by project maintainers.
55
+
This Code of Conduct applies both within project spaces (including the Community Slack
56
+
and GitHub Discussions forums) and in public spaces when an individual is representing the
57
+
project or its community. Examples of representing a project or community include
58
+
using an official project e-mail address, posting via an official social media account,
59
+
or acting as an appointed representative at an online or offline event. Representation
60
+
of a project may be further defined and clarified by project maintainers.
0 commit comments