(Note that this isn't a suggestion, but this topic should be useful enough for users who want to decide whether what someone is suggesting is good or not.)

A suggestion is an idea someone has, and shares it with others to see what they think of it, and then they use it.

There are millions of things being suggested to be added everyday. But sometimes, users including the Scratch Team don't think they are useful. Why is this so? You see, suggestions that have been the most liked are because they have a lot of usefulness, and it helps prevent users from doing difficult alternatives.

So, do you want to decide if a suggestion is good or not? Here are a few steps you can do to help you decide.

Is The Topic Actually A Suggestion?
Either the users are trolls, or sometimes they accidentally post stuff in the wrong forum. Therefore, you can request it to be closed.

Do You Understand The Suggestion?
Users sometimes aren't specific, and they say only a sentence or two, such as, “I want this.”

If the user has no reason, ask them, “Why do you think this suggestion is useful? We can't decide if this should be added unless you tell us how this works.” We can't be sure if the suggestion actually has a lot of meaning in it and that it can help users in the future.

Is There An Older Topic?
To keep suggestions organized, topics that suggest something that has already been suggested is usually told so with a link, and the topic is closed. However, if the original topic has been closed, and not because of the idea being rejected, or if the original topic was closed because of off-topic stuff, then the topic can be kept. To find out if there is an older topic, type this at Google: “site:scratch.mit.edu/discuss INSERT SUGGESTION HERE”. If you find an older topic that has the idea, it's best you tell the user on the thread, and request it to be closed.

Rejected Suggestion?
Some suggestions are rejected because of many disadvantages of confusion. For example, adding currency in Scratch is not something the Scratch Team would be interested in adding because it involves competition, and then users might brag, “I have more money than you! I am better than you, you are so poor that nobody likes you, idiot!”

Some other reasons are because of a potential of bullying. If the user is suggesting something that can increase the amount of bullying, tell them no!

Is It Already Being Considered To Be Added?
Many things such as cloud lists, are being to considered to be added. If you see someone suggesting any of these, tell them, “No need to suggest, they are already going to add it.”

Send a link to the topic (sticky or the ITOPIC) that shows a list of rejected suggestions. They usually have a list of suggestions that are being considered to be added, such as more custom blocks.

You may also look at the preview of the Scratch 3.0 Editor to see if any new blocks have been added there. This tells us that those blocks will be featured in the 3.0 editor. Here are some examples:

go [forward v] (1) layers :: looks

go [backward v] (1) layers :: looks

set drag mode [draggable v] :: sensing

set drag mode [not draggable v] :: sensing

<[hello] contains [world]? :: operators>

These blocks can be all seen in the new editor.

Is There An Alternative? (Workaround)
Sometimes, a suggestion doesn't need to be added, because there's already a way to do that. However, if the alternative is difficult and not well known, might as well prevent that! If someone is suggesting something like this:

(() + () + () :: operators )

Tell them, “No need to, just do this:”

(() + (() + ()))

It can be useful to learn. Otherwise, Scratch would be like a calculator that does everything for you, while you just sit there and do nothing. How ridiculous. You should be out there trying to do something! The only exception is that if the alternatives are more understandable for certain groups (such as workarounds for a block only secondary schoolers and above would find easily). We can't just abandon it all because of such as difficult workaround.

Also note that some workarounds can seem ridiculous or maybe not nice or actually “not easy” even if the procedure is simple. For example, even though the link to the Forums is just a click away from the front page, you have to scroll all the way to the bottom, and users might not even know the forums link is at the bottom! It's very, very tiring to have to keep scrolling to the bottom of a page to replace a suggestion that requests to add a link to the forums somewhere such as the front page!

Take A Look At What Other Users Have To Say
If you still don't understand, but the others do, look at what they say! If you are convinced, quote their post and say that you agree with what is being said on why whatever idea is being share is useful or not.

However, don't just quote the posts. Some users think you are spamming.

A Few Categories You Have To Beware Of
Per talk about “rejected suggestions”, here are some things you have to watch out for in a suggestion:
1. Is it private messaging? Can only certain users see it?
2. Does it involve being popular? Scratch is not about being popular.
3. Can spam happen if the idea was added?
4. Does it restrict users from remixing and see inside?
5. Does it have ambiguity?

If the suggested idea has or can promote any of these things, then maybe you should tell them no.

Does It Help All Of The Community?
Things shouldn't just apply to certain people. If an idea is useful to many people, then it would certainly be a good idea. If it applies to only certain people, then what's the point of having if it's just only for like one person?

Everything shouldn't just apply to you.

Take A Look At The Examples
Examples are a good way to demonstrate why a suggestion is useful. If you think the examples demonstrate good thoughts about something, then it's definitely useful.

“Title Says It All”
Does the OP say, “Title says it all.”, or something like that? If so, then I have to tell you, that is not constructive. Yes, everyone knows about the title, but that's not the best way for everyone to know what someone is suggestion. That's why there are descriptions that users should put. (see above)

Believe me, I've still seen topics that still have this setup, and it's not impressing to me.

If there is no description how will you know if the suggestion is useful or not?

“Other Websites Use It/Other Programming Languages Have It”
I would not recommend trusting this statement. The Scratch Team can do whatever they want with their website. Just because another thing has something doesn't mean this site is supposed to have that. Also other websites contain things that are rejected.

For programming languages, you might see someone say this:

<(letter (0) of [hello]) = [hello]>

This should be true

Even if the letter “0” in a string is always the first letter in other programming languages, this may seem confusing to users who don't use those languages. To make things more simple, letter 1 of hello is the letter h, not e, so letter 0 of hello is nothing, not h.

Have any other things you want me to add? Reply below!

Have fun!

Add if it would help all of the community and not just you.

There is a sticky that's kind of similar to this, but overall this is a pretty good guide.

Impressive. Maybe this could be made into a project, a how-to on how to evaluate a suggestion for Scratch.

Charles12310 wrote:

Have fun!

That is half of the key to kingdom. It is easy to lose or forget. So, remember where you put it.

HyperNova35 wrote:

There is a sticky that's kind of similar to this, but overall this is a pretty good guide.

Yes, that is mostly on how you should respond to a suggestion. This topic mostly mentions on determining usefulness of an idea.

Nice guide! I think a lot of users will benefit from this.

marigoldkit wrote:

ok i had a much longer post but i reread the thread and it actually covers most of my ideas so gj

-frostyiceprincess- wrote:

Nice guide! I think a lot of users will benefit from this.

Thank you.

Charles12310 wrote:

HyperNova35 wrote:

There is a sticky that's kind of similar to this, but overall this is a pretty good guide.

Yes, that is mostly on how you should respond to a suggestion. This topic mostly mentions on determining usefulness of an idea.

Oh. Didn't notice that.
Anyway this is a pretty nice guide. Good job.

eeymao wrote:

support

Why Do You Support This?
channeling my inner lu
also that joke is kinda old

DaEpikDude wrote:

eeymao wrote:

support

Why Do You Support This?
channeling my inner lu
also that joke is kinda old

That post is a TOTAL joke.

DaEpikDude wrote:

lu

Did Someone Mention Me?

Lu2333 wrote:

DaEpikDude wrote:

lu

Did Someone Mention Me?

. . . yes

DaEpikDude wrote:

Lu2333 wrote:

DaEpikDude wrote:

lu

Did Someone Mention Me?

. . . yes

Okay, Just Don't Gossip.

Support, this is a great thing that a lot of people would find useful.

No support, though, because if we all think the same about suggestions there will be nothing to discuss. ↑

walkcycle wrote:

No support, though, because if we all think the same about suggestions there will be nothing to discuss. ↑

I change my stance to semi-support for this reason

Nice guide! +1

aking_ wrote:

Support, this is a great thing that a lot of people would find useful.

walkcycle wrote:

No support, though, because if we all think the same about suggestions there will be nothing to discuss. ↑

aking_ wrote:

walkcycle wrote:

No support, though, because if we all think the same about suggestions there will be nothing to discuss. ↑

I change my stance to semi-support for this reason

Please tell me this is a joke, have you even read the first parts of the topic?

Charles12310 wrote:

Please tell me this is a joke, have you even read the first parts of the topic?

You think I should support it, you mean, or not support it?

I read this part.

Woah, white space!

walkcycle wrote:

Charles12310 wrote:

Please tell me this is a joke, have you even read the first parts of the topic?

You think I should support it, you mean, or not support it?

I read this part.
-snip-
Woah, white space!

Charles12310 said that this topic wasn't made for supporting or not supporting, but being a “guide” or something along those lines.