When working on Apache ShardingSphere projects, have you ever been confused by these questions:

  • Interested in the project, but not sure what you can contribute to it
  • Among many issues, I cannot find an issue task suitable for myself to participate in
  • Think that the threshold to participate in open source projects is high, and are not confident in their own ability

In order to make it easier for more developers to understand and participate in this project, Gitee X Apache ShardingSphere launched 11 Issues, covering 6 Good First issues suitable for beginners and 5 medium difficulty issues. Complete the issue and take home a nice gift!

Active process

Participation in issue resolution: May 27 – June 30

Best/Best Contributor selection: July 1-2

Results announcement + prize distribution: July 5th

Participate in the way

  • Select one or more Issue tasks in the New/Other Issue area and complete it.
  • After completing the issue description requirements, submit the Pull Request in the warehouse where the issue belongs, copy the issue ID to the PR description, and submit it for review (note: Please note [Gitee 8th Anniversary Event]) Fork + PullRequest help document when submitting PR
  • Submit in the comments section of the activity page: Issue number + submitted

The novice area issue

Serial number type Issue description Issue link
1 Code refactoring Refactor the For loop using Lambda expressions Check the details
2 Documentation of new Added the shardingSphere-Proxy configuration change history document Check the details
3 Code refactoring Remove the enumeration TransactionOperationType for Proxy Check the details
4 Document to optimize Complete document adjustment of shardingSphere-JDBC Spring namespace configuration change history according to requirements Check the details
5 Document to optimize Adjust the ShardingSphere-JDBC Spring Boot Starter configuration change history documents based on the requirements Check the details
6 Document to optimize Complete document optimization of ShardingSphere-JDBC Java API change history according to requirements Check the details

The other issue

Serial number type Issue description Issue link
7 The new configuration Provide a queryWithCipherColumn configuration for each table Check the details
8 Code logic optimization The check logic of the target class verifies that the table to be deleted has a reference in BindingTableRules and throws a reasonable exception if there is a reference Check the details
9 Document to optimize Migrate the API change history to a unified directory for easy search. Content proofreading, check the correctness of the change history in each mode, and supplement the incomplete content. Check the details
10 Code optimization PG Prepare statement parsing code optimized Check the details
11 Document to optimize Adjust the document level in the Others directory by referring to the optimization of the API configuration change history document. Check the details

See more projects to participate in >>

Activities to reward

🎖 All partners who submit PR and pass the review can get a Gitee open source theme sticker + camera cover sticker.

🎖 The maintainer of this project will award the “best contributor” among the partners who participate in issue solving during the activity, and reward a JD shopping card of 500 yuan.

🎖 The maintainer of this project will evaluate the “outstanding contributors” among the partners who participate in issue solving during the activity and award a Gitee gift package.

About the Apache ShardingSphere

ShardingSphere, with the characteristics of “platforming, pluggable, cloud native”, is an ideal solution for large-scale data applications and data value-added applications.

Project address: gitee.com/Sharding-Sp…