#CandyZen Old
next dome
cloud raven
https://www.reddit.com/r/zen_browser/comments/1j37via/full_zen_browser_theme_ava...
damn i love that color scheme
next dome
damn i love that color scheme
thx i love it
alpine tangle
woah.... bro just made a new browser! 🔥
grave sandal
that urlbar animation is really awesome 
i love it
faint salmon
where install instructions
faint salmon
ok
next dome
where can I upload
next dome
I'll upload to github here the folder I need to send
faint salmon
ok
next dome
faint salmon
https://github.com/blatantq/CandyZen
...thats just pineapple fried and natsumi
@arctic owl
next dome
Yes, I'm saying it's customized
next dome
aha only wanted to share my theme which is created from all these mod
and if anyone would like it, I just wanted it to be a simpler copy paste
faint salmon
youre still plagiarizing our work since you didnt credit us properly for it
next dome
on github I've posted links to all the other mods that are included
sweet igloo
Obligatory not a lawyer and this is not legal advice:
- Natsumi is under the MIT lisence
- Cohesion is under the GPLv3
- Advanced Tab Groups and My Internet have no listed license, which means theyre technically propreitary
Just because things are on github and are source-available, does not mean you can do whatever you want with them. Licenses are legally binding, and have been repeatedly found in court to be so. MIT requires, for example, that you include the MIT lisence alongside the code you copied (from Natsumi in this case). GPLv3 requires several things, but most notably that your repository, which would be considered a derivative work, also should be licensed under GPLv3 or a compatible license. Currently, you have no listed license, so your repository is propreitary... which may be a copyleft violation. Propreitary software you cant use at all really, without expressed permission from the author - so advanced tab groups and my internet cant be used in your repository most likely.
Dont mean this to sound harsh. Its very common for people not used to this stuff to make these mistakes and its genuinely chill, but these ARE important things. Both for legal reasons, and also to respect the work of others
my person advice is you either look through the licenses and adjust your repository accordingly (remove the propreitary sections, add a GPLv3 license to the whole project, add a copy of the MIT license alongside Natsumi) or you adjust the repository to include no code you yourself didnt write, but just share the steps you took to make your theme out of these other ones so someone could replicate it themselves without you violating any license
faint salmon
my person advice is you either look through the licenses and adjust your reposit...
there's actually more license violations prob
since the zip file contains a fuckton of zen mods
sweet igloo
ohhhh i didnt even notice that
yeah then its likely a massive number in total. I dont really want to look into every included zen mod and what their licenses are haha but if the OP of this plans on keeping them in the repo thats something theyll need to do
faint salmon
one can assume theyre MIT given the theme store repo is MIT licensed
sweet igloo
if so then it wouldnt be too bad to fix, as MIT is very permissive, but yeah thats one violation for every included mod then
faint salmon
mhm
lemme open an issue rq
25 license violations found
-# 27 - 2 no license = 25 violations
next dome
also if I add to the folder LICENSE from all mods that are included so it's ok?
otherwise thank you for the explanation
I'm doing this for the first time
sweet igloo
alongside the code of each mod that is licensed as MIT, there needs to be a copy of the MIT license. Thats Natsumi and probably all the mods, but it might be good to double check
otherwise, you need to make your entire repository under the GPLv3 repo (there may be other GPLv3 rules im not thinking of rn, I suggest reading through the license to be sure) for Cohesion
you also need to remove the code of anything that isnt licensed, such as Advanced Tab Groups and My Internet. You cannot legally use their code in your repository.
again, not a lawyer and this is not legal advice
this is the admittedly less fun part of open source haha, but its an important part nonetheless
next dome
that's quite a lot to delete :DD ,but thank you, it will come in handy
arctic owl
@sweet igloo @faint salmon @next dome
Hey all, sorry this confusion probably stemmed from me. I saw this on reddit and encouraged the OP to submit here. I didnt take a super close look at the work, but just at a glance noticed a few differences so I thought it was unique.
sweet igloo
No worries! Its a really cool setup and I'm glad they submitted. Im always happy to get a chance to explain licenses to people haha
All this was was a classic (and fairly harmless if fixed) mistake made by someone new to open source
sweet igloo
that's quite a lot to delete :DD ,but thank you, it will come in handy
also on this - you may be able to include the propreitary bits if you get permission by the people who made them. As theres no license as far as i can see, no one can say how theyre allowed to be used but them
next dome
okey thanks for the info, I'll keep an eye on it
sweet igloo
also on this - you may be able to include the propreitary bits if you get permis...
I reached out to both of the people who made them, and they had just both forgotten to add a license. They both opted for MIT, so if youre still working on this, you can use all the code in your repository now so long as you add copies of the license alongside it
faint salmon
nice
next dome
okay thank you
faint salmon
ok now theres one problem with the license in your repo
it's in the root folder of the repo and says "Copyright (c) 2024 Green (@greeeen-dev)" which pretty much means i own candyzen
when i dont
hold up ill restructure your repo and do a PR
faint salmon
opened PR: https://github.com/blatantq/CandyZen/pull/2
queen coral