| <?xml version="1.0" encoding="utf-8" standalone="yes"?> |
| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> |
| <channel> |
| <title>ShardingSphere</title> |
| <link>https://shardingsphere.apache.org/community/en/</link> |
| <description>Recent content on ShardingSphere</description> |
| <generator>Hugo -- gohugo.io</generator> |
| <language>en-us</language> |
| |
| <atom:link href="https://shardingsphere.apache.org/community/en/index.xml" rel="self" type="application/rss+xml" /> |
| |
| |
| <item> |
| <title>Subscribe Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/subscribe/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/subscribe/</guid> |
| <description>When using or contributing to ShardingSphere, if you encounter any problem, or you have any suggestions or new ideas, you can use the Apache mailing-list to participate in the community building, or join the ShardingSphere Slack channel to connect with other community members. |
| To join the mailing list: |
| Send an e-mail to subscribe. Use your mailbox to send an e-mail to dev-subscribe@shardingsphere.apache.org with any subject or content. |
| Receive and reply the confirmation e-mail.</description> |
| </item> |
| |
| <item> |
| <title>How to Set Up Your DEV Environment</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/establish-project/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/establish-project/</guid> |
| <description>Git Installation Use the latest version. |
| You could download Git from Git Downloads. |
| If you&rsquo;re running macOS or Linux, you could install Git from software repository. |
| Git Settings If you&rsquo;re running Windows, following settings should be done before cloning ShardingSphere code. |
| Execute following command in PowerShell or cmd to prevent from filename too long error on cloning ShardingSphere code: |
| git config --global core.longpaths true JDK Installation Use JDK8+. |
| You could download JDK from OpenJDK Downloads.</description> |
| </item> |
| |
| <item> |
| <title>Contributor Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/contributor/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/contributor/</guid> |
| <description>You can report a bug, submit a new function enhancement suggestion, or submit a pull request directly. |
| Submit an Issue Before submitting an issue, please go through a comprehensive search to make sure the problem cannot be solved just by searching. Check the Issue List to make sure the problem is not repeated. Create a new issue and choose the type of issue. Define the issue with a clear and descriptive title.</description> |
| </item> |
| |
| <item> |
| <title>Committer Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/committer/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/committer/</guid> |
| <description>Committer Promotion The ShardingSphere community follows the Apache Community’s process on accepting a new committer. After a contributor participates ShardingSphere community actively, PMC and Committers will make a decision to invite the contributor to join Committers and PMC. |
| Committer Responsibilities Develop new features; Refactor codes; Review pull requests reliably and in time; Consider and accept feature requests; Answer questions; Update documentation and example; Improve processes and tools; Check whether CI Scheduled Workflow works or not periodically; Guide new contributors join community.</description> |
| </item> |
| |
| <item> |
| <title>Code of Conduct</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/code-conduct/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/code-conduct/</guid> |
| <description>The following code of conduct is based on full compliance with ASF CODE OF CONDUCT. |
| Development Guidelines Write codes with heart. Pursue clean, simplified and extremely elegant codes. Agree with concepts in &lt;Refactoring: Improving the Design of Existing Code&gt; and &lt;Clean Code: A Handbook of Agile Software Craftsmanship&gt;. Be familiar with codes already had, to keep consistent with the style and use. Highly reusable, no duplicated codes or configurations. Delete codes out of use in time.</description> |
| </item> |
| |
| <item> |
| <title>Document Specification</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/document-conduct/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/document-conduct/</guid> |
| <description>Each topic does not need to write a title. GitHub supports the automatic generation of titles. Each table shall be arranged in strict accordance with the table style so that follow-up personnel can see clearly and take over. The end of the period of a paragraph should be wrapped, otherwise a paragraph will be too long. Leave a blank line at the end of each topic. There should be a blank line before the title in each topic.</description> |
| </item> |
| |
| <item> |
| <title>Issue Conduct</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/issue-conduct/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/issue-conduct/</guid> |
| <description>Issue Submit Conduct Issue lists should be readable and retrievable. The author is obligated to summarize the title that is meaningful and convenient for retrieval, and to ensure the correctness and completeness of the content; Please confirm that there is no relevant existing Issue after sufficient search, and then submit a new Issue; The type of issue is divided into bug, new feature and problem. When you edit an issue, please select the correct template and fill in content according to the template; For problems caused by uncertain configuration, please submit the relevant reproducible code to Github, so that community contributors can locate and identify the problem more efficiently; Please reply to the Issue after it has been resolved to form a closed loop that will provide effective information for others who browse the Issue; Please pay attention to the submitted issues in time.</description> |
| </item> |
| |
| <item> |
| <title>Documents Contributor Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/document-contributor/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/document-contributor/</guid> |
| <description>If you want to help contribute shardingsphere documents or websites, we are happy to help you! Anyone can contribute, whether you&rsquo;re new to a project or have been using shardingsphere for a long time, whether you&rsquo;re a self identified developer, end-user, or someone who can&rsquo;t stand typos,can contribute to documents or websites. In the contributor guide, we have mentioned how to submit Issues and pull request. here we will introduce how to submit pull request to document.</description> |
| </item> |
| |
| <item> |
| <title>ShardingSphere Release Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/release/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/release/</guid> |
| <description>Prepare before release procedure 1. Confirm release notes The release note should be provided in Chinese / English, confirm whether the Chinese description is clear and whether the English translation is accurate, and shall be classified according to the following labels: |
| New Feature API Change Enhancement Refactor Bug Fix 2. Confirm issue list Open GitHub issues, filter the issue whose milestone is ${RELEASE.VERSION} and status is open: |
| Close the completed issue For outstanding issues, communicate with the developer in charge.</description> |
| </item> |
| |
| <item> |
| <title>ElasticJob Release Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/release-elasticjob/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/release-elasticjob/</guid> |
| <description>Preparation GPG Setup Please refer to Release Guide. |
| Setting settings.xml Add the following template to ~/.m2/settings.xml, all the passwords need to be filled in after encryption. For encryption settings, please see here. |
| &lt;settings&gt; &lt;servers&gt; &lt;server&gt; &lt;id&gt;apache.snapshots.https&lt;/id&gt; &lt;username&gt; &lt;!-- APACHE LDAP username --&gt; &lt;/username&gt; &lt;password&gt; &lt;!-- APACHE LDAP encrypted password --&gt; &lt;/password&gt; &lt;/server&gt; &lt;server&gt; &lt;id&gt;apache.releases.https&lt;/id&gt; &lt;username&gt; &lt;!-- APACHE LDAP username --&gt; &lt;/username&gt; &lt;password&gt; &lt;!-- APACHE LDAP encrypted password --&gt; &lt;/password&gt; &lt;/server&gt; &lt;/servers&gt; &lt;/settings&gt; Publishing Apache Snapshot Deploying to Apache Snapshot Repository 1.</description> |
| </item> |
| |
| <item> |
| <title>ElasticJob-UI Release Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/release-elasticjob-ui/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/release-elasticjob-ui/</guid> |
| <description>GPG Settings Please refer to Release Guide. |
| Apache Maven Central Repository Release 1. Set settings.xml |
| Add the following template to ~/.m2/settings.xml, all the passwords need to be filled in after encryption. For encryption settings, please see here. |
| &lt;settings&gt; &lt;servers&gt; &lt;server&gt; &lt;id&gt;apache.snapshots.https&lt;/id&gt; &lt;username&gt; &lt;!-- APACHE LDAP username --&gt; &lt;/username&gt; &lt;password&gt; &lt;!-- APACHE LDAP encrypted password --&gt; &lt;/password&gt; &lt;/server&gt; &lt;server&gt; &lt;id&gt;apache.releases.https&lt;/id&gt; &lt;username&gt; &lt;!-- APACHE LDAP username --&gt; &lt;/username&gt; &lt;password&gt; &lt;!-- APACHE LDAP encrypted password --&gt; &lt;/password&gt; &lt;/server&gt; &lt;/servers&gt; &lt;/settings&gt; 2.</description> |
| </item> |
| |
| <item> |
| <title>2FA</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/2fa/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/2fa/</guid> |
| <description>Two-factor authentication(2FA) Two factor authentication (2FA) refers to the authentication method that combines both passport, and an object (credit card, SMS phone, token or biomarkers as fingerprint) to identify a user. To ensure the security of the committer’s account, we need you to enable 2FA to sign in and contribute codes on GitHub. |
| More details, please refer to 2FA. |
| To be noticed: If you do not enable 2FA, you will be removed from the project and unable to access our repositories and the fork from our private repository.</description> |
| </item> |
| |
| <item> |
| <title>Sign ICLA Guide</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/icla/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/icla/</guid> |
| <description>Sign Apache ICLA guide Apache CLA short for Apache Contributor License Agreement, the purpose of this agreement is to clearly define the terms under which intellectual property has been contributed to the ASF and thereby allow us to defend the project should there be a legal dispute regarding the software at some future time. A signed ICLA is required to be on file before an individual is given commit rights to any ASF project.</description> |
| </item> |
| |
| <item> |
| <title>New committer voting process</title> |
| <link>https://shardingsphere.apache.org/community/en/contribute/vote/</link> |
| <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate> |
| |
| <guid>https://shardingsphere.apache.org/community/en/contribute/vote/</guid> |
| <description>Voting process of becoming a new committer 1. Start the discussion and vote in @private. Only current PMC member could nominate. |
| Example： To：private@shardingsphere.apache.org Title： [VOTE] New committer:(nominee) Content： Hi, everyone This is ^a formal vote^ about inviting (nominee)as our new committer. He/She really made an effort to improve ShardingSphere Parser and fix many issues. The following links will direct you to his/her work. https://github.com/apache/shardingsphere/pull/6319 https://github.com/apache/shardingsphere/pull/6293 https://github.com/apache/shardingsphere/pull/6259 https://github.com/apache/shardingsphere/pull/6211 [^ means these words are subject to change in different case] 2.</description> |
| </item> |
| |
| </channel> |
| </rss> |
