- "Collaboration" redirects here. For other uses, see Collaboration (disambiguation).
|This page has links to outside of the Scratch website or Wikipedia. Remember to stay safe when using the internet as we can't guarantee the safety of other sites.|
A collaboration, or collab for short, is a group of Scratchers who work together to make one or more projects. A collaboration may also sometimes be referred to as a "company", coming from the idea that these groups of Scratchers exemplify a great amount of teamwork and dedication. Each Scratcher contributes his or her own talents to the benefit of other team members, very much like how a real company operates. In the official Scratch Team Blog, andresmh has described collaborations as "[a] group of Scratchers that get together (virtually) to create collaborative projects", and mentions how collaborations on Scratch are an "interesting phenomena" occurring in the Scratch Website. Many companies/collaborations have their own logo, studio, forum thread, and sometimes even a motto. 2010 has been called "the year of the companies" by some users due to many companies/collaborations forming, possibly due to the addition of the Collaboration Forum.
A common structure of having all of the members share a single account is frowned upon and highly discouraged by the ST, and could lead to a block of that account. Instead, it is recommended that the users remix existing projects by other members of the collaboration. The owner of the collaboration account can then put the final result on it.
- 1 Qualities of a Good Scratch Collaboration
- 2 Common Jobs in Collaborations
- 3 Common Structures of Collaborations
- 4 Elections and Voting Systems
- 5 Other Types of Collaborations
- 6 Example Collaborations
- 7 What Other Kind of Collaborations are there?
- 8 Collab Camp 2011 and 2012
- 9 I'd Like to Teach the World to Code
- 10 See Also
- 11 External Links
- 12 References
Qualities of a Good Scratch Collaboration
A good Scratch collaboration requires teamwork and agreement. All participants need to know what is being done in order to make the collaboration successful. Progress should be rapid (but not rushed); if left for too long, participants can lose interest and greatly slow the project. Many people use the Collaborations forum for discussions. Studios are a great way to keep track of the different versions of the projects. The following list has many qualities that make a collaboration successful:
- Every user has his/her own particular category to work in
- The entire group discusses often about the project
- The group has a leader, who takes the responsibility of assuring everyone's jobs
- An organized forum topic with the members and their jobs listed; the communication page
- Who uploads what, and what will be remixed by whom so the uploaded projects do not get mixed up of out of control
|Note:||These are subject to opinion|
Common Jobs in Collaborations
In collaborations, members of the collaboration are assigned to a particular job. Listed below are some common jobs in collaborations.
Programmers may help with the coding in Scratch. Some collaborations will have ranks of programmers based on their abilities and skill in that area. Some collaborations have specialised programmers that work in areas such as Cloud Variables and using 3D in Scratch.
Graphic Artists may design the sprites for projects. But they may also help with graphics for the collaboration and completing art orders for shop collaborations.
Sound Experts may deal with sound effects in Scratch projects or composing music for projects. Some band collaborations have different roles for sound experts such as drummers, composers, pianists and guitarists.
Ideas people may help with brainstorming and designing the game. Many collaborations allow all members to brainstorm but not all.
Testers help to test the current project and give feedback including bugs and areas for improvement.
Writers may write story lines for projects or for a writing based collaboration.
Common Structures of Collaborations
All collaboration structures are different, however here is one hierarchy of a collaboration. Many collaborations have set-ups similar to this but not all.
- Leader: There is usually one leader per collaboration. They tend to have the last say and are responsible for the overall running of the collaboration.
- Executives: Executives are members trusted by the leader and are responsible for helping the leader run the collaboration. They often have the power to hire and dismiss members. May be known as Deputy Chief, Assistant Executive and Co-leader.
- Managers: Managers tend to have less power than executives and may not be able to hire and dismiss members. They are responsible for running teams within the collaboration.
- Worker: Although the workers have the least power, they make up the backbone of a collaboration.
Standard Structure Similar to the hierarchy above.
Democratic Variant Similar to the hierarchy above, but members are allowed to vote on some decisions.
Community Variant This collaboration tends to be between a few friends on Scratch who have equal say in decisions about the collaboration.
Massive Variant This collaboration has many members. They usually have several layers of teams and departments with many levels to the hierarchy.
Elections and Voting Systems
In some collaborations, certain roles are elected by the whole collaboration. There are some different voting systems collaborations can use for this. Included below are examples of a few of them.
First Past The Post Also known as Winner Takes All and abbreviated FPTP. This is voting at its most simple. Essentially, the voters choose one candidate and the candidate with the most votes wins. It is quick, simple, and easy to organise. However, it allows a minority rule and causes a spoiler effect.
Alternative Voting Abbreviated to AV and also known as instant-runoff voting, this voting method is used to elect one candidate from many.
- 1. Instead of voting in First Past The Post, voters do not just chose one candidate, but rather order them in preference.
- 2. If one candidate has over 50% of votes cast, they win.
- 3. If not, eliminate the candidate with the lowest number of votes.
- 4. Take the votes from this candidate and redistribute them based on the order of preference on each individual vote cast. Repeat steps 2 - 4 until one candidate reaches 50%.
Alternative voting removes the spoiler effect and allows the candidate that the majority agree on to win. However, it is a more complicated process than FPTP.
Single Transferable Vote STV tries to achieve proportional voting and is used to elect multiple officials. Before the voting process, the number of elected officials must be decided to calculate the threshold. To work out the threshold, you can use different formulas:
Droop Quota: votes needed to win = (votes cast / (seats to fill + 1)) + 1
Simple: votes needed to win = (votes cast / seats to fill)
- 1. Voters order candidates in preference.
- 2. If candidates have exceeded the threshold, the surplus votes are redistributed.
- 3. If candidates have reached the threshold, they win.
- 4. Eliminate the candidate with the lowest number of votes and redistribute them.
- 5. Repeat steps 2 - 4 until the correct number of seats have been filled.
Other Types of Collaborations
Not all collaborations are restricted to project creation — some groups decide to collaborate on other things, such as Scratch Modifications. Some collaborations try to give advice with Scratch, such as H4U (Help For You).
Band collaborations are collaborations that make music. Some band collaborations record their music separately before sharing it with the others to improvise and record their parts, and then putting it together into one song, a technique used by bands such as Frozen Coco and Probehæd. One band collaboration called The 10th Dimension uses an online music notation software to put together their songs which means their members do not have to record anything.
One thing a lot of band collaborations do is make colourful covers for their songs. Here are some examples:
Content ranges from articles about parts of Scratch, game reviews, and interviews with Scratchers. Often members of these types of collaborations will either write new articles or edit existing articles. The finished project will usually contain buttons allowing one to skip from one article to the next. Some examples of newspaper collaborations' projects are:
Some Scratchers may collaborate in making a studio that serves a specific purpose to the Scratch Community. Projects relating to the purpose of the studio will be added. Since studio collaborations have very specific intentions, curators of studio collaborations may be picked cautiously and sparsely.
This section lists a few of the most successful collaborations and gives an insight into how collaborations work:
Gray Bear Productions
Gray Bear Productions was founded by the users Forcemaster, Robin7, and Lanie in June 2008. As time went on, many more people joined. Although members were not assigned specific positions, they tended to find a type of task they enjoy most, such as art, music, or storyline, and develop that for each project the collaboration makes.
When deciding what projects to create, members all offered suggestions and then voted on which ones to use. With the new idea that was voted on, members got to work and create a long chain of remixes which built on each other to create a better project each time.
The latest project in its studio was made in October 2010 and the collab has been mysteriously inactive ever since.
Chrono Wars was a collaboration that aimed to make one full real-time strategy game.
The Chrono Wars collaboration was started in August 2010 by ScratchReallyROCKS. Initially, there was absolutely no idea of what the collaboration was going to make, and there was room for thirty participants to work in different groups. After much discussion, the game was decided to be a real-time strategy game with some unique features, and was named TimeCraft (this name was later changed to Chrono Wars). After weeks of small discussion, website problems, ideas and new participants, they finally decided to do the heavy work on the game in mid-2011, when they would all have more time to program.
Frozen Coco was the first band formed on the Scratch Forums, a purely online collaboration between Scratch users DIY (Diyath Yavin), technoguyx (Bastián Núñez), hpotter134 (Matt Hambra), and jslomba (Luke Slomba). Both leaders, Yavin and Núñez, however, later agreed that it was in the best interest of the band that they discontinue releasing on Scratch, as the band planned to move onto better sites for sharing and popularising their music. This decision was formulated during the month of August in 2012.
Since its inception in summer 2011, Frozen Coco released seven singles, an EP, and a full-length album. The band was working on their second studio album before splitting up. An album title was never decided upon, but they stated that they planned to incorporate multiple instrument overdubs and several orchestral arrangements in the release, in contrast to their previous work. As of the formal split in December 2013, all production plans for the album were abandoned.
The Scratch Helper Mentoring Committee
The Scratch Helper Mentoring Committee is a collaboration which works to help new scratchers gain experience with Scratch and its website. Mentors work with the new scratchers for one week to teach them all the aspects and allow the New Scratchers to ask any questions they have. The Program was founded by makethebrainhappy. Currently, one can join if they are a scratch team member, a scratch mentor, or a scratch helper. This collaboration is ongoing.
What Other Kind of Collaborations are there?
There are many more, including the kinds of collaborations above. One of the most often collaborations are where two Scratchers agree to make a collaboration together, and make projects on any kind of topic. Another one can be an account where a certain group of curators in a studio agree to make an account, and make projects that have certain activities for that certain studio. There are more examples above.
Collab Camp 2011 and 2012
The Scratch Team released a remix of the Collab Challenge on August 1 of 2011, called the Collab Camp. Users had to work together to create interactive stories. It was successful the first year so they decided to do it again, but this time it was on February 12, 2012. Users had to create a music mashup.
I'd Like to Teach the World to Code
In June of 2015, the Scratch Team did a collaboration with anyone that was interested on Scratch! People could remix this project, record themselves singing the "I'd like to teach the world to code" song, written by Scratch Team member Mres, add their own characters, and submit a link to their project here. Many people participated in this fun-filled event, and it was featured in some news articles.The final project can be found here.
- Gray Bear Productions: Archived Forum Topic
- Gray Bear Productions: Studio
- Chrono Wars: Archived Forum Topic
- Frozen Coco: Website
- The Scratch Mentoring Committee Forums
- The Scratch Mentoring Committee Studio