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 Marketing Working Group meeting to the configuration, scheduled for February 4, 2025.

[coderabbitai]

Walkthrough

A new meeting entry for the "Marketing WG Meeting" has been added to the meetings.json configuration file. The entry includes details such as a calendar link, a GitHub issue URL, and is scheduled for February 4, 2025. This update introduces a single additional meeting record to the existing configuration without modifying any previous entries.

Changes

File	Change Summary
config/meetings.json	Added new meeting entry for Marketing WG Meeting on 2025-02-04

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3580: Updates to the meetings.json file
• chore: update meetings.json and newsrooom_videos.json #3582: Removal of a meeting entry from meetings.json
• chore: update meetings.json and newsrooom_videos.json #3585: Another modification to meeting entries in the configuration file

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

🐰 Hop, hop, a meeting's on the way!
Marketing WG joins the fray
In config's cozy little nest
A new event has come to rest
February's calendar now bright
With plans that sparkle pure and light! 📅✨

---

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	bb56eb0
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/678eeaf928e6e7000881b0f6
😎 Deploy Preview	https://deploy-preview-3589--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 (e674818) to head (bb56eb0).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3589   +/-   ##
=========================================
  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.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	36
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-3589--asyncapi-website.netlify.app/

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

config/meetings.json (1)

Line range hint 1-99: Consider sorting entries chronologically.

While the new entry is valid, consider maintaining entries in chronological order for better readability and maintenance. The new entry (2025-02-04) could be sorted among other entries based on the date field.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e674818 and bb56eb0.

📒 Files selected for processing (1)

• config/meetings.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

🔇 Additional comments (1)

config/meetings.json (1)

93-98: LGTM! The new meeting entry is well-structured.

The new Marketing WG Meeting entry maintains consistency with existing entries and includes all required fields with proper formatting.