There is no need. It's illegal. Cut and dry.

You keep denying the fact, that I said it can happen, nothing prevents microsoft itself from paying a dev to insert code in ReactOS or Wine, you cannot guarantee that it doesn't happen or whoever saw the source code try to do a PR on the jira or github , now the ReactOS team needs to consult a legal expert, to know the impacts on the ReactOS project, with the disclosure of the source code. You are not helping, I'm talking about real things and problems, none of this has happened yet, but it can happen!

No one ever said that it couldn’t happen. What we’ve been telling you over & over is that no one wants it to happen & no one wants to hear anything about the leaked source code here. You keep bringing the source code up, but we really don’t care about it. The project already had experience with dealing with this type of situation. They don’t want code from anyone who’s looked at the leaked source -period. Nothing that you could ever say will change that.

No one ever said that it couldn’t happen. What we’ve been telling you over & over is that no one wants it to happen & no one wants to hear anything about the leaked source code here. You keep bringing the source code up, but we really don’t care about it. The project already had experience with dealing with this type of situation. They don’t want code from anyone who’s looked at the leaked source -period. Nothing that you could ever say will change that.

One thing is leakage of old programs and utilities, another thing is leakage of OS, it is not possible to deal in the same way, I am not posting 10 links, only an idiot acts the same way in different situations, what I am pointing out is a problem future, you are thinking that problems of the past, are equal to problems of the present, it is obvious that team ReactOS will have to change, I mean in the way of treating source codes for PR, I am not talking about microsoft source code, but about practices that ensure clean room reverse engineering!

Now ReactOS can have compatible code and move faster in development! https://www.reddit.com/r/windowsxp/comments/iz46du/comment/g6gwcpo

are you kidding? copyright laws are clear and quite similar everywhere in the world (their enforcement or less is another thing, and i wouldn't count on it when microsoft is on the other side). if you have a leak and/or someone publishes your code, you still have copyright protection and all legal and economic rights to it. if i buy the music sheet of a song it doesn't mean that this song doesn't have copyright anymore and that i can use it as i wish. the same for code.

Copyright laws only work for those who have money and influence, if a corporation violates it, nothing happens, it rarely loses. But honestly, in a world where people use mods and hacks in video games, consoles, smartphones, TVs, etc., even if they don’t know programming language or electronics, where everything is available on the Internet, you can imagine a world where it doesn’t happen, believe in the worst, but do not try to understand that the situation has changed! You have to know that a student who participates in GSoC 2021, has already looked at the microsoft source code, nobody can know!

i read the link. i still can't believe someone really wants to use it as his/her very own. and, btw, the fact that someone included plot theories mockumentaries in the pack, as written in that link, makes me wonder a lot both in the origin and authenticity of the content.

https://www.theverge.com/2020/9/25/21455655/microsoft-windows-xp-source-code-leak

it's not only question of money and power, but also of the good name of the project and development blocked. maybe you don't remember the audit times. that was hell, no development at all for over a years, and for waaaaaay less than this

https://www.zdnet.com/article/microsoft-admits-its-gpl-violation-will-reissue-windows-7-tool-under-open-source-license/

I know, there are ex employees who make complaints, call microsoft saying that company x, where they worked uses unlicensed software, even though the complaint is false, the misfortune has already been made, the company becomes a pandemonium, with microsoft supervision!

ok, so can we please avoid that (again)?

The only way to avoid it is to adopt code verification practices!

The only way to avoid it is to adopt code verification practices!

no

I speak of PR in the jira or github, nobody has the power to know that they have seen or not source code, nor can they guarantee whether the person did reverse engineering or not!

they can. clean room reverse engineering is done by two persons, not just one

does anyone tried to compile leaked winxp source?

If you look at the previous posts, no one will say yes, even if someone has compiled it!

so basically you're saying "since no one can say if you're behaving correctly, let's do something openly unlawful"

I'm saying that no one can predict the damage done by disclosing the source code, since it is the source of the entire OS, this has great implications!

(sorry for the italian, just saying that i'm from veneto, a region of italy, before someone thinks it's racism against italians or such)

This doesn't just happen in Italy, Trump's election is living proof of that!

ok, but you can predict that, if you use this in your project, the project will be shut down

This microsoft does anything it sees as a threat, but now microsoft has big problems, which they saw with mods, hack, viruses, trojans and customized versions of xp!

i cant believe the stupidity of people either some of them are genuinely this dumb or want to intentionally shut down ReactOS by playing dumb

But there's one argument which is that you could look into leaked source code, see how stuff works and code it differently, but it's also wrong I think

But there's one argument which is that you could look into leaked source code, see how stuff works and code it differently, but it's also wrong I think

and after doing that you are not allowed to contribute to ReactOS... nice

here's what you need to do: 1. dont look at the windows source code 2. live a happy and normal life

here's what you need to do: 1. dont look at the windows source code 2. live a happy and normal life

The source code has become public knowledge now, even though it is intellectual property, anyone in the world can look at the source code, create compatible code, but will not be able to use the original source code!

What about ReactOS on Wii? xD I remembered someone tried to boot in DosBox, also available on Wii.