makethebrainhappy wrote:

When you apply for a collaboration or project, you really want to be accepted. Couple that with collaborations low rejection rate, and it feels even worse when you receive one. While some basic collaborations won't even require applications, as the sophistication goes up, so does the length of the application form. Major functions on Scratch such as becoming FPC and joining the Scratch Wiki have very general forms, yet the reviewers on the other side have a very narrow focus. To make sure that your application is top-notch, here are some tips compiled by experienced applicant reviewers. Enjoy

1.) Read the application guidelines, if necessary. Being informed on them is necessary to fill out a good application, and to not be embarrassed by a denial because you did not meet one of them. If that is the case, but you still want to join, acknowledging such shows that you are informed and seek information. You will automatically prove that you dedicated and interested in their project.

2.) Be active in the forums. Some collaborations have minimum post values which you need to achieve before you can be accepted. Having 100+ shows great activity. This translate into someone who can be dedicated to the future collaboration. Being active also makes you recognizable, and that also makes it easier to be accepted. Make sure to post constructive comments possible in the help with scripts, Show + Tell, and Suggestions forums to increase your post count!

3.) Grammar. It's not the biggest factor in the world, but it is important to avoid some of the grammar mistakes which may make an applicant turn you away. Nobodies spell-checking your posts for specific errors, since everyone makes them all the time. Just try to avoid continuously not capitalizing the word at the start of the sentence, or misspelling multiple words in a sentence. Language and word-choice are usually not heavily evaluated.

4.) Make sure that you can handle it. It's no use applying for an art shop if you can't do art. Also (this usually applies more to collaborations rather than shops), make sure that you can dedicate time to that that collaboration. If you apply for something, you've got to put time and effort into it. It's no use either if you apply for a collaboration but never get anything done. Make sure that you are committed to what you have applied for.

5.) Try your best. If a shop asks for an example of your work, make sure to give it your all and show them what you really can do. If a shop has a training programme, be sure to try your best. Remember, effort is more important than skill. People usually look for dedication and effort over skill.

6.) First impressions count. Unless you already know the Scratcher that runs the shop/collaboration, your application is the first thing somebody will see about you. If you haven't tried hard to make it your best, then it affects the owner's opinion on you, maybe eventually being the tipping point for your rejection. Make your application as good as you can make it, and you will be much more likely to be accepted.

7.) Research. If the collaboration is a cloud platformer, look up other cloud platformers on Scratch. See where this one is similar and different. Never apply for a collaboration without any background knowledge. Otherwise it will be difficult for you to join the general conversation if you are accepted. It will be evident in your application whether or not you researched before joining.

8.) Be careful. If a collaboration asks for your age or location or any other personally identifiable information, under no circumstances post in on the Scratch Forums. Rather, report it. Reread the community guidelines if it is unclear.

An example of a bad application:
Application form taken from The Nano Paper
DISCLAIMER: These applications are completely made up. This is NOT any particular user's application

Username: (Self-explanatory)
Alternate account(s) (if any): (Self-explanatory)
Job you want (max 1 for now): riter
Example of work (an example of your work for the job you want): don hav won
How often will you work on new articles (The Nano Paper will be a weekly newspaper): dunno
How active are you on Scratch (on a scale of 1/10): wen i are botherd
Are you following this topic (yes/no): nah
Are you following our official studio (find it here): nop
Comments (anything else?): no

This application is very bad in many ways, let's pick out what's wrong in this.

1. Persistently incorrect spelling and grammar. This goes for the whole application. Although not the most important part, incorrect spelling and grammar looks unprofessional and casual, and gives the owner a bad first impression. To optimise your chances of being accepted, try to look professional with correct spelling and grammar.
   
2. No example of work. This means that owners can't tell how good you are in your job, and so have nothing to go on. Remember, an example of work is very important and can heavily affect your chances of acceptance wither way.
   
3. Low activity levels. The fact that this applicant can barely be bothered to come on Scratch is a big indication of inactivity lack of dedication, meaning that they will be of no use to the collaboration.
   
4. Not following the thread or the studio. In almost all collaborations and shops, following the thread/studio is a definite requirement. This aspect alone is enough for an instant rejection.
   

An example of a good application
Now, using what we have just picked put as bad, we can make an example of a good application:

Username: (Self-explanatory)
Alternate account(s) (if any): (Self-explanatory)
Job you want (max 1 for now): Writer
Example of work (an example of your work for the job you want): (The applicant should link an example of their own work that relates to their desired position)
How often will you work on new articles (The Nano Paper will be a weekly newspaper): I'll try to work on one every day
How active are you on Scratch (on a scale of 1/10): 9/10
Are you following this topic (yes/no): Yes
Are you following our official studio (find it here): Yes
Comments (anything else?): No

Now that we've established what a bad application has, we can pick out what is good about this application:

1. Correct spelling and grammar. This gives the applicant a professional look and will improve the owner's opinion on them, creating a higher chance of acceptance.
   
2. Example of work. The applicant has included a link to their best work that relates to their desired position.
   
3. High activity levels. The high rating out of 10 and the promise to try to write an article every day is a big indicator of an active and dedicated Scratcher who will work really hard for the collaboration.
   
4. Following the thread. This means that the applicant wants to be active in the thread and the studio.
   

Where are top-notch applications needed?

The Scratch Wiki- is a collaborative community who write the guide for everything on scratch. Information and How-To's need to be accurate and well written. This is why the admins are very selective in who they give an account to.

jvvg wrote:

As someone who actually processes these requests, I can tell you we are looking for one very specific thing: Can the requesting user follow instructions? The most important part of the Wiki is being able to follow instructions so we can maintain the standard of writing and community necessary for high-quality articles. We check this by having them read S:CONTRIB and seeing if their request meets the requirements on that page. Also, scmb1 said a while ago that we can't publicly release rejected requests, so unfortunately no. However, we do have some examples we wrote (based on common things we see) that can help you.

As some of the authors have read rejected wiki applications (before the rule was in place), we can say that good grammar, specific examples of what you want to accomplish, and following all instructions are very important!

Here is an example of a real successful wiki application by Jromagnoli.

I would love to become a wiki contributor because I feel that there are articles that could benefit from different scripts.
Among the articles that I feel I can improve, https://wiki.scratch.mit.edu/wiki/Platforming_Base and https://wiki.scratch.mit.edu/wiki/Studio. The first example is very short and uses a script that could be improved. The last example lacks a few details such as:
1. Managers can delete their own comments
2.There are more categories of studios: political, chat studios, and invite everyone studios.
I believe that by becoming a wiki contributor I will be able to fix articles like the above and help make the wiki a better place. I have read all the necessary material for joining. I will await your response.
Regards, jromagnoli
P.S. blizzard

The Front Page Curator Position
Each week the Scratch Team chooses a new user to recommend projects on the front page in the third row. Only 1 application is chosen, and it must be top-notch. You can apply with a project at the studio here. The Scratch Team has released a project detailing what is required in the application, and this is located here.

There are some great resources to help you create the perfect application. While the ST does not provide many guidelines, this project by former FPC st19_galla gives you some great tips on formulating it. You can also use FPC Applications which have been accepted as a reference! Being knowledgeable means that you have an edge over your competitors for the position.

As Novakitty, a former FPC, advises

In general, I would say the best thing you can do is to be yourself, and incorporate what you love doing in Scratch into your application. If you like making games or animating, make your app a game or animation! Also, don't say what you think they want to hear; they've heard it a thousand times and the unique app will stand out! It will show that you are being dedicated and truthful and give you the best chance!

Disclaimer: This is meant as a guide. Following all these instructions does not necessary mean that you will be accepted 100% of time. All such decisions are up to the discretion of the collaboration manager.

Written by MakeTheBrainHappy, -Lite-, and Drunken_Sailor. The awesome banner is by jromagnoli.

TonPan wrote:

when green flag clicked
ask [Input Question] and wait
if <(answer) = [answer]> then 
say [Correct!] for (2) secs

else
say [Wrong!] for (2) secs

TonPan wrote:

when green flag clicked
ask [Input Question] and wait
if <(answer) = [answer]> then 
say [Correct!] for (2) secs

else
say [Wrong!] for (2) secs

makethebrainhappy wrote:

When you apply for a collaboration or project, you really want to be accepted. Couple that with collaborations low rejection rate, and it feels even worse when you receive one. While some basic collaborations won't even require applications, as the sophistication goes up, so does the length of the application form. Major functions on Scratch such as becoming FPC and joining the Scratch Wiki have very general forms, yet the reviewers on the other side have a very narrow focus. To make sure that your application is top-notch, here are some tips compiled by experienced applicant reviewers. Enjoy

1.) Read the application guidelines, if necessary. Being informed on them is necessary to fill out a good application, and to not be embarrassed by a denial because you did not meet one of them. If that is the case, but you still want to join, acknowledging such shows that you are informed and seek information. You will automatically prove that you dedicated and interested in their project.

2.) Be active in the forums. Some collaborations have minimum post values which you need to achieve before you can be accepted. Having 100+ shows great activity. This translate into someone who can be dedicated to the future collaboration. Being active also makes you recognizable, and that also makes it easier to be accepted. Make sure to post constructive comments possible in the help with scripts, Show + Tell, and Suggestions forums to increase your post count!

3.) Grammar. It's not the biggest factor in the world, but it is important to avoid some of the grammar mistakes which may make an applicant turn you away. Nobodies spell-checking your posts for specific errors, since everyone makes them all the time. Just try to avoid continuously not capitalizing the word at the start of the sentence, or misspelling multiple words in a sentence. Language and word-choice are usually not heavily evaluated.

4.) Make sure that you can handle it. It's no use applying for an art shop if you can't do art. Also (this usually applies more to collaborations rather than shops), make sure that you can dedicate time to that that collaboration. If you apply for something, you've got to put time and effort into it. It's no use either if you apply for a collaboration but never get anything done. Make sure that you are committed to what you have applied for.

5.) Try your best. If a shop asks for an example of your work, make sure to give it your all and show them what you really can do. If a shop has a training programme, be sure to try your best. Remember, effort is more important than skill. People usually look for dedication and effort over skill.

6.) First impressions count. Unless you already know the Scratcher that runs the shop/collaboration, your application is the first thing somebody will see about you. If you haven't tried hard to make it your best, then it affects the owner's opinion on you, maybe eventually being the tipping point for your rejection. Make your application as good as you can make it, and you will be much more likely to be accepted.

7.) Research. If the collaboration is a cloud platformer, look up other cloud platformers on Scratch. See where this one is similar and different. Never apply for a collaboration without any background knowledge. Otherwise it will be difficult for you to join the general conversation if you are accepted. It will be evident in your application whether or not you researched before joining.

8.) Be careful. If a collaboration asks for your age or location or any other personally identifiable information, under no circumstances post in on the Scratch Forums. Rather, report it. Reread the community guidelines if it is unclear.

An example of a bad application:
Application form taken from The Nano Paper
DISCLAIMER: These applications are completely made up. This is NOT any particular user's application

Username: (Self-explanatory)
Alternate account(s) (if any): (Self-explanatory)
Job you want (max 1 for now): riter
Example of work (an example of your work for the job you want): don hav won
How often will you work on new articles (The Nano Paper will be a weekly newspaper): dunno
How active are you on Scratch (on a scale of 1/10): wen i are botherd
Are you following this topic (yes/no): nah
Are you following our official studio (find it here): nop
Comments (anything else?): no

This application is very bad in many ways, let's pick out what's wrong in this.

1. Persistently incorrect spelling and grammar. This goes for the whole application. Although not the most important part, incorrect spelling and grammar looks unprofessional and casual, and gives the owner a bad first impression. To optimise your chances of being accepted, try to look professional with correct spelling and grammar.
   
2. No example of work. This means that owners can't tell how good you are in your job, and so have nothing to go on. Remember, an example of work is very important and can heavily affect your chances of acceptance wither way.
   
3. Low activity levels. The fact that this applicant can barely be bothered to come on Scratch is a big indication of inactivity lack of dedication, meaning that they will be of no use to the collaboration.
   
4. Not following the thread or the studio. In almost all collaborations and shops, following the thread/studio is a definite requirement. This aspect alone is enough for an instant rejection.
   

An example of a good application
Now, using what we have just picked put as bad, we can make an example of a good application:

Username: (Self-explanatory)
Alternate account(s) (if any): (Self-explanatory)
Job you want (max 1 for now): Writer
Example of work (an example of your work for the job you want): (The applicant should link an example of their own work that relates to their desired position)
How often will you work on new articles (The Nano Paper will be a weekly newspaper): I'll try to work on one every day
How active are you on Scratch (on a scale of 1/10): 9/10
Are you following this topic (yes/no): Yes
Are you following our official studio (find it here): Yes
Comments (anything else?): No

Now that we've established what a bad application has, we can pick out what is good about this application:

1. Correct spelling and grammar. This gives the applicant a professional look and will improve the owner's opinion on them, creating a higher chance of acceptance.
   
2. Example of work. The applicant has included a link to their best work that relates to their desired position.
   
3. High activity levels. The high rating out of 10 and the promise to try to write an article every day is a big indicator of an active and dedicated Scratcher who will work really hard for the collaboration.
   
4. Following the thread. This means that the applicant wants to be active in the thread and the studio.
   

Where are top-notch applications needed?

The Scratch Wiki- is a collaborative community who write the guide for everything on scratch. Information and How-To's need to be accurate and well written. This is why the admins are very selective in who they give an account to.

jvvg wrote:

As someone who actually processes these requests, I can tell you we are looking for one very specific thing: Can the requesting user follow instructions? The most important part of the Wiki is being able to follow instructions so we can maintain the standard of writing and community necessary for high-quality articles. We check this by having them read S:CONTRIB and seeing if their request meets the requirements on that page. Also, scmb1 said a while ago that we can't publicly release rejected requests, so unfortunately no. However, we do have some examples we wrote (based on common things we see) that can help you.

As some of the authors have read rejected wiki applications (before the rule was in place), we can say that good grammar, specific examples of what you want to accomplish, and following all instructions are very important!

Here is an example of a real successful wiki application by Jromagnoli.

I would love to become a wiki contributor because I feel that there are articles that could benefit from different scripts.
Among the articles that I feel I can improve, https://wiki.scratch.mit.edu/wiki/Platforming_Base and https://wiki.scratch.mit.edu/wiki/Studio. The first example is very short and uses a script that could be improved. The last example lacks a few details such as:
1. Managers can delete their own comments
2.There are more categories of studios: political, chat studios, and invite everyone studios.
I believe that by becoming a wiki contributor I will be able to fix articles like the above and help make the wiki a better place. I have read all the necessary material for joining. I will await your response.
Regards, jromagnoli
P.S. blizzard

The Front Page Curator Position
Each week the Scratch Team chooses a new user to recommend projects on the front page in the third row. Only 1 application is chosen, and it must be top-notch. You can apply with a project at the studio here. The Scratch Team has released a project detailing what is required in the application, and this is located here.

There are some great resources to help you create the perfect application. While the ST does not provide many guidelines, this project by former FPC st19_galla gives you some great tips on formulating it. You can also use FPC Applications which have been accepted as a reference! Being knowledgeable means that you have an edge over your competitors for the position.

As Novakitty, a former FPC, advises

In general, I would say the best thing you can do is to be yourself, and incorporate what you love doing in Scratch into your application. If you like making games or animating, make your app a game or animation! Also, don't say what you think they want to hear; they've heard it a thousand times and the unique app will stand out! It will show that you are being dedicated and truthful and give you the best chance!

Disclaimer: This is meant as a guide. Following all these instructions does not necessary mean that you will be accepted 100% of time. All such decisions are up to the discretion of the collaboration manager.

Written by MakeTheBrainHappy, -Lite-, and Drunken_Sailor. The awesome banner is by jromagnoli.

Sharkpedos wrote:

makethebrainhappy wrote:

I am impressed that this somehow does not have a title xD

doesn't it?

Unicorngirl289 wrote:

This really helped. Thanks!

RealChutacoPlayz wrote:

This is a off-topic question bump, but what should you do if you accept someone?

-FrostAnimator- wrote:

k Thank