Repository navigation
fix: deliver package licenses and required notices - #1133
Conversation
Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com>
|
Fern preview: https://nvidia-preview-pr-1133.docs.buildwithfern.com/nemo/datadesigner
|
andreatnvidia
left a comment
There was a problem hiding this comment.
Thanks @nabinchha for covering the package licenses, notices, and DCO updates. Requesting changes to sync the generated Colab notebooks before this reaches main. There’s also a smaller, non-blocking correction to the DCO instructions.
| # SPDX-FileCopyrightText: Copyright (c) 2025-2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. | ||
| # SPDX-License-Identifier: Apache-2.0 |
There was a problem hiding this comment.
[P2] Sync the generated Colab notebooks
These headers create an extra Jupytext cell in all six tutorials, but the tracked Colab notebooks are unchanged and omit the notices. Please run make generate-colab-notebooks and commit the updated outputs. The notebook-sync check only runs against main, so it hasn’t caught the mismatch on this PR’s Slurm base branch.
There was a problem hiding this comment.
Fixed in 1f2802f. Ran make generate-colab-notebooks and committed all six regenerated Colab notebooks. Verified that each tracked output matches fresh generation when ignoring random cell IDs and contains the license notice; unchanged cell IDs were retained to reduce diff noise. The focused documentation/package-license suites passed: 84 tests, 2 skips.
| Every commit in a contribution must include a `Signed-off-by` trailer. By signing off, you certify that you have the right to submit the contribution under the project's open source license, as set out in the Developer Certificate of Origin (DCO) below. | ||
|
|
||
| Add your sign-off with `git commit -s`: | ||
|
|
||
| ```bash | ||
| git commit -s -m "describe your change" |
There was a problem hiding this comment.
[P3] Keep the DCO bot-signing step documented
Could we retain the bot-signing instructions alongside git commit -s in both contribution guides? The existing workflow still requires a first-time contributor’s PR-comment signature, so following these instructions alone won’t satisfy the DCO check. This is non-blocking, but documenting both steps would avoid confusion.
There was a problem hiding this comment.
Fixed in 1f2802f. Both contribution guides now document the first-time DCO Assistant signature alongside the per-commit git commit -s requirement, including the exact PR-comment phrase configured in the workflow and the recheck command. The full DCO certification remains unchanged. Fern validation and internal-link checks passed.
Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com>
[Medium impact] This PR appears safe to merge. SummaryThis PR adds complete license copies to the published packages and checks their contents in wheels and source archives.
nabinchha explicitly deferred the unchanged ZIP-to-area-code asset’s source and redistribution terms. This review does not treat that item as resolved. Reviews (1) · Last reviewed commit: "docs: sync notebook notices and DCO sign..." · Reviewed by Greptile |
* fix: deliver package licenses and required notices Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com> * docs: sync notebook notices and DCO signing Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com> --------- Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com>
* fix: deliver package licenses and required notices Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com> * docs: sync notebook notices and DCO signing Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com> --------- Signed-off-by: Nabin Mulepati <nmulepati@nvidia.com>
📋 Summary
Ensure all four published packages include the complete Apache license text and NVIDIA copyright notice. Complete contributor sign-off instructions, source headers, and external-material notices while preserving tutorial notebook metadata.
🔗 Related Issue
N/A — package licensing and contribution-documentation corrections.
🔄 Changes
🔍 Attention Areas
The bundled ZIP-to-area-code asset is unchanged. Confirming its original source and applicable redistribution terms remains a separate follow-up; this PR does not resolve that provenance item.
🧪 Testing
✅ Checklist