On Tue, Feb 10, 2026, at 15:12, Evgeni Burovski wrote: > >> 3. be careful not to breach any copyright or license terms (yes, we >> take those seriously!). >> > > For a contributor this recommendation is not easily actionable. "I used a > tool X and it gave me this code" --- how to make sure I understand the code, > this is clear yes I can do that; how am I meant to carefully check for > copyright?
It's near impossible, so I suspect the only way to truly play it safe is to only provide code that cannot reasonably be copyrighted. > So maybe it'd be helpful to have a link to some guide, however rough, plus > some reading material. > Or (am putting a maintainer hat on) maybe we want to ask the contributor to > show some analysis. As in, "this code is only a refcounting fix where the > origin traces straight to CPython docs" vs "this code can be traced to this > Stackoverflow answer" (BTW, what's the copyright status of that?) CC-BY-SA https://stackoverflow.com/legal/terms-of-service/public > (I planned to stay out of this thread) 😉 Stéfan
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
