docs(bounty): change Bounty Program schedule to monthly#2192
Conversation
aeworxet
requested review from
asyncapi-bot-eve,
bandantonio,
derberg and
thulieblack
as code owners
WalkthroughReworks the AsyncAPI Bounty Program from a quarter-based model to a month-based model for 2026 onward: monthly budgeting, per-month issue quotas (4–8), updated submission windows, labeling, randomization, suspension/renewal, timelines, and related wording and links. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Suggested labels
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (4)
25-39: Budget restructuring is clear and mathematically sound.The transition from quarterly (USD 20,000) to monthly (USD 21,400 annual) allocation is well-documented with explicit monthly and annual figures. Per-month budget (USD 1,600) and coordination costs (USD 150/month) are clearly itemized. ✓
However, note that line 39 has a compound adjective spacing issue per static analysis. Consider:
- - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transfers: USD 400.00 for all payouts per twelve calendar month rounds (approximate; the exact commission per transfer depends on the method chosen and the beneficiary's location and cannot be precisely calculated in advance). + - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transfers: USD 400.00 for all payouts per twelve calendar month rounds (approximate; the exact commission per transfer depends on the method chosen and the beneficiary's location and cannot be precisely calculated in advance).
73-103: Submission window and labeling updated consistently for monthly cadence.The shift from quarterly to monthly submission windows (now "second full calendar week of the month") is clearly articulated. Type-based labels (
bounty/coding,bounty/devops,bounty/docs,bounty/design) properly supplement the complexity and period labels. The label formatbounty/2026-03is unambiguous for month tracking. ✓Minor style suggestion: Lines 88–90 have three successive "In case" sentence beginnings. Per static analysis, consider rewording one to reduce repetition:
In case documentation must be provided together with the solution requested in the Bounty Issue, such requirement should be explicitly stated in the Scope. In case two Bounty Issues are inextricably linked and cannot be completed separately from each other, such connection must be explicitly stated in the Scope. - In case the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round of the Bounty Program, a full list of submitted Bounty Issues undergoes randomization using the randomization service provided by [random.org](https://random.org). + When the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round of the Bounty Program, a full list of submitted Bounty Issues undergoes randomization using the randomization service provided by [random.org](https://random.org).
181-195: End-of-Life rules properly restructured for monthly period boundaries.Lines 181–195 successfully translate quarterly End Of Life logic to monthly cycles: EOL occurs "after the last second of the last day of the calendar month round" with consistent historical labels (
bounty/unpicked,bounty/dropped,bounty/misperformed,bounty/canceled,bounty/eol). ✓Minor terminology note: Line 195 uses "can not" (two words). Per style guidelines, this should be:
- A dropped Bounty Issue can not be assigned again to the same Bounty Program Participant who dropped it in the next calendar month rounds of the Bounty Program. + A dropped Bounty Issue cannot be assigned again to the same Bounty Program Participant who dropped it in the next calendar month rounds of the Bounty Program.
139-139: Minor formatting and URL issues flagged by static analysis.Three issues to resolve:
Line 139: Tense consistency — "silently dropped" should align with other descriptions if this is describing a general state. Current text reads: "it is assumed that the task cannot be completed within the rest of the time, and that the Bounty Program Participant has silently dropped the Bounty Issue." This appears correct as stated (past tense for a completed action).
Lines 269–270 (bare URLs): Static analysis flags bare URLs in the Sources section. Wrap them in angle brackets or markdown link syntax for linter compliance:
- ##### https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246 - ##### https://github.com/asyncapi/community/issues/2163 + ##### [https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246](https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246) + ##### [https://github.com/asyncapi/community/issues/2163](https://github.com/asyncapi/community/issues/2163)
- Line 33: Spaces inside emphasis markers. The expression
(4 * 400)and(8 * 200)appear unaffected in the provided code, but verify no emphasis markers have internal spaces in the rendered markdown.Also applies to: 269-270
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md(8 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
[uncategorized] ~39-~39: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ds). - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transf...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~88-~88: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...uld be explicitly stated in the Scope. In case two Bounty Issues are inextricably...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~90-~90: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ust be explicitly stated in the Scope. In case the total reward for all submitted...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~195-~195: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ...ssue Candidate. A dropped Bounty Issue can not be assigned again to the same Bounty Pr...
(CAN_NOT_PREMIUM)
🪛 markdownlint-cli2 (0.18.1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
269-269: Bare URL used
(MD034, no-bare-urls)
270-270: Bare URL used
(MD034, no-bare-urls)
⏰ 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: preview
🔇 Additional comments (2)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (2)
113-151: Timeline rules updated for monthly cycles; example dates remain historical context.The shift from quarterly "first Monday of the new calendar quarter" to monthly "first Monday of the new calendar month round" is clear and consistent. Relative week-based timelines (Draft PR by week 2/3, Final PR by week 4/6 or 6/8) scale well to any month length. ✓
Note: The timeline example (lines 148–151) uses 2024 dates. These appear to be illustrative historical examples rather than forward-looking guidance. If they serve as documentation reference, no action is needed; if they are meant to reflect 2026+ timelines, consider updating them for clarity.
242-254: Suspension periods redefined for monthly cadence; logic is sound.Suspension windows are now properly anchored to calendar month boundaries:
- First Suspension: 2 months from the beginning of the next calendar month
- Second Suspension: 8 months from the beginning of the next calendar month
- Cleanup window: 6 months after First Suspension expires
The three scenarios (single issue dropped, one of two dropped, both issues dropped/misperformed simultaneously) are clearly delineated. ✓
|
🚀 Docs preview deployed |
aeworxet
force-pushed
the
docs-bounty-change-bounty-program-schedule-to-monthly
branch
from
f112db5 to
603bf56
Compare
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (3)
23-40: Verify budget implementation aligns with 2026 start date across all related systems.The budget structure is mathematically sound (USD 1,600/month × 12 + USD 150/month × 12 + USD 400 commission = USD 21,400). However, ensure that Open Collective project pages, coordination workflows, and label automation are ready for the January 2026 monthly cadence start. The reference to "Bounty Program 2025" in line 217 should also be updated if this goes live before 2026.
87-93: Consider varying sentence structure to reduce repetition.Three successive sentences begin with "In case," which impacts readability. Consider restructuring to improve flow—for example, using transitional phrases or combining related conditions.
Current:
In case documentation must be provided together with the solution requested in the Bounty Issue, such requirement should be explicitly stated in the Scope. In case two Bounty Issues are inextricably linked and cannot be completed separately from each other, such connection must be explicitly stated in the Scope. In case the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round of the Bounty Program...Example refactor:
Documentation requirements should be explicitly stated in the Scope if they must accompany the solution. For inextricably linked Bounty Issues that cannot be completed separately, their connection must be explicitly stated in the Scope. When the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round of the Bounty Program...
269-270: Wrap bare URLs in brackets for Markdown compliance.Lines 269–270 contain bare URLs. Wrap them in brackets to align with Markdown best practices (MD034).
Apply this diff:
-##### https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246 -##### https://github.com/asyncapi/community/issues/2163 +##### [https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246](https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246) +##### [https://github.com/asyncapi/community/issues/2163](https://github.com/asyncapi/community/issues/2163)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md(8 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
[uncategorized] ~39-~39: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ds). - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transf...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~88-~88: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...uld be explicitly stated in the Scope. In case two Bounty Issues are inextricably...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~90-~90: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ust be explicitly stated in the Scope. In case the total reward for all submitted...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🪛 markdownlint-cli2 (0.18.1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
269-269: Bare URL used
(MD034, no-bare-urls)
270-270: Bare URL used
(MD034, no-bare-urls)
⏰ 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). (2)
- GitHub Check: Test NodeJS PR - windows-latest
- GitHub Check: preview
🔇 Additional comments (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (1)
217-217: Update Open Collective project reference if this documentation is published before 2026.Line 217 references "Bounty Program 2025" page. If this documentation is deployed in 2025, consider whether to temporarily maintain the 2025 page or create/update a 2026 page. This affects where bounty participants will submit expenses.
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (5)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (5)
35-39: Add hyphen to compound adjective.Line 39: "fund transfer commission" should be hyphenated as "fund-transfer commission" when modifying the following noun. This is a formatting improvement per English grammar rules.
- Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transfer: USD 400.00 for all payouts per twelve calendar month rounds (approximate; the exact commission per transfer depends on the method chosen and the beneficiary's location and cannot be precisely calculated in advance). + Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund-transfer: USD 400.00 for all payouts per twelve calendar month rounds (approximate; the exact commission per transfer depends on the method chosen and the beneficiary's location and cannot be precisely calculated in advance).
88-88: Consider varying sentence structure for stylistic improvement.Multiple consecutive sentences begin with "In case" (lines 88, 90). While acceptable in a formal specification, rewording some of these for variety would improve readability.
Example rewrite:
- In case two Bounty Issues are inextricably linked and cannot be completed separately from each other, such connection must be explicitly stated in the Scope. + Inextricably linked Bounty Issues that cannot be completed separately must have this connection explicitly stated in the Scope. - In case the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round of the Bounty Program, a full list of submitted Bounty Issues undergoes randomization using the randomization service provided by [random.org](https://random.org). + When the total reward for all submitted Bounty Issues exceeds the budget allocated for the upcoming calendar month round, a randomization process using [random.org](https://random.org) is applied to the full list of submitted issues.Also applies to: 90-90
113-113: Consider updating timeline example dates to reflect 2026 effective date.While the timeline logic is correctly updated and the mathematical calculations are sound, the example dates (lines 146-151) reference June–August 2024, predating the 2026 effective date of this monthly model. Updating these to 2026 or using a neutral "Year X" notation would improve clarity and reduce potential confusion.
|Complexity Level|Assignment Date (by GitHub)|Start Date (by BP Rules)|End Date (by BP Rules)|Draft PR Submission|Final PR Merge Start|Final PR Merge End| |----------------|---------------------------|------------------------|----------------------|-------------------|--------------------|------------------| - |Medium |2024-06-21 |2024-07-01 |**2024-08-11** |2024-07-14 |2024-07-28 |**2024-08-11** | - |Advanced |2024-06-25 |2024-07-01 |**2024-08-25** |2024-07-21 |2024-08-11 |**2024-08-25** | + |Medium |2026-01-21 |2026-02-01 |**2026-03-15** |2026-02-14 |2026-02-28 |**2026-03-15** | + |Advanced |2026-01-25 |2026-02-01 |**2026-03-29** |2026-02-21 |2026-03-15 |**2026-03-29** |Also applies to: 146-151
269-270: Wrap bare URLs in angle brackets for markdown lint compliance.Lines 269–270 contain bare URLs that violate markdown lint rule MD034. Wrap them in angle brackets to comply.
- ##### https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246 - ##### https://github.com/asyncapi/community/issues/2163 + ##### <https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246> + ##### <https://github.com/asyncapi/community/issues/2163>
33-33: Remove spaces inside emphasis markers.Line 33 has spaces inside emphasis markers around the parenthetical math expressions. This violates markdown lint rule MD037. Remove or restructure to eliminate the space.
- The approximate maximum number of Bounty Issues per calendar month round ranges from four to eight (from (4 * 400) to (8 * 200)). + The approximate maximum number of Bounty Issues per calendar month round ranges from four to eight (from 4 * 400 to 8 * 200).Alternatively, if parentheses are needed within the range notation:
- The approximate maximum number of Bounty Issues per calendar month round ranges from four to eight (from (4 * 400) to (8 * 200)). + The approximate maximum number of Bounty Issues per calendar month round ranges from four to eight (4 × 400 to 8 × 200).
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md(9 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
[uncategorized] ~39-~39: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ds). - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transf...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~88-~88: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...uld be explicitly stated in the Scope. In case two Bounty Issues are inextricably...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~90-~90: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ust be explicitly stated in the Scope. In case the total reward for all submitted...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🪛 markdownlint-cli2 (0.18.1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
269-269: Bare URL used
(MD034, no-bare-urls)
270-270: Bare URL used
(MD034, no-bare-urls)
⏰ 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: preview
🔇 Additional comments (3)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (3)
73-93: Submission window and randomization logic successfully updated to monthly cadence.The changes to submission timing ("second full (seven-day) calendar week of the month"), randomization thresholds, and exclusion rules are clear and consistent with the new monthly model. The label format
bounty/2026-03is appropriate for month-based tracking.
181-195: End of Life section correctly transitioned to monthly cadence.References to "calendar month round" are consistent throughout. The rules for unlabeled, dropped, misperformed, and canceled statuses are preserved. Note that dropped issues now face monthly reassignment restrictions (vs. quarterly before), which is more stringent but aligns with the increased cadence.
254-254: Suspension reset timing is clear and consistent.The reset rule ("six calendar months from the beginning of the next calendar month after the expiration of the First Suspension") is appropriately defined and aligns with the two-month suspension window. This provides a clear boundary for status cleanup.
thulieblack
left a comment
thulieblack
left a comment
There was a problem hiding this comment.
I think we should remove the rounds/round wording throughout the doc to improve clarity, since we are now doing it monthly.
Aside, all looks good!
|
Mention of They may also be stretched and not necessarily overlap in any meaningful way with calendar months or with each other. Most importantly: the tracked units within the informational structure The explicit statement of |
|
I understand, but in terms of context, clarity, and improving readability, I suggest maybe saying |
aeworxet
force-pushed
the
docs-bounty-change-bounty-program-schedule-to-monthly
branch
from
524016f to
b3f24e8
Compare
|
Modified |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (1)
269-270: Consider wrapping bare URLs in angle brackets for markdown consistency.Lines 269–270 contain bare URLs. Wrapping them in angle brackets (e.g.,
<https://github.com/...>) aligns with markdown best practices and enables proper link rendering in some contexts.🔎 Apply formatting to URLs:
- ##### https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246 - ##### https://github.com/asyncapi/community/issues/2163 + ##### <https://github.com/asyncapi/community/issues/2085#issuecomment-3407063246> + ##### <https://github.com/asyncapi/community/issues/2163>
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md(9 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: aeworxet
Repo: asyncapi/community PR: 2192
File: docs/010-contribution-guidelines/BOUNTY_PROGRAM.md:242-250
Timestamp: 2025-12-16T12:48:45.635Z
Learning: In the AsyncAPI Bounty Program documentation (docs/010-contribution-guidelines/BOUNTY_PROGRAM.md), suspension condition logic should not be modified as part of PRs that only change the schedule from quarterly to monthly, as suspension conditions have their own independent logic.
📚 Learning: 2025-12-16T12:48:40.652Z
Learnt from: aeworxet
Repo: asyncapi/community PR: 2192
File: docs/010-contribution-guidelines/BOUNTY_PROGRAM.md:242-250
Timestamp: 2025-12-16T12:48:40.652Z
Learning: In docs/010-contribution-guidelines/BOUNTY_PROGRAM.md, do not modify the suspension condition logic as part of pull requests that only change the schedule from quarterly to monthly. Suspension conditions have their own independent logic and should be updated only with changes that specifically address those conditions.
Applied to files:
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
🪛 LanguageTool
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
[uncategorized] ~39-~39: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ds). - Open Collective's Fiscal Host, 'Open Source Collective,' commission for fund transf...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~88-~88: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...uld be explicitly stated in the Scope. In case two Bounty Issues are inextricably...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~90-~90: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ust be explicitly stated in the Scope. In case the total reward for all submitted...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🪛 markdownlint-cli2 (0.18.1)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
33-33: Spaces inside emphasis markers
(MD037, no-space-in-emphasis)
269-269: Bare URL used
(MD034, no-bare-urls)
270-270: Bare URL used
(MD034, no-bare-urls)
⏰ 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: preview
🔇 Additional comments (6)
docs/010-contribution-guidelines/BOUNTY_PROGRAM.md (6)
25-39: Budget restructuring is mathematically sound and properly maintains monthly consistency.The annual USD 21,400 allocation breaks down correctly: USD 1,600/month (issue rewards, USD 19,200/year) + USD 150/month (coordination, USD 1,800/year) + USD 400 (fiscal commission) = USD 21,400/year. The monthly framing appropriately replaces the previous quarterly model.
73-73: Submission and randomization sections consistently updated to monthly cadence.References to quarters have been systematically replaced with "calendar-month round" throughout. The randomization logic (lines 91–93) retains the same prioritization and budget-ceiling mechanism, with only the time unit updated from quarterly to monthly.
Also applies to: 85-85, 91-93
99-99: Month-based label format is clear and supports automation.The label format
bounty/2026-03uses standard YYYY-MM convention, enabling straightforward filtering and sorting by calendar month.
113-113: Month-boundary rule for timeline start dates is well-defined.The provision that assignments in weeks 3–4 of a month trigger start dates on the first Monday of the next calendar-month round ensures predictable timeline commencement across month boundaries.
181-181: End-of-Life rules correctly transition to monthly cadence.The definition (line 181) uses precise language ("last second of the last day... inclusive") to avoid ambiguity. Lines 193 and 195 correctly update label assignment and reassignment restrictions to the monthly model. The logic structure is preserved from the quarterly version.
Also applies to: 193-193, 195-195
242-250: Suspension timeline periods appropriately updated to monthly cadence.The suspension rules have been updated to reference calendar months in place of quarters. The timing structure (First Suspension: 2 months; Second Suspension: 8 months; post-suspension reset: 6 months) maintains the intended disciplinary escalation and cooling-off periods.
Note: The inconsistency in phrasing around "starting from the current moment" (present in lines 242, 244, 250 but absent in lines 246, 248) was identified in the prior review and is out-of-scope per the learnings for this quarterly-to-monthly conversion PR.
Also applies to: 254-254
|
/rtm |
aeworxet
deleted the
docs-bounty-change-bounty-program-schedule-to-monthly
branch
|
@CosmicJesterX, would you like to be blocked from the AsyncAPI GitHub Organization for posting random, senseless comments in random issues? |
|
@CosmicJesterX (
@asyncapi/code_of_conduct, please assess this situation and take action if required. 
|
|
@CosmicJesterX was blocked for spamming, which is against our Code of Conduct at AsyncAPI. |
5 participants
This PR implements the proposal, approved by the TSC vote, to achieve the Community Goal 2026.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.