Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine and document the rules for copyright header inclusion #3340

Closed
rlratzel opened this issue Mar 15, 2023 · 1 comment · Fixed by #3519
Closed

Determine and document the rules for copyright header inclusion #3340

rlratzel opened this issue Mar 15, 2023 · 1 comment · Fixed by #3519
Assignees
Labels
Story Tracking issues as a story level - likely to exist within a single release.

Comments

@rlratzel
Copy link
Contributor

rlratzel commented Mar 15, 2023

Who: cugraph devs
What: ensure the rules for copyright header inclusion are documented
Why: Nvidia policy needs to be followed for Nvidia OSS for copyright inclusion

Determine where we need the full copyright header vs. where the copyright year-only line should be used, then document it in CONTRIBUTING.md

context: #3317 (comment)

@rlratzel
Copy link
Contributor Author

rlratzel commented Apr 7, 2023

I was recently told the following:
"It is Nvidia policy to put a copyright and license in all files that support comments."

I'll open a PR to update CONTRIBUTING.md shortly.

@rlratzel rlratzel added the Story Tracking issues as a story level - likely to exist within a single release. label Apr 25, 2023
@rapids-bot rapids-bot bot closed this as completed in #3519 May 4, 2023
rapids-bot bot pushed a commit that referenced this issue May 4, 2023
…n instruction (#3519)

closes #3340 

Updates contributing steps to add copyright and license text inclusion instruction.
This is consistent with the changes in rapidsai/docs#376

Authors:
  - Rick Ratzel (https://github.com/rlratzel)

Approvers:
  - Chuck Hastings (https://github.com/ChuckHastings)
  - Brad Rees (https://github.com/BradReesWork)

URL: #3519
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Story Tracking issues as a story level - likely to exist within a single release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant