| 目录 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
To quickly learn about OpenFDE, please click here. Quick Start
2. Sign in CLA
Before participating in community contributions, you are required to sign the OpenFDE Contributor License Agreement (CLA). Depending on your role, you can choose to sign the Individual CLA, Employee CLA, or Corporate CLA. Please click in here.
...
set up the development environment for OpenFDE
If you want to contribute to coding development and prepare the development environment for OpenFDE, please refer to development environment preparation Quick Building
get codes and pull branches
If you want to contribute code, it is important to understand how to download code from Gitee and merge code through pull requests. OpenFDE utilizes the Gitee code hosting platform. For detailed instructions, please refer to Gitee Workflow Guide.
The usage of Gitee is similar to GitHub. If you have prior experience with GitHub, you can have a general understanding of the content in this section and even skip it if you wish.
modify, build, and locally verificate
After making modifications on the local branch, proceed with building and locally verifying the changes. Please refer to Building Software Packages for detailed instructions.
submit a pull-request
When you submit a PR, it means that you have started contributing code to the community. Please refer to OpenFDE Community PR Submission Guidelines for more information.
3.2.3 contribute a software package
...
OpenFDE supports automatically creating a corresponding repository on the OpenFDE in Gitee when a new software package is added on Gitee. This allows for automatic code compilation checks when submitting code to the created Gitee repository. For the specific process, please refer to How to Add a New Software Package.
3.2.4 contribute an original open-source project
...
To develop in other communities and integrate it into OpenFDE, you simply need to follow How to Add a New Software Package and add the software to the OpenFDE repository.
...
For reviewers, it is strongly recommended to abide by the Code Codes of Conduct, go beyond self-interest, respect each other, and promote collaboration. The focus of the review can be referred to as Gentle Art of Patch Review. During the review, you can focus on the following aspects:
...
Testing is the responsibility of all contributors. For detailed guidelines, please refer to Community Developer Testing Contribution GuidePlease refer to the detailed guide for more information(to be updated and supplemented with [Testing Contribution Guidelines]).
3.2.7 documentation contribution
You can contribute your technical articles to this community by following Blog Contribution GuidePages provided by OpenFDE.
3.2.8 selecting community components for packaging
You can also participate in packaging community components. Please refer to How to Package for more information.
3.2.9 community security issue disclosure
...
Security Incident Response Process--briefly describe the process of handling security issues.
...
The packaging tutorial is pending an update.