vercel[bot]
commented
1 year ago @sse245 is attempting to deploy a commit to the PaperMC Team on Vercel.
A member of the Team first needs to authorize it.
Closed stefvanschie closed 1 year ago
vercel[bot]
commented
1 year ago @sse245 is attempting to deploy a commit to the PaperMC Team on Vercel.
A member of the Team first needs to authorize it.
vercel[bot]
commented
1 year ago The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| site | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 19, 2023 1:40pm |
This PR does not make material changes to the guidelines.
Currently the community guidelines are phrased in such a way that it sometimes addresses a general member and sometimes moderators. For example, point 6c states: "Someone pinging a particular person because they are responding to that person is not a problem and not even warranting of a warning." The last part seems to address moderators, as they are the ones that warn members for inappropriate behaviour. For the average member, this is irrelevant, since they can't issue warnings in the first place. The majority of changes in this PR change the way such items are phrased, by only telling what is and is not allowed, leaving out how this should be resolved.
Items which explain what the result of violating a rule is, such as point 3a, "Spam bots and trolling users will be immediately banned without warning.", are not changed, since this describes what the punishment will be and is therefore relevant to the reader.
Some auxiliary changes have also been made:
Specific instances where the document referred to #paper-help as "the help channel" has been removed. This has been done because a user asking questions might have questions about software other than Paper and should therefore use one of the other help channels, not #paper-help.
Point 5c has been generalised. Instead of saying that server ips and plugins can go into the Discord status, the document now states that they should be in less visible fields, such as a Discord status. This because the document also governs the IRC channels, forums, and GitHub organization, which don't have a Discord status.
Point 6a has been changed to explain that #paper-exploit-report should be used for reporting vulnerabilities. "when normal users may not be able to help" has been left out as a valid reason for staff pings, since I think it's not really needed and pretty vague. In practice pretty much all questions can be resolved by non-staff. If such a situation does occur, there are generally plenty of staff watching the community spaces that can escalate this to the right person if really needed. And of course, moderators can also reason that if a ping is really valid they don't need to do anything. Ultimately I think we don't need to describe such a niche situation here - it probably leads to more false pings than correct ones.
Point 6b has been removed since it didn't describe any kind of guideline or rule and overall does not add anything to the document in my opinion.
Point 8 has been updated to mention authenticating against Microsoft (accounts) instead of Mojang. While there is currently still time for players to migrate, so some people still have a Mojang account, the deadline is pretty soon. I think it makes sense to already change the wording to Microsoft and leave out Mojang. This saves us from editing this once more when the migration is over.
Point 9 has ben updated to state "how to bypass chat, username, and skin reporting". Recently the ability to report usernames and skins has been introduced in a snapshot. While this already falls under that rule, the phrasing now makes it explicit. Currently no PaperMC software supports a version which includes this, but adding it to the guidelines now saves us from having to edit this document again in (probably) the near future.
Any feedback is appreciated.