search

scratchfoundation / scratch-www

Standalone web client for Scratch
https://scratch.mit.edu
BSD 3-Clause "New" or "Revised" License
1.58k stars 834 forks source link

Mention policies you announced somewhere more accessible #6987

Open DNin01 opened 2 years ago

DNin01 commented 2 years ago

I personally think that the policies like your Browser Extension/Userscript Policy or Cloud chat projects announcements in the Discussion forums should be easier to find, like maybe you could list them in your Community Guidelines. I never stop seeing people mention browser extensions on the Discussion forums by accident, so I think saying something about browser extensions on the Community Guidelines would be beneficial.

PPPDUD commented 2 years ago

+1. This would clean up the Scratch community and would help with some very big problems.

Although may I please ask if you could also suggest for forum rules to be shown to first-time users on that forum? I'm 90% sure that this extra suggestion is a duplicate, but I have no link to prove it.

Offtopic: I am signing off soon because my sandwich is going cold slowly. Any responses will most likely be from tomorrow. Also, Grammarly needs to return to school. No offense to them by that! :)

benjiwheeler commented 2 years ago

I am labeling this with a priority, not because we're sure we want to do this, but because it's worth considering.

PPPDUD commented 2 years ago

Good point.

On Wed, Aug 31, 2022, 12:08 PM CST1229 @.***> wrote:

I am labeling this with a priority, not because we're sure we want to do this, but because it's worth considering.

Who in the world would

— Reply to this email directly, view it on GitHub https://github.com/LLK/scratch-www/issues/6987#issuecomment-1233138005, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZTWPZLGNM2AE2FN7PWDGK3V357PFANCNFSM56XZSEBQ . You are receiving this because you commented.Message ID: @.***>

ghost commented 2 years ago

I am labeling this with a priority, not because we're sure we want to do this, but because it's worth considering.

No offence, but who in the world would look in forum topics (the hidden rotting place 90% of scratchers don’t know about) to find rules? Why aren't they elsewhere?

Scratchfangs commented 2 years ago

I agree, 2 years ago I had 0 idea that the policy was a thing. And I got a warn on my record for it.

CocoTheMii commented 1 year ago

I am labeling this with a priority, not because we're sure we want to do this, but because it's worth considering.

With all due respect, why wouldn't you want to do this? Does the Scratch Team somehow benefit from keeping their guidelines intentionally vague? From a community perspective, it only serves to increase confusion.

Take face reveals, for example. Until around early 2022 (iirc), users were allowed to show their face in a project, provided that it was not the primary focus. However, this rule was suddenly changed to ban faces in projects altogether, a change which was never formally announced. As a result, many users remain unaware of the change, even today.

Transparency is key. It is not enough to simply imply the existence of these rules (i.e. removing the camera button from the editor); it should be perfectly clear to any given user what is and is not allowed on Scratch. This means two things:

  1. Announcing rule changes immediately upon implementation at the very latest, and in a location where it will be seen by as many Scratchers as possible
  2. Providing an up-to-date list of every rule not already defined in the Community Guidelines or Terms of Use

Otherwise, you simply cannot expect every user to follow every single rule that they don't know about.