How to Present an Issue/PR in a Development Meeting: feedback wanted

Meshery
, ,
1

Why

Contributors don’t always present issues or agenda items the same way in Meshery development meetings. Giving enough context up front makes it much easier for everyone to follow the problem and give useful feedback. This came up in the Sept 23, 2026 Development Meeting.

Tracking issue: [Docs/Enhancement] Create an Issue & Agenda Presentation Guide · Issue #22064 · meshery/meshery · GitHub (parent: #22063)

What we’re building

A short demo video plus a brief written guide, “How to Present an Issue/PR”, covering:

  • What context to provide before presenting
  • How to clearly explain the problem or topic
  • What to prepare beforehand
  • Common do’s and don’ts
  • How to make the discussion easy for others to follow and contribute to

The video is cut from the Sept 23 meeting recording (00:00-09:30), where an issue is presented and discussed, with voice-over where it helps. The same approach applies to PRs: what changed, why, and how to review it.

Plan

  1. Edit the demo clip and add voice-over
  2. Share the draft for community and maintainer feedback (Wednesday’s development meeting)
  3. Incorporate feedback
  4. Maintainers host the approved version on YouTube
  5. Add a short “How to Present an Issue/PR” note to the newcomer/community welcome guidance

Feedback wanted

  • Is the clip clear and the right length?
  • Is anything missing from the guidance above?
  • Should the PR side get its own example?

Draft video:

Comments here or on the issue are welcome.

2

The demo video looks good! Could we also include some points on explaining why the proposed fix is the right approach for the issue and how it was validated? The risk aspect is already covered, so kudos for that!

The voice over could be clearer before the video is ready to be posted on YouTube, and I think an intro with the Meshery logo would look good too.

3

the video serves its intended purpose, but i feel like we can make it lil slower or attach one more reference of “how to present pr/proposal” if possible. As of now, i find the video a bit faster (coming from a person who hasn’t presented anything in dev meeting as of now, so in order to understand it in a better way, i’ll prefer a bit slower and flowy video.)

4

The demo video does cover the intended topics ,but I feel as rightly mentioned by others,especially the voice over part speed can be slowed down.

I think we can add different types of PR s as example in the video .(ie,one UI Pr and one backend PR and one while proposing a new blog/documentation/idea)