NVIDIA / NVIDIA/TensorRT-Model-Connect

[Community] Launch recurring Model Connect livestreams

Open
#1,105 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

Create a recurring technical livestream that shows how TensorRT Model Connect is built and gives the community a direct way to learn, ask questions, and contribute.

Tasks

  • Define the format, cadence, host, backup host, target audience, and distribution channels.
  • Prepare the first session around a concrete end-to-end Model Connect workflow.
  • Include practical material such as model onboarding, CI debugging, or performance optimization.
  • Reserve time for community pull requests and live questions.
  • Define moderation, accessibility, recording-consent, and code or artifact publication practices.
  • Create a repeatable production checklist covering topic selection, technical validation, promotion, rehearsal, streaming, recording, and follow-up.
  • Prepare a validated live environment and prerecorded fallback for demonstrations.
  • Publish recordings, code, commands, slides, and follow-up links after each session.
  • Collect feedback and use it to select future topics.
  • Assign ownership for scheduling, technical preparation, moderation, and archive maintenance.

Acceptance criteria

The first livestream is delivered and archived with its reproducible code and follow-up resources.

A documented production and promotion process exists and can be reused for subsequent sessions without rebuilding the format from scratch.

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 repository files, tests, or entry points are named. Start by reviewing the listed livestream tasks and acceptance criteria, then determine the owners, first-session workflow, production checklist, and publication process. Done means the first livestream is delivered and archived with reproducible code and follow-up resources, alongside a reusable documented process.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
content, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.