No, this is not a list of commonly suggested suggestions. Chrischb covered most of them. This is a guide on how to make your suggestion the most efficient.
Step 1-Thinking of the Idea
When you write suggestions, you want a new feature or something of the sort. But what if the feature is already possible? Then you'd've wasted time. Make sure the feature does not already exist. Also, there are upcoming features in Scratch 2.0 that have been confirmed, like Block Creating. If you are not sure, you should search. If you can't find it, then the feature probably does not exist.
Remember, if the feature already exists, you could be spending your time thinking of new suggestions rather than posting a new suggestion topic.
TL;DR: First, when thinking of a new suggestion for Scratch, make sure the feature is new and does not already exist. Or else you'd be asking for an apple you are already eating. Also make sure no one else has suggested it. If you have something to add on to theirs, tell them on their thread.
Oops. Made the TL;DR too long.
TL;DRTTL;DR: Make sure it doesn't exist or isn't already suggested!
Step 2-Creating Details
For this section, I shall use examples.
Let's take the example of "Better Friending System". I know this is already probably going to be in 2.0, but it's just an example.
Let's say I go up and post a suggestion about a better friending system. (Ignore step 1 for this example, please.)
I wrote:
There should be a better friending system.
as the main post. But what exactly does that mean? Does that mean two-way and one-way friending? Or does that just mean only two-way but there could be groups of friends? I did not include details, that's why it's unclear. You don't have to make a post as long as this one, but make sure you include the details about the suggestion. What would have been a little better would be
I wrote:
There should be a better friending system. In order to be friends with someone, you have to approve of it. Also, you can follow someone without their permission.
See how I included detail about the suggestion in a short little post? That can be good enough.
TL;DR: Another way to save time of everyone is to make sure that you include details, or else they'll ask you how you want your suggestion to be. Without details, not many people will support it because they won't understand it. People who understand something probably will agree to it if it's good.
Agh! Made this one too long too!
[b]TL;DRTTL;DR: Include details so peo
Edit: my post is cut off. I don't know why. and I don't remember what I wrote. if you're reading this guide, wondering why it ends with "peo" I just want to let you know that that's not the end. I'll rewrite it sometime soon when i have time.
Last edited by kayybee (2012-09-25 00:37:13)
Offline
This is really good.
Offline
"TL;DR: Make sure the suggestion is beneficial and possible."
That''s pretty much all we need
Offline
This will help a lot of Scratchers, nice work
Offline
*thumbs up to you*
Offline
*Sticky*
Offline
Super guide. Nice and short and to the point.
TL;DR: It's like my ITopic in NSM. XD
Last edited by scimonster (2012-01-24 11:13:45)
Offline
TL:DR.
I read the TL:DR of the TL:DR, and it seems pretty simple.
kayybee wrote:
TL;DRTTL;DR: Make sure it doesn't exist or isn't already suggested!
Offline
This should be ITopiced. It is a great guide.
Offline
joletole wrote:
This should be ITopiced. It is a great guide.
Yep. But as Paddle said on your thread, "they are growing like moss!" xD
Offline