Skip to content

chore: update meetings.json and newsrooom_videos.json #3326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
asyncapi-bot merged 1 commit into from
Oct 25, 2024
Merged

chore: update meetings.json and newsrooom_videos.json #3326

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 7 additions & 14 deletions config/meetings.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,25 +1,11 @@
[
{
"title": "Essential Building Blocks Working Group",
"calLink": "https://www.google.com/calendar/event?eid=M2pxNGNwZnRqNGpjcDg2cXVnc3VqZ2wwMHMgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
"url": "https://github.com/asyncapi/community/issues/1294",
"banner": "",
"date": "2024-07-16T18:00:00.000Z"
},
{
"title": "Community Meeting",
"calLink": "https://www.google.com/calendar/event?eid=am5kcG50YW9obGUzcmVucWZqMTQ4NDlsbjQgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
"url": "https://github.com/asyncapi/community/issues/1305",
"banner": "https://github.com/asyncapi/community/assets/40604284/65376079-c5e8-467d-b513-21dfaba4570f",
"date": "2024-07-23T16:00:00.000Z"
},
{
"title": "Marketing WG Meeting",
"calLink": "https://www.google.com/calendar/event?eid=Z3NzN2JvcjdnY2diMnJpczA4dWMxMGh2ZGcgY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
"url": "https://github.com/asyncapi/community/issues/1309",
"banner": "",
"date": "2024-07-16T14:00:00.000Z"
},
{
"title": "Marketing WG Meeting",
"calLink": "https://www.google.com/calendar/event?eid=b2twOWkyZ3ExcGxnYnAxbzBobzA1MWxvcW8gY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
Expand Down Expand Up @@ -159,5 +145,12 @@
"url": "https://github.com/asyncapi/community/issues/1562",
"banner": "",
"date": "2024-10-30T10:00:00.000Z"
},
{
"title": "Conference Dry Run",
"calLink": "https://www.google.com/calendar/event?eid=ZmR1c25lZG1wc2swOWloNDd2c2VudWc5OTggY19xOXRzZWlnbG9tZHNqNm5qdWh2YnB0czExY0Bn",
"url": "https://github.com/asyncapi/community/issues/1566",
"banner": "",
"date": "2024-10-28T16:00:00.000Z"
Comment on lines +149 to +154
Copy link
Contributor

@coderabbitai coderabbitai bot Oct 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Maintain consistent naming for conference-related events

The file shows three conference-related events in chronological order:

  1. "AsyncAPI Online Conference 2024 Dry-Run" (Oct 18)
  2. "Conference Dry Run" (Oct 28)
  3. "AsyncAPI Online Conference 2024" (Oct 30)

The new entry should follow the established naming pattern. Suggest renaming "Conference Dry Run" to "AsyncAPI Online Conference 2024 Dry-Run 2" for consistency and clarity.

🔗 Analysis chain

Verify the need for multiple conference dry runs.

I notice there are now three conference-related meetings scheduled:

  1. "AsyncAPI Online Conference 2024 Dry-Run" on Oct 18
  2. "Conference Dry Run" (this new entry) on Oct 28
  3. "AsyncAPI Online Conference 2024" on Oct 30

While multiple dry runs might be intentional, please verify if this is needed.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if the multiple dry runs are discussed in the linked issues
echo "Checking issue discussions for dry run context..."
gh issue view asyncapi/community#1559  # First dry run
gh issue view asyncapi/community#1566  # Second dry run

Length of output: 284

Script:

#!/bin/bash
# Let's verify the chronological order and naming patterns of conference meetings
rg -U "\"title\".*Conference.*\"date\".*2024" config/meetings.json

Length of output: 64

Script:

#!/bin/bash
# Let's check the entire meetings.json content to analyze conference-related entries
cat config/meetings.json

Length of output: 7523

}
]