Contribute a Linyaps application: the original packaging and submission workflow

On this page

Join linyaps-packaging SIG to participate in Linyaps application contributions and become a core contributor to the Linyaps community

Ruyi Linglong (Linyaps) is a new independent package management toolset that focuses on solving compatibility issues caused by the complexity and cross-dependencies of traditional software package formats under Linux systems. The project uses advanced isolation technology to completely decouple applications from systems, fundamentally solve application compatibility issues caused by environmental changes, and achieve "one architecture, one build". It is committed to simplifying the software development process, reducing maintenance costs, strengthening data security, promoting collaboration between technology and platforms, and building a more prosperous, secure and efficient Linux software ecological environment.

We have officially established a special interest group focused on enriching the Linyaps application ecosystem ( linyaps-packaging SIG ), is committed to building and adapting Linyaps format package applications, and continues to optimize the software construction and distribution process to promote the development of the Linux ecosystem. We sincerely invite you to join the ecosystem collaboration SIG group- linyaps-packaging SIG：1、 Group Charter Portal 2、 Group Activity Repository >>>

Group Goals:

Enrich Linyaps application ecosystem, including packaging, construction and distribution.
Promote software packaging standardization, improve cross-platform compatibility, and improve developer packaging efficiency.
Work together to solve and optimize technical problems in the software packaging process.
Communicate and share packaging tools and practical tutorials to promote knowledge dissemination.

How to participate in Linyaps application contribution:

01

Sign community CLA
02

Configure Linyaps environment
03

Application build export
04

Application submission
05

Application Distribution

1. Sign Community CLA (Contributor License Agreement)

Sign the open source community contributor agreement to ensure that your contribution to the community is legal and valid.

Individual Contributor License Agreement >>>

Legal Person Contributor License Agreement >>>

2. Configure Linyaps environment

Obtain the Linyaps environment, refer to the documentation: Install Linyaps | Linyaps

3. Export project configuration file (.yaml) /Linyaps format application (.layer)

Solution 1, semi-automatic conversion: ll-pica

Reference documentation: ll-pica Introduction | Linyaps

First step, Prepare files to be converted

Support type: 1) deb 2）Appimage 3）Flatpak (coming soon)

Document source: 1) Local files 2) Obtain via the Internet

The second step, Enter basic build parameters/commands

View tutorial: Pica conversion tool tutorial & adep module application examples

The third step, get pica Conversion Exported Project configuration file (.yaml) or finished Linyaps format application

Option 2. Highly customizable build: ll-builder

Reference documentation: Introduction to ll-builder | Linyaps

First step, Choosing the right build type

1) Online Git repository pull and compile

2) Local source code compilation

3) Local binary executable file

The second step, Manually write the build project configuration file (.yaml)

Configuration content includes but is not limited to: Application name, version number, package name/id, configuration runtime, build rules

The third step, Execute the build process and export the Linyaps application , complete the test yourself

4. Application submission

Solution 1. Project configuration file submission - submit and automatically build through the automated public build platform

Passed Automated public build platform Submit as PR, After creating PR, you will Trigger OBS build

CICD Workflow

Create a repository Create a new repository based on the PR submission
Set up OBS webhook and add OBS webhook to the new repository created.
Trigger OBS build after creating PR. Trigger OBS build Linyaps application through webhook.
Reply to the download address of the layer below the PR. After the build is successful, you can see the built layer file in the download address.
Modify the linglong.yaml version field to automatically publish tags. Automatically publish tags after merging PRs that modify the version field. The tag number is consistent with version.
Check multiple linglong.yaml files to keep the version consistent. When building PR, check that the version number of multiple linglong.yaml files in multiple architectures must be consistent.
Trigger OBS build after publishing tag. Trigger OBS to build Linyaps application through webhook.
After the tag is built, push the layer to the repository. After the OBS build is completed, the publish script is triggered. The publish script pushes the layer to the online repository.

Option 2. Submission of finished product package - Submit the successfully constructed Linyaps package through the UnionTech Developer Platform

Finished package (. layer ) can be passed UnionTech Developer Platform Delivery

5. Application Distribution

After completing the above steps, the submitted software package will be automatically pushed to the following stores for distribution after being reviewed and approved by the SIG repository administrator and merged into the PR or after completion of the UnionTech App Store shelf test:

Linyaps application store web version （ No restriction on distribution, online distribution ）

Linyaps App Store Client ( No restriction on distribution version, independent client ）

UnionTech App Store UOS and deepin official distribution channel

Note: Linyaps app store is Linyaps Simple Store SIG An independent project maintained, welcome to participate.

Junior Contributor

New members should start studying the adaptation documents and use the adaptation tools. Able to complete simple adaptation tasks independently 。

Key contributions and requirements

The contributor account must be responsible for maintaining at least 1 Linyaps application on the shelf (maintained through GitHub automated construction platform or UnionTech developer platform account, ensuring the availability of the application and keeping the software updated)
If you submit a web page package application through the community quick packaging activity, you need to have at least ≥5 applications under your personal account to obtain the Junior Contributor title and certificate

Responsibility and authority

Response assigned issue and PR
Update and maintain package versions
Create and maintain new software packages
Issues or PRs can be assigned
Becoming a senior contributor can obtain a contribution certification certificate issued by the community

Intermediate Contributor

Have certain experience in software adaptation and be able to handle adaptation problems of medium complexity.

Key contributions and requirements

The contributor account name must be at least responsible for maintenance 10 There are Linyaps applications on the shelf (maintained through GitHub automated construction platform or UnionTech developer platform account, the availability of the application must be ensured, and the software must be kept updated). Source code construction or conversion using ll-pica is encouraged, but pure web page packaging applications will not be counted.

Responsibility and authority

Response assigned issue and PR
Update and maintain package versions
Create and maintain new software packages
Issues or PRs can be assigned
Becoming a senior contributor can obtain a contribution certification certificate issued by the community

Senior ecological contributor Senior Contributor

has rich adaptation experience, can solve complex adaptation problems, and has in-depth understanding and contribution to adaptation strategies and technologies.

Key contributions and requirements

The contributor account name must be at least responsible for maintenance 30 There are Linyaps applications on the shelf (maintained through GitHub automated construction platform or UnionTech developer platform account, the availability of the application must be ensured, and the software must be kept updated). Source code construction or conversion using ll-pica is encouraged, but pure web page packaging applications will not be counted.

Responsibility and authority

Response assigned issue and PR
Update and maintain package versions
Create and maintain new software packages
Issues or PRs can be assigned
Becoming a senior contributor can obtain a contribution certification certificate issued by the community

Reviewer (Committer)

Reviewer ( Committer ) can be audited at SIG events Contributor The submitted code ensures the quality of the PR. The reviewers generally have a good understanding of Linux software engineering principles.

Key contributions and requirements

reached Intermediate Contributor requirements, and Serve as a primary reviewer at least Received 10 code submissions or software reviews
Able to independently review the quality of PR software code, control the quality of merged and submitted software packages, and guide SIG members in ecological adaptation work
Familiar with SIG repository code and able to Write and maintain adaptation scripts, participate in adaptation process optimization, and improve adaptation quality
Can be self-nominated, or nominated by a reviewer or maintainer of this SIG, and approved with a 2/3 vote

Responsibility and authority

Review PR submitted by Contributor
Track, discover, distribute and fix various problems in software packages, distribute and handle issues
Develop test specifications and provide basic test cases for testing regression
Can participate in various public activities of the community as a core contributor
Participate in SIG meetings and jointly develop SIG development plans

Project maintainer (Maintainer)

Project maintainer ( Maintainer ） is the leader of the SIG group or a member of the management committee and can review and approve like a committer Code contributions.

Has the responsibility and authority of all Committers, and is responsible for the team's technical route, internal and external coordination, etc.

Key contributions and requirements

As a reviewer At least 3 months and participated as the main reviewer for at least 30 code submissions or software releases
Ability to design and implement complex adaptation solutions to improve the quality of group work
Be able to participate in the development of building adaptation tools (ll-pica/ll-builder) to a certain extent
Guide SIG members, lead SIG members to grow, deeply participate in the community, and promote the ecological development of Linyaps
Can be self-nominated or nominated by another Maintainer without objection from other Maintainers

Responsibility and authority

Convene SIG meetings regularly and make relevant decisions
Participate in community PM activities and coordinate milestone timeline matching of SIG plans and community releases
Participate as a SIG representative e.g. Italian Linyaps Community Technical Committee or Council Organization Events and specific meetings, etc.
Nominate new core members

Linyaps community contributor certificate:

Based on the SIG contribution growth description, we will issue the corresponding level of "Linyaps Community Contributor Certificate" to developers who contribute every month;

Among them, Junior Contributor (junior ecological contributor) will only issue electronic certificates, and the remaining four levels of contributors will be issued the highest level physical certificate at the end of the year.