Attach appropriate header (copyright) to go files

[wackxu]

@jlewi @zjj2wry @gaocegege @ScorpioCPH

[gaocegege]

Do you mean the copyright header? I am not sure if I understand your idea 🤔

[wackxu]

@gaocegege Yes, copyright header for go files is confused， we can make a boilerplate for all go files

[gaocegege]

SGTM

[ScorpioCPH]

copyright header for go files is confused.

Do you mean we need an auto-generate script?

[jlewi]

Does anyone have a link to what the requirements are for copyrigh/license headers?

/cc @foxish @vishh @aronchick

[aronchick]

uh, no idea. /cc @ewilderj

[ewilderj]

Check out https://opensource.google.com/docs/releasing/preparing/#include-license-file-and-source-code-headers

[gaocegege]

Who should be the copyright owner: google or kubeflow? I think we should communicate with the community.

[jlewi]

I think it has to be Google until Kubeflow becomes part of a foundation (e.g. CNCF). At which point CNCF can be used.

[gaocegege]

@jlewi Well, I will file a PR to solve the issue.

[ewilderj]

Actually, it doesn't have to be Google. For TensorFlow, it is just "The TensorFlow Authors." I will check out what ought to be recommended for us, but as a working presumption, I'd go with "The Kubeflow Authors."

[jlewi]

Great

…

On Feb 1, 2018 7:35 AM, "Edd Wilder-James" ***@***.***> wrote: Actually, it doesn't have to be Google. For TensorFlow, it is just "The TensorFlow Authors." I will check out what ought to be recommended for us, but as a working presumption, I'd go with "The Kubeflow Authors." — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#266 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAvcA6DljuztmPpw3suIA1Hi9_MJBNb2ks5tQdm0gaJpZM4RT7Px> .

[ewilderj]

I can confirm that "Copyright The Kubeflow Authors" is the right copyright line, followed by the Apache 2 header.

[gaocegege]

@ewilderj The Kubeflow Authors SGTM, and I will update the PR 😄