Za-Chary wrote:

Okay, I think I understand what you mean now. I would like to rescind my earlier post, and make a new one.

Support, but only with the following critera:

1. The project is always accessible to the public from the project owner's profile. As you indicate, “the project would be on the last person was working on the collab project's “My stuff” page.” I think this could work well, but the project should still be on the project owner's profile since he/she started it. Would it be accessible on the collaborator's profile as well? Perhaps. But it shouldn't “bounce back and forth” between profiles.
   
   
2. Rather than immediately adding users, you must invite them. That is, the user must accept the request to collaborate. I imagine this would work similarly to how studio invites work. It might lead to more notifications, but it's a small sacrifice to the alternative, which is “collaborating” on projects you don't actually want to work on. Furthermore, only the “project owner” (the user who started the project) can invite users, to reduce unwanted invites.
   
   
3. All users who helped collaborate on the project get credit in some way. This could be as simple as putting “by Za-Chary and LuckyLucky7” under the project title, with the user who initially started the project having their name put first. Obviously we don't want to steal credit from anyone. Furthermore, once added to a collaboration, no one's credit can be removed, although their privileges of working on the project may be revoked (again, by the project owner).
   
   
4. There is a “timeout” mechanic. Without one, you could share a project, invite me to collaborate on it, and then allow me my turn to work on it. At this point, I could just quit Scratch (be inactive), and you would never get your turn. With the timeout option, after a week (regardless of inactivity or not), you (as the project owner) automatically gain control of the project again, although the project would still say that I helped collaborate on it. If I was actually working on it and took a week off, you could just send me a “It's your turn” message again.
   
   
5. There is a maximum number of 2 people allowed to work on a project at a time. That is, you can only send an invite to one other person. This way we don't have any games of “owner keep-away” where 3 other people send “It's your turn” messages to each other, and not the project owner. Doing this would also eliminate any use of “invite everyone” projects, which could just get confusing.
   

Perhaps some of this was implied in your original suggestion, in which case, I'm sorry for going into so much detail. I do like your suggestion now — I think this could work well. Let me know what you think of my feedback.

RandomPersonGRAA wrote:

LuckyLucky7, I do believe bumping this post isn't great, considering as it has had at least 5 bumps with no comments, let alone constructive ones.

Za-Chary wrote:

Okay, I think I understand what you mean now. I would like to rescind my earlier post, and make a new one.

Support, but only with the following critera:

1. The project is always accessible to the public from the project owner's profile. As you indicate, “the project would be on the last person was working on the collab project's “My stuff” page.” I think this could work well, but the project should still be on the project owner's profile since he/she started it. Would it be accessible on the collaborator's profile as well? Perhaps. But it shouldn't “bounce back and forth” between profiles.
   
   
2. Rather than immediately adding users, you must invite them. That is, the user must accept the request to collaborate. I imagine this would work similarly to how studio invites work. It might lead to more notifications, but it's a small sacrifice to the alternative, which is “collaborating” on projects you don't actually want to work on. Furthermore, only the “project owner” (the user who started the project) can invite users, to reduce unwanted invites.
   
   
3. All users who helped collaborate on the project get credit in some way. This could be as simple as putting “by Za-Chary and LuckyLucky7” under the project title, with the user who initially started the project having their name put first. Obviously we don't want to steal credit from anyone. Furthermore, once added to a collaboration, no one's credit can be removed, although their privileges of working on the project may be revoked (again, by the project owner).
   
   
4. There is a “timeout” mechanic. Without one, you could share a project, invite me to collaborate on it, and then allow me my turn to work on it. At this point, I could just quit Scratch (be inactive), and you would never get your turn. With the timeout option, after a week (regardless of inactivity or not), you (as the project owner) automatically gain control of the project again, although the project would still say that I helped collaborate on it. If I was actually working on it and took a week off, you could just send me a “It's your turn” message again.
   
   
5. There is a maximum number of 2 people allowed to work on a project at a time. That is, you can only send an invite to one other person. This way we don't have any games of “owner keep-away” where 3 other people send “It's your turn” messages to each other, and not the project owner. Doing this would also eliminate any use of “invite everyone” projects, which could just get confusing.
   

Perhaps some of this was implied in your original suggestion, in which case, I'm sorry for going into so much detail. I do like your suggestion now — I think this could work well. Let me know what you think of my feedback.

Za-Chary wrote:

Okay, I think I understand what you mean now. I would like to rescind my earlier post, and make a new one.

Support, but only with the following critera:

1. The project is always accessible to the public from the project owner's profile. As you indicate, “the project would be on the last person was working on the collab project's “My stuff” page.” I think this could work well, but the project should still be on the project owner's profile since he/she started it. Would it be accessible on the collaborator's profile as well? Perhaps. But it shouldn't “bounce back and forth” between profiles.

[…]

Orangey2011 wrote:

Support!

Although I think this is a cool idea, the Scratch Team might have to approve the project before letting the other user continue the collab.