LTS

    Innovation Version

      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:

        FieldDescriptionMandatory
        nameSIG name, which is related to the software package domain.
        descriptionDescription of the SIG.
        mailing_listSubscribed email addresses of the SIG×
        meeting_urlSIG meeting link×
        maintainersManager of the SIG, responsible for review and merging of PRs of the SIG repositories.
        repositoriesSIG repositories
        committersCommitters of SIG repositories are responsible for review and merging of PRs of the corresponding repositories.

        Fields in nginx.yaml:

        FieldDescriptionMandatory
        namePackage name (repository name)
        descriptionSoftware package description
        upstreamUpstream repository address of software package
        branchesRepository branches
      2. Add source code files.

        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.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份