LionCoder10 wrote:

RecessFailsOffical wrote:

Sounds really similar to this. Therefore…

This topic is a duplicate. Please continue discussing here to keep the discussion all in one place.

The link you're bringing up is the suggestion of collaborating
But my idea is just giving credit, at the END of a collab or remix-chain.

I am not suggestion collaboration, but giving credit for a collaboration

LionCoder10 wrote:

So, me and my brother are planning a collaboration. However, we are deciding; when we share the project, what will we do?
We could:
-Share it on only one profile and credit the other person
-Share it on two profiles and ask for people to heart/star both
However, each of those has their cons. For the first one, if someone hearts/stars the project, the other person won't know, as it techingaclly isn't their project. For the second idea, its not a guarantee that people will love both.

Ok, enough with the chatting. My idea is that, similar to this idea, there should be an “add collaborate button” (which only the host can do) When the project is shared, the title page would say, as an example:
“Test Project-Collab” by @LionCoder10 and @username
Now, when someone hearts, stars, or comments on a project, it sends a message to both creators. Also, when the project is shared, on one of the collaborators activity, it could say something like “@username collaborated with @LionCoder10 to make ”Test Project-Collab“”
I hope this makes collabs more fair, and make sure that everyone gets proper credit.

RecessFailsOffical wrote:

LionCoder10 wrote:

RecessFailsOffical wrote:

Sounds really similar to this. Therefore…

This topic is a duplicate. Please continue discussing here to keep the discussion all in one place.

The link you're bringing up is the suggestion of collaborating
But my idea is just giving credit, at the END of a collab or remix-chain.

I am not suggestion collaboration, but giving credit for a collaboration

LionCoder10 wrote:

So, me and my brother are planning a collaboration. However, we are deciding; when we share the project, what will we do?
We could:
-Share it on only one profile and credit the other person
-Share it on two profiles and ask for people to heart/star both
However, each of those has their cons. For the first one, if someone hearts/stars the project, the other person won't know, as it techingaclly isn't their project. For the second idea, its not a guarantee that people will love both.

Ok, enough with the chatting. My idea is that, similar to this idea, there should be an “add collaborate button” (which only the host can do) When the project is shared, the title page would say, as an example:
“Test Project-Collab” by @LionCoder10 and @username
Now, when someone hearts, stars, or comments on a project, it sends a message to both creators. Also, when the project is shared, on one of the collaborators activity, it could say something like “@username collaborated with @LionCoder10 to make ”Test Project-Collab“”
I hope this makes collabs more fair, and make sure that everyone gets proper credit.

The OP of the original topic links a project (which YOU linked in the OP) that has the same “add collaborate button”

RecessFailsOffical wrote:

Sounds really similar to this. Therefore…

This topic is a duplicate. Please continue discussing here to keep the discussion all in one place.

The-Sushi-Cat wrote:

RecessFailsOffical wrote:

Sounds really similar to this. Therefore…

This topic is a duplicate. Please continue discussing here to keep the discussion all in one place.

Similar, yet still different. OP is only suggesting adding more credit, not adding collabs.

But back to the actual topic:

I have a few questions/comments

1. How many people could you add? I've collabed on projects where there are many people. Some people are coding, some are drawing, some more are coding, someone is putting the project together, someone else is coding… etc etc. There would have to be a limit, to prevent spam and lag (especially on projects like MAPs, where there are tens of people animating)

2. There should be a way to remove/reject your credit. If you participated in a project that you no longer want notifications from, you should be able to remove yourself. If someone tries to add you, it would be like a studio invite. You'd have to go there in person to accept or reject it, so people aren't getting added to projects they didn't participate in and getting unwanted notifications. This is how spam would be prevented

3. The host shouldn't be able to remove other people. I think it might cause drama if they can.

4. Does the credited person have access to the project at all other than basic features anyone has? (IE. Turning off comments, editing the description, and changing the project title. NOT editing the inside project)

Thats all right now lol

LionCoder10 wrote:

The-Sushi-Cat wrote:

RecessFailsOffical wrote:

Sounds really similar to this. Therefore…

This topic is a duplicate. Please continue discussing here to keep the discussion all in one place.

Similar, yet still different. OP is only suggesting adding more credit, not adding collabs.

But back to the actual topic:

I have a few questions/comments

1. How many people could you add? I've collabed on projects where there are many people. Some people are coding, some are drawing, some more are coding, someone is putting the project together, someone else is coding… etc etc. There would have to be a limit, to prevent spam and lag (especially on projects like MAPs, where there are tens of people animating)

2. There should be a way to remove/reject your credit. If you participated in a project that you no longer want notifications from, you should be able to remove yourself. If someone tries to add you, it would be like a studio invite. You'd have to go there in person to accept or reject it, so people aren't getting added to projects they didn't participate in and getting unwanted notifications. This is how spam would be prevented

3. The host shouldn't be able to remove other people. I think it might cause drama if they can.

4. Does the credited person have access to the project at all other than basic features anyone has? (IE. Turning off comments, editing the description, and changing the project title. NOT editing the inside project)

Thats all right now lol

Ok…let’s se how I can answer these…
1. A max would probably be good, maybe like three or five or something
2. I agree with that. You can remove yourself, reject invites, etc.
3. I’m not sure completely, they are the host after all. You are right,, however, so maybe I agree with you
4. Probably not. Only the host will be able to do that
Thanks for the questions!

The-Sushi-Cat wrote:

You should add a blurb explaining how this isn't a dupe, so it doesn't get closed again.

Malicondi wrote:

LionCoder10 wrote:

Wait, where is it rejected? I don't see it in TOLORS, but I may be wrong

they're probably talking about this:

Za-Chary wrote:

2.1 Adding users to work on projects
Having multiple Scratchers work on the same project would be difficult to moderate not only due to technological limitations but also because it could lead to private messaging; for more information, see #7.1 on this list. This suggestion includes live editing (similar to Google Docs) and other forms of private collaboration. If you would like to work on a project with another Scratcher, you can remix each others' projects.

But, i don't see how this applies. This suggestion is about giving 2 people credit and notifications from a single project, not two people working in the project at the same time. I think this would be a nice feature as people don't always pay attention to other people who collaborated with you.
support

LuckyLucky7 wrote:

Why can't there be collaborations on Scratch? 2 people working on a project at the same time is rejected, but instead of doing that, they would get turns.

Pros of getting turns:

• Better able to encourage Scratchers to cooperate and share their ideas
  
• Would not take up as much server space/memory as 2 people working on a project at the same time
  
• Is a fair system, as it includes giving credit to both people in the collaboration
  

(Idea from @Nambaseking01):

Nambaseking01 wrote:

Maybe you should also mention that not giving credits to the user that helped with the collaboration could also cause legal issues because Scratch's license requires people to give credits (which will be automated, but I feel like this needs to be clarified in OP)

chippysmall4 wrote:

Snip

the_awsome_penguinja wrote:

question:
would the project show up on the profiles of all those credited?

starlightsparker wrote:

*huge sigh*

The-Sushi-Cat wrote:

chippysmall4 wrote:

Snip

This is only for credit- nothing else. If someone hosts a MAP, they can invite people to have credit instead of allowing them onto the project, allowing for people to potentially ruin the project. If it's not a two person collab, then inviting someone, having them leave immediately, then inviting someone else is tedious.

Doesn't matter if that one ALSO includes, credit, this one is different. ST closed this, then reponed it. They've decided it's not a dupe.

LionCoder10 wrote:

Bump (I will not accidentally close this this time )

chippysmall4 wrote:

The-Sushi-Cat wrote:

chippysmall4 wrote:

Snip

This is only for credit- nothing else. If someone hosts a MAP, they can invite people to have credit instead of allowing them onto the project, allowing for people to potentially ruin the project. If it's not a two person collab, then inviting someone, having them leave immediately, then inviting someone else is tedious.

Doesn't matter if that one ALSO includes, credit, this one is different. ST closed this, then reponed it. They've decided it's not a dupe.

It was accidentally closed.

LionCoder10 wrote:

Bump (I will not accidentally close this this time )