There is a very popular collaboration suggestion, but this is not a duplicate.
It suggests another solution for collaborations.
This one would be based around remixes, and most people dislike remix collabs, but hear me out.

When someone remixes a project, the owner of the original project can choose to pull changes made in that remix to their projects.
There would be a pull button, but only on remixes of one of your own projects.

It would look like this, using one of my projects as an example:

So, the project was remixed by 7alexV, who made performance improvements (thanks).
If you view a remix of your project, this button would appear:

It would pop up this: (sorry for bad styling)

Of course, you could only select either one or both.
After pulling, credit would automatically appear on the original project:

That's it!

Pros

• Collaboration would be way easier.
  
• More users are allowed to collaborate on a project, but they can't prevent the owner from editing.
  
• Credit is automatically given.
  
• Encouranges remixing.
  
• Prevents collab raids, as the user can review the changes.
  
• Easy to use.
  
• If the owner wants to make changes, they will not need to wait for their turn.
  
• No private messaging as only shared projects can be remixed.
  
• Similar to how collaboration is done in the open-source community.
  

Cons

• None I can think of
  

Notes

• Unrelated to git for Scratch. This does not suggest adding Git in Scratch, it simply suggests being able to pull changes from remixes to the original.
  
• Not a duplicate of this. The users would not get turns, instead they would be able to make changes and have the owner accept them.
  
• Only shared projects can be remixed.
  

  What if the creator of the remix doesn't want their changes to be pulled?
  

• Then don't share your project. The CC-BY-SA 2.0 license of Scratch projects allows anyone to use a project's assets as long as credit is given and the result is licensed under the same license. Read more about Copyleft on WIkipedia.
  

Extra

-EmeraldThunder- wrote:

Maybe there would be an in depth pull feature where you would be able to reject or accept particular assets and scripts.
Also it would be beneficial to store the project before merging so the user can decide to revert. Each time a new marge is made that project is overwritten.

Thanks for the idea. There should be an Advanced section and you would be able to select each change.
If there are more than 2 collaborators they should be credited in a Collaborators tab, similar to GitHub

Wouldn’t this allow for private chatting? Just asking, because if you can copy scripts over to an unshared project containing comments that can happen.

mrcreatorluigi wrote:

Wouldn’t this allow for private chatting? Just asking, because if you can copy scripts over to an unshared project containing comments that can happen.

Only shared projects can be remixed.

mumu245 wrote:

mrcreatorluigi wrote:

Wouldn’t this allow for private chatting? Just asking, because if you can copy scripts over to an unshared project containing comments that can happen.

Only shared projects can be remixed.

ah, okay then. Support. (I do have a reason it’s hard to explain it)

Support, this would allow for a much easier way to do collaborations although I do have a few suggestions.
Maybe there would be an in depth pull feature where you would be able to reject or accept particular assets and scripts.
Also it would be beneficial to store the project before merging so the user can decide to revert. Each time a new marge is made that project is overwritten.

(Maybe you could attribute the project to a studio instead to avoid clutter if a lot of people have added features and credit them with a contributors tab.

Support

You have found a perfect solution to a very suggested suggestion.
yes, suggested suggestion

Support. It's really hard to collaborate in Scratch right now

What if the creator of the remix doesn't want their changes to be pulled?

Maybe you could use more obvious wording, like simply “Copy changes”. Many people don't know what “pull” means

this part of the post was eaten by a kumquat commanded by ScratchCat1038

For the suggestion, semi-support. It is much easier than manually copying the code (and auto credit is given) but I still think the other solution is better (no offense).

Bump

Eagle138 wrote:

What if the creator of the remix doesn't want their changes to be pulled?

Maybe you would have to request your changes to be pulled.

-EmeraldThunder- wrote:

Eagle138 wrote:

What if the creator of the remix doesn't want their changes to be pulled?

Maybe you would have to request your changes to be pulled.

No. You already can take things out of the remix, and the license used by Scratch projects allows usage of art and code as long as credit is given.

Bump

Support. This is a good solution to the collaboration problem. There's no private messaging, and it works out neatly.

I just posted on the wrong topic sorry

Support, it would work out neater than the current system, which would be to remix the project.

reallysoftuser wrote:

Maybe you could use more obvious wording, like simply “Copy changes”. Many people don't know what “pull” means

I'm not even an native English speaker and I know the term.

Bacteria999 wrote:

reallysoftuser wrote:

Maybe you could use more obvious wording, like simply “Copy changes”. Many people don't know what “pull” means

I'm not even an native English speaker and I know the term.

Me too.