Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/1468
I'll second @knusbaum's -1. Based on points I made earlier. This has the
potntial to automatically destroy code provenance, especially if more than one
contributor is involved in a pull request. From a legal perspective, the ASF
need to be able to determine the origin of all code changes.
I would recommend any project that uses a variant of this script to
double-check with ASF legal that it is okay. I could be totally wrong, but I'd
rather play it safe.
I'd also argue that a well thought out series of commits cane make reviews
easier. For example, separating maven build changes from code changes. I'd
rather we encourage devs to think out the partitioning of commits themselves
and squash appropriately if necessary.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
