Tf-operator: Attach appropriate header (copyright) to go files

Created on 5 Jan 2018  Â·  14Comments  Â·  Source: kubeflow/tf-operator

@jlewi @zjj2wry @gaocegege @ScorpioCPH

kindiscussion

All 14 comments

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

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

SGTM

copyright header for go files is confused.

Do you mean we need an auto-generate script?

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

/cc @foxish @vishh @aronchick

uh, no idea. /cc @ewilderj

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

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

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

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

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."

Great

On Feb 1, 2018 7:35 AM, "Edd Wilder-James" notifications@github.com 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
https://github.com/tensorflow/k8s/issues/266#issuecomment-362303047, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAvcA6DljuztmPpw3suIA1Hi9_MJBNb2ks5tQdm0gaJpZM4RT7Px
.

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

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

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yph152 picture yph152  Â·  10Comments

chaoleili picture chaoleili  Â·  8Comments

pingsutw picture pingsutw  Â·  7Comments

richardsliu picture richardsliu  Â·  7Comments

dpaks picture dpaks  Â·  5Comments