Phew... If I ever plan to discuss about such nonsense, I will tell ya next time, ok?

Do you REALLY think that I am the only one saying this? Do you REALLY think I did not talk to the others before saying NO? Sorry for you then.

And yes, the first reason why we leave the whole project in IGNORE state is because they steal code by modifying the licensing headers, YES UNDER THE SAME LICENSE IT'S STILL NOT LEGAL WHAT THEY DO.

The theme is claimed questionable, NOT ILLEGAL. Same goes for the whole code they make, because it IS contaminated from it's very start which is the 2nd reason why we leave it in IGNORE state. The guy who started all this was a forum guy who was pissed for being banned for his MULTIPLE attempts to add illegal code anywhere trying to harm us and the whole project with it. Thus this discussion is OVER.


Am 10.09.2018 um 00:03 schrieb theUser BL:
Isn't it fun that ppl simply don't understand a "NO" I give 'em in the
forums?!
Thats only a comment of ONE developer. If your medical doctor syas you 
anything, do you never asks a second doctor again for the same thing, to see if 
he was right?

I even explained why and that GreenteaOS is not more than
stolen ROS code (*)
The only problem you have had is, that he have removed the name "ReactOS" 
everywhere. But it is still al under the same license like ReactOS.

filled with questionable code sources like the
betaarchive forums. So "NO" means go on the other dev's nerves for a
ugly theme violating our and MS's copyrights?
Why is an Win8-theme violating MS-copyright but
- changing the color of WineMine to Microsofts WinMine
- copying the XP explorer.exe 1:1, only the images on it are different
- having a Look And Feel VERY similar to Win2000
- etc
is all ok?

Greetings
theuserbl
_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to