# Code Contribution<a name="EN-US_TOPIC_0000001055088095"></a>

## Start Contributions<a name="en-us_topic_0000001051566732_section123657169441"></a>

### Design Specifications

-   [OpenHarmony API Governance Charter](../design/OpenHarmony-API-governance.md)

-   [OpenHarmony Security Design Specifications](OpenHarmony-security-design-guide.md)

### Code Style

Develop, review, and test code following the OpenHarmony coding standards. Make sure code is written in the same style.

-   [C++ Coding Style Guide](OpenHarmony-cpp-coding-style-guide.md)
-   [C Coding Style Guide](OpenHarmony-c-coding-style-guide.md)
-   [JavaScript Coding Style Guide](OpenHarmony-JavaScript-coding-style-guide.md) 
-   [Python Coding Style Guide](https://pep8.org/)
-   [C&C++ Secure Coding Guide](OpenHarmony-c-cpp-secure-coding-guide.md)
-   [Java Secure Coding Guide](OpenHarmony-Java-secure-coding-guide.md)
-   [Logging Guide](OpenHarmony-Log-guide.md)

## Contribution Workflow<a name="en-us_topic_0000001051566732_section15769105812369"></a>

For details, see  [Contribution Process](contribution-process.md).

## Security Issue Disclosure<a name="en-us_topic_0000001051566732_section725624119448"></a>

-   [Security Issue Handling and Release Processes](https://gitee.com/openharmony/security/blob/master/en/security-process/README.md)

-   [OpenHarmony Security and Disclosure Statement](https://gitee.com/openharmony/security/blob/master/en/security-process/security-disclosure.md)