5 ms·
> Do the engineers that made this hand edit this file? Or did they have other source that they used and this is the build product? Do any open source product p
by godelski 3y ago
> Do the engineers that made this hand edit this file? Or did they have other source that they used and this is the build product?
Do any open source product provide all the tools used to make software? I haven't seen the linux kernel included in any other open source product and that'd quite frankly be insane. As well as including vim/emacs, gcc, gdb, X11, etc.
But I do agree that training data is more important than those things. But you need to be clear about that because people aren't understanding what you're getting at. Don't get mad, refine your communication.
> Windows was free for a year. Did that make it open source?
Windows didn't attach an Apache-2.0 license to it. This license makes this version of the code perpetually open source. They can change the license later, but it will not back apply to previous versions. Sorry, but this is just a terrible comparison. Free isn't what makes a thing "open source." Which let's be clear, is a fuzzy definition too.
- monocasa 3y agoWhat I'm asking for is pretty clear. The snapshot of code and data the engineers have checked into their repos (including data repositories) that were processed into this binary release. > This license makes this version of the code perpetually open source. It doesn't because they didn't release the source. There's nothing stopping me from attaching an Apache 2 license to a shared library I never give the source out to. That also would not be an open source release. There has to be actual source involved.
- jncfhnb 3y agoIf this ML algorithm were not open source, it would be illegal for you to release it yourself as Apache 2.
- monocasa 3y agoWhat exactly is stopping anyone from releasing a binary as Apache 2 and never releasing the source?
- jncfhnb 3y agoYou’re welcome to fuck around and find out. Go release llama2 under Apache 2. You’re saying that’s fine right? The answer to your question is that code stored as a binary is not different from code stored as text. Pickled models are code.
- monocasa 3y ago> You’re welcome to fuck around and find out. Go release llama2 under Apache 2. You’re saying that’s fine right? You're missing my point. Obviously you can't release someone else's IP under whatever license you see fit. You can release your own binary under Apache 2. Doing so without releasing the source doesn't make it open source despite being an open source license. > The answer to your question is that code stored as a binary is not different from code stored as text. Pickled models are code. I'm not saying it's not code; I'm saying it's not source.
- jncfhnb 3y agoIt is source. The data used to derive this model is not different from the brain and worldly observations and learnings of the engineers, which are not part of any open source materials.
- camgunz 3y agoWhat are you talking about "the brain" of the engineers, this is bonkers. Monocasa is being excruciatingly patient with you all but the fact is this was generated with tools and is not a source release, it's a final product or compiled or generated release.
- jncfhnb 3y agoIt’s bonkers because Monocasa’s take is bonkers. Code generated with tools is still code. This code is the source. The output of the code is the output. Monocasa is failing to understand or perhaps intentionally not understanding the difference. In some contexts a “compiled release” implies an output that is largely immutable for practical purposes. That is not what this is. It’s technically a binary object, but it’s a binary object you can easily unpack to get executable code that you can read and edit. It is a convenient format different from classical text code. The fact that it’s a binary is completely irrelevant. It’s akin to arguing that code that is provided in a zip file cannot be open source. Both because it’s a compressed file and because it doesn’t include the compression algorithm. With that understood, demanding the “tools” that were used to create the code is like asking for the engineers’ notebooks of design thoughts along the way. It has no bearing on your ability to use or modify it. This is not an open source project to make neural nets. This an open source project of a neural net. If someone releases math_funcs.py, you don’t need anything about the tools that were used to create math_funcs.py to consider it open source.
- lmm 3y ago> Do any open source product provide all the tools used to make software? I haven't seen the linux kernel included in any other open source product and that'd quite frankly be insane. As well as including vim/emacs, gcc, gdb, X11, etc. BSD traditionally comes as a full set of source for the whole OS, it's hardly insane. But the point is you don't need those things to work on Linux - you can use your own preferred editor, compiler, debugger, ... - and you can work on things that aren't Linux with those things. Calling something "open source" if you can only work on it with proprietary tools would be very dubious (admittedly some people do), and calling a project open source when the missing piece you need to work on it is not a general-purpose tool at all but a component that's only used for building this project is an outright falsehood.
- godelski 3y agoBut what's proprietary here? That's what I'm not getting from the other person. You have the algorithm. Hell, they even provided the model in pytorch/python. They just didn't provide training parameters and data. But that's not necessary to use or modify the software just like it isn't necessary for nearly any other open sourced project. I mean we aren't calling PyTorch "not open source" because they didn't provide source code for vim and VS code. That's what I'm saying. Because at that point I'm not sure what's the difference between saying "It's not open source unless you provide at least one node of H100 machines." That's what you kinda need to train this stuff.
- lmm 3y ago> But what's proprietary here? That's what I'm not getting from the other person. You have the algorithm. Hell, they even provided the model in pytorch/python. They just didn't provide training parameters and data. But that's not necessary to use or modify the software just like it isn't necessary for nearly any other open sourced project. It's necessary if you want to rebuild the weights/factors/whatever the current terminology is, which are a major part of what they're shipping. If they found a major bug in this release, the fix might involve re-running the training process, and currently that's something that they can do and we users can't. > I mean we aren't calling PyTorch "not open source" because they didn't provide source code for vim and VS code. You can build the exact same PyTorch by using emacs, or notepad, or what have you, and those are standard tools that you can find all over the place and use for all sorts of things. If you want to fix a bug in PyTorch, you can edit it with any editor you like, re-run the build process, and be confident that the only thing that changed is the thing you changed. You can't rebuild this model without their training parameters and data. Like maybe you could run the same process with an off-the-shelf training dataset, but you'd get a very different result from the thing that they've released - the whole point of the thing they've released is that it has the weights that they've "compiled" through this training process. If you've built a system on top of this model, and you want to fix a bug in it, that's not going to be good enough - without having access to the same training dataset, there's no way for you to produce "this model, but with this particular problem fixed". (And sure, maybe you could try to work around with finetuning, or manually patch the binary weights, but that's similar to how people will patch binaries to fix bugs in proprietary software - yes it's possible, but the point of open source is to make it easier)
- deleted 3y ago[deleted]