diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index b806588..59832b2 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -89,6 +89,19 @@ jobs: git lfs install --local git lfs pull + # Isaac Sim 6.0.1 on nvcr.io requires authenticated pull; anonymous + # access that worked for 6.0.0-dev2 is denied for this tag. + - name: Log in to NGC + env: + NGC_API_KEY: ${{ secrets.NGC_API_KEY }} + run: | + if [ -z "${NGC_API_KEY}" ]; then + echo "NGC_API_KEY secret is empty; cannot pull nvcr.io/nvidia/isaac-sim" + exit 1 + fi + # $oauthtoken is the literal NGC username. + echo "${NGC_API_KEY}" | docker login nvcr.io -u '$oauthtoken' --password-stdin + - name: Run E2E tests run: ./scripts/ci/run_tests.sh diff --git a/.github/workflows/nightly.yml b/.github/workflows/nightly.yml index 9d4b4d2..f8d4750 100644 --- a/.github/workflows/nightly.yml +++ b/.github/workflows/nightly.yml @@ -61,6 +61,19 @@ jobs: git lfs install --local git lfs pull + # Isaac Sim 6.0.1 on nvcr.io requires authenticated pull; anonymous + # access that worked for 6.0.0-dev2 is denied for this tag. + - name: Log in to NGC + env: + NGC_API_KEY: ${{ secrets.NGC_API_KEY }} + run: | + if [ -z "${NGC_API_KEY}" ]; then + echo "NGC_API_KEY secret is empty; cannot pull nvcr.io/nvidia/isaac-sim" + exit 1 + fi + # $oauthtoken is the literal NGC username. + echo "${NGC_API_KEY}" | docker login nvcr.io -u '$oauthtoken' --password-stdin + - name: Run full E2E suite run: ./scripts/ci/run_tests.sh diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..a7848ec --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,45 @@ +## Isaac AutoData Contribution Rules + +This document describes the rules for contributing to Isaac AutoData + + +#### Signing Your Work + +* We require that all contributors "sign-off" on their commits. +This certifies that the contribution is your original work, or you have rights to submit +it under the same license, or a compatible license. + +* Any contribution which contains commits that are not Signed-Off will not be accepted. + +* To sign off on a commit you simply use the `--signoff` (or `-s`) option when committing your changes: + ```bash + $ git commit -s -m "Add cool feature." + ``` + This will append the following to your commit message: + ``` + Signed-off-by: Your Name + ``` + +* Full text of the DCO: + + ``` + Developer Certificate of Origin Version 1.1 + + Copyright (C) 2004, 2006 The Linux Foundation and its contributors. + + Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. + ``` + + ``` + Developer's Certificate of Origin 1.1 + + By making a contribution to this project, I certify that: + + (a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or + + (b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or + + (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it. + + (d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved. + ``` diff --git a/CONTRIBUTORS.md b/CONTRIBUTORS.md new file mode 100644 index 0000000..75c8cbd --- /dev/null +++ b/CONTRIBUTORS.md @@ -0,0 +1,22 @@ +# Isaac AutoData Developers and Contributors + +This is the official list of Isaac AutoData Project developers and contributors. + +Guidelines for modifications: + +* Please keep the **lists sorted alphabetically**. +* name (optional institution) + +## Core Team +* Ansh Gandhi (NVIDIA) +* Heron Ordonez Guillen (NVIDIA) +* Neel Jawale (NVIDIA) +* Peter Du (NVIDIA) +* Stephan Pleines (NVIDIA) +* Tuur Stuyck (NVIDIA) + +## Contributors + +* Ashley Chow (NVIDIA) +* Caelan Garrett (NVIDIA) +* Xinjie Yao (NVIDIA) diff --git a/LICENSE b/LICENSE.md similarity index 99% rename from LICENSE rename to LICENSE.md index 261eeb9..2e0af2d 100644 --- a/LICENSE +++ b/LICENSE.md @@ -1,3 +1,5 @@ +# License {#license} + Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ @@ -186,7 +188,7 @@ same "printed page" as the copyright notice for easier identification within third-party archives. - Copyright [yyyy] [name of copyright owner] + Copyright 2026 NVIDIA CORPORATION Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..9d1a711 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,24 @@ +## Security + +NVIDIA is dedicated to the security and trust of our software products and services, including all source code repositories managed through our organization. + +If you need to report a security issue, please use the appropriate contact points outlined below. **Please do not report security vulnerabilities through GitHub.** If a potential security issue is inadvertently reported via a public issue or pull request, NVIDIA maintainers may limit public discussion and redirect the reporter to the appropriate private disclosure channels. + +## Reporting Potential Security Vulnerability in an NVIDIA Product + +To report a potential security vulnerability in any NVIDIA product: +- Web: [Security Vulnerability Submission Form](https://www.nvidia.com/object/submit-security-vulnerability.html) +- E-Mail: psirt@nvidia.com + - We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key) + - Please include the following information: + - Product/Driver name and version/branch that contains the vulnerability + - Type of vulnerability (code execution, denial of service, buffer overflow, etc.) + - Instructions to reproduce the vulnerability + - Proof-of-concept or exploit code + - Potential impact of the vulnerability, including how an attacker could exploit the vulnerability + +While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information. + +## NVIDIA Product Security + +For all security-related concerns, please visit NVIDIA's Product Security portal at https://www.nvidia.com/en-us/security