chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features
  • Added a new meeting entry titled "Marketing WG Meeting" with a calendar link, event URL, and scheduled date.

[coderabbitai]

Walkthrough

A new meeting entry titled "Marketing WG Meeting" has been added to the meetings configuration file. The entry includes a calendar link, a URL reference, an empty banner, and a scheduled date. This update increases the total number of meetings listed in the configuration.

Changes

File	Change Summary
config/meetings.json	Added a new meeting entry "Marketing WG Meeting" with calendar link, URL, banner (empty), and date information.

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3632: Adds a new meeting entry while the referenced PR removes an existing entry for "Marketing WG Meeting", indicating a direct conflict.
• chore: update meetings.json and newsrooom_videos.json #3326: Involves removing an existing "Marketing WG Meeting" entry, directly conflicting with this addition.
• chore: update meetings.json and newsrooom_videos.json #3589: Both PRs add a "Marketing WG Meeting" entry but specify different dates and details, suggesting a code-level discrepancy.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

In a burrow of code, a meeting took flight,
"Marketing WG Meeting" now shines so bright.
With links and dates, the JSON hops along,
A festive update sung in a rabbit’s song.
Codes and carrots, all in playful delight!

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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 ready!

Name	Link
🔨 Latest commit	b48a1e5
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67aa9ac024ad880008e4fcba
😎 Deploy Preview	https://deploy-preview-3665--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (7df20e0) to head (b48a1e5).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3665   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          732       732           
=========================================
  Hits           732       732           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/meetings.json (1)

1-65: Suggestion: Consider Chronological Ordering

For improved readability and easier management, you might consider ordering the meeting entries chronologically based on the "date" field. This additional organizational change is optional but can help ensure that future maintenance remains straightforward.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7df20e0 and b48a1e5.

📒 Files selected for processing (1)

• config/meetings.json (1 hunks)

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

• GitHub Check: Redirect rules - asyncapi-website
• GitHub Check: Header rules - asyncapi-website
• GitHub Check: Pages changed - asyncapi-website
• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Lighthouse CI

🔇 Additional comments (1)

config/meetings.json (1)

57-63: New Marketing WG Meeting Entry: Verify Details

The newly added meeting entry for "Marketing WG Meeting" includes the expected details:

• Calendar Link: "https://www.google.com/calendar/event?eid=Y29uZzNvNWxrcWs0Z2NqaWI4NjBmYnVwOWcgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn"
• URL: "https://github.com/asyncapi/community/issues/1705"
• Banner: an empty string
• Date: "2025-02-18T14:00:00.000Z"

Please confirm that this new entry is intentional and not duplicative with other "Marketing WG Meeting" events in the list.