communication: name the No Solicitation policy and link to it from each platform guideline#9064
Open
dims wants to merge 1 commit into
Open
communication: name the No Solicitation policy and link to it from each platform guideline#9064dims wants to merge 1 commit into
No Solicitation policy and link to it from each platform guideline#9064dims wants to merge 1 commit into
Conversation
…orm guidelines The community-wide policy on unsolicited commercial content already existed in communication/README.md under 'Appropriate Content for Community Resources', but nothing pointed to it and it had no citable name. Retitle it 'No Solicitation' and add a one-line cross-reference from each platform guideline (Slack, Discuss, mailing lists, Zoom, calendar) and from the moderation guidelines, so moderators on any platform have canonical policy text to cite. Signed-off-by: Davanum Srinivas <[email protected]>
kubernetes-prow
Bot
added
sig/contributor-experience
kubernetes-prow
Bot
added
the
size/M
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dims The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
cncf-cla: yes
dims
changed the title
No Solicitation policy and link to it from each platform guideline
Member
Author
|
Why am i doing this? a slack dm from this morning .. went looking for a handy link to point the person to stop this behavior.. 
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The community rule about unsolicited commercial content lives in
communication/README.md under the heading "Appropriate Content for
Community Resources". That heading is hard to cite, and nothing else in
the repo points to it. The Slack guidelines state their own detailed
version of the same rule. The guidelines for Discuss, mailing lists,
Zoom, and the shared calendar do not mention it at all.
This PR makes the existing policy easy to find and to cite. It does not
change any rules. It does the following:
Add a closing note that says the policy applies to every platform and
that moderators enforce it.
guidelines that points to the renamed section.
policy text to cite when they remove spam.
Nothing linked to the old heading anchor, so the rename does not break
any existing links. hack/verify-spelling.sh passes.
/sig contributor-experience
/area community-management