4 ms·
Don’t entertain meetings without compensation from megacrop. But the project is open source. The author provided the right for them to take it in any way possib
by orochimaaru 2y ago
Don’t entertain meetings without compensation from megacrop. But the project is open source. The author provided the right for them to take it in any way possible and copy it. If I’m not mistaken the MIT license allows what they did.
I’m assuming the complaint is more about Microsoft duplicity in asking for information as opposed to the forking of the code. The latter is fine - the license explicitly allows it.
- robmccoll 2y agoYou are mistaken. The license explicitly allows it subject to the terms of the license: > The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Microsoft didn't follow these terms. They copied "substantial portions of the Software" and didn't include the notice.
- palata 2y agoWhich notice? None of the *.go source files I have opened in Spegel contain a notice. Microsoft cannot remove a notice that does not exist... In my opinion, it's the Spegel author's fault: they should have added a notice in every single file!
- tedivm 2y agoThe "notice" is the literal license file. It is illegal to strip someone else's license from their work. It doesn't matter that they replaced MIT with MIT, because they stripped the author and attribution from it. https://github.com/Azure/peerd/blob/main/LICENSE https://github.com/Azure/peerd/blob/main/LICENSE If you read that file you'd think that Microsoft was the copyright holder, but they very clearly aren't.
- palata 2y ago> but they very clearly aren't. Peerd seems very different from Spegel, so Microsoft does hold quite a bit of copyright over Peerd. Now I genuinely wonder if the main LICENSE should say "copyright Spegel and Microsoft", or if somewhere in the repo Microsoft should just have a copy of the Spegel LICENSE file?
- robmccoll 2y agoGenerally, you would want to do one of: a) Keep any code that you've pulled in from another project in its own directory structure with a license file indicating where it came from and its licensing terms. b) If you intend to modify the code or integrate it more tightly with your own, copy the notice into each source file that was taken and perhaps put a pre-amble along the lines of "Portions of this file were copied from XXX under the MIT license as follows:". Ideally you would make a commit with the file in its initial state as copied, and then if you ever need to determine what came from where and how it was licensed, it shouldn't be too difficult.
- palata 2y agoGenerally, what I take from this discussion is that what you want to do is get as much inspiration as you want from the code, but absolutely rewrite it from scratch such that it is yours and yours only.
- saagarjha 2y agoThat would still be infringement.
- palata 2y agoAbsolutely not. How would it be infringement to write your own code from scratch?
- saagarjha 2y agoIf you read someone else's code and copy it down, then you are infringing on it. There's a reason why https://en.wikipedia.org/wiki/Clean-room_design https://en.wikipedia.org/wiki/Clean-room_design exists.
- palata 2y agoWhere did I say that you copy it? I used the words "you rewrite it from scratch", not "you copy it".
- w0m 2y agoIt looks like they relatively recently migrated the entire codebase from Apache to MIT. I wonder if that was in relation to pulling in code from Spegel. They updated ~every header.