On Wednesday, May 14, 2025 1:51:27 PM Mountain Standard Time Aigars Mahinovs wrote: > That is not what I asked. Redistributing is a completely different > question from a different point of DFSG and even from interpretation > of whether DFSG even applies to the training data as such. And that in > turn very specifically depends on a very isolated question - what is > the preferred form of modification. And that is why I am > *specifically* asking how your opinion that "training data is the > prefered form of modification" works in real world examples. > > Only that specific criteria. Not about Debian, not about main or > non-main. Not for other people or for the project. > > What does "preferable form of modification" mean for *you*? For > example in that case above. Is the raw training data *really* _the_ > preferable form of modification? Or is it the data definition? Which > would you *prefer* to *modify*?
In my opinion, the preferred form of modification is the raw training data. I apologize if I did not make this clear in my previous email. I thought I had. For an ML to be included in main, the raw training data must also be included in main. To be more specific, to be included in main, the ML program source code, the weights (which can be thought of as the compiled training data), and the raw training data (which can be thought of as the training data source code) must all be DFSG-free and must all be included in main. Otherwise, the DFSG-free parts can be included in contrib and the non-DFSG- free parts can be included in non-free (assuming we have the right to distribute them). I know there are people who disagree with this assessment of the raw training data being the preferred form of modification, and I can understand and respect those who feel that way. That is, after all, the core of this entire discussion, which would not exist if there weren’t disagreements on this issue. However, as you asked my opinion of what Debian’s policy should be, I endorse the above. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
