cm0002@midwest.social to Linux@programming.dev · 1 month agoVoid Linux maintainer orphans 100+ packages over AI policy disputewww.phoronix.comexternal-linkmessage-square18fedilinkarrow-up123cross-posted to: linux@lemmy.mlprogramming@programming.devlinux@sh.itjust.workslinux@lemmy.world
arrow-up123external-linkVoid Linux maintainer orphans 100+ packages over AI policy disputewww.phoronix.comcm0002@midwest.social to Linux@programming.dev · 1 month agomessage-square18fedilinkcross-posted to: linux@lemmy.mlprogramming@programming.devlinux@sh.itjust.workslinux@lemmy.world
minus-squaremofongo@discuss.tchncs.delinkfedilinkarrow-up2·1 month agoWe’ll see what happens the next time Windows source code leaks if it contains AI slop code. It’d be heaven sent to ReactOS.
minus-squarefruitcantfly@programming.devlinkfedilinkarrow-up2·1 month agoOnly the parts written by LLMs would be public domain. Everything else would still be copyrighted by Microsoft. See https://fsfe.org/news/2026/news-20260825-01.html And since there’s no easy way for outsiders to determine which part is what, it would be a minefield for anyone trying to use the leaked source code. ReactOS devs would have to stay far, far away to avoid giving MS an easy way to sink the project
We’ll see what happens the next time Windows source code leaks if it contains AI slop code. It’d be heaven sent to ReactOS.
Only the parts written by LLMs would be public domain. Everything else would still be copyrighted by Microsoft. See https://fsfe.org/news/2026/news-20260825-01.html
And since there’s no easy way for outsiders to determine which part is what, it would be a minefield for anyone trying to use the leaked source code. ReactOS devs would have to stay far, far away to avoid giving MS an easy way to sink the project