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
| Line 1: | Line 1: | ||
This page describes how to select a project, find a bug to fix, or help with Lustre testing. | This page describes how to select a project, find a bug to fix, or help with Lustre testing. | ||
== Selecting a Project == | == Selecting a Project == | ||
[[ | If you'd like to take on a project to enhance 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 [[email: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 [[email:lustre-devel@lists.lustre.org lustre-devel]]. | |||
* ''Propose a project that can be developed as a separate module on top of Lustre.'' Be sure to get feedback on your proposal on [[email: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 | |||
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 [[email:lustre-devel@lists.lustre.org 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." | |||
== Finding a Bug to Fix == | == Finding a Bug to Fix == | ||
Revision as of 10:10, 3 September 2009
This page describes how to select a project, find a bug to fix, or help with Lustre testing.
Selecting a Project
If you'd like to take on a project to enhance 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 email: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 email:lustre-devel@lists.lustre.org lustre-devel.
- Propose a project that can be developed as a separate module on top of Lustre. Be sure to get feedback on your proposal on email: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 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 email:lustre-devel@lists.lustre.org 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."
Finding a Bug to Fix
Helping with Lustre Testing
To find out how you can contribute to the testing of upcoming Lustre releases, see Lustre Test Plans.
