Skip to content
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.

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

chore(blog): add last summary of the year #3463

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

thulieblack
Copy link
Member

@thulieblack thulieblack commented Dec 11, 2024

Last blog of the year including Paris highlights and some community updates

Summary by CodeRabbit

  • New Features

    • Introduced a new community update document for November and December 2024, detailing community activities and the AsyncAPI Conference in Paris.
    • Expanded the October community update to include conference summaries, proposals for future goals, and event participation details.
  • Bug Fixes

    • Corrected the title and date of the October community update to reflect accurate information.
  • Documentation

    • Added cover image, author details, and excerpts to the new community update document.

Copy link

coderabbitai bot commented Dec 11, 2024

Walkthrough

A new markdown file titled "November and December Community Update And AsyncAPI Conf in Paris 2024" has been created, detailing community activities and reflections, including a summary of the AsyncAPI Conference held in Paris. Additionally, the existing October summary document has been updated to reflect recent events, community goals, and conference details. Both documents emphasize community engagement and upcoming initiatives.

Changes

File Path Change Summary
markdown/blog/2024-december-and-paris.md New file created with a community update, conference summary, author details, and a cover image.
markdown/blog/2024-october-summary.md Existing document updated with a new title and date, expanded content on community engagement, conference details, a proposal for 2025 goals, rebranding information, and a preview of upcoming updates.

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

  • akshatnema
  • derberg
  • magicmatatjahu
  • anshgoyalevil
  • Mayaleeeee
  • devilkiller-ag
  • sambhavgupta0705
  • sambhavgupta0705

Poem

🐰 In December's glow, we share our cheer,
With tales of Paris, our hearts draw near.
Community strong, together we stand,
Building our future, hand in hand.
So hop along, let’s spread the delight,
For 2024’s journey shines ever so bright! 🌟


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d07902c and a286c90.

📒 Files selected for processing (1)
  • markdown/blog/2024-december-and-paris.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-december-and-paris.md

[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...

(AWESOME)


[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...

(ENGLISH_WORD_REPEAT_RULE)

🔇 Additional comments (8)
markdown/blog/2024-december-and-paris.md (8)

1-15: LGTM! Frontmatter is well-structured.

The metadata is complete and follows the standard blog post structure.


27-27: Update the conference introduction paragraph.

This content was previously reviewed and corrected.

🧰 Tools
🪛 LanguageTool

[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...

(AWESOME)


45-45: Update the TMForum keynote description.

This content was previously reviewed and corrected.


77-77: Update the presentation description.

This content was previously reviewed and corrected.


130-138: LGTM! Conclusion is well-written.

The final remarks provide a good closure to the blog post and year.


122-128: Verify the GitHub profile link.

Let's ensure the GitHub username is correct for the new maintainer.

✅ Verification successful

GitHub profile link is valid and correctly referenced

The GitHub username ashmit-coder exists and matches exactly with the profile link used in the code.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify GitHub username exists
gh api users/ashmit-coder --jq '.login'

Length of output: 52

🧰 Tools
🪛 LanguageTool

[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...

(ENGLISH_WORD_REPEAT_RULE)


31-116: Verify the existence of conference images.

Let's ensure all referenced conference images exist in the repository.

✅ Verification successful

All conference images are present in the repository

All referenced images in the blog post exist at the expected location under public/img/posts/paris-conf-2024/. Each image file was found and verified.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if all conference images exist
image_paths=(
  "full-room.webp"
  "lukasz-and-fran.webp"
  "naresh-and-pierre.webp"
  "frank.webp"
  "leonid.webp"
  "hugo.webp"
  "julien-and-alessandro.webp"
  "annegret.webp"
  "jonathan.webp"
  "hari-and-joel.webp"
  "laurent-and-hugo.webp"
)

for img in "${image_paths[@]}"; do
  if [ -f "public/img/posts/paris-conf-2024/$img" ]; then
    echo "✓ Found: $img"
  else
    echo "✗ Missing: $img"
  fi
done

Length of output: 1955


22-23: Verify the GitHub PR link accessibility.

The link to the community goals proposal PR is crucial for community engagement.

✅ Verification successful

GitHub PR link is valid and accessible

The PR #1575 in asyncapi/community repository is open and correctly titled "AsyncAPI Community Building Goals 2025 Proposal", matching the context of the blog post.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the GitHub PR link is accessible
gh pr view 1575 --repo asyncapi/community --json state,title

Length of output: 148


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
🪧 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. (Experiment)
  • @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.

Copy link

netlify bot commented Dec 11, 2024

👷 Deploy Preview for asyncapi-website processing.

Name Link
🔨 Latest commit a286c90
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/675ab012a0ccc4000800430e

Copy link

codecov bot commented Dec 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.22%. Comparing base (fa7a967) to head (d68cf06).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3463   +/-   ##
=======================================
  Coverage   77.22%   77.22%           
=======================================
  Files          21       21           
  Lines         663      663           
=======================================
  Hits          512      512           
  Misses        151      151           

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

@asyncapi-bot
Copy link
Contributor

asyncapi-bot commented Dec 11, 2024

⚡️ Lighthouse report for the changes in this PR:

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

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-december-and-paris.md (1)

13-13: Consider enhancing the excerpt for better SEO and readability.

The current excerpt is quite similar to the title and could be more descriptive. Consider adding key highlights or takeaways from the post.

-excerpt: 'November and December Community Update And Paris Conference Summary'
+excerpt: 'Highlights from AsyncAPI Conference in Paris, community achievements, and welcoming new TSC members as we wrap up an eventful 2024'
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7f81142 and d07902c.

📒 Files selected for processing (2)
  • markdown/blog/2024-december-and-paris.md (1 hunks)
  • markdown/blog/2024-october-summary.md (0 hunks)
💤 Files with no reviewable changes (1)
  • markdown/blog/2024-october-summary.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-december-and-paris.md

[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...

(AWESOME)


[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...

(ENGLISH_WORD_REPEAT_RULE)

🔇 Additional comments (5)
markdown/blog/2024-december-and-paris.md (5)

16-18: LGTM!

The introduction effectively sets the context and tone for the blog post.


130-138: LGTM!

The conclusion effectively wraps up the blog post with appropriate holiday wishes and future plans.


122-128: Verify the GitHub profile link.

Let's ensure the GitHub username is correct and the profile is accessible.

✅ Verification successful

GitHub profile link is valid and matches the name

The GitHub profile ashmit-coder exists and the name matches "Ashmit Jagtap" as specified in the Profiles component.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify GitHub profile exists and matches the name
gh api users/ashmit-coder --jq '.name'

Length of output: 53

🧰 Tools
🪛 LanguageTool

[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...

(ENGLISH_WORD_REPEAT_RULE)


31-35: Verify the existence and accessibility of conference images.

Let's ensure all referenced images exist in the repository.

Also applies to: 39-43, 47-51, 55-59, 63-67, 71-75, 79-83, 87-91, 96-100, 104-108, 112-116

✅ Verification successful

All conference images are present and accessible

All referenced images in the public/img/posts/paris-conf-2024/ directory have been verified to exist, including:

  • full-room.webp (referenced in the reviewed snippet)
  • All other conference images referenced in lines 39-116
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if all referenced images exist
fd -e webp -p "public/img/posts/paris-conf-2024/" | while read -r img; do
  basename=$(basename "$img")
  echo "Checking: $basename"
  if [ -f "$img" ]; then
    echo "✓ Found: $img"
  else
    echo "✗ Missing: $img"
  fi
done

Length of output: 3997


22-23: Verify the PR status and accessibility.

Let's ensure the referenced PR is still open and accessible.

✅ Verification successful

PR link is valid and active

The referenced PR (#1575) in the AsyncAPI Community repository is open and accessible, correctly discussing the 2025 Community Building Goals proposal as mentioned in the blog post.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the PR is still open and accessible
gh pr view 1575 --repo asyncapi/community --json state,url,title

Length of output: 208

Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

some minor comments

probably would be good to share linkedin of all speakers

btw, now you have nice task to gather all slides and recordings (if speakers recorded their talks through Apidays resources)


## AsyncAPI Conf in Paris 2024

The AsyncAPI Conf was back again in Paris this December, thanks to [Mehdi Medjaoui](https://www.linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.global/) for hosting and sponsoring the venue. We participated in the three-day event, celebrating a year of the `API Open Standards Booth` alongside friends from OpenAPI, JSON Schema, and GraphQL.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
The AsyncAPI Conf was back again in Paris this December, thanks to [Mehdi Medjaoui](https://www.linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.global/) for hosting and sponsoring the venue. We participated in the three-day event, celebrating a year of the `API Open Standards Booth` alongside friends from OpenAPI, JSON Schema, and GraphQL.
The AsyncAPI Conf was back again in Paris this December, thanks to [Mehdi Medjaoui](https://www.linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.global/) for hosting and sponsoring the venue. We participated in the three-day event, celebrating a year of the `API Standards` booth alongside friends from OpenAPI, JSON Schema, and GraphQL. Special thanks to all the members of AsyncAPI community that could join the conference and help at the booth: [Hugo Guerrero](https://www.linkedin.com/in/hugoguerrero/), [Fran Méndez](https://www.linkedin.com/in/fmvilas/), [Richard Coppen](https://www.linkedin.com/in/richard-coppen/), [Hari Krishnan](https://www.linkedin.com/in/harikrishnan83/), [Lukasz Gornicki](https://www.linkedin.com/in/lukasz-gornicki-a621914/)

that was the final name we used

className="text-center"
/>

Naresh Jain and Pierre Gauthier presented their keynote on `TM Forum's AsyncAPI for a New Era of Event-Driven Architecture`. During the session, they announced AsyncAPI as the standard, with over 100 telecommunications APIs already in production. TM Forum has around 800 telco companies, and they will implement all APIs in an async manner, extensively utilizing the request-reply pattern.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Naresh Jain and Pierre Gauthier presented their keynote on `TM Forum's AsyncAPI for a New Era of Event-Driven Architecture`. During the session, they announced AsyncAPI as the standard, with over 100 telecommunications APIs already in production. TM Forum has around 800 telco companies, and they will implement all APIs in an async manner, extensively utilizing the request-reply pattern.
Naresh Jain and Pierre Gauthier presented their keynote on `TMForum's AsyncAPI for a New Era of Event-Driven Architecture`. During the session, Pierre announced TMForum adopts AsyncAPI as a standard, with around 120 telco APIs already in production. TMForum has around 800 telco companies, and they will implement all APIs in an async manner, extensively utilizing the request-reply pattern.

className="text-center"
/>

Julien and Alessandro shared how organizations can harness the full potential of event-driven integration by leveraging GoldenGate Data Streams, AsyncAPI, and Solace PubSub+ Event Mesh.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Julien and Alessandro shared how organizations can harness the full potential of event-driven integration by leveraging GoldenGate Data Streams, AsyncAPI, and Solace PubSub+ Event Mesh.
Julien and Alessandro shared how organizations can harness the full potential of event-driven integration by leveraging GoldenGate Data Streams, AsyncAPI, and Solace PubSub+ Event Mesh. They shared a great use case for AI and how it can be trained real-time and standardized with AsyncAPI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants