On Thu, Apr 06, 2017 at 06:15:52PM +0000, Brett Cannon wrote: > But the bot will never be adjusted to make its own call on what is or is > not covered. It's too risky legally to get this wrong, e.g. there are > patents guarding against how you iterate through things in telecom > switches, so you could theoretically use a patent by changing a single line > in a code example by how you iterate through something. I know that's an > extreme example, but that's the sort of world we have to guard ourselves > against. We also have lots of companies that ship Python in their product > who would be totally screwed if we got this wrong as they would then > potentially be liable for patent licensing costs.
Right, I was imagining a scenario in which the bot could be "kicked" to go fetch CLA information if it misjudged the triviality of a patch. Perhaps too much trouble than it's worth, though, given how critical this is to get right (which I certainly didn't have a good sense of before your message). Thanks for the (highly informative) reply! AJ
signature.asc
Description: PGP signature
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
