Contribute: Difference between revisions
Jump to navigation
Jump to search
KenRawlings (talk | contribs) (Initial creation as part of accelerated wiki migration) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 10: | Line 10: | ||
<strong>Getting started...</strong> | <strong>Getting started...</strong> | ||
* See <ins>[[Finding_a_Project|Finding a Project]]</ins> for information about how to select a project, find a bug to fix, help with Lustre testing, or contribute to the Lustre user documentation. | * See <ins>[[Finding_a_Project|Finding a Project]]</ins> for information about how to select a project, find a bug to fix, help with Lustre testing, or contribute to the Lustre user documentation. | ||
* Join, post to, and search <ins>[[Lustre_Mailing_Lists|Lustre mailing lists]]</ins> for developers, administrators, and users. | * Join, post to, and search <ins>[[Lustre_Mailing_Lists|Lustre mailing lists]]</ins> for developers, administrators, and users. | ||
| Line 18: | Line 17: | ||
* See <ins>[[Building Lustre Code]]</ins> for how to install and build a working version of Lustre. | * See <ins>[[Building Lustre Code]]</ins> for how to install and build a working version of Lustre. | ||
* See <ins>[[Applying Lustre Patches to a Kernel]]</ins> for how to apply Lustre patches to an unpatched kernel and how to modify an existing kernel patch. | * See <ins>[[Applying Lustre Patches to a Kernel]]</ins> for how to apply Lustre patches to an unpatched kernel and how to modify an existing kernel patch. | ||
* Follow Lustre <ins>[[Coding Guidelines]]</ins> to avoid problems when merging your code. | * Follow Lustre <ins>[[Lustre Coding Style Guidelines]]</ins> to avoid problems when merging your code. | ||
* Use the Lustre <ins>[[Documenting Code]]</ins> guidelines to add reference documentation to your Lustre code contribution. | * Use the Lustre <ins>[[Documenting Code]]</ins> guidelines to add reference documentation to your Lustre code contribution. | ||
<strong>Debugging and testing your code...</strong> | <strong>Debugging and testing your code...</strong> | ||
* See <ins>[[Testing Lustre Code]]</ins> for procedures to verify the code works before you submit it. | * See <ins>[[TestingLustreCode|Testing Lustre Code]]</ins> for procedures to verify the code works before you submit it. | ||
<strong>Submitting your code...</strong> | <strong>Submitting your code...</strong> | ||
* See <ins>[[ | * See <ins>[[Submitting Changes]]</ins> to find out how to submit your changes to be reviewed for acceptance into a mainline Lustre branch. | ||
</div> | </div> | ||
Latest revision as of 05:44, 18 March 2022
| Note: This page originated on the old Lustre wiki. It was identified as likely having value and was migrated to the new wiki. It is in the process of being reviewed/updated and may currently have content that is out of date. |
|---|
Access guidelines for contributing code and testing Lustre® along with developer resources and tools.
Contributing to Lustre® technology
Getting started...
- See Finding a Project for information about how to select a project, find a bug to fix, help with Lustre testing, or contribute to the Lustre user documentation.
- Join, post to, and search Lustre mailing lists for developers, administrators, and users.
Developing your code...
- See Accessing Lustre Code for how to download Lustre code.
- See Building Lustre Code for how to install and build a working version of Lustre.
- See Applying Lustre Patches to a Kernel for how to apply Lustre patches to an unpatched kernel and how to modify an existing kernel patch.
- Follow Lustre Lustre Coding Style Guidelines to avoid problems when merging your code.
- Use the Lustre Documenting Code guidelines to add reference documentation to your Lustre code contribution.
Debugging and testing your code...
- See Testing Lustre Code for procedures to verify the code works before you submit it.
Submitting your code...
- See Submitting Changes to find out how to submit your changes to be reviewed for acceptance into a mainline Lustre branch.
Developer Resources
- Lustre Design Documents provides access to presentations and design documents describing Lustre features currently under development by the Lustre engineering team.
- The Lustre Design Document Archive contains older architecture and design documents including feature and architectural descriptions, high-level design documents and detailed-level design documents.
- Lustre Subsystem Map describes each of the subsystems in the Lustre code.
Questions or Comments?
If you have questions or comments about how you can contribute or about any of the procedures on this page, please let us know.