|
7 | 7 |
|
8 | 8 | IvorySQL grows through contributions from developers, testers, documentation writers, translators, community advocates, and users around the world. This guide will help you understand how to participate in the IvorySQL community, from getting started to making in-depth contributions. |
9 | 9 |
|
10 | | -== Ways to Contribute |
11 | | - |
12 | | -The IvorySQL community believes that open source should be approachable and that no contribution is too small. You can participate in a way that matches your background and interests: |
13 | | - |
14 | | -* *Code contributions*: kernel development, feature iteration, bug fixes, plugin development, ecosystem tool adaptation, regression tests, and code review. |
15 | | -* *Non-code contributions*: issue reports, documentation improvements, technical translation, community Q&A, online or offline talks, case studies, migration experience sharing, and community promotion. |
16 | | - |
17 | | -If you are not ready to submit code yet, you can still make a meaningful contribution by reproducing issues, clarifying requirements, improving docs, or helping other users in community discussions. |
18 | | - |
19 | | -== Community Collaboration Process |
20 | | - |
21 | | -The IvorySQL community employs a closed-loop open-source collaboration process, ensuring that every step—from issue submission to version release—receives closed feedback and continuous improvement. This process encourages良性互动 between users and developers, allowing community development to evolve around actual needs. |
22 | | - |
23 | | -The entire closed-loop collaboration process is as follows: |
24 | | - |
25 | | -🐛 *Submit Issue* |
26 | | - |
27 | | -Users or developers submit bugs, feature suggestions, or usage feedback on the GitHub Issues page. |
28 | | - |
29 | | -💬 *Discussion* |
30 | | - |
31 | | -Maintainers and community members discuss the issue, confirm its nature and priority, and add it to the ToDo List. |
32 | | - |
33 | | -🛠️ *Development Branch (Fork & Dev)* |
34 | | - |
35 | | -Developers claim the Issue, fork the repository, develop and test locally, and prepare to submit code. |
36 | | - |
37 | | -🚀 *Submit Pull Request (PR)* |
38 | | - |
39 | | -Push the development branch to the forked repository and initiate a merge request to the upstream repository. |
40 | | - |
41 | | -🧐 *Code Review* |
42 | | - |
43 | | -Maintainers or core developers review the PR, provide modification suggestions, and ensure quality. |
44 | | - |
45 | | -🔀 *Merge to Main Branch* |
46 | | - |
47 | | -After approval, the PR is merged into the main branch, and the corresponding Issue is closed. |
48 | | - |
49 | | -📦 *Release* |
50 | | - |
51 | | -The project regularly releases new versions (minor versions quarterly, major versions annually), including the latest fixes and features. |
52 | | - |
53 | | -🧪 *User Testing* |
54 | | - |
55 | | -Users upgrade to the new version, provide feedback on new issues, and new Issues are generated, forming a complete feedback loop. |
56 | | - |
57 | | -image::p23.jpg[] |
58 | | - |
59 | | -Through this complete closed-loop collaboration mechanism, IvorySQL achieves full-process closure of issue response → development contribution → quality assurance → release feedback, promoting the continuous healthy evolution of the project. |
60 | | - |
61 | | -📢 Please read and abide by our https://github.com/IvorySQL/IvorySQL/blob/master/CODE_OF_CONDUCT_CN.md[IvorySQL Community Code of Conduct]. |
62 | | - |
63 | 10 | == Roles and Responsibilities |
64 | 11 |
|
65 | 12 | Before contributing, please confirm your current participation role to more efficiently understand the contribution methods suitable for you: |
|
0 commit comments