moshengren
Gitee
|
|
@ -0,0 +1,298 @@
|
|||
---
|
||||
title: openKylin download address and installation method
|
||||
description.
|
||||
published: true
|
||||
date: 2022-08-01T02:46:12.687Z
|
||||
tags.
|
||||
editor: markdown
|
||||
dateCreated: 2022-05-17T07:44:04.711Z
|
||||
---
|
||||
|
||||
This article describes in detail the two platforms (Windows, Linux) boot disk production methods and three (full installation, dual system, virtual machine) openKylin open source operating system installation tutorial, please read according to their needs selectively.
|
||||
|
||||
The first step to install and use openKylin open source operating system is to get the openKylin open source operating system image file, which we can download directly from the openKylin official website.
|
||||
|
||||
Download link: https://www.openKylin.top/downloads
|
||||
|
||||
# I. Make a boot disk
|
||||
|
||||
In the process of reinstalling or installing a system, we all go through the process of making a boot disk, and I'm sure we've read a lot of information to learn. Then by me to give you a summary of the boot disk production several methods. Welcome to take notes.
|
||||
|
||||
Boot disk creation tools, of which the common ones are Ventoy and Micro PE Toolbox, are similar in what they do.
|
||||
|
||||
First of all, they can both be used to create a boot disk, the main function is the same, but Micro PE Toolbox can also create a system CD, Ventoy can not do, in addition, Micro PE Toolbox can also set PE personalized icons, wallpapers and other personalized content.
|
||||
|
||||
Ventoy's function is relatively simple, it is mainly used to create system disks, no complicated functions, so its size is also relatively small, if you want to carry around, Ventoy will be more suitable.
|
||||
|
||||
In constant experimentation, I got Ventoy to implement all the features of the microPE toolkit! So let's install openkylin with the boot disk creation tool fixed to Ventoy!
|
||||
|
||||
First download the boot disk creation tool - ventoy. ventoy is different from other boot disk creation tools, we do not need to repeatedly format the U disk, just copy the image file to the U disk to boot normally, and can allow multiple image files to exist at the same time. ventoy will display a menu for us to choose when booting, very convenient and fast.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Download link: https://www.lanzoui.com/b01bd54gb or https://www.ventoy.net/cn/download.html
|
||||
|
||||
## 1. Windows system usage details
|
||||
Insert the U disk and wait for the download to finish, after the download is done, unzip it, go to the unzip directory, double click to run Ventoy2Disk.exe.
|
||||
|
||||
|
||||
|
||||
The run screen is shown as follows:
|
||||
|
||||
|
||||
① is the information of the inserted USB stick;
|
||||
② is the version information of this Ventoy;
|
||||
③ is the Ventoy version information in the USB stick (empty if Ventoy is not installed)
|
||||
④ is the installation option, click Install to install Ventoy into the corresponding USB flash drive;
|
||||
|
||||
If the internal version is lower than the installation package version, we can click the "Upgrade" option below to upgrade.
|
||||
|
||||
|
||||
|
||||
Note: The upgrade operation is safe and will not lose the existing image files in the USB drive.
|
||||
|
||||
After Ventoy is successfully installed, just copy the image file of the openKylin system into the USB drive.
|
||||
|
||||
## 2. Linux system usage details
|
||||
|
||||
Download the Linux version zip package, unzip it, and open a terminal in the directory where the installation package was unzipped;
|
||||
|
||||
Execute: `sudo sh VentoyWeb.sh`
|
||||
|
||||
After entering the user password, you will be prompted that the service has been started, open a browser, and visit http://127.0.0.1:24680 directly
|
||||
|
||||
Note: On most systems you can press the ctrl key while clicking on the link with the mouse, no need to open the browser manually anymore.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The browser page is displayed as follows:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After that, the usage is the same as Windows mode, please refer to Windows usage.
|
||||
|
||||
# II. Full disk installation of openKylin open source OS
|
||||
|
||||
Insert the created USB boot disk, reboot the computer, and press "F2" to enter the BIOS system at boot;
|
||||
|
||||
|
||||
|
||||
Next, enter the "Boot" screen with the left and right arrow keys, press the up and down arrow keys to select the "Boot Option #1" tab, enter. Select "Boot from USB" as the boot method, i.e. select your USB stick and enter.
|
||||
|
||||
Enter.
|
||||
|
||||
|
||||
|
||||
|
||||
Afterward, use the left and right arrow keys to enter the "Save & Exit" screen, select "Save Changes and Exit", and enter. In the pop-up selection box, select "Yes" and enter.
|
||||
|
||||
Enter.
|
||||
|
||||
|
||||
|
||||
Now the computer starts to reboot and you will see the preparation screen for the openKylin open source OS installation:
|
||||
|
||||
|
||||
|
||||
After a short wait you will enter the new version of the system installation screen, as follows:
|
||||
|
||||
|
||||
|
||||
We select "Install openKylin" on the desktop to jump to the installation interface, the system will let us do the language, time zone and configure the user information interface. The following image shows:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After configuring this information we select the installation method screen and choose "Custom installation", as follows:
|
||||
|
||||
|
||||
|
||||
Since we are doing a full installation, we will delete the existing partitions, and add partitions after the deletion, first add the root partition, the size I have allocated here is 100G, you can allocate it according to your needs, as follows:
|
||||
|
||||
|
||||
|
||||
After that we add the efi partition, the efi partition is a boot partition, so 256M is sufficient.
|
||||
|
||||
|
||||
|
||||
After that we add the data partition and backup partition as data partition and backup restore partition, just allocate about 20G to 30G.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Click "Next" after all allocations are done to start the installation of openKylin OS.
|
||||
|
||||
|
||||
|
||||
|
||||
Wait for the installation to complete and click Reboot Now.
|
||||
|
||||
|
||||
|
||||
After reboot, you can use openKylin open source OS normally.
|
||||
|
||||
|
||||
|
||||
|
||||
# III. Install Windows 10 and openKylin dual system
|
||||
|
||||
First, you need to create a blank disk partition on Win10, select "This PC" - right click "Manage".
|
||||
|
||||
Right click on "Manage".
|
||||
|
||||
|
||||
|
||||
Go to the "Computer Management" page, click on "Storage > Disk Management", select the disk space you want to partition, right-click on the disk, and select "Compress Volume".
|
||||
|
||||
Right-click on the disk and select "Compressed Volume".
|
||||
|
||||
|
||||
|
||||
The compression window will pop up, enter the amount of space to be compressed, about 135G will be allocated here (it is recommended to allocate at least 30G, if the size is not enough, you can reallocate the disk space to make sure the partition has enough free space and the original partition is big enough). After confirming the amount of space to be compressed, click "Compress".
|
||||
|
||||
|
||||
|
||||
When the compression is finished, there will be one more free space and the disk partition will be finished.
|
||||
|
||||
|
||||
|
||||
Insert the created USB boot disk, restart the computer and press "F2" at boot to enter the BIOS system;
|
||||
|
||||
|
||||
|
||||
Next, enter the "Boot" screen with the left and right arrow keys, press the up and down arrow keys to select the "Boot Option #1" tab, enter. Select the boot method to boot from USB, i.e. select your own USB stick, enter.
|
||||
|
||||
Enter.
|
||||
|
||||
|
||||
|
||||
|
||||
Afterwards, use the left and right arrow keys to enter the "Save & Exit" screen, select "Save Changes and Exit", and enter. In the pop-up selection box, select "Yes" and enter.
|
||||
|
||||
Enter.
|
||||
|
||||
|
||||
|
||||
|
||||
Now the computer starts to reboot and you will see the preparation screen for the openKylin open source OS installation:
|
||||
|
||||
|
||||
|
||||
Wait a bit and enter the new version of openKylin installation screen, double-click "Install openKylin". The following figure shows:
|
||||
|
||||
|
||||
|
||||
Next, enter the installation configuration page - select the language, time zone and set the user information, you can set it according to your situation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Wait until the Select installation method screen appears and select "Custom installation".
|
||||
|
||||
|
||||
|
||||
After that, go to the partition page, as follows:
|
||||
|
||||
|
||||
|
||||
As you can see, there is already a Windows system on the system, and "free" corresponds to the free partition we just compressed. Since we are installing a dual system, the next thing we need to do is to install the openKylin system in this free partition.
|
||||
|
||||
Select the "free" partition - click the "Add" button on the far right to enter the New partition page.
|
||||
|
||||
First add the root partition, the size allocated here is 80G, you can allocate it according to your needs, but make sure there is enough space available afterwards, as follows:
|
||||
|
||||
|
||||
|
||||
Since the Windows system already has an EFI boot partition, we again do not need to add an EFI boot partition.
|
||||
After that, add the data and backup partitions as data partition and backup restore partition, and allocate 20G each here.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Click "Next" after all allocations are done to start installing openKylin open source OS.
|
||||
|
||||
|
||||
|
||||
Wait for the installation to complete and click "Reboot Now".
|
||||
|
||||
|
||||
|
||||
After rebooting, the Select System screen will appear, as follows:
|
||||
|
||||
|
||||
|
||||
Select the system we want to enter by using the up and down keys and enter. At this point, the dual system has been installed.
|
||||
|
||||
# IV. Install openKylin open source operating system on a virtual machine (VMware)
|
||||
|
||||
First, open VMware Workstation and click Create New Virtual Machine.
|
||||
|
||||
|
||||
|
||||
|
||||
Once you enter the virtual machine boot screen, select the "Typical" option and click Next;
|
||||
|
||||
|
||||
|
||||
Select "Install the operating system later" and click Next;
|
||||
|
||||
|
||||
|
||||
Select "Linux" for the client operating system and Ubuntu 64-bit for the version, and click Next;
|
||||
|
||||
|
||||
|
||||
Enter the name of the virtual machine and choose the path to install it, and click Next;
|
||||
|
||||
|
||||
|
||||
Set the default disk size allocated to the virtual machine to 50G, 50G is perfectly sufficient under normal circumstances, you can also adjust it appropriately according to your situation. Select "Split the virtual disk into multiple files" and click Next;
|
||||
|
||||
|
||||
|
||||
Then click on "Customize hardware" to enter the hardware configuration interface;
|
||||
|
||||
|
||||
|
||||
We select our image file at "New CD/DVD (SATA)".
|
||||
|
||||
|
||||
|
||||
Then you can make a series of settings for memory, processor, etc. in the hardware configuration interface, click the Close button in the lower right corner after the settings are complete, and click Finish after returning to the New Virtual Machine orientation. At this point, you will automatically jump to the boot screen of the virtual machine, click "Open this virtual machine" to start the system installation.
|
||||
|
||||
Select the language setting "Chinese (Simplified)" and click Next;
|
||||
|
||||
|
||||
|
||||
Select "Shanghai" as the time zone and click Next;
|
||||
|
||||
|
||||
|
||||
When the user information is set, click Next;
|
||||
|
||||
|
||||
|
||||
Select Full installation for the installation method and click Next;
|
||||
|
||||
|
||||
|
||||
|
||||
check the box Format all disks and click Install Now;
|
||||
|
||||
|
||||
|
||||
Wait for the installation to complete, click "Reboot Now", and you can use openKylin open source OS on your virtual machine.
|
||||
|
|
@ -0,0 +1,66 @@
|
|||
---
|
||||
title: Installation Guide
|
||||
description:
|
||||
published: true
|
||||
date: 2022-07-18T09:21:33.933Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-03-11T03:16:53.878Z
|
||||
---
|
||||
|
||||
# Installation Guide (For MacOS)
|
||||
|
||||
This article is for Mac notebooks with Intel and Apple Silicon chips, and details the installation tutorial for installing openKylin open source operating system in macOS via virtual machine. (For Windows and Linux installation tutorials, please move to https://docs.openkylin.top/zh/社区参与) Guide/openKylin download address and installation method )
|
||||
|
||||
# Preparation
|
||||
The first step to install and use openKylin open source operating system is to get the openKylin open source operating system image file, we can directly download it from the openKylin official website.
|
||||
|
||||
Download link: https://www.openKylin.top/downloads Select the appropriate version (64-bit x86 architecture as an example)
|
||||
|
||||
|
||||
# I. Installing VMware Fusion
|
||||
|
||||
VMware Fusion provides the best way to run Windows, Linux, and other operating systems on Apple Macs without rebooting.
|
||||
|
||||
Fusion 13 supports Intel and Apple Silicon Macs running macOS 12 and later and offers features for developers, IT administrators and everyday users.
|
||||
|
||||
Use the following link to get started with a free, fully functional 30-day trial (no registration required)
|
||||
|
||||
Download link: https://www.vmware.com/cn/products/fusion/fusion-evaluation.html
|
||||
|
||||
|
||||
|
||||
# II. Install the openKylin open source operating system
|
||||
|
||||
Open the virtual machine software VMware Fusion and click on New in the File menu.
|
||||
|
||||
! [%E6%96%B0%E5%BB%BA%E8%99%9A%E6%8B%9F%E6%9C%BA.png] (./assets/installation-guide/%E6%96%B0%E5%BB%BA%E8%99%9A%E6%8B%9F%E6%9C%BA.png)
|
||||
|
||||
Create the virtual machine by dragging the downloaded ISO file from the preparation into the window.
|
||||
|
||||
|
||||
|
||||
Once you enter the virtual machine boot screen, follow the default options and click Continue.
|
||||
|
||||
Select "Install the operating system later" and click Next.
|
||||
|
||||
Select "Linux" for the client operating system and Ubuntu 64-bit for the version, and click Next.
|
||||
|
||||
Enter the name of the virtual machine and choose the path to install it, click Next.
|
||||
|
||||
Then you can make a series of settings for memory, processor, etc. in the hardware configuration interface, click the Close button at the bottom right corner after the settings are completed, go back to the New Virtual Machine guide and click Finish. At this point, you will automatically jump to the boot screen of the virtual machine, click "Open this virtual machine" to start the system installation.
|
||||
|
||||
Click "Open this virtual machine" to start the system installation.
|
||||
|
||||
|
||||
|
||||
Select the language setting "Chinese (Simplified)" and click Next.
|
||||
|
||||
|
||||
Select "Shanghai" as the time zone, click next.
|
||||
|
||||
|
||||
After the user information is set, click Next.
|
||||
|
||||
|
||||
Wait for the installation to finish, click the "Reboot Now" button, and you can use openKylin open source OS on the virtual machine.
|
||||
|
|
@ -0,0 +1,295 @@
|
|||
## openKylin Community Participation Guide
|
||||
|
||||
On June 24, 2022, with the theme of "Create the momentum of open source and enjoy a borderless future", the launch of openKylin, China's first root community for desktop operating systems, was successfully held online, and the openKylin open source community was officially released. The conference attracted countless developers, and was once again featured in CCTV news and top searches on many social media platforms. During the period after the release of openKylin, we have received a lot of questions from our partners, among which the most concerned are how to participate in the openKylin community correctly and how to submit personal contributions in the community correctly.
|
||||
|
||||
### 1. Sign the CLA
|
||||
|
||||
The full name of CLA is `Contributor License Agreement`, which translates to Contributor License Agreement. In order to avoid some unnecessary troubles or disputes, no matter you are an enterprise, employee or individual developer, you need to sign the CLA with the corresponding identity before adding bricks to the openKylin community. openKylin community CLA signing The address is [https://cla.openkylin.top](https://cla.openkylin.top), the following is a brief introduction to the three forms of CLA signing for the openKylin community and the corresponding signing process.
|
||||
|
||||
#### 1.1 Enterprise CLA Signing
|
||||
|
||||
The process of enterprise signing is more complicated, and the enterprise CLA signers who pass the openKylin community audit can join the community membership system.
|
||||
|
||||
- Apply for candidacy to the Council, enjoy guidance on community development direction, development planning and implementation guidance;
|
||||
- Apply for [create](https://www.openkylin.top/join/application-cn.html) SIG group, and can assign SIG group Owner to run for the technical committee;
|
||||
- Apply to [join](https://www.openkylin.top/join/application-cn.html) existing [SIG groups](https://www.openkylin.top/join/sig-cn.html) and participate in technical code and other development discussions and contributions;
|
||||
- Apply to run for the Eco Committee to participate in community operation activities, co-branding promotion, gift exchange and other rights and interests.
|
||||
|
||||
The process for companies to sign the CLA is shown in the following diagram
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. First, submit the basic information for enterprise signing in the [enterprise signing](https://cla.openkylin.top/cla/sign/corporation_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, where `enterprise`, ` contact person`, `position`, `email` and `validation code` are required fields, other information can be left out;
|
||||
2. after clicking the sign button, you will receive an email in the email address you filled in the previous step, which includes the basic information filled in the previous step and three attached files, follow the instructions in the email to complete the subsequent steps;
|
||||
3. openKylin community administrator will review the information filled in after receiving the mailed items, and after the review is approved, the attachments will be uploaded on the CLA platform and the enterprise administrator account of your enterprise will be automatically added, which will be sent to the email address filled in the first step;
|
||||
4. log in to the enterprise administrator account on the CLA platform and change the password, at this point the signing process of enterprise CLA is completed (this step is not required, but it is recommended to complete this step in order to prevent forgetting or deleting the enterprise administrator email by mistake);
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> After finishing enterprise signing, the account received in enterprise mailbox is enterprise administrator account, which is used to review the signing information of associated enterprise employees. If the enterprise administrator also needs to submit contributions on gitee, he/she also needs to sign the employee CLA using the mailbox suffix that matches the enterprise to bind the gitee id, so as to pass the CI's CLA signing check!
|
||||
|
||||
#### 1.2 Employee CLA Signing
|
||||
|
||||
After your enterprise has finished signing the enterprise CLA, you can use the mailbox that matches your enterprise mailbox suffix to sign the employee CLA. The process of employee signing is shown below.
|
||||
|
||||
The process of employee signing is shown below.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Open the [Employee Signing](https://cla.openkylin.top/cla/sign/employee_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, fill in the basic information, click the Send Captcha button, and enter the email verification code into the verification code box, check the box **I have read the agreement and agree to sign**, click the sign button, a pop-up prompt employee sign has been submitted;
|
||||
2. contact the enterprise administrator, who will activate the employee signing request submitted by you on the employee management page;
|
||||
3. after the enterprise administrator activates your signing request, the email you applied for will receive an alert email that the CLA signing is complete, supporting that the employee CLA signing is all complete;
|
||||
|
||||
#### 1.3 Personal CLA Signing
|
||||
|
||||
If you are an individual developer or your company does not have an enterprise CLA, you can submit your contribution to the openKylin community by signing a personal CLA, the personal CLA signing process is similar to the employee CLA signing process, as shown in the figure below.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
1. Open the [Personal Signing](https://cla.openkylin.top/cla/sign/person_cla/openKylin-f46f289e01bc11edb8990242ac110005) page, fill in your basic personal information, click the Send Captcha button, put the verification code from your email address Enter the verification code into the verification code box, check **I have read the agreement and agree to sign**, click the sign button, and a pop-up will appear to indicate successful signing;
|
||||
2. open the personal signing mailbox, you can receive a personal CLA signing audit approval email;
|
||||
|
||||
> **TIPS!**
|
||||
> - Each mailbox can only be signed once.
|
||||
> - Each mailbox can only sign CLA once
|
||||
> - The `gitee id` in the employee signing and personal signing should be filled in correctly, if it is filled in incorrectly, then the PR submitted on gitee will not pass the CI's CLA check, and your submitted PR will be tagged with `openkylin-cla/no`.
|
||||
|
||||
#### 1.4 Differences between the three types of signatures
|
||||
|
||||
Speaking of which, some of you may ask, "Why do we need to make these three forms of CLA signature? Don't worry, let me see the following picture
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Employee signing is mandatory for enterprises. If the enterprise where the developer works signs the enterprise CLA, then all employees of that enterprise can sign the employee CLA belonging to that enterprise, so **contributions submitted by employees in the openKylin community (including but not limited to PR, ISSUE, etc.) are attributed to the enterprise's contribution to the openKylin community**.
|
||||
|
||||
If an individual developer or a developer's company does not sign a corporate CLA, then they can sign a CLA in the form of individual signing. Therefore, contributions submitted by developers** in the openKylin community through individual CLA signing form belong to the individual developer**.
|
||||
### 2. Submitting Contributions
|
||||
|
||||
After the first step of CLA signing, you can start to submit your contributions to the openKylin community. Here is a simple repository to demonstrate how to submit your `PR contributions`.
|
||||
|
||||
openKylin uses the industry's popular `git workflow`, so we need to have a little basic understanding of `git` before contributing.
|
||||
|
||||
#### 2.1 git environment configuration
|
||||
|
||||
As the old saying goes, if you want to do a good job, you need to do a good job. Before we can formally introduce how to commit our own contributions, we need to configure our local ``git environment'' now.
|
||||
|
||||
``bash
|
||||
# debian
|
||||
apt install git
|
||||
# arch Linux
|
||||
pacman -S git
|
||||
```
|
||||
|
||||
After the installation is complete, type `git version` in the terminal. If the output corresponds (similar to the image below), the installation was successful.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
After confirming that the git installation is complete, we can enter commands in the terminal to configure our personal information, we just need to configure the simplest user information.
|
||||
|
||||
```bash
|
||||
git config --global user.email "zhangsan@gmail.com" # Configure the commit email
|
||||
git config --global user.name "zhangsan" # Configure the committer username
|
||||
```
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> It is recommended that the `email, name` configuration information match your gitee account `binding email` and `user ID` so that you can see your contribution history heat map in your profile!
|
||||
|
||||
#### 2.2 Submitting a PR
|
||||
|
||||
In the previous section, we completed the `git` environment locally, the next is the code contribution process, before that we need to go to `gitee` to create an account, if you do not have a `gitee` account, you can click this link to create https://gitee.com/signup, after creating a gitee account, you can submit your personal contributions to the openKylin community on gitee. The submission process is shown below, and the following is an example of how to submit PR to the openKylin community on gitee through the openKylin/ukui-menu repository
|
||||
|
||||
|
||||
|
||||
1. Fork a copy of the repository you are interested in to your personal account on gitee (this article uses ukui-menu as an example), as follows, click the fork button to copy the repository to your personal account
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
2. After forking the repository to your personal account, you can modify the code in our local environment by cloning the code locally with the following command
|
||||
|
||||
```bash
|
||||
cd /home/test/data/work/openkylin/code # Find a path you like
|
||||
git clone https://gitee.com/jiangwei124/ukui-menu # Clone the ukui-menu code locally
|
||||
```
|
||||
|
||||
3. With the second step, we have cloned the `ukui-menu` repository code under our own account to local, next find an IDE you are comfortable with to open the `ukui-menu` project or operate directly from the command line (if you feel more familiar with it), here is the simplest demonstration, add the `README-zh.md` description document, if you are not a If you are not a techie, it is generally recommended to start submitting your community contributions from ``documentation``, as this is the easiest and easiest way to pass the community review.
|
||||
|
||||
```bash
|
||||
cd /home/test/data/work/openkylin/code/ukui-menu
|
||||
touch README-zh.md # New
|
||||
vim README-zh.md # Enter the contents
|
||||
```
|
||||
|
||||
After translating the `README.md` file and saving the translated content to the `README-zh.md` file, you can commit our new content to our personal `gitee repository` via `git`, and you can see the following image on gitee to indicate that the push was successful.
|
||||
|
||||
```bash
|
||||
cd /home/test/data/work/openkylin/code/ukui-menu
|
||||
git add README-zh.md # Add the file to the staging area
|
||||
git commit -m "add README-zh.md file" # Commit the changes
|
||||
git push # Push the changes to the remote repository
|
||||
git push
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
4. After pushing our changes, you can commit your PR on gitee by clicking on the `Pull Requests` option in the image above, then click on `New Pull Request` on the right side to create a new `Pull Request`, fill in the corresponding information on the page, click on Create Pull Request, and you You have successfully submitted your first PR.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> 1. be careful not to choose the wrong branch for your personal repository when choosing a branch, and choose the `openkylin/yangtze` branch for the openKylin community target repository;
|
||||
> 2. If you have an associated issue, you can associate this Pull Request to the issue, so that when the PR is accepted and merged, the associated issue will be automatically set to the completed status!
|
||||
|
||||
5. At this point, your first openKylin community contribution is basically complete, and then you will wait for CI to automatically compile your submitted code, and if the CI process is successful, it will automatically merge your submitted PRs, and if it fails, the repository administrator will step in to review your PRs!
|
||||
|
||||
#### 2.3 Checking PR status
|
||||
|
||||
After the PR submission is completed, there will be a record of the submission information on the personal homepage by clicking on it to jump to the PR details page, where you can see the information shown below
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Clicking on the link in the green box in the image above will both jump to the build log and view detailed build information! In short, everything you care about PR can be seen on the details page of your PR submission.
|
||||
|
||||
If you want to check whether your submitted PR has been applied to the latest ISO distribution, you can go to [openKylin ISO download page](https://www.openkylin.top/downloads/) to download the latest ISO to check.
|
||||
|
||||
#### 2.4 Submitting Issues
|
||||
|
||||
In addition to the PR contribution method, issue is also a contribution method. For example, if you stumble upon a bug while using the `openKylin system`, you can submit a bug issue in the `openKylin` organization.
|
||||
|
||||
- If it is a system-level bug, then you can submit a `bug issue` under the [openKylin/community](https://gitee.com/openkylin/community/issues) repository.
|
||||
- If it is an application-level bug, you can submit `bug issues` under the corresponding repository in the openKylin community. For example, if you find a bug that sometimes flickers when you use kylin video, you can submit `bug issues` under [openKylin/kylin-video](https://gitee.com/) openkylin/kylin-video/issues) repository;
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> When submitting a bug issue, describe the bug as clearly as possible, and if you have a log file also click the Upload Attachment button to upload the log file to the issue!
|
||||
|
||||
### 3. Join SIGs
|
||||
|
||||
SIG is called Special Interest Group, if you want to participate deeply in the openKylin community, you can apply to join the SIG of the direction you are more interested in, the current `openKylin` community SIG list can go to https://www.openkylin.top/join The current list of `openKylin` community SIGs can be viewed at /sig-cn.html, and the process for developers to join SIGs is as follows.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Next, let's demonstrate how to join the SIG by a chestnut, if I want to join the `HTML5` SIG
|
||||
|
||||
1. fork `openKylin/community` repository to my personal gitee account, refer to section 2.2;
|
||||
|
||||
2. clone the community repository under your personal account to local, and modify `community/sig/html5/sig.yaml` and `community/sig/html5/README.md`, the files are modified as follows
|
||||
|
||||
**sig.yaml**
|
||||
|
||||
```yaml
|
||||
name: html5
|
||||
description: html5 team
|
||||
owner.
|
||||
- pierre4long
|
||||
- insomnia_kylin
|
||||
maintainers.
|
||||
- name: oatoam
|
||||
- name: tylwj
|
||||
- name: wonschange
|
||||
- name: jiangwei124 # add
|
||||
packages.
|
||||
- gecko_b2g
|
||||
- gaia_homescreen
|
||||
- manifests
|
||||
- gaia_system
|
||||
- gaia-buildinkeyborad
|
||||
```
|
||||
|
||||
**README.md**
|
||||
|
||||
```mariadb
|
||||
### Maintainers
|
||||
- Tao Mao (maotao@kylinos.cn)
|
||||
- Wenjie Li(liwenjie@yhkylin.cn)
|
||||
- Changqi Wang(wanghcangqi@kylinos.cn)
|
||||
- Jiang Wei(jiangwei1@kylinos.cn) # Add
|
||||
````
|
||||
|
||||
3. After the modification is done, submit the modified content to your personal gitee repository, then submit PR to `openKylin/community` repository according to part 2.2. Next is to wait patiently for SIG owner to review, after the review is passed, the CI process will automatically merge your application into the main repository!
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> - The new information in the name field in the sig.yaml file is your personal `gitee id`, you must `make sure the gitee id really exists`, otherwise, even if the SIG owner passes the audit, the CI process will fail, and thus your application cannot be merged into the `openKylin/community` repository correctly! .
|
||||
> - Signing CLA is the a priori condition for applying SIG, you must sign CLA before applying to join SIG
|
||||
|
||||
### 4. Apply for Single Package Maintainer
|
||||
|
||||
Because the community's SIG member privileges are too high, if you want to join the SIG in the openKylin community, you need to have certain contributions in the community before the technical committee may pass your application to join the SIG, so for general developers, it is recommended to apply for single package maintainer at the beginning, the process of single package maintainer is shown in the figure below, the specific instructions for single package maintainer can be viewed in [this link document](https://gitee.com/openkylin/community/blob/master/packages/README.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### 4.1 Applying to become a new single package maintainer
|
||||
|
||||
Suppose you want to become a single package maintainer for `ukui-menu`, but there is no information about the package in the `community/packages` directory, you can apply to become a new single package maintainer by following the procedure below
|
||||
|
||||
1. First fork the community repository to your personal gitee account, and then clone it locally
|
||||
|
||||
```bash
|
||||
cd /home/test/openkylin/community # Find a path you like
|
||||
git clone https://gitee.com/jiangwei124/community.git
|
||||
```
|
||||
|
||||
2. Add a new `ukui-menu.yaml` file to the `community/packages` path, and enter the following as you see fit
|
||||
|
||||
```yaml
|
||||
name: ukui-menu
|
||||
path: ukui-menu
|
||||
maintainers.
|
||||
- name: zhangsan # gitee id
|
||||
openkylinid.
|
||||
displayname: Zhang San
|
||||
email: zhangsan@gmail.com
|
||||
```
|
||||
|
||||
> **TIPS!**
|
||||
>
|
||||
> Note that the `path` field can be omitted if the repository path name is the same as the package name. Considering that the package name does not necessarily match the gitee repository naming convention, to avoid repository creation failure, you can specify another path!
|
||||
|
||||
3. Submit the above changes to your personal gitee repository, and then submit PR to the community repository of the openKylin community both, and wait for the administrator to review and approve, you have `ukui-menu` repository permissions, application for a new single package maintainer has been completed!
|
||||
|
||||
#### 4.2 Apply for an existing single package maintainer
|
||||
|
||||
Similar to the previous section on becoming a new single package maintainer, applying to become an existing single package maintainer is even simpler, first you need to fork the `openKylin/community` repository to your gitee account, then you just need to modify the corresponding package yaml file. packages/ukui-menu.yaml` file with the following content
|
||||
|
||||
```yaml
|
||||
name: ukui-menu
|
||||
path: ukui-menu
|
||||
maintainers.
|
||||
- name: zhangsan
|
||||
openkylinid.
|
||||
displayname: Zhang San
|
||||
email: zhangsan@gmail.com
|
||||
# Add your personal information
|
||||
- name: lisi # gitee id
|
||||
openkylinid.
|
||||
displayname: 李四
|
||||
email: lisi@gmail.com
|
||||
```
|
||||
|
||||
This is the end of the openKylin community participation guide, if there are other questions, you are welcome to submit issues, or join the developer exchange WeChat group!
|
||||
|
After Width: | Height: | Size: 608 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 244 KiB |
|
After Width: | Height: | Size: 491 KiB |
|
After Width: | Height: | Size: 2.2 MiB |
|
After Width: | Height: | Size: 2.2 MiB |
|
After Width: | Height: | Size: 2.0 MiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 1.7 MiB |
|
After Width: | Height: | Size: 806 KiB |
|
After Width: | Height: | Size: 909 KiB |
|
After Width: | Height: | Size: 744 KiB |
|
After Width: | Height: | Size: 899 KiB |
|
After Width: | Height: | Size: 2.0 MiB |
|
After Width: | Height: | Size: 616 KiB |
|
After Width: | Height: | Size: 1.6 MiB |
|
After Width: | Height: | Size: 476 KiB |
|
After Width: | Height: | Size: 212 KiB |
|
After Width: | Height: | Size: 147 KiB |
|
After Width: | Height: | Size: 147 KiB |
|
After Width: | Height: | Size: 1.2 MiB |
|
After Width: | Height: | Size: 121 KiB |
|
After Width: | Height: | Size: 157 KiB |
|
After Width: | Height: | Size: 157 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 65 KiB |
|
After Width: | Height: | Size: 97 KiB |
|
After Width: | Height: | Size: 536 KiB |
|
After Width: | Height: | Size: 120 KiB |
|
After Width: | Height: | Size: 247 KiB |
|
After Width: | Height: | Size: 813 KiB |
|
After Width: | Height: | Size: 61 KiB |
|
After Width: | Height: | Size: 252 KiB |
|
After Width: | Height: | Size: 252 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 111 KiB |
|
After Width: | Height: | Size: 111 KiB |
|
After Width: | Height: | Size: 372 KiB |
|
After Width: | Height: | Size: 372 KiB |
|
After Width: | Height: | Size: 417 KiB |
|
After Width: | Height: | Size: 417 KiB |
|
After Width: | Height: | Size: 55 KiB |
|
After Width: | Height: | Size: 55 KiB |
|
After Width: | Height: | Size: 1.8 MiB |
|
After Width: | Height: | Size: 1.8 MiB |
|
After Width: | Height: | Size: 67 KiB |
|
After Width: | Height: | Size: 67 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 67 KiB |
|
After Width: | Height: | Size: 441 KiB |
|
After Width: | Height: | Size: 297 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 215 KiB |
|
After Width: | Height: | Size: 215 KiB |
|
After Width: | Height: | Size: 215 KiB |
|
After Width: | Height: | Size: 215 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 259 KiB |
|
After Width: | Height: | Size: 259 KiB |
|
After Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 170 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 73 KiB |
|
After Width: | Height: | Size: 9.7 KiB |
|
After Width: | Height: | Size: 212 KiB |
|
After Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 108 KiB |
|
After Width: | Height: | Size: 103 KiB |
|
After Width: | Height: | Size: 101 KiB |
|
After Width: | Height: | Size: 108 KiB |
|
After Width: | Height: | Size: 84 KiB |
|
After Width: | Height: | Size: 164 KiB |
|
After Width: | Height: | Size: 77 KiB |
|
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
title: Documentation Platform User Guide
|
||||
description:
|
||||
published: true
|
||||
date: 2022-05-17T07:16:35.227Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-03-11T03:17:18.988Z
|
||||
---
|
||||
|
||||
# Documentation Platform User Guide
|
||||
|
|
@ -0,0 +1,73 @@
|
|||
---
|
||||
title: Mailing List User's Guide
|
||||
description:
|
||||
published: true
|
||||
date: 2022-06-23T07:23:30.999Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-03-11T03:17:23.928Z
|
||||
---
|
||||
# Mailing List User's Guide
|
||||
|
||||
## Mailing List Introduction
|
||||
|
||||
- Access address：<a target="blank" href="https://mailweb.openkylin.top/postorius/lists/">mailweb.openkylin.top</a>
|
||||
Mail group introduction: Each mail group will have a special mailbox to manage the mail group, take UKUI as an example, as follows
|
||||
ukui@lists.openkylin.top (mail group mailbox address)
|
||||
ukui-request@lists.openkylin.top(mail group subscription mailbox address)
|
||||
ukui-owner@lists.openkylin.top(mail group administrator email address)
|
||||
|
||||
## How to subscribe to SIG group
|
||||
|
||||
1. After entering the [mailing list homepage](https://mailweb.openkylin.top/postorius/lists/)，as shown below, click the SIG group you want to subscribe to.
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
2. After entering the corresponding mailing group, as shown below, fill in the email address and name in the input box, and click Subscribe button below to receive the confirmation email of subscribing SIG.
|
||||
|
||||
|
||||
|
||||
3.The subscription mailbox will receive a confirmation message to join, follow the instructions to enter the verification information to join the corresponding SIG group.
|
||||
|
||||
4.If the subscription is successful, you will receive a welcome email from the mailing list group, as shown in the following figure.
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
<span style="color:red">Note: If all the above steps are normal, but you do not receive the email, please contact contact@openkylin.top the email address to explain the situation</span>
|
||||
|
||||
|
||||
## How to unsubscribe SIG group
|
||||
|
||||
1. Take UKUI group as an example, send an email to ukui-request@list.openkylin.top, the content subject and body of the email contains "unsubscribe", as shown in the following picture
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
2. Next, you will receive an unsubscribe verification email, as shown below
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
3. According to the prompted information, bring the verification information when you reply, and use it as the subject and body of the email to complete the subscription to the SIG group, as shown in the following figure.
|
||||
|
||||
---
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
4. After the SIG group is successfully verified, the SIG group is unsubscribed.
|
||||
|
||||
## How to send emails to SIG group members
|
||||
Any member can send email to all members of SIG group, the email address is the address of SIG group, take UKUI as an example, the email address is ukui@lists.openkylin.top.
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
title: Guide to using the translation platform
|
||||
description: Include requirements + contribution portal
|
||||
published: true
|
||||
date: 2022-05-17T07:16:37.030Z
|
||||
tags:
|
||||
editor: markdown
|
||||
dateCreated: 2022-03-11T03:17:21.464Z
|
||||
---
|
||||
|
||||
# Translation Platform User Guide
|
||||
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 39 KiB |