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 pull request titled "feat: added test for build-rss.js" to the hot discussions section.
  • Introduced another pull request titled "docs: add Bounty Program Rules" to the hot discussions section.

• Improvements

  • Updated the score for the issue "Brand Refresh: Mascot," reflecting its new ranking.

• Removals

  • Removed a previously existing entry for the pull request "feat: added test for build-rss.js."

[coderabbitai]

Walkthrough

The changes in this pull request primarily involve modifications to the dashboard.json file, specifically in the hotDiscussions section. A new pull request entry has been added, replacing an existing one with the same ID. Additionally, the score for an existing issue has been updated, and another new pull request has been introduced. The overall structure of the JSON remains unchanged, with no alterations to the goodFirstIssues section.

Changes

File	Change Summary
dashboard.json	- Added new pull request entry for "feat: added test for build-rss.js" by "vishvamsinh28", replacing the previous entry with the same ID. - Updated score for issue "Brand Refresh: Mascot" from 15.79 to 16.08. - Added new entry for "docs: add Bounty Program Rules" by "aeworxet".

Possibly related PRs

• docs(community): update latest maintainers list #3273: The changes in this PR involve updates to the MAINTAINERS.json file, which is related to the overall project structure and contributor management, similar to the updates made to the dashboard.json in the main PR regarding pull request entries.
• docs(community): update latest maintainers list #3291: This PR also updates the MAINTAINERS.json file, reflecting ongoing efforts to maintain contributor information, which aligns with the updates made in the main PR concerning the management of pull request metadata in dashboard.json.

Poem

In the dashboard's glow, new entries appear,
A rabbit hops by, spreading joy and cheer.
With scores that rise and discussions anew,
The garden of code blooms, fresh as the dew.
So let’s celebrate changes, both big and small,
For every new pull request, we cherish them all! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 67aafb6 and a3b6603.

📒 Files selected for processing (1)

• dashboard.json (3 hunks)

🔇 Additional comments (4)

dashboard.json (4)

30-40: LGTM: PR entry structure is valid.

The PR entry for "feat: added test for build-rss.js" follows the correct structure with all required fields (id, isPR, isAssigned, title, author, resourcePath, repo, labels, score).

---

70-70: LGTM: Score update is valid.

The score update for the "Brand Refresh: Mascot" issue from 15.79 to 16.08 appears to be a legitimate automated recalculation.

---

147-157: LGTM: New PR entry structure is valid.

The PR entry for "docs: add Bounty Program Rules" follows the correct structure with all required fields and maintains consistent formatting with other entries.

---

Line range hint 30-157: Verify the score calculations.

The scores for the hot discussions appear to follow a descending order (34.46 → 19.52 → 19.24 → 18.37 → 16.08 → ... → 10.65), which is consistent with a proper ranking system. However, it would be good to verify the scoring algorithm.

✅ Verification successful

Let me gather more specific information about the scoring implementation.

---

Score calculation verified and found to be correctly implemented

The scoring algorithm is implemented in scripts/dashboard/build-dashboard.js and follows a well-defined formula:

• Score = totalInteractions / (monthsSince(lastUpdate) + 2)^1.8
• Where totalInteractions = reactions + comments + comment reactions + (for PRs: reviews + review comments)
• The time decay factor (monthsSince + 2)^1.8 ensures newer discussions rank higher
• Results are properly sorted in descending order (line 122)

The descending scores in the dashboard.json are consistent with this implementation.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the scoring algorithm implementation
# Look for the scoring calculation logic in the codebase

# Search for files containing score calculation logic
rg -l "score" --type ts --type js

# Search for specific score calculation patterns
ast-grep --pattern 'function $FUNC_NAME($_) {
  $$$
  score
  $$$
}'

Length of output: 190

---

Script:

#!/bin/bash
# Look at the scoring implementation in build-dashboard.js
cat scripts/dashboard/build-dashboard.js

# Also search for specific score calculation patterns
rg -n "score" scripts/dashboard/build-dashboard.js

Length of output: 5965

---

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 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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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	a3b6603
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/671c39708084fe00087bd1b9
😎 Deploy Preview	https://deploy-preview-3329--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 47.32%. Comparing base (67aafb6) to head (a3b6603).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3329   +/-   ##
=======================================
  Coverage   47.32%   47.32%           
=======================================
  Files          22       22           
  Lines         672      672           
=======================================
  Hits          318      318           
  Misses        354      354           

☔ 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	41
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

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