Lustre Development Activities
The next release under development (accepting new features)
If you are looking for small development projects to add minor improvements to Lustre and/or become more familiar with the code and development process, there is a keyword easy that is added to tickets that are suitable: easier development items
The Submitting Changes page covers steps you'll need to follow to contribute code changes.
The Code Reviewers page describes how to find developers willing to perform code reviews on particular sections of the Lustre code.
The Upstream contributing page covers how to contribute to the Linux kernel Lustre client.
Updating the Lustre User Manual is a very useful way for non-coders to contribute to Lustre. See Making Changes to the Lustre Manual for more information on how to contribute changes, and the list of open documentation tickets.
Please see Lustre Coding Style Guidelines and Lustre Style Guide Includes for information about writing Lustre code, and Submitting Changes for details on how to submit patches. There is also Lustre Script Coding Style for writing test scripts.
Patches and landing status can be tracked via some Gerrit searches courtesy of John Hammond:
As Lustre runs in the Linux kernel it can be sensitive to changes between Linux kernel version. While Lustre is used in production on a wide variety of Linux distributions, testing efforts are concentrated on a limited number of primary Linux distributions. There are usually some secondary Linux distributions that either have been demonstrated to work to some reasonable degree or are work-in-progress towards becoming a primary distribution in the future. The primary Linux distributions are what is called out in the release page and the Lustre support matrix, but both the primary and secondary Linux distributions will be mentioned in the Lustre change log.
There is some work-in-progress Lustre Protocol Documentation available (PDF format). While the documentation is not complete, it may still prove to be a valuable resource for developers, and contributions and improvements to the protocol documentation project are welcome.