Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bounty] A bunch of bugs that can be completed through the Bounty program #1012

Closed
2 tasks done
smoya opened this issue Jun 11, 2024 · 17 comments
Closed
2 tasks done
Assignees
Labels
bounty AsyncAPI Bounty

Comments

@smoya
Copy link
Member

smoya commented Jun 11, 2024

Describe the bug

The completion of all of the following bugs can be considered as completing a single Bounty Program issue of medium complexity level :

@aeworxet
Copy link
Contributor

I would like to work on this issue within the Bounty Program.

@smoya smoya transferred this issue from asyncapi/spec Jun 12, 2024
@smoya
Copy link
Member Author

smoya commented Jun 17, 2024

I would like to work on this issue within the Bounty Program.

A pleasure. Assigned to you @aeworxet

@asyncapi-bot asyncapi-bot added the bounty AsyncAPI Bounty label Jun 17, 2024
@aeworxet
Copy link
Contributor

Bounty Issue's service comment

Text labels: bounty/2024-Q3, bounty/medium, bounty/coding
First assignment to third-party contributors: 2024-06-21 00:00:00 UTC+12:00
End Of Life after: 2024-07-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.
Third-party contributors should coherently articulate how they are going to approach the resolution process when expressing a desire to work on this Bounty Issue.

@aeworxet
Copy link
Contributor

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
Medium 2024-06-17 2024-07-01 2024-08-11 2024-07-14 2024-07-28 2024-08-11
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.

@asyncapi-bot
Copy link
Contributor

@ramishj is not authorized to use the Bounty Program's commands.
These commands can only be used by members of the Bounty Team.

@aeworxet
Copy link
Contributor

No PRs have been submitted yet; a code investigation is ongoing.

#980 (comment)

#936 (comment)

@aeworxet
Copy link
Contributor

To lay the foundation for fixing #980, PR stoplightio/spectral#2658 was submitted to https://github.com/stoplightio/spectral, so the Timeline of this Bounty Issue is frozen until that PR is merged.

@aeworxet
Copy link
Contributor

PR stoplightio/spectral#2658 was merged in one day, so the Timeline of this Bounty Issue is resumed from the same point.

@aeworxet
Copy link
Contributor

AsyncAPI Maintainer (@jonaslagoni) delayed response for one period of three consequent working days
#936 (comment)
#936 (comment)
so all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.

Bounty Issue's Timeline Extended

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-17 2024-07-01 2024-08-25 2024-07-14 2024-08-11 2024-08-25
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.

@aeworxet
Copy link
Contributor

@aeworxet
Copy link
Contributor

aeworxet commented Aug 6, 2024

@aeworxet
Copy link
Contributor

PR asyncapi/studio#1126 with the final fix of #936 for Studio was submitted on 2024-08-05 and is still waiting for a review.

@aeworxet
Copy link
Contributor

Response, critical for technical resolution of this Bounty Issue (review of the PR) was delayed for one period of three consecutive working days
asyncapi/studio#1126 (comment)
asyncapi/studio#1126 (review)

so all remaining target dates of the Bounty Issue's Timeline are extended by two calendar weeks.

Bounty Issue's Timeline Extended

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-17 2024-07-01 2024-09-08 2024-07-14 2024-08-25 2024-09-08
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.

@aeworxet
Copy link
Contributor

The last PR for this Bounty Issue was merged on 2024-08-14, and since that time I'm waiting for confirmation of the technical resolution of this Bounty Issue.

@smoya
Copy link
Member Author

smoya commented Aug 28, 2024

I confirm the issue is solved now.

@aeworxet
Copy link
Contributor

Bounty Issue Is Completed 🎉

@aeworxet, please go to the AsyncAPI page on Open Collective and submit an invoice for USD 200.00 with the expense title Bounty parser-js#1012, tag bounty, and full URL of this Bounty Issue in the description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty AsyncAPI Bounty
Projects
Status: Completed
Development

No branches or pull requests

3 participants