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

Perfect workflow for notifying triagers #3214

Open
sambhavgupta0705 opened this issue Sep 11, 2024 · 8 comments
Open

Perfect workflow for notifying triagers #3214

sambhavgupta0705 opened this issue Sep 11, 2024 · 8 comments
Assignees
Labels
bounty AsyncAPI Bounty program related label enhancement

Comments

@sambhavgupta0705
Copy link
Member

sambhavgupta0705 commented Sep 11, 2024

Why do we need this improvement?

Currently the workflow for notifying triage maintainers of code and doc is not working properly for which we need to setup a perfect workflow to notify triage maintainers

How will this change help?

It will help us in maintaining the code review architecture in a better way

How could it be implemented/designed?

Need to setup a workflow for this

@JeelRajodiya
Copy link
Contributor

JeelRajodiya commented Sep 12, 2024

Hello, I looked up the logs of the notify-triager workflow. Is this error relevant to the issue? or we have some other issue with the workflow?

@sambhavgupta0705
Copy link
Member Author

need to look into it

@asyncapi-bot asyncapi-bot added the bounty AsyncAPI Bounty program related label label Sep 16, 2024
@aeworxet
Copy link
Contributor

Bounty Issue's service comment

Text labels: bounty/2024-Q4, bounty/medium, bounty/coding
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.

@aialok
Copy link

aialok commented Sep 16, 2024

Hi team,

I would like to take on this issue. I have good experience with GitHub Actions from my GSoC work, where I built the CI/CD pipeline for the JSON Schema website.

Thank you! : )

@Gmin2
Copy link

Gmin2 commented Sep 16, 2024

Hi @anshgoyalevil , i would like to take this up

@sambhavgupta0705
Copy link
Member Author

@aeworxet I would like to work on this issue under bounty program

@aeworxet
Copy link
Contributor

@sambhavgupta0705 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
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-09-17 2024-10-07 2024-11-17 2024-10-20 2024-11-03 2024-11-17
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty AsyncAPI Bounty program related label enhancement
Projects
Status: In Progress
Development

No branches or pull requests

6 participants