As long as we don't release with their code in it, I think it's fine for it to be committed & then reverted.
Note too, that AFAIK, there's no way for us to verify CCLAs :S I was imagining adding this to our automated build. E.g. maybe have a coho command for doing this, and then having our build fail if that command ever fails. On Fri, Apr 25, 2014 at 3:37 PM, Marcel Kinard <[email protected]> wrote: > This sounds to me like the simplest approach. > > Would a git commit hook catch this scenario so a commit never goes in > without ICLA verification? Even if a non-ICLA author's commit can be > reverted, that content is still in the repo, which doesn't sound idea. > > On Apr 25, 2014, at 3:31 PM, Andrew Grieve <[email protected]> wrote: > > > Instead of having a map of username -> Real Name, we could maintain a > list > > of usernames that we know have a valid ICLA. > >
