docs(community): update latest community documentation #4493
Conversation
asyncapi-bot
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg,
sambhavgupta0705 and
thulieblack
as code owners
✅ Deploy Preview for asyncapi-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
asyncapi-bot
requested review from
CBID2,
ashmitjsg,
bandantonio and
vishvamsinh28
WalkthroughThis PR adds a comprehensive AsyncAPI Maintainership Program (AMP) documentation suite with 24 markdown files covering program overview, contributor and mentor pathways, evaluation processes, payments, sponsorship, and community guidelines. A configuration entry is added to expose the new guide section. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes The review scope is primarily documentation content additions with homogeneous structure and low complexity. The main focus is validating content organization, internal consistency, completeness of the guide structure, and the single configuration change. No code logic, interdependencies, or intricate patterns require detailed scrutiny. Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4493--asyncapi-website.netlify.app/ |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (7)
markdown/docs/community/maintainership-guide/amp-code-of-conduct.md (1)
47-48: Wrap email addresses in markdown link syntax or refactor the formatting.Line 47 contains bare email addresses formatted as
(ea.elegbede@gmail.com | sibanda.thulie@gmail.com). For consistency with markdown best practices and to improve accessibility, consider wrapping them as mailto links:- **Email the Program Organizers** (ea.elegbede@gmail.com | sibanda.thulie@gmail.com) + **Email the Program Organizers** + - [ea.elegbede@gmail.com](mailto:ea.elegbede@gmail.com) + - [sibanda.thulie@gmail.com](mailto:sibanda.thulie@gmail.com)Alternatively, if you prefer inline formatting:
- **Email the Program Organizers** (ea.elegbede@gmail.com | sibanda.thulie@gmail.com) + **Email the Program Organizers**: [ea.elegbede@gmail.com](mailto:ea.elegbede@gmail.com) or [sibanda.thulie@gmail.com](mailto:sibanda.thulie@gmail.com)markdown/docs/community/maintainership-guide/amp-program-goals.md (1)
14-15: Consider stronger wording for contributor relationships.Line 15 uses "deep contributor relationships." While not incorrect, consider alternatives like "meaningful," "sustained," or "enduring" to strengthen the language.
markdown/docs/community/maintainership-guide/amp-communications.md (1)
21-21: Standardize spacing around emphasis markers.Several lines have inconsistent spacing around underscore emphasis markers (
_text_). Lines 21, 30, 36, and 52 have extra spaces before or after underscores. Apply this diff to standardize the formatting:+_Contributors must follow contribution guidelines and use clear, descriptive messages._ +_Be sure to check your inbox regularly and avoid missing critical updates from the program organizers._ +_Tip: Turn on Slack and program's GitHub discussions notifications to ensure you never miss important updates._Also applies to: 30-30, 36-36, 52-52
markdown/docs/community/maintainership-guide/amp-sponsorship-why-it-matters.md (1)
7-16: Reduce sentence-initial repetition for polish. Lines 7 and 13 both open with "At AsyncAPI, we believe..." and "We're proud..." Consider rephrasing for variety. For example, restructure line 13 to avoid repeating the opening from line 7.markdown/docs/community/maintainership-guide/amp-mentor-project-tips-and-submission.md (1)
44-54: Consider alternative to repeated "right" word. Line 44 uses "finding the right contributor," and the word "right" appears frequently in this section. Consider varying word choice (e.g., "finding the ideal contributor" or "finding the best fit") for stylistic polish.markdown/docs/community/maintainership-guide/amp-timeline-and-schedule.md (2)
28-32: Reduce repetitive sentence beginnings in timeline intro. Lines 30–32 have three consecutive sentences starting with "Program" (Program coordinators, Program organizers, A breakdown). Vary the structure for better flow. For example:**Program announcement period — [July 1-7]:** - Program coordinators begin volunteer outreach. -- Program organizers begin the process of securing sponsorships to support contributor stipends and program operations. +- Simultaneously, sponsorship efforts kick off to fund contributor stipends and program operations. - A breakdown of the yearly budget is shared to determine the number of contributor slots.
52-61: Reduce repetition of "Mentors" and "Applicants" at sentence start (lines 54–61). Several consecutive bullets start with "Mentors provide," "Mentors help," "Mentors provide," and so on. While the content is clear, varying sentence structure would improve readability:- Approved applicants begin contributing to the selected projects. - Program organizers match applicants with mentors and share contribution guidelines. - Mentors host virtual onboarding calls to introduce applicants to the project and the AsyncAPI community. -- Mentors help applicants set up development environments and guide their contributions. +- During setup, mentors assist applicants with development environments and guide their contributions. -- Mentors provide feedback and request improvements as needed on contributions. +- Feedback loops are established, with mentors requesting improvements on contributions as needed.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (27)
config/edit-page-config.json(1 hunks)markdown/docs/community/maintainership-guide/_section.md(1 hunks)markdown/docs/community/maintainership-guide/amp-budget.md(1 hunks)markdown/docs/community/maintainership-guide/amp-code-of-conduct.md(1 hunks)markdown/docs/community/maintainership-guide/amp-communications.md(1 hunks)markdown/docs/community/maintainership-guide/amp-community-values.md(1 hunks)markdown/docs/community/maintainership-guide/amp-contributor-application-review-process.md(1 hunks)markdown/docs/community/maintainership-guide/amp-contributor-benefits-and-expectations.md(1 hunks)markdown/docs/community/maintainership-guide/amp-contributor-how-to-apply.md(1 hunks)markdown/docs/community/maintainership-guide/amp-definitions.md(1 hunks)markdown/docs/community/maintainership-guide/amp-evaluation-checkin-process.md(1 hunks)markdown/docs/community/maintainership-guide/amp-evaluation-process.md(1 hunks)markdown/docs/community/maintainership-guide/amp-faq.md(1 hunks)markdown/docs/community/maintainership-guide/amp-mentor-onboarding-process.md(1 hunks)markdown/docs/community/maintainership-guide/amp-mentor-project-tips-and-submission.md(1 hunks)markdown/docs/community/maintainership-guide/amp-mentor-responsibilities-and-best-practices.md(1 hunks)markdown/docs/community/maintainership-guide/amp-mentor-support-and-escalation-path.md(1 hunks)markdown/docs/community/maintainership-guide/amp-organizer-volunteers.md(1 hunks)markdown/docs/community/maintainership-guide/amp-overview.md(1 hunks)markdown/docs/community/maintainership-guide/amp-payments-disbursement.md(1 hunks)markdown/docs/community/maintainership-guide/amp-payments-eligibility.md(1 hunks)markdown/docs/community/maintainership-guide/amp-program-goals.md(1 hunks)markdown/docs/community/maintainership-guide/amp-sponsorship-secure-sponsorship.md(1 hunks)markdown/docs/community/maintainership-guide/amp-sponsorship-why-it-matters.md(1 hunks)markdown/docs/community/maintainership-guide/amp-timeline-and-schedule.md(1 hunks)markdown/docs/community/maintainership-guide/amp-what-mentees-says.md(1 hunks)markdown/docs/community/maintainership-guide/index.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/docs/community/maintainership-guide/amp-overview.md
[grammar] ~7-~7: Use a hyphen to join words.
Context: ...unity, designed to empower aspiring open source contributors and guide them towar...
(QB_NEW_EN_HYPHEN)
markdown/docs/community/maintainership-guide/_section.md
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- title: Maintainership Program Guide weight: 5 ---
(QB_NEW_DE)
markdown/docs/community/maintainership-guide/amp-program-goals.md
[style] ~15-~15: Consider a different adjective to strengthen your wording.
Context: ...age Long-Term Engagement** Foster deep contributor relationships that extend b...
(DEEP_PROFOUND)
markdown/docs/community/maintainership-guide/amp-timeline-and-schedule.md
[style] ~31-~31: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...oordinators begin volunteer outreach. - Program organizers begin the process of securin...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~32-~32: Consider using a more formal adjective.
Context: ...rogram operations. - A breakdown of the yearly budget is shared to determine the numbe...
(YEARLY_ANNUAL)
[style] ~58-~58: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...nments and guide their contributions. - Mentors provide feedback and request improvemen...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
markdown/docs/community/maintainership-guide/amp-code-of-conduct.md
[style] ~35-~35: Try using a synonym here to strengthen your wording.
Context: ...rassment, discrimination, or derogatory comments - Demeaning, insulting, or aggressive l...
(COMMENT_REMARK)
markdown/docs/community/maintainership-guide/amp-what-mentees-says.md
[style] ~13-~13: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...exity. The AsyncAPI community itself is amazing, full of highly skilled and welcoming d...
(AWESOME)
[style] ~19-~19: Consider a different adjective to strengthen your wording.
Context: ...e learned so much from you and gained a deeper understanding of how different kinds of...
(DEEP_PROFOUND)
markdown/docs/community/maintainership-guide/amp-mentor-project-tips-and-submission.md
[style] ~44-~44: You have already used ‘right’ in nearby sentences. Consider using an alternative word to let your writing stand out and sound more polished.
Context: ...r project idea is accepted, finding the right contributor is crucial. - **One Idea, ...
(REP_RIGHT)
markdown/docs/community/maintainership-guide/amp-sponsorship-why-it-matters.md
[style] ~16-~16: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...source growth, not just run a program. We’re proud to serve a vibrant and growing...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🪛 markdownlint-cli2 (0.18.1)
markdown/docs/community/maintainership-guide/amp-sponsorship-secure-sponsorship.md
57-57: Bare URL used
(MD034, no-bare-urls)
markdown/docs/community/maintainership-guide/amp-code-of-conduct.md
47-47: Bare URL used
(MD034, no-bare-urls)
47-47: Bare URL used
(MD034, no-bare-urls)
markdown/docs/community/maintainership-guide/amp-mentor-support-and-escalation-path.md
12-12: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
13-13: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
17-17: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
18-18: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
22-22: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
23-23: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
24-24: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
28-28: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
34-34: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
38-38: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
markdown/docs/community/maintainership-guide/amp-mentor-project-tips-and-submission.md
62-62: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
64-64: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
66-66: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
71-71: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
73-73: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
77-77: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
79-79: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
81-81: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
83-83: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
markdown/docs/community/maintainership-guide/amp-sponsorship-why-it-matters.md
19-19: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
21-21: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Automerge PR autoapproved by a bot
- GitHub Check: Lighthouse CI
🔇 Additional comments (22)
config/edit-page-config.json (1)
66-69: LGTM!The new config entry for
community/maintainership-guideis properly structured and follows the existing pattern. The href correctly points to the GitHub community repository path for editing.markdown/docs/community/maintainership-guide/_section.md (1)
1-4: LGTM!Clean front matter for section navigation. The weight value is appropriate for ordering this section within the documentation hierarchy.
Note: The static analysis grammar warning is a false positive from LanguageTool's language detection.
markdown/docs/community/maintainership-guide/amp-code-of-conduct.md (1)
1-54: Well-structured Code of Conduct with clear expectations and reporting procedures.The document establishes a welcoming environment, clearly defines expected and unacceptable behaviors, and provides concrete reporting channels. The content is comprehensive and aligns well with the AsyncAPI community values defined in other AMP documentation.
markdown/docs/community/maintainership-guide/amp-what-mentees-says.md (1)
1-19: LGTM!The testimonials provide authentic, compelling evidence of the program's impact. The diverse perspectives from different mentees (design, development, documentation) effectively showcase the program's value across different contribution types.
markdown/docs/community/maintainership-guide/amp-mentor-onboarding-process.md (1)
1-52: LGTM!Well-structured onboarding process that clearly outlines the journey from application through kickoff. The eligibility criteria are comprehensive and appropriately set expectations. The section on mandatory kickoff calls and access to resources demonstrates thoughtful program design.
markdown/docs/community/maintainership-guide/index.md (1)
1-22: LGTM!The Code of Conduct link points to the AsyncAPI community health files repository, and the link is correctly formatted as a markdown reference. The landing page effectively introduces the purpose and scope of the Maintainership Program Guide.
markdown/docs/community/maintainership-guide/amp-community-values.md (1)
1-44: LGTM!Comprehensive community values document that sets clear expectations across excellence, accessibility, fairness, and safety. The structure effectively communicates the program's commitment to contributors across multiple dimensions.
markdown/docs/community/maintainership-guide/amp-mentor-responsibilities-and-best-practices.md (1)
1-48: LGTM!Comprehensive and practical mentor guidance that covers the full mentorship lifecycle. The four key areas (Onboarding, Communication, Guidance, Evaluation) are well-organized with actionable advice. The accountability note ensures program quality is maintained.
markdown/docs/community/maintainership-guide/amp-definitions.md (1)
1-57: Solid definitions guide.Clear, concise definitions of key AMP terminology. This will serve as a helpful reference for readers navigating the broader AMP documentation.
markdown/docs/community/maintainership-guide/amp-faq.md (1)
1-76: Comprehensive and well-structured FAQ.Excellent coverage of common participant questions. The FAQ effectively directs readers to other documentation while addressing immediate concerns about eligibility, stipends, and program mechanics.
markdown/docs/community/maintainership-guide/amp-payments-eligibility.md (1)
1-32: Clear and concise eligibility criteria.Well-structured documentation of stipend eligibility for both contributors and mentors. Criteria are specific and directly tied to program expectations defined elsewhere in the documentation.
markdown/docs/community/maintainership-guide/amp-organizer-volunteers.md (1)
1-50: Excellent volunteer guide with clear pathways.Comprehensive overview of volunteer opportunities with practical roles and clear entry points. The tone is welcoming and the structure effectively guides potential volunteers through options and next steps.
markdown/docs/community/maintainership-guide/amp-contributor-how-to-apply.md (1)
1-93: Well-structured contributor application guide. The documentation is clear, well-organized, and provides practical guidance for applicants. The eligibility requirements are concrete, and the step-by-step process is easy to follow. The section on non-selection helps set expectations positively.markdown/docs/community/maintainership-guide/amp-contributor-benefits-and-expectations.md (1)
1-59: Excellent two-way expectations framework. This document strikes a good balance between benefits and expectations, using a respectful two-way framing that sets clear expectations while emphasizing support. The time commitment is explicit, and the sections on communication, collaboration, and commitment are practical and comprehensive.markdown/docs/community/maintainership-guide/amp-overview.md (1)
1-35: Strong program overview with compelling narrative. The document effectively communicates the program's purpose, supportive philosophy, and impact. The "Why the Maintainership Program Matters?" section makes a compelling case for the initiative, and the Isaac Newton quote provides good inspiration. The list of supportive measures is concrete and human-centered.markdown/docs/community/maintainership-guide/amp-timeline-and-schedule.md (1)
1-101: Comprehensive and well-structured timeline. The table overview is excellent for quick reference, and the detailed breakdown provides clear phase-by-phase guidance. Dates, responsibilities, and deliverables are all clearly articulated. The only opportunities for improvement are stylistic (reducing repetitive sentence structure), which are optional.markdown/docs/community/maintainership-guide/amp-evaluation-checkin-process.md (1)
1-24: Clear and concise check-in workflow documentation. The document effectively communicates the evaluation reminder schedule and follow-up process. The emphasis on support and removing blockers is well-placed. The Slack DM follow-up at the 3-day mark is practical and provides ample opportunity for participants to submit.Consider clarifying what happens if an evaluation is still not submitted after the Slack DM follow-up (after day 3). Should this section reference escalation procedures or consequences documented elsewhere (e.g., stipend eligibility impact mentioned in line 6)?
markdown/docs/community/maintainership-guide/amp-contributor-application-review-process.md (1)
1-44: Well-defined two-phase application review process. The document clearly explains the screening and evaluation criteria at each phase. The distinction between handling multiple vs. single contributors in the final phase is practical. The four evaluation criteria (Communication, Project Understanding, Quality of Contributions, Collaboration & Conduct) are comprehensive and well-defined.Consider adding a cross-reference to the timeline document to show when each phase occurs, and clarify what happens after mentors submit their assessments (e.g., final decision-making process by program organizers).
markdown/docs/community/maintainership-guide/amp-mentor-support-and-escalation-path.md (1)
6-8: Clear and empathetic framing of mentor support.The introduction effectively sets the tone for a supportive program structure. The content clearly communicates available resources and escalation paths.
markdown/docs/community/maintainership-guide/amp-budget.md (2)
13-36: Clear budget model with transparent allocations.The fixed $2,000 per-project budget is well-explained with practical examples. The cost breakdown table effectively communicates how funds are allocated between contributor stipends and mentor recognition. The annual projection example makes the scaling approach concrete and understandable.
7-11: Open Collective links verified as active.Both links in the document are accessible and correctly point to AsyncAPI's funding resources:
- Main Open Collective page (line 7): HTTP 200
- Maintainership Program project page (line 11): HTTP 200
No issues found. The document content is accurate.
markdown/docs/community/maintainership-guide/amp-evaluation-process.md (1)
1-49: Well-structured evaluation workflow documentation.The document clearly explains evaluation timing, process, and outcomes. The emphasis on ongoing feedback before evaluations (lines 10-16) is a strong practice. The mandatory evaluation submission requirement (lines 33) and confidentiality guidelines are appropriately emphasized.
| ## Payments - Be Patient | ||
|
|
||
| Once your evaluation is marked as “pass,” you will be eligible to request your stipend via the [AsyncAPI Mentorship Open Collective](https://opencollective.com/asyncapi/projects/asyncapi-mentorship) page. | ||
|
|
||
| Please allow **a few business days** for your payment to be processed after submission. If you’re unsure how to submit your expense, [refer to this guide](../stipend-and-payments/disbursement). No newline at end of file |
There was a problem hiding this comment.
🧩 Analysis chain
Verify internal link path and payment guide references.
The document references an internal link to the disbursement guide (line 54) using a relative path. Additionally, line 52 references the Open Collective page (already flagged in File 2). Ensure both the internal path ../stipend-and-payments/disbursement is correct and accessible, and that the external Open Collective link is valid.
🏁 Script executed:
#!/bin/bash
# Description: Verify internal documentation links are correct
# Search for files matching the referenced disbursement guide
fd -t f "disbursement" markdown/docs/community/
# Look for any stipend-and-payments directory or related files
fd -t d "stipend-and-payments" markdown/docs/community/
# Also verify the file structure around maintainership-guide
find markdown/docs/community/maintainership-guide -maxdepth 1 -type f | head -20Length of output: 1549
Fix broken internal link to disbursement guide.
The relative path ../stipend-and-payments/disbursement (line 54) is incorrect. There is no stipend-and-payments directory in the community docs folder. The actual disbursement file is amp-payments-disbursement.md in the same directory. Update the link to ./amp-payments-disbursement.
🤖 Prompt for AI Agents
In markdown/docs/community/maintainership-guide/amp-evaluation-process.md around
lines 50 to 54 the relative link ../stipend-and-payments/disbursement is invalid
because the stipend-and-payments directory doesn't exist; update the link target
to ./amp-payments-disbursement (the disbursement file in the same directory) so
the anchor points to ./amp-payments-disbursement (adjust extension if
necessary).
| - **Set Healthy Boundaries** | ||
|
|
||
| - You are not expected to be available 24/7. | ||
|
|
||
| - Schedule weekly or bi-weekly check-ins. | ||
|
|
||
| - Define working and non-working hours upfront. | ||
|
|
||
|
|
||
| - **Take a Break When Needed** | ||
|
|
||
| - It’s okay to step back if life gets hectic. | ||
|
|
||
| - Let fellow mentors or admins know if you’re overwhelmed; burnout helps no one. | ||
|
|
||
| - **It’s Okay to Fail a Contributor** | ||
|
|
||
| - If, despite your best efforts, the pairing doesn’t work: | ||
|
|
||
| - They disappear or stop communicating. | ||
|
|
||
| - They oversold their skills and cannot meet expectations. | ||
|
|
||
| - Persistent issues like ignoring feedback or violating community standards. | ||
|
|
There was a problem hiding this comment.
Fix nested list indentation to meet markdown standards. Multiple bullet points (lines 62–83) in nested list structures have incorrect indentation. These should use 2 spaces for sub-bullets, not 3. This affects the entire "Set Healthy Boundaries," "Take a Break When Needed," and "It's Okay to Fail a Contributor" sections.
Apply this diff to one of the problematic sections as an example:
- **Set Healthy Boundaries**
- - You are not expected to be available 24/7.
+ - You are not expected to be available 24/7.
- - Schedule weekly or bi-weekly check-ins.
+ - Schedule weekly or bi-weekly check-ins.
- - Define working and non-working hours upfront.
+ - Define working and non-working hours upfront.Apply the same indentation fix to lines 71–73, 77–83, and anywhere else in the document with the same pattern.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - **Set Healthy Boundaries** | |
| - You are not expected to be available 24/7. | |
| - Schedule weekly or bi-weekly check-ins. | |
| - Define working and non-working hours upfront. | |
| - **Take a Break When Needed** | |
| - It’s okay to step back if life gets hectic. | |
| - Let fellow mentors or admins know if you’re overwhelmed; burnout helps no one. | |
| - **It’s Okay to Fail a Contributor** | |
| - If, despite your best efforts, the pairing doesn’t work: | |
| - They disappear or stop communicating. | |
| - They oversold their skills and cannot meet expectations. | |
| - Persistent issues like ignoring feedback or violating community standards. | |
| - **Set Healthy Boundaries** | |
| - You are not expected to be available 24/7. | |
| - Schedule weekly or bi-weekly check-ins. | |
| - Define working and non-working hours upfront. | |
| - **Take a Break When Needed** | |
| - It's okay to step back if life gets hectic. | |
| - Let fellow mentors or admins know if you're overwhelmed; burnout helps no one. | |
| - **It's Okay to Fail a Contributor** | |
| - If, despite your best efforts, the pairing doesn't work: | |
| - They disappear or stop communicating. | |
| - They oversold their skills and cannot meet expectations. | |
| - Persistent issues like ignoring feedback or violating community standards. |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
62-62: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
64-64: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
66-66: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
71-71: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
73-73: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
77-77: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
79-79: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
81-81: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
83-83: Unordered list indentation
Expected: 2; Actual: 3
(MD007, ul-indent)
🤖 Prompt for AI Agents
In
markdown/docs/community/maintainership-guide/amp-mentor-project-tips-and-submission.md
around lines 60 to 84, several nested list items under "Set Healthy Boundaries",
"Take a Break When Needed" and "It’s Okay to Fail a Contributor" use incorrect
3-space indentation for sub-bullets; change those sub-bullets to use 2 spaces
before the hyphen (i.e., reduce indentation from 3 to 2 spaces) so they render
as proper nested lists, apply the same 2-space rule to lines 71–73, 77–83 and
any other places in the file with the same pattern, and ensure consistent
nesting levels for all bullets in those sections.
| ### 1. AsyncAPI Mentor Support Channel | ||
|
|
||
| - You’ll have access to a dedicated Slack channel exclusively for mentors | ||
| - You'll use this space to share challenges, seek advice, or ask questions from fellow mentors and program organizers | ||
|
|
||
| ### 2. Program Organizers Check-Ins | ||
|
|
||
| - Program leads will schedule periodic check-ins **(optional)** to see how things are going, provide support, and gather feedback | ||
| - You can always request a **one-on-one** with the organizers if you encounter blockers that need private or immediate attention (especially when handling difficult contributors) | ||
|
|
||
| ### 3. Conflict Resolution Path | ||
|
|
||
| - If you face interpersonal challenges, such as an uncooperative/nonchalant contributor or community conflicts, escalate early: | ||
| - First, attempt a private conversation with the mentee, framed around constructive feedback | ||
| - If the issue remains unresolved, report it to the program organizers via Slack DM or email | ||
|
|
||
| ### 4. Time or Commitment Challenges | ||
|
|
||
| - If unexpected time constraints arise or your availability as a mentor changes: | ||
| - Let the program organizers know as early as possible | ||
| - We can explore shared mentorship, backup mentor support, or a contributor transition plan | ||
|
|
||
| - If a contributor is showing signs of non-commitment during the program phase: | ||
| - Reach out to the contributor privately to understand the reason for no commitment | ||
| - If there is no response within a week, please inform the program organizers as soon as possible | ||
|
|
||
| ### 5. Code of Conduct & Reporting | ||
| - All mentors and contributors are expected to uphold the AsyncAPI Code of Conduct | ||
| - For violations or inappropriate behaviour, use our [formal reporting process](https://github.com/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md) or contact the CoC team No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Fix unordered list indentation throughout the document.
The file has multiple markdown formatting violations (MD007) where unordered list items are improperly indented. This affects consistency and readability. Update all list items to use correct indentation (0 spaces for top-level items, 2 spaces for nested items).
Apply this diff to fix the list indentation:
### 1. AsyncAPI Mentor Support Channel
- - You'll have access to a dedicated Slack channel exclusively for mentors
- - You'll use this space to share challenges, seek advice, or ask questions from fellow mentors and program organizers
+ - You'll have access to a dedicated Slack channel exclusively for mentors
+ - You'll use this space to share challenges, seek advice, or ask questions from fellow mentors and program organizers
### 2. Program Organizers Check-Ins
- - Program leads will schedule periodic check-ins **(optional)** to see how things are going, provide support, and gather feedback
- - You can always request a **one-on-one** with the organizers if you encounter blockers that need private or immediate attention (especially when handling difficult contributors)
+ - Program leads will schedule periodic check-ins **(optional)** to see how things are going, provide support, and gather feedback
+ - You can always request a **one-on-one** with the organizers if you encounter blockers that need private or immediate attention (especially when handling difficult contributors)
### 3. Conflict Resolution Path
- - If you face interpersonal challenges, such as an uncooperative/nonchalant contributor or community conflicts, escalate early:
- - First, attempt a private conversation with the mentee, framed around constructive feedback
- - If the issue remains unresolved, report it to the program organizers via Slack DM or email
+ - If you face interpersonal challenges, such as an uncooperative/nonchalant contributor or community conflicts, escalate early:
+ - First, attempt a private conversation with the mentee, framed around constructive feedback
+ - If the issue remains unresolved, report it to the program organizers via Slack DM or email
### 4. Time or Commitment Challenges
- - If unexpected time constraints arise or your availability as a mentor changes:
- - Let the program organizers know as early as possible
- - We can explore shared mentorship, backup mentor support, or a contributor transition plan
+ - If unexpected time constraints arise or your availability as a mentor changes:
+ - Let the program organizers know as early as possible
+ - We can explore shared mentorship, backup mentor support, or a contributor transition plan
- - If a contributor is showing signs of non-commitment during the program phase:
- - Reach out to the contributor privately to understand the reason for no commitment
- - If there is no response within a week, please inform the program organizers as soon as possible
+ - If a contributor is showing signs of non-commitment during the program phase:
+ - Reach out to the contributor privately to understand the reason for no commitment
+ - If there is no response within a week, please inform the program organizers as soon as possible
### 5. Code of Conduct & Reporting
- - All mentors and contributors are expected to uphold the AsyncAPI Code of Conduct
- - For violations or inappropriate behaviour, use our [formal reporting process](https://github.com/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md) or contact the CoC team
+ - All mentors and contributors are expected to uphold the AsyncAPI Code of Conduct
+ - For violations or inappropriate behaviour, use our [formal reporting process](https://github.com/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md) or contact the CoC team📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### 1. AsyncAPI Mentor Support Channel | |
| - You’ll have access to a dedicated Slack channel exclusively for mentors | |
| - You'll use this space to share challenges, seek advice, or ask questions from fellow mentors and program organizers | |
| ### 2. Program Organizers Check-Ins | |
| - Program leads will schedule periodic check-ins **(optional)** to see how things are going, provide support, and gather feedback | |
| - You can always request a **one-on-one** with the organizers if you encounter blockers that need private or immediate attention (especially when handling difficult contributors) | |
| ### 3. Conflict Resolution Path | |
| - If you face interpersonal challenges, such as an uncooperative/nonchalant contributor or community conflicts, escalate early: | |
| - First, attempt a private conversation with the mentee, framed around constructive feedback | |
| - If the issue remains unresolved, report it to the program organizers via Slack DM or email | |
| ### 4. Time or Commitment Challenges | |
| - If unexpected time constraints arise or your availability as a mentor changes: | |
| - Let the program organizers know as early as possible | |
| - We can explore shared mentorship, backup mentor support, or a contributor transition plan | |
| - If a contributor is showing signs of non-commitment during the program phase: | |
| - Reach out to the contributor privately to understand the reason for no commitment | |
| - If there is no response within a week, please inform the program organizers as soon as possible | |
| ### 5. Code of Conduct & Reporting | |
| - All mentors and contributors are expected to uphold the AsyncAPI Code of Conduct | |
| - For violations or inappropriate behaviour, use our [formal reporting process](https://github.com/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md) or contact the CoC team | |
| ### 1. AsyncAPI Mentor Support Channel | |
| - You'll have access to a dedicated Slack channel exclusively for mentors | |
| - You'll use this space to share challenges, seek advice, or ask questions from fellow mentors and program organizers | |
| ### 2. Program Organizers Check-Ins | |
| - Program leads will schedule periodic check-ins **(optional)** to see how things are going, provide support, and gather feedback | |
| - You can always request a **one-on-one** with the organizers if you encounter blockers that need private or immediate attention (especially when handling difficult contributors) | |
| ### 3. Conflict Resolution Path | |
| - If you face interpersonal challenges, such as an uncooperative/nonchalant contributor or community conflicts, escalate early: | |
| - First, attempt a private conversation with the mentee, framed around constructive feedback | |
| - If the issue remains unresolved, report it to the program organizers via Slack DM or email | |
| ### 4. Time or Commitment Challenges | |
| - If unexpected time constraints arise or your availability as a mentor changes: | |
| - Let the program organizers know as early as possible | |
| - We can explore shared mentorship, backup mentor support, or a contributor transition plan | |
| - If a contributor is showing signs of non-commitment during the program phase: | |
| - Reach out to the contributor privately to understand the reason for no commitment | |
| - If there is no response within a week, please inform the program organizers as soon as possible | |
| ### 5. Code of Conduct & Reporting | |
| - All mentors and contributors are expected to uphold the AsyncAPI Code of Conduct | |
| - For violations or inappropriate behaviour, use our [formal reporting process](https://github.com/asyncapi/community/blob/master/code_of_conduct/coc-incident-resolution-procedures.md) or contact the CoC team |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
12-12: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
13-13: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
17-17: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
18-18: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
22-22: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
23-23: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
24-24: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
28-28: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
29-29: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
34-34: Unordered list indentation
Expected: 2; Actual: 4
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
38-38: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
🤖 Prompt for AI Agents
In
markdown/docs/community/maintainership-guide/amp-mentor-support-and-escalation-path.md
around lines 10 to 38, several unordered list items are misindented causing
MD007 violations; fix by normalizing list indentation so all top-level list
markers start at column 0 and nested list items are indented by 2 spaces, ensure
sub-bullets under a parent bullet are exactly 2 spaces deeper than that parent,
remove any stray extra spaces before list markers, and verify the final file
renders correctly with consistent 0/2-space indentation for top-level and nested
unordered lists.
| weight: 10 | ||
| --- | ||
|
|
||
| The AsyncAPI Maintainership Program (AMP) is the official mentorship initiative piloted by the AsyncAPI community, designed to empower aspiring open source contributors and guide them toward becoming active code triagers and maintainers of AsyncAPI projects. Born out of AsyncAPI’s deep commitment to open source and community growth, this program creates a structured pathway for contributors to gain hands-on experience, mentorship, and long-term engagement within the ecosystem. |
There was a problem hiding this comment.
Add hyphen to compound adjective. Line 7 should read "aspiring open-source contributors" (hyphenated) rather than "open source contributors" since it's used as a compound adjective before the noun. This is a standard grammar rule.
Apply this diff:
-The AsyncAPI Maintainership Program (AMP) is the official mentorship initiative piloted by the AsyncAPI community, designed to empower aspiring open source contributors and guide them toward becoming active code triagers and maintainers of AsyncAPI projects.
+The AsyncAPI Maintainership Program (AMP) is the official mentorship initiative piloted by the AsyncAPI community, designed to empower aspiring open-source contributors and guide them toward becoming active code triagers and maintainers of AsyncAPI projects.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The AsyncAPI Maintainership Program (AMP) is the official mentorship initiative piloted by the AsyncAPI community, designed to empower aspiring open source contributors and guide them toward becoming active code triagers and maintainers of AsyncAPI projects. Born out of AsyncAPI’s deep commitment to open source and community growth, this program creates a structured pathway for contributors to gain hands-on experience, mentorship, and long-term engagement within the ecosystem. | |
| The AsyncAPI Maintainership Program (AMP) is the official mentorship initiative piloted by the AsyncAPI community, designed to empower aspiring open-source contributors and guide them toward becoming active code triagers and maintainers of AsyncAPI projects. Born out of AsyncAPI's deep commitment to open source and community growth, this program creates a structured pathway for contributors to gain hands-on experience, mentorship, and long-term engagement within the ecosystem. |
🧰 Tools
🪛 LanguageTool
[grammar] ~7-~7: Use a hyphen to join words.
Context: ...unity, designed to empower aspiring open source contributors and guide them towar...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
In markdown/docs/community/maintainership-guide/amp-overview.md around line 7,
change the phrase "aspiring open source contributors" to "aspiring open‑source
contributors" (hyphenate the compound adjective "open-source") so the compound
adjective preceding the noun is correct; update that occurrence only and keep
the rest of the sentence unchanged.
|
|
||
| 2. Click the **Actions** button | ||
|
|
||
|  |
There was a problem hiding this comment.
🧩 Analysis chain
Verify that referenced image assets exist in the repository.
The document references two image files (open-collective-action.png and open-collective-invoice.png) in the assets/ directory. Ensure these files are present at the expected paths before merging.
Also applies to: 42-42
🏁 Script executed:
#!/bin/bash
# Verify image assets exist for payment disbursement documentation
fd -e png "open-collective" markdown/docs/community/maintainership-guide/Length of output: 0
🏁 Script executed:
#!/bin/bash
# Search entire repository for open-collective PNG files
echo "=== Searching entire repo for open-collective PNG files ==="
fd -e png "open-collective"
echo ""
echo "=== Checking assets directory structure ==="
find . -type d -name assets | head -20
echo ""
echo "=== Listing PNG files in root-level assets if it exists ==="
if [ -d "assets" ]; then
ls -la assets/*.png 2>/dev/null | head -20
fi
echo ""
echo "=== Verifying markdown file location and path ==="
cat markdown/docs/community/maintainership-guide/amp-payments-disbursement.md | grep -n "open-collective"Length of output: 410
🏁 Script executed:
#!/bin/bash
# Search entire repository for open-collective PNG files
echo "=== Searching entire repo for open-collective PNG files ==="
fd -e png "open-collective"
echo ""
echo "=== Checking assets directory structure ==="
find . -type d -name assets | head -20
echo ""
echo "=== Listing PNG files in root-level assets if it exists ==="
if [ -d "assets" ]; then
ls -la assets/*.png 2>/dev/null | head -20
fi
echo ""
echo "=== Verifying markdown file location and path references ==="
cat markdown/docs/community/maintainership-guide/amp-payments-disbursement.md | grep -n "open-collective"Length of output: 421
🏁 Script executed:
#!/bin/bash
# Check markdown/assets directory
echo "=== Checking markdown/assets directory ==="
if [ -d "markdown/assets" ]; then
echo "markdown/assets EXISTS"
ls -la markdown/assets/*.png 2>/dev/null || echo "No PNG files found"
echo ""
echo "All files in markdown/assets:"
ls -la markdown/assets/
else
echo "markdown/assets DOES NOT EXIST"
fi
echo ""
echo "=== Complete list of PNG files in repository ==="
fd -e png "."Length of output: 2178
🏁 Script executed:
#!/bin/bash
# Check markdown/assets directory and all PNG files in repo
echo "=== Checking markdown/assets directory ==="
if [ -d "markdown/assets" ]; then
echo "markdown/assets EXISTS"
ls -la markdown/assets/ 2>/dev/null | grep -E "\.png$" || echo "No PNG files in markdown/assets"
else
echo "markdown/assets DOES NOT EXIST"
fi
echo ""
echo "=== All PNG files in entire repository ==="
fd -e png
echo ""
echo "=== Verify markdown file path resolution ==="
echo "File location: markdown/docs/community/maintainership-guide/amp-payments-disbursement.md"
echo "Path ../../../assets/ resolves to: markdown/assets/"Length of output: 2359
Add missing image assets to markdown/assets/ directory.
The document references two images that do not exist in the repository:
- Line 36:
open-collective-action.png - Line 42:
open-collective-invoice.png
These files must be created and placed in the markdown/assets/ directory before merging, or the image paths must be updated to reference existing assets.
🤖 Prompt for AI Agents
In markdown/docs/community/maintainership-guide/amp-payments-disbursement.md
around lines 36-42, the referenced images open-collective-action.png (line 36)
and open-collective-invoice.png (line 42) are missing; either add the two image
files with those exact names into markdown/assets/ or update the image
references in this document to point to existing assets (correct relative path)
so the links resolve. Ensure filenames and relative paths match exactly and
commit the new image files into the repository if you choose to add them.
|
|
||
| ## Ready to Get Involved? | ||
|
|
||
| **Email us:** community@asyncapi.io |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Wrap bare email URL to comply with markdown linting.
Line 57 contains a bare email address. Wrap it in angle brackets or convert to a mailto link:
-**Email us:** community@asyncapi.io
+**Email us:** <community@asyncapi.io>Alternatively, use a mailto link:
-**Email us:** community@asyncapi.io
+**Email us:** [community@asyncapi.io](mailto:community@asyncapi.io)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Email us:** community@asyncapi.io | |
| **Email us:** <community@asyncapi.io> |
| **Email us:** community@asyncapi.io | |
| **Email us:** [community@asyncapi.io](mailto:community@asyncapi.io) |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
57-57: Bare URL used
(MD034, no-bare-urls)
🤖 Prompt for AI Agents
In
markdown/docs/community/maintainership-guide/amp-sponsorship-secure-sponsorship.md
around line 57, the file contains a bare email address which violates markdown
linting; update the line to wrap the email in angle brackets (e.g.,
<community@asyncapi.io>) or replace it with an explicit mailto link (e.g.,
[community@asyncapi.io](mailto:community@asyncapi.io)) so the email is not a
bare URL and passes linting.
| - 70% of alumni go on to become maintainers, triagers, or community leads in open-source organizations. | ||
|
|
||
| - Over 50% return as mentors for programs like Google Summer of Code and contribute to growing a culture of peer-led learning. |
There was a problem hiding this comment.
Fix list indentation to meet markdown standards. Lines 19 and 21 have incorrect indentation for top-level bullet points (expected 0 spaces, actual 1 space). Align these list items to column 0.
Apply this diff:
- - 70% of alumni go on to become maintainers, triagers, or community leads in open-source organizations.
+- 70% of alumni go on to become maintainers, triagers, or community leads in open-source organizations.
- - Over 50% return as mentors for programs like Google Summer of Code and contribute to growing a culture of peer-led learning.
+- Over 50% return as mentors for programs like Google Summer of Code and contribute to growing a culture of peer-led learning.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - 70% of alumni go on to become maintainers, triagers, or community leads in open-source organizations. | |
| - Over 50% return as mentors for programs like Google Summer of Code and contribute to growing a culture of peer-led learning. | |
| - 70% of alumni go on to become maintainers, triagers, or community leads in open-source organizations. | |
| - Over 50% return as mentors for programs like Google Summer of Code and contribute to growing a culture of peer-led learning. |
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
19-19: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
21-21: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
🤖 Prompt for AI Agents
In
markdown/docs/community/maintainership-guide/amp-sponsorship-why-it-matters.md
around lines 19 to 21, the top-level bullet lines are indented with a leading
space; remove the single leading space so each top-level list item starts at
column 0. Ensure both lines are aligned with other top-level bullets (no leading
spaces) and keep the existing dash and spacing after the dash intact.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4493 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 778 778
Branches 144 144
=========================================
Hits 778 778 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/rtm |
asyncapi-bot
deleted the
update-community-docs-a5e6b1bb5dceb4f65b03e0ebfdf2b4cbc991df42
branch
Co-authored-by: asyncapi-bot <info@asyncapi.io>
commit 785c358 Author: Abhishek <abhiifour@gmail.com> Date: Fri Dec 26 18:24:01 2025 +0530 fix: horizontal scrollbar appearing in Tools flyout menu (asyncapi#4653) Co-authored-by: abhi <abhiifour@gmail.com> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> commit 6521774 Author: DuskWarden <pawar96sameer@gmail.com> Date: Fri Dec 26 12:38:06 2025 +0530 fix: remove deprecated AddThis script and styles (asyncapi#4781) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> commit a2fae36 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 25 01:45:34 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4772) commit e917b0d Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 23 14:23:54 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4719) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit ced4c27 Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 23 14:16:40 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4718) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 6676a43 Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Tue Dec 23 15:02:03 2025 +0200 chore(blog): add last summary (asyncapi#4699) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 65c10bb Author: Vishvamsinh Vaghela <90895835+vishvamsinh28@users.noreply.github.com> Date: Mon Dec 22 10:19:06 2025 +0530 feat: replace bitly urls with netlify redirect (asyncapi#4647) Co-authored-by: Vishvamsinh Vaghela <vaghelavishvamsinh11111@gmail.com> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit f604d92 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 22 01:47:53 2025 +0100 chore: update tools.json (asyncapi#4754) commit 624747e Author: DuskWarden <pawar96sameer@gmail.com> Date: Sun Dec 21 22:35:40 2025 +0530 fix: prevent background scroll when roadmap modal is open (asyncapi#4710) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 52eca18 Author: Shriya Chauhan <78415084+Shriya-Chauhan@users.noreply.github.com> Date: Sun Dec 21 21:59:40 2025 +0530 fix: fixes the failing CI/CD test in .github/workflows/if-nodejs-pr-testing.yml across all platforms (asyncapi#4735) Co-authored-by: Shriya-Chauhan <auroralflower@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 3a1ca24 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 19 01:45:53 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4742) commit 98637a0 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 17:58:38 2025 +0100 docs(community): update latest community documentation (asyncapi#4733) commit a293c4f Author: Ashmit JaiSarita Gupta <43639341+devilkiller-ag@users.noreply.github.com> Date: Thu Dec 18 18:51:08 2025 +0530 feat: updated filters dropdown and created stories for it (asyncapi#3174) Co-authored-by: devilkiller-ag <ashmitgupta.official@gmail.com> Co-authored-by: asyncapi-bot <bot+chan@asyncapi.io> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> Co-authored-by: Miles Porter <milesxporter@gmail.com> commit 1a97aff Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 10:23:59 2025 +0100 docs(community): update latest community documentation (asyncapi#4731) commit bc768aa Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 10:23:57 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4721) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 25a3892 Author: Chan <bot+chan@asyncapi.io> Date: Thu Dec 18 01:44:36 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4730) commit b927d5d Author: Chan <bot+chan@asyncapi.io> Date: Wed Dec 17 17:05:08 2025 +0100 docs(cli): update latest cli documentation (asyncapi#4728) commit 83e282a Author: Chan <bot+chan@asyncapi.io> Date: Tue Dec 16 06:03:54 2025 +0100 chore: update tools.json (asyncapi#4715) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 3c04219 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 15 18:53:51 2025 +0100 docs(community): update latest community documentation (asyncapi#4716) commit 3d2ec88 Author: DuskWarden <pawar96sameer@gmail.com> Date: Mon Dec 15 09:46:16 2025 +0530 docs: fix broken community repository links (asyncapi#4600) Co-authored-by: DuskWarden <pawar96sameer@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Chan <bot+chan@asyncapi.io> Co-authored-by: Prince Rajpoot <prince.rajpoot.20@gmail.com> commit 9c3dcd6 Author: Chan <bot+chan@asyncapi.io> Date: Sat Dec 13 01:45:08 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4707) commit eeed68c Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 12 01:45:00 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4696) commit 1e63086 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 8 01:47:51 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4695) commit f6d7df5 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 8 01:47:46 2025 +0100 chore: update tools.json (asyncapi#4692) commit 0dafc8b Author: Souryavardhan singh <144201791+Sourya07@users.noreply.github.com> Date: Sun Dec 7 17:17:33 2025 +0530 fix: ensure unique TOC slugs for repeated headings(Examples) (asyncapi#4593) Co-authored-by: Sourya07 <singhsourya137@gmail.com> Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit a056c20 Author: Varshitha Besthavemula <152318309+batchu5@users.noreply.github.com> Date: Sun Dec 7 13:47:47 2025 +0530 chore: add php, laravel and symphony in tage-color.ts (asyncapi#4667) Co-authored-by: Varshitha Besthavemula <varshithabesthavemula@gmail.com> commit a677dc6 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:52:47 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4665) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 4d06094 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:38:09 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4623) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 127ac98 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:23:49 2025 +0100 ci: update of files from global .github repo (asyncapi#4612) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 56d5d41 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:15:48 2025 +0100 docs(community): update latest maintainers list (asyncapi#4666) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 3647eaa Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 17:05:44 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4679) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 962820d Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:58:33 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4633) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 7ad740c Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:20:16 2025 +0100 docs(community): update latest maintainers list (asyncapi#4678) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 222a622 Author: Chan <bot+chan@asyncapi.io> Date: Fri Dec 5 16:06:31 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4660) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit fea45f1 Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Fri Dec 5 19:55:54 2025 +0530 chore: add Prince Rajpoot as codeowner (asyncapi#4628) commit 3fc64a4 Author: Chan <bot+chan@asyncapi.io> Date: Mon Dec 1 01:52:20 2025 +0100 chore: update tools.json (asyncapi#4654) commit 5f83885 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 30 11:11:37 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4651) commit fea633b Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 30 11:11:35 2025 +0100 docs(community): update latest maintainers list (asyncapi#4650) commit 4094d22 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 11:24:47 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4622) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit ad3d012 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 11:00:29 2025 +0100 docs(community): update latest maintainers list (asyncapi#4626) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 40b340f Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 26 09:58:18 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4637) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 0291d0b Author: Ashish Padhy <ashishpadhy1729@gmail.com> Date: Wed Nov 26 14:18:37 2025 +0530 chore(blog): publish postmortem on recent security breach (asyncapi#4640) Co-authored-by: Shurtu-gal <ashishpadhy1729@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit ddc2d87 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 25 01:41:32 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4641) commit 7accc24 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 24 01:46:56 2025 +0100 chore: update tools.json (asyncapi#4639) commit 33db13d Author: Chan <bot+chan@asyncapi.io> Date: Sat Nov 22 01:41:38 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4635) commit d39efdf Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 21 13:56:32 2025 +0100 docs(community): update latest maintainers list (asyncapi#4620) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 85ce754 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 20 01:42:28 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4630) commit d9e34fc Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Wed Nov 19 21:24:10 2025 +0530 migrate macOS version to macos-latest (asyncapi#4625) commit e63c6c3 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 08:19:29 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4610) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit d861164 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 07:42:50 2025 +0100 docs(generator): update latest generator documentation (asyncapi#4611) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 47a9d92 Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 18 01:42:54 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4618) commit 7d42caf Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon Nov 17 18:00:11 2025 +0100 chore(deps-dev): bump js-yaml from 3.14.1 to 3.14.2 (asyncapi#4616) commit f0127ac Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 17 09:19:31 2025 +0100 docs(community): update latest maintainers list (asyncapi#4606) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit dbad9ab Author: Pottabathini Vivekananda <145771776+nandu-99@users.noreply.github.com> Date: Mon Nov 17 13:22:45 2025 +0530 chore: update Slack invite link (asyncapi#4597) Co-authored-by: Pottabathini Vivekananda <vivekananda.99666@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit 14f2093 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 17 01:44:37 2025 +0100 chore: update tools.json (asyncapi#4609) commit 0e9faba Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 17:19:09 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4607) commit bd8cd1d Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 17:06:18 2025 +0100 docs(community): update latest maintainers list (asyncapi#4605) commit ace905f Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 16:55:27 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4604) commit 964b958 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 16:55:23 2025 +0100 docs(community): update latest maintainers list (asyncapi#4603) commit 085e697 Author: Anushka Sharan <111284729+anushkaaaaaaaa@users.noreply.github.com> Date: Sun Nov 16 12:52:19 2025 +0530 test: add e2e tests for docs and tools pages (asyncapi#4210) * test: add e2e tests for docs and tools pages * fix: minor fixes * test: update e2e test files * test: small changes * fix: small changes * minor change * minor chabge * feat: implement base classes in e2e tests * fix: enhance link verification methods * fix: update tools data import path in E2E tests * feat: add comprehensive tools data to toolsData.json * chore: format JSON structure in docsSections.json for consistency * chore: remove Glee section from docsSections.json * chore: update tools and docs navigation methods in HomePage class * refactor: replace verifyConceptSection with goToConceptsSection for consistency * refactor: enhance page verification methods in ToolsPage * refactor: update documentation links and headings in docsSections.json * refactor: improve link verification logic in ToolsPage * Add newline at end of meetings.json Fix missing newline at end of meetings.json file. * Fix JSON formatting in newsroom_videos.json * chore: add newline at the end of BasePageTools.js * docs: add Community Travel Funding guidelines * docs: update links to AsyncAPI tool documentation * docs: add manual tools building functionality and related tests * remve line * add line * smhtg --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> commit b9c3673 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 07:06:09 2025 +0100 chore: update tools.json (asyncapi#4562) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit fe60602 Author: Chan <bot+chan@asyncapi.io> Date: Sun Nov 16 01:45:57 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4596) commit 9a53cfa Author: DuskWarden <pawar96sameer@gmail.com> Date: Sat Nov 15 19:58:09 2025 +0530 docs: fix broken git-workflow.md links across repository (asyncapi#4585) * docs: fix broken git-workflow.md links Updated links to point to new location after community repo restructuring * revert: remove workflow file change as it is centrally managed --------- Co-authored-by: Chan <bot+chan@asyncapi.io> commit 5bfca09 Author: Chan <bot+chan@asyncapi.io> Date: Sat Nov 15 01:43:23 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4590) commit b87dd1b Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 14 01:45:37 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4584) commit 8cba652 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 13 01:44:26 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4581) commit 722963b Author: Souryavardhan singh <144201791+Sourya07@users.noreply.github.com> Date: Wed Nov 12 21:09:00 2025 +0530 docs: broken link to new-tool-documentation.md in Tools documentation (asyncapi#4542) Co-authored-by: Sourya07 <singhsourya137@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit 4d0d969 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 12 07:32:39 2025 +0100 docs(community): update latest community documentation (asyncapi#4574) commit 6aaecb1 Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 12 01:43:52 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4573) commit 406151e Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 11 01:44:03 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4568) commit be72df8 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 10 01:47:43 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4563) commit cecd342 Author: Prince Rajpoot <prince.rajpoot.20@gmail.com> Date: Sun Nov 9 13:14:15 2025 +0530 feat: enable tools view regeneration at build time (asyncapi#4511) * Add support for tools view regeneration at PR level for manual tools * minor formatting change * minor improvement * minor change * Added test cases * minor improvement * added more assertions commit 445e7c1 Author: Anushka Sharan <111284729+anushkaaaaaaaa@users.noreply.github.com> Date: Fri Nov 7 21:58:31 2025 +0530 test: add E2E tests for home page, header and footer components (asyncapi#4194) * feat: add cypress for e2e testing * feat: add cypress for e2e testing * feat: demo cypress test * feat: header e2e tests * feat: footer e2e tests * feat: add e2e tests for homepage (and other regarding pages) * test: add test for docs button * fix: minor e2e tests fixes * ci: add e2e tests workflow * fix: e2e tests fix * fix: minor fixes * ci: minor fix * fix: minor fix * fix: another fix * ci: another minor fix * fix: final fix * fix: failing test fix * test: update tests to get rid of hardcoded links * fix: replace direct Cypress commands with homePage methods * ci: minor fix * fix: minor fix * ci: minor fix * ci: update dependencies * fix: small change * test: remove files from tsconfig * feat: implement base classes for each test file * fix: small change * fix: small change * fix: changes * feat: add centralized footer data and update footer validation tests * small change in footer.cy.js * refactor: simplify visit method in BasePage class * fix: correct import path for footer data in footer tests * refactor: fix lint issues in ToolsCard and ToolsDashboard components * refactor: revert changes in ToolsCard and ToolsDashboard components * small change * small change * fix(footer): update email contact in news links --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> Co-authored-by: Rohit <108233235+TRohit20@users.noreply.github.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 167fbb9 Author: Chan <bot+chan@asyncapi.io> Date: Fri Nov 7 01:45:16 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4554) commit b5a86b7 Author: Chan <bot+chan@asyncapi.io> Date: Thu Nov 6 01:42:44 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4541) commit 4c5ecac Author: Chan <bot+chan@asyncapi.io> Date: Wed Nov 5 11:41:23 2025 +0100 docs(community): update latest community documentation (asyncapi#4539) commit 8688dc0 Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Wed Nov 5 11:22:05 2025 +0200 chore(blog): add October community summary (asyncapi#4512) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> commit b4bdd8b Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 11:38:41 2025 +0100 docs(community): update latest Board and TSC members list (asyncapi#4532) commit 11414cc Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 11:38:37 2025 +0100 docs(community): update latest maintainers list (asyncapi#4531) commit 005177e Author: Chan <bot+chan@asyncapi.io> Date: Tue Nov 4 01:42:03 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4528) commit 9611f42 Author: Chan <bot+chan@asyncapi.io> Date: Mon Nov 3 01:46:28 2025 +0100 chore: update tools.json (asyncapi#4525) commit 053e5a6 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 30 01:43:09 2025 +0100 chore: update meetings.json and newsrooom_videos.json (asyncapi#4516) commit 04921b1 Author: Lukasz Gornicki <lpgornicki@gmail.com> Date: Tue Oct 28 15:36:16 2025 +0100 chore: add content with case studies (asyncapi#4486) Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> Co-authored-by: Ansh Goyal <anshgoyal1704@gmail.com> commit 6287929 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 10:52:50 2025 +0100 docs(cli): update latest cli documentation (asyncapi#4510) commit e398ae7 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 09:39:38 2025 +0100 ci: update LICENSE and NOTICE files from global .github repo (asyncapi#4509) commit 4788d4b Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 27 01:45:31 2025 +0100 chore: update tools.json (asyncapi#4508) commit d3c31cc Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 24 13:07:33 2025 +0200 docs(cli): update latest cli documentation (asyncapi#4504) commit a57da1f Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 24 02:40:29 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4502) commit 304d2ae Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 22 02:42:59 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4497) commit 6c974fc Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 21 13:26:10 2025 +0200 docs(community): update latest community documentation (asyncapi#4493) Co-authored-by: asyncapi-bot <info@asyncapi.io> commit b1787a0 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 21 02:41:49 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4492) commit 5733a74 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 20 02:45:33 2025 +0200 chore: update tools.json (asyncapi#4490) commit 841a1d3 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 17 06:12:55 2025 +0200 ci: update of files from global .github repo (asyncapi#4475) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit db754f6 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 17 02:41:45 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4487) commit 9de49c1 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 16 02:41:23 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4483) commit 6757477 Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 15 10:07:12 2025 +0200 docs(community): update latest tsc members list (asyncapi#4479) commit 568740e Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 15 02:42:05 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4477) commit f33b0de Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 16:34:12 2025 +0200 docs(community): update latest Board and TSC members list (asyncapi#4472) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 6a18edf Author: Sarthak Karode <sarthakkarodework@gmail.com> Date: Tue Oct 14 19:57:20 2025 +0530 docs: remove glee folder and update introduction-to-glee-a-spec-first-framework.md (asyncapi#4358) Co-authored-by: sarthakKarode <sarthakkarode@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> commit b215375 Author: Zbigniew Malcherczyk <zmalcherczyk@gmail.com> Date: Tue Oct 14 14:29:44 2025 +0200 chore(blog): add TransferGo <> AsyncAPI Blog Post (asyncapi#4434) Co-authored-by: Ferror <zmalcherczyk@gmail.com> Co-authored-by: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 7480244 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 14:18:15 2025 +0200 docs(community): update latest community documentation (asyncapi#4474) commit 7058fd5 Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 09:40:10 2025 +0200 docs(community): update latest maintainers list (asyncapi#4471) commit e18da3b Author: Chan <bot+chan@asyncapi.io> Date: Tue Oct 14 08:42:29 2025 +0200 docs(community): update latest maintainers list (asyncapi#4470) commit ac7e38b Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 18:04:36 2025 +0200 docs(community): update latest Board members list (asyncapi#4469) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 1e3e8e8 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 14:51:16 2025 +0200 docs(community): update latest tsc members list (asyncapi#4468) commit 8560539 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 13 02:43:38 2025 +0200 chore: update tools.json (asyncapi#4467) commit 4fd7abd Author: Chan <bot+chan@asyncapi.io> Date: Sun Oct 12 02:42:39 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4465) commit 19e3c34 Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 10 18:11:58 2025 +0200 docs(community): update latest community documentation (asyncapi#4462) commit 4b2284c Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 10 02:42:27 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4461) commit 7affdb1 Author: Pastukhov Nikita <diementros@yandex.ru> Date: Fri Oct 10 02:45:03 2025 +0300 docs: fix FastStream tools dead links (asyncapi#4458) * docs: update FastStream tools link * docs: update FastStream tools links * chore: remove empty line * Update tools.json * Update tools-manual.json --------- Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit 55d08d5 Author: Chan <bot+chan@asyncapi.io> Date: Mon Oct 6 02:41:28 2025 +0200 chore: update tools.json (asyncapi#4459) commit 3b4454f Author: V Thulisile Sibanda <66913810+thulieblack@users.noreply.github.com> Date: Fri Oct 3 11:45:21 2025 +0200 chore(blog): add the september summary (asyncapi#4438) Co-authored-by: thulieblack <sibanda.thulie@gmail.com> commit 2e4022c Author: Chan <bot+chan@asyncapi.io> Date: Fri Oct 3 02:39:43 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4449) commit bfda003 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 2 17:10:30 2025 +0200 docs(community): update latest community documentation (asyncapi#4444) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit dc85424 Author: Fran Méndez <fmvilas@gmail.com> Date: Thu Oct 2 16:43:56 2025 +0200 chore: replace press email with info email address (asyncapi#4443) Co-authored-by: Fran Méndez <fmvilas@gmail.com> Co-authored-by: Sambhav Gupta <81870866+sambhavgupta0705@users.noreply.github.com> commit 75cd925 Author: Chan <bot+chan@asyncapi.io> Date: Thu Oct 2 02:42:15 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4442) commit 960a6b5 Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 1 21:38:20 2025 +0200 chore: update meetings.json, newsrooom_videos.json and dashboard.json (asyncapi#4426) Co-authored-by: asyncapi-bot <info@asyncapi.io> Co-authored-by: Eve <bot+eve@asyncapi.io> commit 4234dda Author: Chan <bot+chan@asyncapi.io> Date: Wed Oct 1 02:46:05 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4441) commit d4a1175 Author: Chan <bot+chan@asyncapi.io> Date: Tue Sep 30 02:43:19 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4440) commit 231498d Author: Chan <bot+chan@asyncapi.io> Date: Mon Sep 29 02:42:47 2025 +0200 chore: update tools.json (asyncapi#4439) commit 42eac67 Author: Chan <bot+chan@asyncapi.io> Date: Sun Sep 28 02:43:54 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4437) commit 0be788f Author: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Date: Fri Sep 26 21:58:26 2025 +0200 chore(deps): bump tar-fs (asyncapi#4436) commit c19543b Author: Chan <bot+chan@asyncapi.io> Date: Fri Sep 26 02:39:08 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4435) commit 9a8c037 Author: Chan <bot+chan@asyncapi.io> Date: Thu Sep 25 12:54:38 2025 +0200 docs(community): update latest community documentation (asyncapi#4432) commit 54b7241 Author: Zbigniew Malcherczyk <zmalcherczyk@gmail.com> Date: Thu Sep 25 09:55:27 2025 +0200 chore: initial TransferGo CaseStudy (asyncapi#4409) Co-authored-by: Ferror <zmalcherczyk@gmail.com> Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com> commit 78769a8 Author: Chan <bot+chan@asyncapi.io> Date: Wed Sep 24 02:40:34 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4431) commit 1ac8db4 Author: Chan <bot+chan@asyncapi.io> Date: Tue Sep 23 02:40:29 2025 +0200 chore: update meetings.json and newsrooom_videos.json (asyncapi#4430) commit 9791f0d Author: Chan <bot+chan@asyncapi.io> Date: Mon Sep 22 02:43:56 2025 +0200 chore: update tools.json (asyncapi#4429)
Updated community documentation is available and this PR introduces update to community folder on the website
Summary by CodeRabbit
Release Notes