[BOUNTY] Set of issues for resolution under the Bounty Program 2024-Q4

[aeworxet]

This is an Aggregated Bounty Issue consisting of GitHub issues

• [BUG] Intermittent 403 RequestError in build-dashboard.js script #2894
• [BUG] tweetLimit in community/newsroom isn't been reflected #3132
• [BUG] Responsiveness issue on the View on Github button  #3008

that are subject to resolution in the Bounty Program's calendar quarter round 2024-Q4.

This particular Aggregated Bounty Issue was created out of #2894 with appended GitHub issues, for the sake of accounting simplification.

@sambhavgupta0705 @akshatnema
@asyncapi/bounty_team

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[aeworxet]

All Bounty Program information has been transferred from #2894.

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/advanced, bounty/coding, bounty/upgraded
First assignment to regular contributors: 2024-09-20 00:00:00 UTC+12:00
End Of Life after: 2024-10-31 23:59:59 UTC-12:00

@asyncapi/bounty_team

The Bounty Program is not a Mentorship Program. The accepted level of Bounty Program Participants is Middle/Senior.

Regular contributors should explain in meaningful words how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

[aeworxet]

@akshatnema is an AsyncAPI Maintainer specified in https://raw.githubusercontent.com/asyncapi/community/master/MAINTAINERS.yaml, so they fall under the first category in the prioritization list.

[aeworxet]

Bounty Issue's Timeline

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
Advanced	2024-09-19	2024-10-07	2024-12-01	2024-10-27	2024-11-17	2024-12-01

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

Keep in mind the responsibility for violations of the Timeline.

[omarsoufiane]

hi@aeworxet , you can create a bounty on Bountyhub, it's integrated into github, (a bot will comment to let other people know that there is a bounty) and if no one solves your bounty you can retract it and get your money back, it's a simple process where you import issues by pasting the issue URL and the payment is upfront so that developers attempting to solve the issue know that the amount is already available.

[aeworxet]

@omarsoufiane
Thank you for your suggestion, but this is a Bounty Issue of the internal self-contained AsyncAPI's Bounty Program, and it is not meant to be published on external resources.

[akshatnema]

@aeworxet Everything is done in this issue. Can you please mark it as done?

[aeworxet]

@akshatnema
The original Bounty Issue #2894 was submitted by @sambhavgupta0705. Did he submit it on your behalf?

[akshatnema]

@aeworxet Yeah, he submitted on my behalf.

[aeworxet]

Bounty Issue Is Completed 🎉

@akshatnema (githubID 76521428), please go to the AsyncAPI page on Open Collective and submit an invoice for USD 400.00 with the expense title Bounty website#3247, tag bounty, and full URL of this Bounty Issue in the description.

[aeworxet]

@akshatnema

In the future, please submit GitHub issues for participation in the Bounty Program using your own account to maintain a clear chain of responsibility.