On 3/11/26 8:26 AM, Kai Krakow wrote: >> ... or only contribute LLM-free proposals, since LLM-free contributions >> are compliant with the policy if it *does* apply, and cause no issues if >> it *doesn't* apply. ;) > > That's a logical consequence if code is actually my own creation. But > I cannot be so sure about code I include from other sources (be it > vendoring some dependency, or copying a useful function from another > open source project with a compatible license, where "vendoring" is > something to avoid anyways, I don't mean to advertise vendoring here, > and I don't mean to copy code without proper attribution). The > definition aboves helps to narrow down when *not* to use code from > other sources. > > Thanks again, I think this answered at least all *my* questions for now.
But just like distros dislike vendoring *libraries*, they also tend to dislike "copy half of a library but without calling it vendoring". You could always just, take the "logical consequence" and use dependencies instead of copying. -- Eli Schwartz
OpenPGP_signature.asc
Description: OpenPGP digital signature
