[Improvement][community] Add bot to congrats user first contribution

[zhongjiajie]

Describe the question

I think we should add some bot to encourage and congrats user first contribution.
"Community Over Code", one of Apache way, besides some IM software(slack, wechat) we should also add a bot for congrating user first contribution, encourage user further contribution.

For example, we have PR #6109

[github-actions]

Hi:

• Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/zh-cn/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.

[ruanwenjun]

Right now, after a new user's first contribution has been merged, the community will contact him and congrats he. I think DolphinScheduler community is doing well to encourage new user in the past.

Adding bot can reduce the community work, but I actually don't want to see bot messages, if I am a new user.

[CalvinKirs]

Agree with wenjun, we prefer the PR merger to do this, the community needs to maintain these contributors to achieve the purpose of motivating them to actively contribute, for me, the bot's words do not seem to have any emotional color, I will not be patient to read through what it says.

[Narcasserun]

+1

[cxin-william]

+1

[zhongjiajie]

I got the point and I don't have strong opinion here. But if manually do that rather than by bot, should we add some doc in such as committer to describe committer "duties" here?

[CalvinKirs]

I got the point and I don't have strong opinion here. But if manually do that rather than by bot, should we add some doc in such as committer to describe committer "duties" here?

That's a good suggestion.

[zhongjiajie]

I would create PR and add some docs to describe it this week.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.