Skip to content

chore(blog): add the march summary #3966

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

Merged
merged 21 commits into from
Apr 5, 2025

Conversation

thulieblack
Copy link
Member

@thulieblack thulieblack commented Mar 25, 2025

Add the March Community Update Summary for 2025

Summary by CodeRabbit

  • Documentation
    • Updated an existing blog post by removing its featured marker.
    • Introduced a new monthly community update post highlighting key announcements, upcoming events, and new project initiatives.
    • Updated release notes by removing the featured marker.

Copy link
Contributor

coderabbitai bot commented Mar 25, 2025

Walkthrough

This pull request makes updates to the blog content by removing the featured: true metadata entry from the February summary post and the release notes for version 3.0.0. Additionally, it introduces a new markdown file for the March 2025 community update, which outlines announcements regarding the Google Summer of Code (GSoC), community events, and project initiatives.

Changes

File(s) Change Summary
markdown/blog/2025-february-summary.md, markdown/blog/release-notes-3.0.0.md Removed the featured: true metadata field from both documents.
markdown/blog/2025-march-summary.md Added a new blog post detailing community updates, including announcements for GSoC, AsyncAPI Conference, and project initiatives.

Possibly related PRs

Suggested labels

ready-to-merge

Suggested reviewers

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

Poem

I'm a bunny, hopping with glee,
Celebrating changes as light as can be.
No longer featured, yet still so bright,
New updates shine in the digital light.
Hop along, dear coder, let our work take flight!
🐇✨


🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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 Mar 25, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 53549fb
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67f0ec6823a96e00087898a5
😎 Deploy Preview https://deploy-preview-3966--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Member Author

@thulieblack thulieblack left a comment

Choose a reason for hiding this comment

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

@derberg anything I missed?

Copy link

codecov bot commented Mar 25, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (838f699) to head (53549fb).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3966   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@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

🧹 Nitpick comments (6)
markdown/blog/2025-march-summary.md (6)

1-15: Review YAML Front Matter Metadata

The metadata is well structured and comprehensive. One point to note: the front matter still includes featured: true, while the February summary had this metadata removed. Please confirm if featuring the March update is the intended behavior.


17-18: Consider Rewording to Reduce Wordiness

The sentence in these lines uses the phrase "in anticipation of being accepted to the program." A more concise alternative (e.g., "expecting acceptance into the program") may improve clarity and readability.

Proposed diff:

-... join the workspace in anticipation of being accepted to the program.
+... join the workspace expecting acceptance into the program.
🧰 Tools
🪛 LanguageTool

[style] ~17-~17: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


22-22: Refine the "Thank You" Expression

The phrase "a big thank you goes out to our Code of Conduct Committee" might be improved with a more formal expression such as "sincere thanks" to better align with the overall tone.

🧰 Tools
🪛 LanguageTool

[grammar] ~22-~22: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


33-37: Vary Bullet List Introductions in Call for Speakers

Each bullet point in this section begins with "Submit your proposal." To enhance readability, consider rephrasing some of these lines to avoid repetitive wording (for example, using alternates like "Apply by" or "Proposals due by").

🧰 Tools
🪛 LanguageTool

[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


54-54: Adjust Verb Tense for the Discussion Section

The sentence "We have an interesting discussion about conducting usability research on some of our tools in AsyncAPI" may benefit from a tense adjustment. Consider revising it to clarify whether the discussion is ongoing or has been initiated (e.g., "There is an interesting discussion..." or "We are hosting a discussion...").

🧰 Tools
🪛 LanguageTool

[uncategorized] ~54-~54: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...icipating. ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)


59-59: Replace Informal Descriptor for Speakers

The wording "amazing speakers" appears informal. Replacing "amazing" with a term like "outstanding" or "exceptional" would impart a more professional tone.

Proposed diff:

-... as we have amazing speakers sharing knowledge
+... as we have outstanding speakers sharing knowledge
🧰 Tools
🪛 LanguageTool

[style] ~59-~59: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...nd the city, [please join us as we have amazing speakers sharing knowledge](https://con...

(AWESOME)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 91b25e0 and 3c654fd.

📒 Files selected for processing (2)
  • markdown/blog/2025-february-summary.md (0 hunks)
  • markdown/blog/2025-march-summary.md (1 hunks)
💤 Files with no reviewable changes (1)
  • markdown/blog/2025-february-summary.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~17-~17: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[grammar] ~22-~22: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[uncategorized] ~54-~54: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ...icipating. ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)


[style] ~59-~59: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...nd the city, [please join us as we have amazing speakers sharing knowledge](https://con...

(AWESOME)

⏰ Context from checks skipped due to timeout of 180000ms (4)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Lighthouse CI

@derberg
Copy link
Member

derberg commented Mar 25, 2025

can you also in the PR do a cleanup of featured articles and basically unfeature all 😄 there is a lot of old content, like v3 release notes and others, and new articles are lost because if it. I think best is to go with the flow where all articles are featured: false

on the content side:

  • introduce the new ambassador
  • introduce 3 new TSC members - we will merge their PRs soon

Copy link
Contributor

@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: 1

🧹 Nitpick comments (7)
markdown/blog/2025-march-summary.md (7)

16-16: Simplify the Phrase "in anticipation of."
The sentence “...many enthusiasts join the workspace in anticipation of being accepted to the program” can be made more concise for improved readability. Consider a shorter alternative such as “...many enthusiasts join the workspace hoping to be accepted.”

🧰 Tools
🪛 LanguageTool

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


21-21: Refine the "big thank you" Expression.
The phrase “a big thank you” might be refined for a more polished tone (for example, “our sincere thanks” or optionally hyphenated as “thank-you”) to better suit formal community updates.

🧰 Tools
🪛 LanguageTool

[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


32-36: Vary Phrasing in Call for Speakers List Items.
All list items begin with “Submit your proposal...” Consider rephrasing one or more items (e.g., “Proposals are due by...”) to add variety and avoid repetitive structure.

🧰 Tools
🪛 LanguageTool

[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


42-44: Break Up Lengthy Sentence for Clarity.
The Spec x Tooling section (especially the long sentence on line 44) could be split into shorter sentences to improve readability and ensure the key points stand out.


52-53: Review Redundancy in TSC Designation.
The phrase “Technical Steering Committee (TSC) members” might feel a bit repetitive. Verify if including both the full title and abbreviation is necessary for clarity or if one could be omitted.


54-54: Correct Grammatical Number in Community Member Description.
The sentence “And finally, one of our long-time community member” should be adjusted to “one of our long-time community members” for grammatical agreement.


84-86: Review Verb Tense in the Community Discussions Section.
The sentence “We have an interesting discussion about conducting usability research on some of our tools in AsyncAPI” might benefit from verifying the verb tense. If the discussion is ongoing, consider “We are having an interesting discussion…” to better reflect the current engagement.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3c654fd and c0b58d4.

📒 Files selected for processing (2)
  • markdown/blog/2025-march-summary.md (1 hunks)
  • markdown/blog/release-notes-3.0.0.md (0 hunks)
💤 Files with no reviewable changes (1)
  • markdown/blog/release-notes-3.0.0.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[duplication] ~55-~55: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: 'Charles d'Avernas', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~73-~73: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member. <Profiles profiles={[ { name: 'L...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~76-~76: Possible typo: you repeated a word.
Context: ...e of our long-time community member. <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~85-~85: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

🔇 Additional comments (5)
markdown/blog/2025-march-summary.md (5)

1-14: Metadata Front Matter Looks Solid.
The front matter is well structured—with clear title, date (ISO format), type, tags, cover image, authors, and an excerpt—which supports consistent blog metadata.


46-47: AsyncAPI Governance Board Section is Clear.
The update on the Governance Board explains upcoming changes and invites community input effectively.


49-50: AsyncAPI Bounty Program Section is Informative.
The section conveys the status of the bounty program clearly and engagingly.


55-71: TSC Profiles Block is Well Structured.
The <Profiles> component for the new TSC members is correctly formatted and provides all necessary details.

🧰 Tools
🪛 LanguageTool

[duplication] ~55-~55: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: 'Charles d'Avernas', ...

(ENGLISH_WORD_REPEAT_RULE)


87-90: "Coming in March" Section Reads Well.
The upcoming events and newsletter details are clearly presented and provide a good call-to-action for readers.

@derberg
Copy link
Member

derberg commented Mar 25, 2025

can you also mention this in the summary? asyncapi/raml-dt-schema-parser#255

I'd like to have community input

Copy link
Contributor

@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

🧹 Nitpick comments (5)
markdown/blog/2025-march-summary.md (5)

16-18: Refine Introductory Phrase for Conciseness

The phrase “in anticipation of being accepted to the program” could be made more concise. Consider rephrasing it, for example to “while awaiting acceptance to the program.”

🧰 Tools
🪛 LanguageTool

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


19-21: Improve Clarity in Appreciation Statement

Line 21 contains redundancy with “stepping up and upholding.” To enhance clarity, consider revising it as follows:

- That said, we view this as a valuable lesson for improvement, and a big thank you goes out to our Code of Conduct Committee for stepping up and upholding the rules.
+ That said, we view this as a valuable lesson, and a sincere thank you to our Code of Conduct Committee for stepping up to uphold the rules.

This change removes the duplicate “up” and streamlines the sentence.

🧰 Tools
🪛 LanguageTool

[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


32-36: Vary Language in Call for Speakers Section

The bullet points in this section all begin with “Submit your proposal,” which can feel repetitive. Consider varying the phrasing to improve readability. For example, for the Bangalore entry:

- **[AsyncAPI Conference in Bangalore](https://conference.asyncapi.com/venue/Bangalore):** Submit your proposal **before June 29**, 2025.
+ **[AsyncAPI Conference in Bangalore](https://conference.asyncapi.com/venue/Bangalore):** Ensure your proposal reaches us by **June 29**, 2025.

This minor change adds variety without compromising clarity.

🧰 Tools
🪛 LanguageTool

[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


73-73: Correct Grammatical Number

The sentence “And finally, one of our long-time community member.” uses a singular noun where a plural is required. Consider updating it as follows:

- And finally, one of our long-time community member.
+ And finally, one of our long-time community members.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~73-~73: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member. <Profiles profiles={[ { name: 'L...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


85-85: Ensure Tense Consistency in Community Discussions

To maintain tense consistency in this section, consider rephrasing the sentence. For example:

- We have an interesting discussion about conducting usability research on some of our tools in AsyncAPI.
+ An interesting discussion is underway regarding usability research on our AsyncAPI tools.

This revision ensures the sentence flows smoothly.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~85-~85: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c0b58d4 and 226700d.

📒 Files selected for processing (1)
  • markdown/blog/2025-march-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...uable lesson for improvement, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[duplication] ~55-~55: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: 'Charles d'Avernas', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~73-~73: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member. <Profiles profiles={[ { name: 'L...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~76-~76: Possible typo: you repeated a word.
Context: ...e of our long-time community member. <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~85-~85: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

🔇 Additional comments (1)
markdown/blog/2025-march-summary.md (1)

1-14: Front Matter Setup is Correct

The YAML front matter is well-structured and includes all the necessary metadata for the update.

Copy link
Contributor

@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

🧹 Nitpick comments (7)
markdown/blog/2025-march-summary.md (7)

16-17: Simplify the Opening Phrase
The opening paragraph uses “in anticipation of being accepted,” which may be slightly wordy. Consider a more concise phrasing to improve readability, e.g., “...as the community eagerly awaited acceptance…”

🧰 Tools
🪛 LanguageTool

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


21-21: Refine Expression and Correct Repetition
The sentence on line 21 contains a duplicated word (“stepping up and upholding”) and uses “thank you” that could be tightened. For example, consider changing it to:

-That said, we view this as a valuable lesson, and a big thank you goes out to our Code of Conduct Committee for stepping up and upholding the rules.
+That said, we view this as a valuable lesson, and a heartfelt thank-you goes out to our Code of Conduct Committee for stepping up and upholding the rules.

This ensures clarity and avoids repetition.

🧰 Tools
🪛 LanguageTool

[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...ew this as a valuable lesson, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


32-36: Vary Sentence Structure in the Call for Speakers List
The entries in the “Call for Speakers” section (lines 32–36) all start similarly, which can feel repetitive. Consider rewording them to vary the structure. For example:

-**[AsyncAPI Conference in Munich](https://conference.asyncapi.com/venue/Munich):** Submit your proposal **before May 11**, 2025.
+**[AsyncAPI Conference in Munich](https://conference.asyncapi.com/venue/Munich):** Please submit your proposal by **May 11**, 2025.

Apply similar adjustments to the other list items to enhance readability.

🧰 Tools
🪛 LanguageTool

[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


44-44: Streamline Redundant Phrase
In the Meetup Section (line 44), the phrase “discuss topics related to AsyncAPI outside of the main conference events” can be streamlined to “discuss topics related to AsyncAPI outside the main conference events” for conciseness.

🧰 Tools
🪛 LanguageTool

[style] ~44-~44: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


53-54: Improve Clarity in the RAML Schema Parser Description
There appears to be a missing comma which affects the clarity of the sentence about the RAML Schema Parser. Consider this revision:

-We are looking to archive the RAML schema parser, a standard for RAML data types unless a community member is interested in maintaining the project.
+We are looking to archive the RAML schema parser, a standard for RAML data types, unless a community member is interested in maintaining the project.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~54-~54: Possible missing comma found.
Context: ...schema parser, a standard for RAML data types unless a community member is interested...

(AI_HYDRA_LEO_MISSING_COMMA)


84-84: Correct Grammatical Number
On line 84, the phrase “one of our long-time community member” should be pluralized to “one of our long-time community members” for grammatical correctness. For example:

-And finally, one of our long-time community member.
+And finally, one of our long-time community members.
🧰 Tools
🪛 LanguageTool

[uncategorized] ~84-~84: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member. <Profiles profiles={[ { name: 'L...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


96-96: Adjust Verb Tense for Consistency
In the “Community Discussions” section (line 96), consider revising “We have an interesting discussion…” to “There is an interesting discussion…” to better reflect the ongoing nature of the conversation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~96-~96: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 226700d and a858b4d.

📒 Files selected for processing (1)
  • markdown/blog/2025-march-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[grammar] ~21-~21: It appears that ‘thank you’ is missing a hyphen or needs to be quoted.
Context: ...ew this as a valuable lesson, and a big thank you goes out to our Code of Conduct Committ...

(A_THANK_YOU)


[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~44-~44: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


[uncategorized] ~54-~54: Possible missing comma found.
Context: ...schema parser, a standard for RAML data types unless a community member is interested...

(AI_HYDRA_LEO_MISSING_COMMA)


[duplication] ~66-~66: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: 'Charles d'Avernas', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~84-~84: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member. <Profiles profiles={[ { name: 'L...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~87-~87: Possible typo: you repeated a word.
Context: ...e of our long-time community member. <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~96-~96: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

🔇 Additional comments (1)
markdown/blog/2025-march-summary.md (1)

1-14: Metadata Section is well formatted
The front matter (lines 1–14) clearly defines the post’s metadata—title, date, type, tags, cover image, authors, and excerpt—in the expected format.

@thulieblack
Copy link
Member Author

@TRohit20 can you please approve first. @akshatnema Can you also approve, as well as the blog needs to be merged at least by tomorrow latest (but it was for today)

Copy link
Contributor

@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

🧹 Nitpick comments (6)
markdown/blog/2025-march-summary.md (6)

16-17: Simplify Overly Wordy Expression

In line 16, the phrase “in anticipation of being accepted to the program” can be made more concise. For example, consider “while awaiting program acceptance” to improve clarity and flow.

🧰 Tools
🪛 LanguageTool

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


21-21: Eliminate Redundant Wording

The sentence on line 21 uses “stepping up and upholding the rules,” which appears repetitive. A revised version such as “stepping up to uphold the rules” would be clearer.


32-36: Vary Bullet Point Introductions

The “Call for Speakers” section (lines 32–36) repeats the phrase “Submit your proposal” in each bullet. Varying the wording or sentence structure could enhance readability and make the list feel less monotonous.

🧰 Tools
🪛 LanguageTool

[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


44-44: Refine Redundant Prepositional Phrase

In line 44, “outside of the main conference events” could be shortened to “outside the main conference events” for reduced redundancy.

🧰 Tools
🪛 LanguageTool

[style] ~44-~44: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


84-84: Correct Grammatical Number in Profile Introduction

The text on line 84 reads “one of our long-time community member and AsyncAPI Ambassador:” Consider revising it to “one of our long-time community members and AsyncAPI Ambassadors:” or rephrasing for clarity.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~84-~84: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member and AsyncAPI Ambassador: <Profiles pr...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


96-96: Adjust Verb Tense for Clarity

Line 96 states “We have an interesting discussion about conducting usability research on some of our tools in AsyncAPI.” Consider revising this sentence to ensure consistent and correct tense usage, which will improve the overall clarity of the statement.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~96-~96: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fc4a5cf and 88812b4.

📒 Files selected for processing (1)
  • markdown/blog/2025-march-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~44-~44: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


[duplication] ~66-~66: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: "Charles d'Avernas", ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~84-~84: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member and AsyncAPI Ambassador: <Profiles pr...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~87-~87: Possible typo: you repeated a word.
Context: ...nity member and AsyncAPI Ambassador: <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~96-~96: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

🔇 Additional comments (2)
markdown/blog/2025-march-summary.md (2)

1-14: YAML Front Matter is Well Structured

The metadata (title, date, type, tags, cover, authors, and excerpt) is clearly defined and conforms to the expected structure. This sets a good foundation for the blog post.


1-101: Overall Document Approval

This new March 2025 community update is well-organized and thorough. The content clearly outlines upcoming events, new projects, and community discussions. Please consider the above nitpicking suggestions for enhanced clarity and style before merging.

🧰 Tools
🪛 LanguageTool

[style] ~16-~16: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[style] ~34-~34: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~44-~44: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


[duplication] ~66-~66: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: "Charles d'Avernas", ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~84-~84: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member and AsyncAPI Ambassador: <Profiles pr...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~87-~87: Possible typo: you repeated a word.
Context: ...nity member and AsyncAPI Ambassador: <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~96-~96: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

Copy link
Contributor

@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

🧹 Nitpick comments (8)
markdown/blog/2025-march-summary.md (8)

1-15: YAML Front Matter Consistency
The front matter is well structured; however, note that the featured field is currently set to true. In light of recent recommendations to unfeature outdated content (and to align with the cleanup suggestions), please consider setting this value to false if this new post isn’t intended to appear as featured.


17-23: Introduction Content & Wordiness
The introductory paragraph clearly outlines the excitement around GSoC and the subsequent community challenges. However, consider rephrasing “join the workspace in anticipation of being accepted to the program” to a more concise alternative such as “join the workspace ahead of program acceptance.” Additionally, the phrase “stepping up and upholding the rules” in line 22 repeats the “up” term; a slight reword (e.g. “stepping up and enforcing the rules”) could improve readability.

🧰 Tools
🪛 LanguageTool

[style] ~17-~17: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


31-37: Consistency in Call-for-Speakers Language
The bullet points under “Call for Speakers” consistently use “Submit your proposal” to introduce each deadline. Although this repetition reinforces clarity, varying the phrasing slightly (e.g. “Send in your proposal” or “Share your proposal”) may help alleviate the monotony and enhance style.

🧰 Tools
🪛 LanguageTool

[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


44-47: AsyncAPI Meetup Section Wording Refinement
In the Meetup Section description (line 45), the phrase “outside of the main conference events” could be simplified to “beyond the main conference events” to avoid redundancy. Overall, the section is clear and informative.

🧰 Tools
🪛 LanguageTool

[style] ~45-~45: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


58-60: AsyncAPI Governance Board Section Clarity
The Governance Board section communicates ongoing discussions and invites community input effectively. For clarity, you might consider a minor rephrase such as “allowing Ambassadors the option to join the TSC” instead of “have the option of Ambassadors becoming TSC members.”


64-95: TSC x Ambassadors Presentation & Grammar
The TSC x Ambassadors section is well organized. A couple of points for improvement:

  • In the profiles block (lines 67–83), ensure consistency in formatting and spacing of the author details.
  • On line 85, the phrase “one of our long-time community member and AsyncAPI Ambassador” should be revised for grammatical correctness. Consider changing it to “our long-time community member and AsyncAPI Ambassador” or “one of our long-time community members who is also an AsyncAPI Ambassador.”
    These changes will improve clarity and consistency in the presentation of community profiles.
🧰 Tools
🪛 LanguageTool

[duplication] ~67-~67: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: "Charles d'Avernas", ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~85-~85: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member and AsyncAPI Ambassador: <Profiles pr...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~88-~88: Possible typo: you repeated a word.
Context: ...nity member and AsyncAPI Ambassador: <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


96-98: Community Discussions Verb Tense
The “Community Discussions” section is engaging; however, the opening sentence “We have an interesting discussion about conducting usability research on some of our tools…” could benefit from a tense adjustment for clarity. For example, “There is an interesting discussion underway about conducting usability research…” might better convey that this is an ongoing conversation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~97-~97: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)


99-102: Coming in March – Final Section
The “Coming in March” section effectively previews upcoming events. The content is clear, though please ensure that any trailing or extra line (e.g. an unexpected “103” marker) is corrected to maintain consistency in the markdown file formatting.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 88812b4 and a2b3e43.

📒 Files selected for processing (1)
  • markdown/blog/2025-march-summary.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2025-march-summary.md

[style] ~17-~17: ‘in anticipation of’ might be wordy. Consider a shorter alternative.
Context: ...een many enthusiasts join the workspace in anticipation of being accepted to the program. However...

(EN_WORDINESS_PREMIUM_IN_ANTICIPATION_OF)


[style] ~35-~35: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... proposal before May 17, 2025. - **[AsyncAPI Conference in Bangalore](https://confer...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~36-~36: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before June 29, 2025. - **[AsyncAPI Conference in London](https://conferenc...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...proposal before July 13, 2025. - **[AsyncAPI Conference in Paris](https://conference...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)


[style] ~45-~45: This phrase is redundant. Consider using “outside”.
Context: ... and discuss topics related to AsyncAPI outside of the main conference events. The goal is...

(OUTSIDE_OF)


[duplication] ~67-~67: Possible typo: you repeated a word.
Context: ...api.com/community/tsc) (TSC) members. <Profiles profiles={[ { name: "Charles d'Avernas", ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~85-~85: The grammatical number of this noun doesn’t look right. Consider replacing it.
Context: ...finally, one of our long-time community member and AsyncAPI Ambassador: <Profiles pr...

(AI_EN_LECTOR_REPLACEMENT_NOUN_NUMBER)


[duplication] ~88-~88: Possible typo: you repeated a word.
Context: ...nity member and AsyncAPI Ambassador: <Profiles profiles={[ { name: 'Laurent Broudoux', ...

(ENGLISH_WORD_REPEAT_RULE)


[uncategorized] ~97-~97: This verb may not be in the correct tense. Consider changing the tense to fit the context better.
Context: ... } ]} /> ## Community Discussions We have an interesting discussion about conduct...

(AI_EN_LECTOR_REPLACEMENT_VERB_TENSE)

🔇 Additional comments (2)
markdown/blog/2025-march-summary.md (2)

49-52: Spec x Tooling and RAML Schema Parser
The descriptions for both Neuroglia.AsyncAPI and the RAML Schema Parser are informative and include helpful links. The messaging regarding community input for the RAML schema parser aligns well with previous feedback. No changes required here.


61-63: AsyncAPI Bounty Program Section
This section is succinct and delivers the update on the bounty program clearly. The link and the statistics provide good context.

@TRohit20
Copy link
Collaborator

TRohit20 commented Apr 1, 2025

I already approved and gave rtm. Do i need to do it again for merge?

@TRohit20
Copy link
Collaborator

TRohit20 commented Apr 1, 2025

/rtm

@asyncapi-bot
Copy link
Contributor

Hello, @TRohit20! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: To request an update from the upstream branch, simply comment /u or /update and our bot will handle the update operation promptly.

       The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR. Also the update will not work if your fork is located in an organization, not under your personal profile.
       Thanks 😄

@TRohit20
Copy link
Collaborator

TRohit20 commented Apr 1, 2025

/update

Copy link
Collaborator

@TRohit20 TRohit20 left a comment

Choose a reason for hiding this comment

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

/rtm

@derberg
Copy link
Member

derberg commented Apr 2, 2025

@TRohit20 there is no merging until @akshatnema approves. He initially did not leave a comment but requested changes and this is blocking the merge

Screenshot 2025-04-02 at 09 08 33

@TRohit20
Copy link
Collaborator

TRohit20 commented Apr 3, 2025

I saw that but prev we could overwrite using "rtm". Guess that isn't the case cz Akshat requested changes. But his changes were resolved. I was wondering it is still blocking

@akshatnema
Copy link
Member

/rtm

@asyncapi-bot
Copy link
Contributor

Hello, @akshatnema! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: To request an update from the upstream branch, simply comment /u or /update and our bot will handle the update operation promptly.

       The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR. Also the update will not work if your fork is located in an organization, not under your personal profile.
       Thanks 😄

@akshatnema
Copy link
Member

/rtm

@asyncapi-bot asyncapi-bot merged commit 1a80ecf into asyncapi:master Apr 5, 2025
19 of 20 checks passed
@thulieblack thulieblack deleted the march-2025 branch April 5, 2025 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants