-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Welcome to contribute #20804
Comments
@ichn-hu is this challenge still effective, can we close this issue? |
I think as for the the challenge, it is not effective, but as a guide for our community contributors, this issue is still valuable (as a pinned issue, they would notice it once they entered the issue page). I could rename the issue to Welcome to contribute and modify the content a little bit to instruct the contributors to pick any bugs that has not yet being assigned to get start. |
As a first time contributor how found this challenge a few weeks ago I just want to agree with what @ichn-hu is saying. This issue with the title "welcome to contribute" was what triggered me to have a deeper look into your project and send in my first PR's. |
Thank you very much for the feedback! And also your PR! |
@ichn-hu sure, but the challenge program has finished, the issue description needs to be clarified. |
@zz-jason sure, the title and content is updated, and the challenge column is removed. |
type/enhancement |
@ichn-hu given we have a good first issue label now, shall we close this issue? https://github.com/pingcap/tidb/contribute From my experience this issue and the bot provides false positive from time to time. That is, already assigned issues or complex issues are listed. |
If you are interested in database development, or you are a TiDB user, no matter what, if you want to contribute to TiDB and learn about how a distributed HTAP database worked, here is the right place.
Let's get started by solving some bugs! Here is a curated list of some easy-to-go bugs, pick the one that you want to smash!
Note: currently the issues are classified by their SIG owners, such as sig/planner and sig/execution, which stands for special interests groups that focus on SQL planning and SQL execution, to know more about TiDB community, see the community repository. We also host discussions on slack, if you are not in the corresponding slack channel, we highly recommend you to join so that you could ask questions and get responses immediately from these SIGs members. Join TiDB Community slack workspace now!
If there is a ❗ before the issue link, it means there is no one assigned, nor a PR linked, nor picked, and it is for the maintainers to track the progress of each issue, it is also a notation of "welcome to take a look".
Feel free to comment on issues that interest you, and ask whatever questions you have on how to get started working on them!
sig/planner
@xuyifangreeneyes
@rebelice
@rebelice
@mjonss
@qw4990
sig/execution
@XuHuaiyu
#27006
#27403
sig/transaction
@crazycs520
sig/DDL
updated at 2021-08-20T03:15:10-00:00
The text was updated successfully, but these errors were encountered: