docs(community): update latest tsc members list

[asyncapi-bot]

Updated Ambassadors list is available and this PR introduces changes with latest information about Ambassadors list

Summary by CodeRabbit

• New Features
  • Added a new ambassador profile featuring detailed professional information and social media links.
  • Included a timeline of contributions highlighting talks and presentations from 2021 to 2024.

[coderabbitai]

Walkthrough

The pull request adds a new ambassador entry for Laurent Broudoux in the AMBASSADORS_MEMBERS.json file. The entry includes his personal details such as name, GitHub, Twitter, country, bio, LinkedIn, company, title, and image. It also provides a list of contributions—spanning from 2021 to 2024—that document his involvement in talks and presentations related to cloud-native architecture and API testing.

Changes

File	Summary
config/AMBASS...MEMBERS.json	Added a new entry for Laurent Broudoux with detailed personal information and a contributions array detailing talks.

Possibly related PRs

• docs(community): update latest tsc members list #3397: Modifies the ambassador list by removing an existing ambassador entry in the same file.
• docs(community): update latest tsc members list #3625: Involves removal of an ambassador entry from AMBASSADORS_MEMBERS.json, aligning with the structural changes.
• docs(community): update latest tsc members list #3482: Updates the ambassador list by adding new members and contributions, similar in context to the current changes.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• magicmatatjahu
• anshgoyalevil
• Mayaleeeee
• devilkiller-ag
• sambhavgupta0705
• asyncapi-bot-eve

Poem

In code fields I hop with delight,
A new entry shines so crisp and bright.
Laurent’s data now takes a stand,
Contributions mapped with a careful hand.
From bunnies to bytes, we celebrate the light!
Happy coding under the moonlit night!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[netlify]

❌ Deploy Preview for asyncapi-website failed.

Name	Link
🔨 Latest commit	6b0043b
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67e1af4d4c828600074b1a33

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (91b25e0) to head (6b0043b).

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3959   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/AMBASSADORS_MEMBERS.json (1)

584-648: New Ambassador Entry for Laurent Broudoux is Well Integrated

The new entry for Laurent Broudoux is formatted consistently with existing ambassador objects. It correctly includes all the standard fields—such as name, github, twitter, country, bio, linkedin, company, title, img—and an array of contributions that follow the same schema as prior entries.

A couple of points to consider:

• Verify that the omission of the "link" field in the first two contribution objects is intentional. If available, adding a URL (or a null value if that’s preferred by your JSON schema) might help maintain consistency.
• If not already in place, consider introducing a JSON schema validation to ensure all ambassador entries conform to the expected structure.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ef83a8d and e280a3a.

📒 Files selected for processing (1)

• config/AMBASSADORS_MEMBERS.json (1 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (2)

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Lighthouse CI

[thulieblack]

what did I miss here @derberg 😥

[derberg]

@thulieblack something is wrong with data provided by Laurent. We need to close this PR and you need to have a look at data that he provided, the ambassador experience, in community repo, maybe some errors there?