Skip to content

Add PyTorch & FlashInfer as community project#6

Open
shljessie wants to merge 1 commit intoNVIDIA:mainfrom
shljessie:add-community-skills-and-fix-node20
Open

Add PyTorch & FlashInfer as community project#6
shljessie wants to merge 1 commit intoNVIDIA:mainfrom
shljessie:add-community-skills-and-fix-node20

Conversation

@shljessie
Copy link
Copy Markdown
Contributor

  • Add PyTorch (12 skills) and FlashInfer (3 skills) to CI sync check as community projects with active NVIDIA contribution
  • Add "Community Projects with NVIDIA Contribution" section to README

Wondering what your thought are on this @mosheabr? These are public open-source repos but we have active NVIDIA engineers & PMs contributing to them.

…ation

- Add PyTorch (12 skills) and FlashInfer (3 skills) to CI sync check
  as community projects with active NVIDIA contribution
- Add "Community Projects with NVIDIA Contribution" section to README
- Bump GitHub Actions to Node.js 24-compatible versions:
  checkout v4→v5, upload-artifact v4→v6, download-artifact v4→v7,
  create-pull-request v7→v8

Made-with: Cursor
@shljessie shljessie requested a review from mosheabr as a code owner April 9, 2026 17:16
Copy link
Copy Markdown
Collaborator

@mosheabr mosheabr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together! The README section and table formatting look great. However, a couple of blockers:

Must Fix

  1. Action version bumps will break CIactions/checkout@v5, upload-artifact@v6, download-artifact@v7, and peter-evans/create-pull-request@v8 don't exist. These need to be reverted to their current versions (v4, v4, v4, v7 respectively). Even if they did exist, version bumps should be a separate PR.

Scope

  1. Community projects are out of scope for this catalog — For now, we're keeping this repo scoped to skills that NVIDIA owns and maintains. PyTorch and FlashInfer are great projects with active NVIDIA contribution, but since we don't own those repos or their skills, we can't guarantee their quality, count stability, or alignment with our signing/verification pipeline.

    This isn't a "never" — we may revisit community/partner tiers down the road — but for the initial catalog we need to keep it tight.

Happy to discuss further if you have thoughts on how community skills could fit in the future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants