Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This seems familiar #4

Open
Explosion-Scratch opened this issue Feb 26, 2022 · 26 comments
Open

This seems familiar #4

Explosion-Scratch opened this issue Feb 26, 2022 · 26 comments

Comments

@Explosion-Scratch
Copy link

https://scratchaddons.com

@cobaltt7
Copy link

cobaltt7 commented Feb 27, 2022 via email

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

Bruh, I made a video: https://youtube.com/watch?v=9vSeRMM4CV8

@cobaltt7
Copy link

I know you made a video. I know that's a rickroll. You still need to give credit to us as you stole most of our website without copyright.

@OftenUser
Copy link
Member

Alright, just please give me the repository link incase I haven't already.

@OftenUser
Copy link
Member

At least I have differences like adding gradients or not as much stuff because I didn't have much to say.

@OftenUser
Copy link
Member

I'm sorry ;(

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

@RedGuy12

Sorry if my work looks the same as yours. I really loved your layout and may have used the same one. I'll be sure to give credit on mine.

Maybe a collab in the future? No hard feelings :)

@Explosion-Scratch
Copy link
Author

@RedGuy12

Sorry if my work looks the same as yours. I really loved your layout and may have accidentally used the same one. I'll be sure to give credit on mine.

Maybe a collab in the future? No hard feelings :)

What do you mean "accidentally" you had to have gone to the repo, selected all the code, copied, pasted, changed some css variables and links, and done. That's not an "accident". You can't just do that and call it an accident. You can fork the repo, if you want, you could ask the creators of scratchaddons.com if you can use their code and negotiate that, but you can't just say you "accidentally" copied scratchaddons.com verbatim.

@Explosion-Scratch
Copy link
Author

In addition to that, you tricked the 13 people who starred this repo, thinking that you wrote this code. That unfairly gives you the credit for writing this code, and it takes away from the proper credit being given to people like @RedGuy12 and others for creating the original website.

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

Oops! My bad. I'll tell you what really happened. I went to your website, opened Dev Tools and clicked Sources... just because, it's a real thing. Besides it doesn't look "exactly" 100% like the code for ScratchAddons' repository called website-v2, or if that's even the right repository for the current Scratch Addons website. Sorry if I've written some of the apology wrong as if I never know what I'm talking about, I took that out now. Sorry for casuing something so controversial.

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

At least I changed some of the code for the very bottom of the footer, so it now says:

© 2022 MWB | Layout inspired by scratchaddons.com

I hope that's better.

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

Yet another difference: You said website-v2 was made using Hugo, well… mine wasn't, so that's why I even decided to use Sources from Dev Tools. 😐

@OftenUser
Copy link
Member

OftenUser commented Feb 27, 2022

I literally never like… thought this kind of day would ever come to me. 😲 😓 😨

@Explosion-Scratch
Copy link
Author

The layout was not inspired, it was copied, as were the styles, even the phrasing and text for most of the website.

@cobaltt7
Copy link

Sorry if my work looks the same as yours.

it's not mine it's @Hans5958's

Besides it doesn't look "exactly" 100% like the code for ScratchAddons' repository called website-v2,

Because website-v2 is made with Hugo, then compiled down to a full raw static HTML page.

or if that's even the right repository for the current Scratch Addons website.

It is.

© 2022 MWB | Layout inspired by scratchaddons.com

You can't copyright our code. And it's not inspired by,

it was copied, as were the styles, even the phrasing and text for most of the website.

Yet another difference: You said website-v2 was made using Hugo, well… mine wasn't, so that's why I even decided to use Sources from Dev Tools. 😐

Hugo just generates the raw HTML from various HTML and Markdown files we provide to it.

@OftenUser
Copy link
Member

I understand that what I did was not cool. I am going to work this week to change it. I'm still pretty new to this stuff (I'm still a kid), and you did inspire me. But I realize that mine is way too similar to yours, and I will fix it. I really do apologize, I messed up and I'm owning it. I hope you will accept my apology and we can all move on.

@OftenUser
Copy link
Member

LOL I didn't know if it was yours since this is collaborative

@Hans5958
Copy link

Hans5958 commented Feb 28, 2022

Hello, website maintainer here. I saw your video about it, commented on it, then got tagged here. I have time to burn off, so here it is. Apologizes for not-so-good English here.

As a software developer facing in this area, I'm assuming good faith on you, and you just forgot or did not know what you need to do to follow an open source license. I'm going to explain to you about this.

A license is a document that explains how something can be used or redistributed. It comes with various degree of permissions, but most times in the context of open source world, it is used to allow people to use and redistribute something.

There are lots of real-world examples of it. Sites like Wikipedia, Fandom and Scratch uses CC-BY-SA, and YouTube uses their own license. In software there are MIT, GPL, Apache etc. I'm going to focus with two licenses.

Do you know why when you click the remix button on a Scratch project, you would have the original project linked to your project? That's because Scratch projects are licensed with CC-BY-SA, which needs you to credit the original author and share the project with the same license. As I said, Scratch helps you to do these duties by giving a link to the original project, while sharing it on the Scratch website again already meant licensed with CC-BY-SA.

The same also applies with GPL, what the website is licensed with. In fact, CC-BY-SA and GPL is in the same group of licenses, called "copyleft" (that's the meaning of the rotated copyright beside the date shared). It fundamentally works the same as CC-BY-SA, credit the original author, and share the project with the same license. Put simply, while Scratch helps you with this, you need to do it yourself in something like GitHub. Last time, you haven't credited the original source, while sharing it without license, which means "all rights reserved," which is basically not the same license. In works outside of Scratch, you need to put the license along with your work. In software, it is a LICENSE file that you put on the root directory.

Now, you can ask me, "what are you going to do? Are you going to call the cops to catch me?" Well, no. In Scratch, I can just report using the report button. In GPL, I could also write them an e-mail. But most likely I won't do it, so it's just ethics, which I hope you can appreciate. It's the same when I recorded your Scratch project, add some edits to it, and telling you that "this is original." I'm sure you will be disappointed.

Regarding you using the source code or not, you could argue that the compiled code is the source code (which also hosted on GitHub), but I'll just assume that it is a basic use and derivate, which, in GPL, still requires you to use the same license. (This is why I don't want to use GPL outside SA)

I won't confuse you more by describe you any complicated implications about GPL, like to not distribute a closed version. Put simply, I just expect that you would do the same duties as you would remix a Scratch project.

Have a good day, my friend, and good luck with your works.

@cobaltt7
Copy link

cobaltt7 commented Feb 28, 2022

I'm still a kid

we all are here lol

I am going to work this week to change it.

so really all we're asking you to do is to:

  • copy the LICENSE file from SA to this repository
  • credit Scratch Addons on the README and/or website for the design and code

thanks

also it's kinda annoying when you put things into 5 different posts when you can just make one

Bruh, I made a video: youtube.com/watch?v=9vSeRMM4CV8

also you look legit 5 in that yk you need to be 13+ to have a github or youtube channel

LOL I didn't know if it was yours since this is collaborative

i mean, lots of people, including me, contributed, but hans made most of it

@Explosion-Scratch
Copy link
Author

also you look legit 5 in that yk you need to be 13+ to have a github or youtube channel

Wait, wasn't that like a meme clip? Also @MWB6763 from that video it really seems like you're bragging about copying the ScratchAddons website, and over here you're saying your super sorry and:

Sorry if my work looks the same as yours. I really loved your layout and may have accidentally used the same one. I'll be sure to give credit on mine.

So you made a video mocking ScratchAddons and bragging about copying the website, then say you accidentally copied the website? At least be honest. All you need to do to fix this is

  • copy the LICENSE file from SA to this repository
  • credit Scratch Addons on the README and/or website for the design and code

(also @RedGuy12 shouldn't that be and, not and/or?)

@Hans5958
Copy link

Hans5958 commented Feb 28, 2022

Chill, Explo, it's fine. It's called "kids playing around", and I'm fine with it.

@Explosion-Scratch
Copy link
Author

Chill, Explo, it's fine. It's called "kids playing around", and I'm fine with it.

Yeah, sorry, got a little worked up, I didn't even do anything for the current version of the SA website. It is a bit annoying to see it copied, but ig if the kid's like 6 and coding that's fine so idrc.

@Cool-Scratcher
Copy link

I'm gonna take credit for exposing Splashy Studios since I found their YouTube comment on one of our videos. (It's deleted now)

@OftenUser
Copy link
Member

@Explosion-Scratch I'm not 6 I'm almost 13 as of this post

@TechDudie
Copy link

cool down bruh we're all coders here it doesnt any make much difference in the long run just credit other peoples code and everything works out fine 😎

@cobaltt7
Copy link

just credit other peoples code and everything works out fine 😎

That's the problem. They aren't giving proper credit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants