Contribution

As an openEuler user, you can contribute to the openEuler community in multiple ways. For details about how to contribute to the community, see How to Contribute. Here, some methods are listed for reference.

Special Interest Groups (SIGs)

openEuler brings together people of common interest to form different special interest groups (SIGs). For details about existing SIGs, see the SIG list.

You are welcome to join an existing SIG or create a SIG. For details about how to create a SIG, see the SIG Management Procedure.

Mail List and Tasks

You are welcome to actively help users solve problems raised in the mail list and issues (including code repository issues and software package repository issues). In addition, you can submit an issue. All these will help the openEuler community to develop better.

Documents

We invite you to contribute to the community by submitting code and feedback on problems and difficulties, or suggestions on improving the usability and integrity of documents. For example, problems in obtaining software or documents and difficulties in using the system. Welcome to pay attention to and improve the documentation module of the openEuler community.

IRC

openEuler has also opened a channel in IRC as an additional channel to provide community support and interaction. For details, see openEuler IRC.

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

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.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.