The comment at dotnet/corefx#3017 (comment) which pointed to dotnet/coreclr#1329 (comment) led me to believe that the done thing was to put one's own name in copyright headers when creating a new file from scratch.
The comment at dotnet/corefx#2401 (comment) suggests that it is not.
The combination leaves me not knowing what I should do if I want to contribute a PR which would involve new files.
(The discussion on that last comment got side-tracked slightly [my own fault] with the question of what would be the best policy for an open-source .Net to have. I want to know what I should put in a file header right now, if there's some unclear approaches and a clearly-allowed-today approaches, I'm happy to use the clearly-allowed-today one).
The comment at dotnet/corefx#3017 (comment) which pointed to dotnet/coreclr#1329 (comment) led me to believe that the done thing was to put one's own name in copyright headers when creating a new file from scratch.
The comment at dotnet/corefx#2401 (comment) suggests that it is not.
The combination leaves me not knowing what I should do if I want to contribute a PR which would involve new files.
(The discussion on that last comment got side-tracked slightly [my own fault] with the question of what would be the best policy for an open-source .Net to have. I want to know what I should put in a file header right now, if there's some unclear approaches and a clearly-allowed-today approaches, I'm happy to use the clearly-allowed-today one).