From Linux NFS
(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| - | The NFSv4 development and testing efforts are organized along the lines
| + | We have a mailing list: linux-nfs@vger.kernel.org. |
| - | of typical Open Source projects. Most discussion occurs on the
| + | And an IRC channel: #linux-nfs at oftc.net. |
| - | nfsv4 [http://developer.osdl.org/dev/nfsv4/site/mailing_lists.php mailing list], including bug reports, requests for help, test results and so forth.
| + | |
| | | | |
| - | For information on adding patches, please see the [http://www.citi.umich.edu/projects/nfsv4/linux/nfsv4-hacking.html NFSv4 Hacking] webpage. Patches can be posted directly to the nfsv4 mailing list.
| + | See also [http://www.citi.umich.edu/projects/nfsv4/linux/nfsv4-hacking.html NFSv4 Hacking]. |
| | | | |
| - | Bugs should be reported directly to the mailing list. There is a [http://developer.osdl.org/dev/nfsv4/bugzilla/ bug tracker] you can review to see if your bug is already known prior to reporting it on the list. The bug tracker is still fairly new, but hopefully by the time users are incorporating nfsv4 into their environments, many of the most common known bugs will be listed there. | + | Bugs may be reported to the mailing list, or to [bugzilla.kernel.org], or (for features that are not yet upstream), [bugzilla.linux-nfs.org]. |
| - | | + | |
| - | We have a [http://developer.osdl.org/dev/nfsv4/wiki/ wiki] available for collaborating on information related to testing and troubleshooting of NFSv4.
| + | |
| - | | + | |
| - | The community has developed a [http://developer.osdl.org/dev/nfsv4/wiki/ Test Matrix] spreadsheet that itemizes in great detail the testing tasks that should be done, prioritized High/Med/Low. This spreadsheet is being [http://developer.osdl.org/dev/nfsv4/wiki/index.php/Test_matrix moved into the wiki] to make it easier for testers to update.
| + | |
| - | | + | |
| - | An easy way to contribute right now, even if you have not started planning your testing efforts, is to write a use case that generally describes your architectural layout and identifies the characteristics of NFS that you think you will be stressing. By sharing your use case with the community, it will help testers better identify areas of NFS to test, which means when you do start doing your NFSv4 testing, you may find it more suitable to your own needs than otherwise.
| + | |
| - | | + | |
| - | When you begin doing your NFSv4 testing, we would encourage you to review the test matrix. This may save you some effort if someone has already done the testing, as you may be able to reuse their results or test scripts. It may also help you identify specific things to test for your own needs that no one else has tested. In this case, please list yourself for that item and post links to your results and test scripts, so others can check your findings (especially if you've found problems that the NFSv4 developers should fix).
| + | |
| - | | + | |
| - | Another important way to contribute to the testing effort is by providing your testing tools for others to use under an Open Source license. This makes it possible for the NFSv4 developers to try to replicate your issue, and allows NFSv4 testers to use your test to check for regressions in new code. This can save you a lot of headaches if you're particularly dependent on an uncommon feature that doesn't show itself in normal testing activities.
| + | |
Revision as of 15:49, 22 November 2010
We have a mailing list: linux-nfs@vger.kernel.org.
And an IRC channel: #linux-nfs at oftc.net.
See also NFSv4 Hacking.
Bugs may be reported to the mailing list, or to [bugzilla.kernel.org], or (for features that are not yet upstream), [bugzilla.linux-nfs.org].
