The process to contribute new drivers in openEuler

As a linux distro, openEuler is supposed to integrate/support many drivers, like network adapters, CPUs, storages, and etc.

What is the process to add a new driver? I prepare a draft and wish community members review it here.

Before contribute a driver to openEuler

Check the current development cycle

From technical point of view, a new driver finally is a patch. For each release schedule, there should be a deadline to accept new features/patches. So please check the current release schedule first.

Understand the 3rd party CI policy

The new driver needs test with the potential changed from openEuler master, so a 3rd party CI is required.

Get to know how to contribute

Analyze what projects will be impacted and read how to contribute of the projects. If you are not sure what projects, please send emails to tc@openeuler.org, and other potential mail lists in https://openeuler.org/en/community/mails.html.
Apply for new SIG for the new driver if new repos are required here.
Send emails to mail list to let members know there will be a new driver.

Writing code

write codes for your driver and submit for review.
prepare the 3rd party CI to test with the masters and different release branches. Get support from infrastructure team infra@openeuler.org if necessary.
prepare test cases. Contact QA team if necessary.
prepare documents for your driver. Contact Docs team if necessary.

After the driver is added

Make sure your driver is documented
- Add the driver description to where to record all the drivers(to be added)
- provide how to contribute about your driver so that anyone can help.
Make sure your driver is maintained
- follow issues
- follow mail list
Maintain the 3rd party CI.

Hey @Fred_Li, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot.
That means the developpers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/command.md to find the details.

@Fred_Li I don't know if this issue comes frome #I18XS0:openEuler对龙芯3Ａ4000的支持？. If so, I don't think that's a question of adding a driver.For Example, Fedora use the Alternate Architectures to manage the different CPU. Adding a CPU, involves many work beyond development, including development environment support, Version Strategies etc....So,the first thing is to discuss the necessity of introduciton, and how to introduce, how to supports development Base this new CPU.

@Fred_Li I don't know if this issue comes frome #I18XS0:openEuler对龙芯3Ａ4000的支持？. If so, I don't think that's a question of adding a driver.For Example, Fedora use the Alternate Architectures to manage the different CPU. Adding a CPU, involves many work beyond development, including development environment support, Version Strategies etc....So,the first thing is to discuss the necessity of introduciton, and how to introduce, how to supports development Base this new CPU.

@Yang.Li Yes, it comes from the issue you mentioned, but also https://mailweb.openeuler.org/hyperkitty/list/community@openeuler.org/thread/G2PO3MSL2PPUKBLFIUYDO5TSVU6RPZQ3/.

Considering this request, what is your new thought?

Thanks.

I think this issue should be assigned to kernel team. drivers are heavily integrated with kernel development process. the kernel team should give more comments.

First, it's better push drivers to upstream;
Second, develop drivers as independent kernel modules, and build as a separate rpm package;
The last, modify the in-tree kernel source code.

openEuler / community-issue

内容风险标识