x/ironic-staging-drivers
Code Issues Proposed changes
3a71aaf0bf
ironic-staging-drivers/README.rst
Dmitry Tantsur 3a71aaf0bf
Harsh but realistic status update 
Change-Id: I53df1de7f9acba3f4a0334727aa139c264ceb86b
2024-02-20 08:57:41 +01:00

2.4 KiB
Raw Blame History

Ironic Staging Drivers

The Ironic Staging Drivers is used to hold out-of-tree Ironic drivers which doesn't have means to provide a 3rd Party CI at this point in time which is required by Ironic.

The intention of this project is to provide a common place for useful drivers resolving the "hundreds of different download sites" problem.

Project status

This project is deprecated and unmaintained. Only critical bug fixes may be provided for the master branch and existing stable branches. The CI status is not monitored. Security issues are not guaranteed to be handled timely. No new deployments should use the staging drivers.

What the Ironic Staging Drivers is not

  • The Ironic Staging Drivers is not a project under Ironic's governance, meaning that the Ironic core group is not responsible for the code in this project (even though, some individuals that work in this project also hold core status in the Ironic project).
  • This project is not a place to dump code and run away hoping that someone else will take care of it for you. Drivers included in this project should be maintained and have their bugs fixed quickly. Therefore, driver owners are going to be asked to "babysit" their driver.

How to contribute

We want to make sure that the Ironic Staging Drivers project is a welcoming and friendly place to contribute code. Therefore, we want to avoid bureaucratic processes as much as possible. If you want to propose a driver to be included in the repository: Just submit the code!

How do I submit the code?

  1. Before we can accept your patches, you'll have to agree to a contributor license agreement.

  2. Learn about how to use our Gerrit review system.

  3. Get the code:

    git clone https://opendev.org/x/ironic-staging-drivers

  4. Make your changes and write a nice commit message explaining the change in details.

  5. Submit the code!

Useful links