Windows 10 steals code

Topic

New Reply

Windows 10: Microsoft now credits maker of package manager it ‘copied stole’ – but offers no apology

Windows 10 steal more code again. Now Zdnet published story that has been on other sites for years claiming that Windows 10 is 80% stole code and 20% from old windows code.

Reply | Quote

Replies

MS did not steal the code, they discussed using the code / base with the developer – as the project is open source there are no prohibitions on using the code.
What MS failed to do was acknowledge the original author. Although they are not required to do this with open source software, it would have been polite to do so.

cheers, Paul

2 users thanked author for this post.

b, Ascaris

Reply | Quote

I seem to remember that open source software distributed under the Free Software Foundation GNU General Public License must include a notice mentioning the original authors, even when the software is modified or added to another and even if this is done in order to make a commercial product than is then sold for profit. With this obligation applying also to those subsequently using the modified and or commercial versions to create their own versions. Naming the software creators is an obligation, not a matter of personal choice.  Perhaps a different kind of licensing was involved here.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

Most of Windows 10 code is from open source when analysis the source code that MS posted. Nothing much is original MS work unlike previous version up to Windows Xp. After XP, MS started to use open source code without giving any credit to the original people. This is why there are more flaws and bugs since MS can not figure out code once they mash it into the OS and wait for the open source community to find the fix for them.

Reply | Quote

The Microsoft group project manager for WinGet had already apologized to the AppGet developer before the start of this thread:

@kayone First of all I regret how we handled the communication during the interview process. A post interview email should have come from me not just an automated email. I own that and I am truly sorry.
https://github.com/microsoft/winget-cli/issues/353#issuecomment-635991975

He had also already arranged for appropriate credit to be attributed in the WinGet readme file:

Just published https://devblogs.microsoft.com/commandline/winget-install-learning/ and an upcoming update to the readme.md on the main repo to provide credit to @kayone. I would like to thank @kayone for working with me over the last couple of days it was a pleasure as always.
https://github.com/microsoft/winget-cli/issues/353#issuecomment-636374783

Those actions were accepted by the AppGet developer within the last 24 hours:

Thanks @aclinick for the blog post, it means a lot.

There are a few areas Andrew and I have been discussing, hopefully we’ll have something to share with you guys soon.
https://github.com/microsoft/winget-cli/issues/353#issuecomment-637016016

Reply | Quote