Not without getting sued, no. But you could do a double blind on it. One person reads it and describes it in freeform prose, and another reads the prose then writes code to implement it as described. In the absence of documents describing the implementation details, this can sometimes work as it will avoid the copyright argument.
Still sketchy though, and you’d really have to verify isolation.
Still difficult in another sense. The person who was reading the code live on twitch or whatever, could never in the future work on wine. They’d have to commit to long term seperation from the project.
(Plus, they’d probably want to do it anonymously, since they’ve illegally obtained the source code.)
Well, it’s out there, but Wine devs can’t look at it.
Not without getting sued, no. But you could do a double blind on it. One person reads it and describes it in freeform prose, and another reads the prose then writes code to implement it as described. In the absence of documents describing the implementation details, this can sometimes work as it will avoid the copyright argument.
Still sketchy though, and you’d really have to verify isolation.
What if they live streamed the entire process, like on twitch?
Still difficult in another sense. The person who was reading the code live on twitch or whatever, could never in the future work on wine. They’d have to commit to long term seperation from the project.
(Plus, they’d probably want to do it anonymously, since they’ve illegally obtained the source code.)