compliance

Open-source software has been used in various industries, and the compliance issue of open-source software development and use has been paid more attention. Based on the lifecycle and use scope of open source software, open source compliance is classified into license compliance, copyright compliance, patent compliance, export control compliance, GDPR compliance, bussiness secret compliance, and trademark compliance. The SIG focuses on compliance research and provides the research results to the community for open source compliance management through tools.

License Compliance Background Introduction

OpenEuler is an open source OS community and uses the Mulan V2 license. Multiple downstream commercial companies have developed commercial releases based on OpenEuler. OpenEuler integrates tens of thousands of open source projects of the upstream open source community, which use various licenses. Check whether the OpenEuler Mulan V2 license is incompatible with the open source license of these upstream projects. wether the license is incompatible or not, a series of rules and tools are required to resolve the incompatibility issue. For example:

• Resolve the file-level license problem. Example: PHP
• The problem of determining the license of the newly introduced component is resolved.
• Resolved the problem that the license of the upstream component changes. Example: mangoDB and ES
• Resolved the problem that the license of the spec file in the RPM package is inconsistent with that of the native community. Example: greenlet

License & Copyright Compliance Introduction

Generally, the public regard the open source code as something "free"(referring to freedom, not price) to use. Here the word "free" does not mean you can use it anyway you want, but under the regulations of its license. Then:

• What is a license?
• Why the open source code author has the right to assign a license to regulate its users?
• What is license & copyright compliance about for open source development?

This chapter will give some explanations:

1. understanding copyright and license
2. license and copyright compliance
3. FAQ
4. terms and abbreviations

Export Control Compliance Introduction

We hope that the SIG can develop rules that meet the community, build the rules into processes, implement these rules through tools and engineering methods, and provide solutions or services to organizations and individuals participating in the community.

Goal

1. Sort out business issues.
2. Gain insights into industry benchmark communities, standards, rules, and methodologies.
3. Release license-related rules.
4. Design the business architecture
5. Design the software architecture.
6. Software development

Contribution

1. Fork the repository
2. Create Feat_xxx branch
3. Commit your code
4. Create Pull Request

Gitee Feature

1. You can use Readme_XXX.md to support different languages, such as Readme_en.md, Readme_zh.md
2. Gitee blog blog.gitee.com
3. Explore open source project https://gitee.com/explore
4. The most valuable open source project GVP
5. The manual of Gitee https://gitee.com/help
6. The most popular members https://gitee.com/gitee-stars/

SIG operation

• Conference agenda Reporting Address
• Summary of Past Meetings
• Previous conference materials
• screen address