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.
Finding a Project: Difference between revisions
No edit summary |
|||
| Line 8: | Line 8: | ||
* ''Search Bugzilla for very old Lustre bugs.'' These are typically non-critical bugs that are not dependent on a release timeline. They can vary widely in complexity. [[How old would a "very old bug" be? logged over a year ago? 2 years ago? older?]] | * ''Search Bugzilla for very old Lustre bugs.'' These are typically non-critical bugs that are not dependent on a release timeline. They can vary widely in complexity. [[How old would a "very old bug" be? logged over a year ago? 2 years ago? older?]] | ||
Once you have selected a bug to work on, contact [ | Once you have selected a bug to work on, contact [mailto:lustre-devel@lists.lustre.org lustre-devel] to discuss the approach to be taken to fix it. | ||
| Line 15: | Line 15: | ||
If you'd like to take on a project to enhance or add a new feature to Lustre, consider one of these options: | If you'd like to take on a project to enhance or add a new feature to Lustre, consider one of these options: | ||
* ''Search the Bugzilla bug tracking system for the keyword "small project".'' Some Lustre developers use this keyword to indicate that an enhancement request or bug is a stand-alone project suitable to be taken on by an external developer. When you have identified a project you'd like to work on, contact [ | * ''Search the Bugzilla bug tracking system for the keyword "small project".'' Some Lustre developers use this keyword to indicate that an enhancement request or bug is a stand-alone project suitable to be taken on by an external developer. When you have identified a project you'd like to work on, contact [mailto:lustre-devel@lists.lustre.org lustre-devel] to discuss the approach be taken to address it. | ||
* ''Assist with keeping Lustre up-to-date with recent kernel changes.'' For some changes, a simple fix to the Lustre code will be required, while for others, a good understanding of the Linux kernel and how Lustre interfaces with it is needed. For guidance in selecting or proceeding with a project, contact [ | * ''Assist with keeping Lustre up-to-date with recent kernel changes.'' For some changes, a simple fix to the Lustre code will be required, while for others, a good understanding of the Linux kernel and how Lustre interfaces with it is needed. For guidance in selecting or proceeding with a project, contact [mailto:lustre-devel@lists.lustre.org lustre-devel]. | ||
* ''Propose a new feature that can be developed as a separate module on top of Lustre.'' Be sure to get feedback on your proposal on [ | * ''Propose a new feature that can be developed as a separate module on top of Lustre.'' Be sure to get feedback on your proposal on [mailto:lustre-devel@lists.lustre.org lustre-devel] before you get started. | ||
In summary, while I think there can be some small amount of bug selection | In summary, while I think there can be some small amount of bug selection | ||
| Line 28: | Line 28: | ||
In all cases developers should | In all cases developers should | ||
contact [ | contact [mailto:lustre-devel@lists.lustre.org lustre-devel] to first discuss the bug and the approach that should | ||
be taken to fix it. | be taken to fix it. | ||
Revision as of 10:17, 3 September 2009
This page describes how to find a bug to fix, select a project to enhance Lustre, or help with Lustre testing.
Finding a Bug to Fix
Fixing bugs in Lustre is a good way to become familiar with the Lustre code if you've not worked on it before. Bugs against the Lustre code are logged in the Bugzilla bug tracking system. To find a bug you'd like to work on:
- Search Bugzilla key words for bugs designated "easy" bugs. Some Lustre developers use this keyword to indicate this bug could be fixed by someone without an in depth familiarity with the Lustre code.
- Search Bugzilla for very old Lustre bugs. These are typically non-critical bugs that are not dependent on a release timeline. They can vary widely in complexity. How old would a "very old bug" be? logged over a year ago? 2 years ago? older?
Once you have selected a bug to work on, contact lustre-devel to discuss the approach to be taken to fix it.
Selecting a Project
If you'd like to take on a project to enhance or add a new feature to Lustre, consider one of these options:
- Search the Bugzilla bug tracking system for the keyword "small project". Some Lustre developers use this keyword to indicate that an enhancement request or bug is a stand-alone project suitable to be taken on by an external developer. When you have identified a project you'd like to work on, contact lustre-devel to discuss the approach be taken to address it.
- Assist with keeping Lustre up-to-date with recent kernel changes. For some changes, a simple fix to the Lustre code will be required, while for others, a good understanding of the Linux kernel and how Lustre interfaces with it is needed. For guidance in selecting or proceeding with a project, contact lustre-devel.
- Propose a new feature that can be developed as a separate module on top of Lustre. Be sure to get feedback on your proposal on lustre-devel before you get started.
In summary, while I think there can be some small amount of bug selection by users, if there is interest in this it probably makes sense to spend some time to annotate bugs that are in the "small project" space and [[add a bugzilla search URL on the referring page]] rather than spend time to try and keep such a list up-to-date.
In all cases developers should contact lustre-devel to first discuss the bug and the approach that should be taken to fix it.
In the past I've also done bug triage for developers who want to contribute so that they can work on projects that are matching their experience level, and also not on a critical path or conflicting with internal development."
Helping with Lustre Testing
To find out how you can contribute to the testing of upcoming Lustre releases, see Lustre Test Plans.
