Matt Armstrong <marmstrong@google.com> writes:
>
> Thanks for thinking about this David.
>
> The good news: in looking into this further, the issue of leaving (c)
> claims in code is secondary.  The primary thing I'm supposed to do is
> send patches with my work email.
>
> If I become a significant author in some file, adding a (c) Google makes
> sense if that the normal thing to do in notmuch.  I'll keep that in
> mind.

Yeah, for example most people creating a new file will put their name in
the copyright header. Or maybe rewriting a significant amount.
But it's an individual judgement call.

>
> Google's open source lawyers tell me that regardless of what (c) marks
> appear in code, the author of code (e.g. significant patches) retains
> copyright unless other arrangements are made, such as those you see in
> FSF projects (https://www.gnu.org/licenses/why-assign.en.html).

Never argue with a happy lawyer, that's motto :). It sounds like we're
good to go; I merged patch 2/2 after moving the NEWS. Then I wanted to
shorten the summary line of the commit, which got a bit more intrusive
than I wanted, hopefully it conveys the intent of the existing message.

d