Co-construction and Future of oepkgs

Contribution as an Individual

1. Submit a PR to create a repository.

   Submit a PR in the oepkgs-management repository and fill in two configuration files. After the PR is merged, the repository creation robot ci-robot automatically creates a repository under src-oepkgs.

   NOTE:

   • The oepkgs repository classifies software packages by domain and category. Software packages of different domains and categories are maintained by different SIGs.
   • Open source software can be introduced to an existing SIG of oepkgs by submitting a PR and modifying the sig-info.yaml file of the SIG. It is not mandatory to create a SIG when a software package is introduced.

   For example, if Nginx is to be introduced, the configuration files in the oepkgs-management repository would be sig-info.yaml and nginx.yaml.

   Fields in sig-info.yaml:

   Field	Description	Mandatory
   name	SIG name, which is related to the software package domain.	√
   description	Description of the SIG.	√
   mailing_list	Subscribed email addresses of the SIG	×
   meeting_url	SIG meeting link	×
   maintainers	Manager of the SIG, responsible for review and merging of PRs of the SIG repositories.	√
   repositories	SIG repositories	√
   committers	Committers of SIG repositories are responsible for review and merging of PRs of the corresponding repositories.	√

   Fields in nginx.yaml:

   Field	Description	Mandatory
   name	Package name (repository name)	√
   description	Software package description	√
   upstream	Upstream repository address of software package	√
   branches	Repository branches	√

2. Add source code files.

   • After step 1 is complete, the https://gitee.com/src-oepkgs/nginx repository is generated within 5 minutes. Add source code files to the repository through PRs. The source code files include nginx.spec that can be used to build RPM packages and nginx-2.12.0.tar.bz2. For details, see https://gitee.com/src-oepkgs/nginx.

   NOTE:

   • After a PR is submitted, the PR quality gate build test will be performed within 5 to 30 minutes. The test result will be submitted as a comment under the PR. It is recommended that the PR be merged after Build_Result is displayed as SUCCESS.
   • The maintainer specified in the oepkgs-management/sig/virtual/sig-info.yaml configuration file can merge the PR by commenting /lgtm and /approve under the PR.

3. Build the software package.

   oepkgs provides a mature CI/CD system to support software package source code building, binary scanning, and basic function verification, ensuring reliable quality and continuous evolution of the software repository.

Future plan

Services for more users and developers

• More services will be opened to users and developers for wider participation, promoting the improvement of the oepkgs service.

Software package patch management

• A software package patch management system has been planned to enhance the display of binary package security hardening information. The query platform uses software package patch management to provide more comprehensive binary package information.

Continuous construction

• The openEuler expansion repository will be continuously developed to include more software. oepkgs works with the official openEuler repository to promote the development of the openEuler ecosystem.