NVIDIA / NVIDIA/TensorRT-Model-Connect

[Community] Prepare TensorRT Model Connect for GTC

Open
#1,108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Community
Dominant language
Python
Stars
254
Forks
58
Avg merge
1d 7h
Merged PRs (30d)
235

Description

Summary

Prepare a clear TensorRT Model Connect story and a reliable end-to-end demonstration for the next GTC.

Tasks

  • Identify the target event, submission dates, content deadlines, and rehearsal milestones.
  • Define the audience, primary message, technical depth, and call to action.
  • Select the models and NVIDIA platforms to demonstrate.
  • Prepare an abstract and session outline.
  • Finalize a reliable live demonstration with a prerecorded fallback.
  • Pin and record the exact source, model, bundle, hardware, and runtime configurations used by the demo.
  • Gather reproducible benchmark, qualification, and community-adoption evidence.
  • Prepare slides, speaker notes, demo scripts, repository links, and QR codes.
  • Review all public claims, assets, licenses, and attribution before publication.
  • Schedule technical validation and presentation rehearsals.
  • Define go or no-go criteria for the live demo.
  • Assign owners and backups for the talk, demonstration, booth support, and post-event follow-up.

Acceptance criteria

The submission and demo package are complete, technically validated, claim-reviewed, and rehearsed before the applicable event deadlines.

The live demonstration has a tested fallback, and every public technical or performance claim is traceable to reproducible evidence.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named in the issue. Start by confirming the GTC event deadlines, then inventory the selected models, platforms, source, bundle, hardware, and runtime configurations for the demonstration. Done means the submission and demo package are validated, claims are traceable to reproducible evidence, and the live demo has a tested fallback and completed rehearsals.

Written by the indexing model from the issue text.

Assessment

Domain
ai, content, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.