Contributing¶

Mailing List¶

We use a public mailing list as our main means of communication. You can find subscription information and the messages archive on the libcamera-devel list information page.

IRC Channel¶

For informal and real time discussions, our IRC channel on irc.oftc.net is open to the public. Point your IRC client to #libcamera to say hello, or use the WebChat.

The IRC channel is also bridged and accessible via Matrix in the #libcamera room:

Source Code¶

libcamera is in active development, including investigations into what a ‘good’ API is for the implementation. We can’t guarantee we have all features implemented, or designed correctly yet, and we have plans to make considerable changes to the API and ABI in our roadmap.

Even so, we provide periodic ‘releases’ to support distributions and packaging teams. To support this we are currently making releases of the 0.y.z version scheme, loosely following semver.

In the foreseeable future, the following applies:

0.y.zActive development, but with ABI breakage detection. The 0.y

version will bump on an ABI/API breakage. Ongoing development will increment the .z version component. Therefore, pre 1.0 ‘y’ is a close equivalent to a major release.

1.y.zStable API and ABI guarantees on the Major version number.

Following semantic versioning as documented at https://semver.org/

The source code is available from the project’s git tree.

$ git clone https://git.libcamera.org/libcamera/libcamera.git

A development mirror is also hosted on Freedesktop.

Freedesktop also provides our CI and testing pipeline.

Issue Tracker¶

Our issue tracker also hosted at Freedesktop tracks all bugs, issues and feature requests.

Documentation¶

Project documentation is created using Sphinx. Source level documentation uses Doxygen. Please make sure to document all code during development.

Submitting Patches¶

The libcamera project has high standards of stability, efficiency and reliability. To achieve those, the project goes to great length to produce code that is as easy to read, understand and maintain as possible. This is made possible by a set of Coding Style Guidelines that all submissions are expected to follow.

We also care about the quality of commit messages. A good commit message not only describes what a commit does, but why it does so. By conveying clear information about the purpose of the commit, it helps speeding up reviews. Regardless of whether you’re new to git or have years of experience, https://cbea.ms/git-commit/ is always a good guide to read to improve your commit message writing skills.

The patch submission process for libcamera is similar to the Linux kernel, and goes through the libcamera-devel mailing list. If you have no previous experience with git-send-email, or just experience trouble configuring it for your e-mail provider, the sourcehut developers have put together a detailed guide available at https://git-send-email.io/.

Patches submitted to the libcamera project must be certified as suitable for integration into an open source project. As such libcamera follows the same model as utilised by the Linux kernel, and requires the use of ‘Signed-off-by:’ tags in all patches.

By signing your contributions you are certifying your work in accordance with the following: