4 ms·
1. What does "source code" even mean, in this context? I don't buy the requirement that all training data needs to also be open sourced for any of the things th
by ben_w 3y ago
1. What does "source code" even mean, in this context? I don't buy the requirement that all training data needs to also be open sourced for any of the things that people normally discuss with regard to open source topics (though that kind of openness would be good for different reasons).
Network weights and biases plus architecture models are things that can be directly build upon, just like graphics are, and I would count a photo licensed under, say, MIT, as "open source" even if the JPEG codec on the camera which took the photo was not.
2. How are these two licenses compatible with https://opensource.org/osd https://opensource.org/osd part 2. Source Code?
a. https://opensource.org/license/unicode-license-v3 https://opensource.org/license/unicode-license-v3 - separately lists data files
b. https://opensource.org/license/nasa1-3-php https://opensource.org/license/nasa1-3-php - "Notwithstanding any provisions contained herein, Recipient is hereby put on notice that export of any goods or technical data from the United States may require some form of export license from the U.S. Government. Failure to obtain necessary export licenses may result in criminal liability under U.S. laws. Government Agency neither represents that a license shall not be required nor that, if required, it shall be issued. Nothing granted herein provides any such export license."
- szundi 3y agoWhatever, but I think the word “source” has a meaning that is pretty sure does not equals “end result binary blob” after a lengthy process
- mvkel 3y agoAgreed. It's like saying it's not true "open source" if you don't include then node_modules folder in your git repo
- Nullabillity 3y agoThis situation is more like they didn't include the package.json.
- HPsquared 3y agoSimply put, it should be reproducible with the published material. An ML model is definitely not reproducible without the training data (or a recipe to reproduce the training data).
- wruza 3y agoThis was said with source code and binaries in mind. Source code is easy to verify, modify and rebuild. Binaries are in practice non-modifiable, non-verifyable except for costly reverse engineering. Large models don’t work like that. The only practical way to modify (finetune, lora, merge) a model is using its binary form. A source dataset may be interesting, but it’s non-modifiable and non-reproducible in practice due to training costs. Rebuild process is usually non-deterministic, so “verify” is basically not an option. So technically true, practically complicated. Open weights and open dataset would be better terms.
- jauntywundrkind 3y agoTo me, open source strongly implies an ability to usefully tinker & play with something yourself. Some trained weights doesn't seem to qualify, to me.
- ben_w 3y agoFor a lot of these models, especially the interesting ones, it's the only thing we can tinker and play with. Well, most of us. I'm sure there's at least one person here who can afford to burn 25 million USD on compute just for fun.