WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Contribute:Contribute: Difference between revisions

From Obsolete Lustre Wiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Developers can support the development of Lustre by submitting code or testing pre-release versions.  
Access guidelines for contributing code and testing Lustre® along with developer resources and tools.  
<div class="categoryLeft">
<big><strong>Contributing to Lustre® technology</strong></big>


<div class="categoryLeft">
<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.
* Read the Lustre <ins>[[Contribution_Policy|Contribution Policy]]</ins> and sign and return a Contributor Agreement.
* Join, post to, and search <ins>[[Lustre_Mailing_Lists|Lustre mailing lists]]</ins> for developers, administrators, and users.
 
<strong>Developing your code...</strong>


<big><strong>Code</strong></big>
* See <ins>[[Accessing Lustre Code]]</ins> for how to download Lustre code.
* 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.
* Follow Lustre <ins>[[Coding 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.


Find out what you need to know to contribute to Lustre's open-source code.
<strong>Debugging and testing your code...</strong>
* See <ins>[[Testing Lustre Code]]</ins> for procedures to verify the code works before you submit it.  


* Join the [[Mailing_Lists|Lustre Development Mailing List]] for developers.
<strong>Submitting your code...</strong>
* Read the [[Contribution_Policy|Contribution Policy]] before testing or submitting code.
* Use [[Open_CVS|Open CVS]] to download pre-release versions of Lustre for coding or test.
* See <ins>[[Submitting_Patches|Submitting Patches]]</ins> to find out how to submit your changes to be reviewed for acceptance into a mainline Lustre branch.  
* Follow [[Coding_Guidelines|Coding Guidelines]] to avoid problems during Lustre code merges.
* Use the Doxygen tool to write reference documentation while [[Documenting_Code|Documenting Code]].


</div>
</div>


<div class="categoryRight">
<div class="categoryRight">
<big><strong>Developer Resources</strong></big>
<big><strong>Developer Resources</strong></big>
* [http://arch.lustre.org/index.php?title=Main_Page Lustre Architecture] wiki offers feature and architectural descriptions, quality attribute scenarios, and vision & scope articles about Lustre.
* <ins>[[Lustre Design Documents]]</ins> provides access to presentations and design documents describing Lustre features currently under development by the Lustre engineering team.
* Lustre design documents
* The <ins>[[Lustre Design Document Archive]]</ins> contains older architecture and design documents including feature and architectural descriptions, high-level design documents and detailed-level design documents.  
** [http://arch.lustre.org/index.php?title=LustreHLDs High-Level Designs] describe the overall design of Lustre features and projects.
* Lustre <ins>[[Subsystem Map]]</ins> describes each of the subsystems in the Lustre code.
** [http://arch.lustre.org/index.php?title=LustreDLDs Detailed-Level Designs] describe the design of individual aspects of a project.
* Resources for high-profile Lustre features under development
** [[ZFS_Resources|ZFS Resources]]
** [[Lustre_OSS/MDS_with_ZFS_DMU|Lustre OSS/MDS with ZFS DMU]]
* [[Lustre_FAQ|Lustre FAQ]] Popular topics, issues and questions from the Lustre community.
 
</div>
</div>
<div class="categoryLeft">


<big><strong>Test</strong></big>
<div class="categoryRight">
 
<big><strong>Questions or Comments?</strong></big>
Read helpful information for testing Lustre.
 
* [[Acceptance_Small_(acc-sm)_Testing_on_Lustre|Acceptance Small Testing]]
* [[Testing_Framework|Testing Framework]]
* [[Lustre_Test_Plans|Lustre Test Plans]]
* [[POSIX_Testing|Posix Testing]]


If you have questions or comments about how you can contribute or about any of the procedures on this page, please [mailto:lustre-wiki-feedback@sun.com let us know].
</div>
</div>

Latest revision as of 15:36, 24 July 2013

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.
  • Read the Lustre Contribution Policy and sign and return a Contributor Agreement.
  • Join, post to, and search Lustre mailing lists for developers, administrators, and users.

Developing your code...

Debugging and testing your code...

Submitting your code...

  • See Submitting Patches 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.