Re: Proposal -- Interpretation of DFSG on Artificial Intelligence (AI) Models
Soren Stoutner <[email protected]>
| Newsgroups | gmane.linux.debian.devel.vote |
|---|---|
| Organization | Debian |
| Message-ID | <6154585.UjTJXf6HLC@soren-desktop> |
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 [email protected]
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmglB0MACgkQwufLJ66w tgOSCw/8DoiTDlrhyIIp6xlGgdm8s1HHmMFIeEZpTGwPts8llgFcaDB6PSdayIUd b4bthmhcSmeuOrNcGckRkcW4O8O/doIQ+Zafs1VMb0N1KmJXv0pzlG25vMhib8CX gNmszuUse8WFsDbjiQU+tHl9wISqX4x/O5ZNjVM8kCWUdC0aQHe15HCGEnTIqvwl flsxzqxN2nmBPkbnMjViOrVFOMO69z/txie7xxBq4nkB438St42IkTXp8DKckNjg JgN3MpSR1hdakL3qP+Ppt9PbszwgB1TCWCV25QaBWTZsy6ASX9vhjmXpAsa3fRol Xx7fUOhJb+QorU15ylUOo32AO9oCv21KBTtHjavt4CJBRQzbxnixwwKlLiBTKDVb EHocYNE9pFsqJHszqalQUnIQwmjks53yRBlTxk6cA8ItXj/8MKrw1ucXQrwSU4Qu KhGjbDSyuvQwv27Ufmph2c8iyMLetMCq5SvZ+P7modVrQ7c4gjVanLHCduHa3O+C T71V8KRB/cQ2cZpZGXfTtkwKAaUHI/VidI9VuQptEoZFWaemLS0ZaxiPbp/ZeREP 0LhkPinn+SLbOYZIQLwGhQAEUaSbDd6KpB9+edG74wehzRHOW8U9x7X8ckIdnUPW eeW/B8SIa0/Ol9KzBu2jDsUsKYEwjWHvbJMa/TpUbZAZEh9Ul4g= =aVxr -----END PGP SIGNATURE-----