-
c0lide opened this issue · 24 comments
This is an issue now because I'm still maintaining the project myself, when I no longer can/will then there's no point keeping it unlicensed anymore. I don't really want someone taking my work as I do it and branding it as something else; That's not even an attack to anybody I just want to protect the time and effort that I put into it.
Also, Sintco Sparxmaths Solver is basically just a rebranded Azalea, and they used the code from when it was still under the MIT license.
The copyright issues come from after I removed the license and they used code from commits where all rights were reserved to me, of which I need to grant permission to do, and I haven't done, so they need to revert the code to a build which was still licensed.
As I mentioned before, I'm not attacking anybody. Najm took the code from Azalea when it was still under the MIT license without any notice or requesting, which, legally, they can do, but morally, I would say they should have at least mentioned that they were going to use the code.
Afterwards, I filed an issue because the license didn't match, which in itself was a license violation, and after they fixed it I gave the green light and politely asked if they could not use the Azalea code but rebranded in their solver, and instead are welcome to reference the code to their desires. My issue was closed without a reply.
Recently, after I pushed my first working prototype of Azalea, Najm took the code, which they weren't permitted to use, built it rebranded as Sintco, without my name mentioned ANYWHERE except in the README and license (mind you this code they are using is now licensed under copyright), obfuscated it, downgraded the version to 3.0.0, and released it, after which they revoked my permission to submit issues.
That seems weird, doesn't it? Blocking my permission to submit issues, and obfuscating the bundle. It's almost like.. they were aware they they are not allowed to use the code they are using. I am fully in my rights to do what I am doing, and I simply want there not to be essentially 2 of the same project, except one is branded and authored by somebody else even though the code belongs to me.
I hope you understand, Thanks, Rosie 💝
Hi @acquitelol & @c0lide.
I would like to formally request permission to use elements of your repo "Azalea" in my project.
Thanks, Najm
Read the reply above this 🤷🏻♀️
holy fuck LMAO how hard is it to just respect her wishes (and LICENSE) and fuck off
holy fuck LMAO how hard is it to just respect her wishes (and LICENSE) and fuck off
Whats your problem?
I've been watching this problem since it started and it seems like @NajmAjmal will not just respect the license and wishes of Rosie
What changes could i make to my repo to continue using the latest version of bundle.js etc.
Hi @acquitelol & @c0lide.
I would like to formally request permission to use elements of your repo "Azalea" in my project.
Thanks, Najm
Well for starters, I would like not to permit anyone to extend the current code as it stands under a new name (as I mentioned in my comment above), so don't take it personally please.
What you can do, is to decrease the release down to one that is still licensed, aka 3.2.0 and lower, like I mentioned in my issue on your repository. If you would like to implement auto bookwork, you are of course able to write it yourself, loosely referencing my code where needed. You are not allowed to use the latest code though, I'm sorry.
However, when I do stop maintaining the code myself, voluntarily or not, I will license it under GPL-3 or MIT again and notify you so you can extend it or edit it as much as you like.
Thanks, Rosie 💖
yes, he just tried to work out an alternative solution.
What changes could i make to my repo to continue using the latest version of bundle.js etc.
Hi @acquitelol & @c0lide.
I would like to formally request permission to use elements of your repo "Azalea" in my project.
Thanks, Najm
Which Rosie has made clear she doesn't want to do
What changes could i make to my repo to continue using the latest version of bundle.js etc.
Hi @acquitelol & @c0lide.
I would like to formally request permission to use elements of your repo "Azalea" in my project.
Thanks, Najm
Well for starters, I would like not to permit anyone to extend the current code as it stands under a new name (as I mentioned in my comment above), so don't take it personally please.
What you can do, is to decrease the release down to one that is still licensed, aka 3.2.0 and lower, like I mentioned in my issue on your repository. If you would like to implement auto bookwork, you are of course able to write it yourself, loosely referencing my code where needed. You are not allowed to use the latest code though, I'm sorry.
However, when I do stop maintaining the code myself, voluntarily or not, I will license it under GPL-3 or MIT again and notify you so you can extend it or edit it as much as you like.
Thanks, Rosie 💖
Thanks @acquitelol.
I will downgrade ASAP
I do not appreciate the presence of @FieryFlames in this issue.
Thanks, Najm
Of course, just be aware I am doing this because I'm not an unfair or mean person.
In my honest opinion, I would be the most satisfied if code from Azalea wasn't used at all, but it's too late for that now and I've given up trying.
What changes could i make to my repo to continue using the latest version of bundle.js etc.
Hi @acquitelol & @c0lide.
I would like to formally request permission to use elements of your repo "Azalea" in my project.
Thanks, Najm
Well for starters, I would like not to permit anyone to extend the current code as it stands under a new name (as I mentioned in my comment above), so don't take it personally please.
What you can do, is to decrease the release down to one that is still licensed, aka 3.2.0 and lower, like I mentioned in my issue on your repository. If you would like to implement auto bookwork, you are of course able to write it yourself, loosely referencing my code where needed. You are not allowed to use the latest code though, I'm sorry.
However, when I do stop maintaining the code myself, voluntarily or not, I will license it under GPL-3 or MIT again and notify you so you can extend it or edit it as much as you like.
Thanks, Rosie 💖Thanks @acquitelol.
I will downgrade ASAP I do not appreciate the presence of @FieryFlames in this issue.
Thanks, Najm
❤️ glad you feel that way. Me personally I don't appreciate people rebranding someone else's project and violating their license and wishes by not crediting them
fiery you're so real with the passive aggressiveness
this is the most drama i've ever seen over an extension for a maths education app
holy moly.
it looks like you are attacking @NajmAjmal. they also put effort into their extension untill the recent sparx update.
Why dont you grant perms to him?
@c0lide FYI, they didn’t actually make the code before the update either.
This is the original https://github.com/alexlostorto/magic-notes
what does that have to do with anything
what does that have to do with anything
idk, ask @00ctrl
no they were saying najmajmal took the code from https://github.com/alexlostorto/magic-notes
it looks like you are attacking @NajmAjmal. they also put effort into their extension untill the recent sparx update.
Why dont you grant perms to him?@c0lide FYI, they didn’t actually make the code before the update either. This is the original https://github.com/alexlostorto/magic-notes
LMAO he really skidded twice for a math extension
it looks like you are attacking @NajmAjmal. they also put effort into their extension untill the recent sparx update.
Why dont you grant perms to him?
@c0lide FYI, they didn’t actually make the code before the update either. This is the original https://github.com/alexlostorto/magic-notes
LMAO he really skidded twice for a math extension
I knew this too 😭😭😭
The magic notes guy doesn't care enough I don't think 🙏🏻