Development: Difference between revisions
(8 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
== Lustre Development Activities == | == Lustre Development Activities == | ||
The next release under development ( | The next release under development (accepting new features) | ||
* [[Release 2.12.0]] | |||
* [[Release 2. | |||
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: | 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: | ||
[https://jira.hpdd.intel.com/issues/?jql=labels% | [https://jira.hpdd.intel.com/issues/?jql=labels%3Deasy%20AND%20resolution%3Dunresolved easier development items] | ||
== Submitting Changes == | == Submitting Changes == | ||
Line 19: | Line 16: | ||
== Upstream contributing == | == Upstream contributing == | ||
The [[Upstream contributing]] page covers how to contribute to the | The [[Upstream contributing]] page covers how to contribute to the Linux kernel Lustre client. | ||
== Updating Documentation == | |||
Updating the [http://lustre.org/documentation Lustre User Manual] is a very useful way for non-coders to contribute to Lustre. | |||
See [https://wiki.hpdd.intel.com/display/PUB/Making+changes+to+the+Lustre+Manual Making Changes to the Lustre Manual] for more information on how to contribute changes, and the list of [https://jira.hpdd.intel.com/issues/?jql=project%3DLUDOC%20AND%20resolution%3Dunresolved open documentation tickets]. | |||
== Developer Meetings == | == Developer Meetings == | ||
Line 27: | Line 29: | ||
== Feature Development == | == Feature Development == | ||
All known development efforts are tracked on the [[Projects]] page. | All known development efforts are tracked on the [[Projects]] page. The [[:Category:Architecture|Architecture]] and [[:Category:Design|Design]] documents of various projects are available for review and future reference. | ||
Please see [[Lustre Coding Style Guidelines]] for information about writing Lustre code, and [[Submitting Changes]] for details on how to submit patches. | 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: | Patches and landing status can be tracked via some Gerrit searches courtesy of John Hammond: | ||
* [https://wiki. | * [https://wiki.whamcloud.com/display/~jhammond/Patch+Status Gerrit Patch Status] | ||
* [https://wiki.whamcloud.com/display/~jhammond/Patch+Status+2 Gerrit Patch Status 2] | |||
== Protocol Documentation == | |||
There is some work-in-progress [https://build.hpdd.intel.com/job/lustre-protocol-reviews/lastSuccessfulBuild/artifact/protocol.html Lustre Protocol Documentation] available ([https://build.hpdd.intel.com/job/lustre-protocol-reviews/lastSuccessfulBuild/artifact/protocol.pdf 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 [https://review.whamcloud.com/#/q/project:doc/protocol protocol documentation project] are welcome. | |||
[[Category: Development]] | [[Category: Development]] |
Revision as of 16:29, 28 August 2018
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
Submitting Changes
The Submitting Changes page covers steps you'll need to follow to contribute code changes.
Code Reviews
The Code Reviewers page lists people willing to perform code reviews on particular sections of the Lustre code.
Upstream contributing
The Upstream contributing page covers how to contribute to the Linux kernel Lustre client.
Updating Documentation
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.
Developer Meetings
Feature Development
All known development efforts are tracked on the Projects page. The Architecture and Design documents of various projects are available for review and future reference.
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:
Protocol Documentation
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.