diff options
| -rw-r--r-- | SUPPORT | 18 |
1 files changed, 9 insertions, 9 deletions
@@ -4,20 +4,20 @@ also be commercial support options available to you -- check http://www.nagios.org/ to track the current status of commercial support offerings. -There are two mailing lits associated wth Nagios Plugin development: +There are two mailing lists associated with Nagios Plugin development: 'help' (mailto:nagiosplug-help@lists.sourceforge.net), and 'devel' (mailto:nagiosplug-devel@lists.sourceforge.net). Unless you are fairly -certain you have found a bug or thet you are requesting a new feature, +certain you have found a bug or that you are requesting a new feature, please direct support requests to 'help'. -Becuase these lists are handled entirely by voluteers, and because +Because these lists are handled entirely by volunteers, and because these same volunteers are often plugin developers who can also use -their time to fix bug and provide feature requests, it is genrally in -you interest to do a modest amount of legwork bfore posting to either +their time to fix bug and provide feature requests, it is generally in +you interest to do a modest amount of legwork before posting to either of these lists. In brief, always provide the version of the software that you are -using, and when requsting features or reporting bugs, first check to +using, and when requesting features or reporting bugs, first check to see that the issue has not already been addressed in the CVS tree. GETTING HELP @@ -28,7 +28,7 @@ subject. A good post would have a subject like: Can I use SSL with check_imap (nagios-plugins 1.3.0-beta2) 1.12 -If you do not include the verion of the plugin, you risk having your +If you do not include the version of the plugin, you risk having your post silently ignored. Be advised that the core plugins (and in fact many of the contributed @@ -46,7 +46,7 @@ Bug reports, investigations of possible bugs, feature requests, and patch submissions should be submitted to the development list at (mailto:nagiosplug-devel@lists.sourceforge.net). -As with the support list, you should identify the version, prefrably +As with the support list, you should identify the version, preferably in the subject line. However, to best use developer resources, it is suggested that you reference your report one of the following sources: @@ -63,7 +63,7 @@ not. However, if you find a bug, you should determine whether it is still present in one of these sources, preferably either (2) or (3) which are most recent>) -From experince, I know that most bugs can be fixed with only a few +From experience, I know that most bugs can be fixed with only a few more moments work than it takes to determine if the bug is still present in the CVS tree. If you can save a developer the expense of that time, you ensure that bugs are fixed more rapidly, and thus you |