Update

[bacula/docs] / docs / home-page / pages / feature-request.php

diff --git a/docs/home-page/pages/feature-request.php b/docs/home-page/pages/feature-request.php
index 770a524f2417d599bc841f042f9a13cd0b669278..b9f3e19d26a8bbd7da4730d833bd281049f0fa45 100644 (file)
--- a/docs/home-page/pages/feature-request.php
+++ b/docs/home-page/pages/feature-request.php
@@ -7,18 +7,39 @@
    <td class="content">
 
 In the past, users informally submitted feature requests by email, and 
-I collected them, then once a version was released, I would publish the
+I (Kern) collected them, then once a version was released, I would publish the
 list for users to vote on.
-
-Now that Bacula has become a bigger project, I would like to formalize
-the process a bit more. The main change will be to require users
+<p>
+Now that Bacula has become a bigger project, this process has been 
+formalized a bit more. The main change is for users
 to carefully think about their feature, and submit it on a feature
 request form. A mostly empty form is shown below along with an 
-example of an actual filled in form.
-
-Once I receive and approve the Feature Request, possibly requesting
-some modifications, I'll add it to the projects file, which contains
-a list of all open Feature Requests.
+example of an actual filled in form. A text copy of the form can
+be found in the <b>projects</b> file in the main source directory
+of the Bacula release. That file also contains a list of all the
+currently approved projects and their status.
+<p>
+The best time to submit a Feature Request is just after a release when
+I officially request feature requests for the next version. The worst
+time to submit a feature request is just prior to a new release (we are
+very busy at that time).  To actually submit the Feature request,
+fill out the form, and submit it to both the bacula-users and
+the bacula-devel email lists. It will then be openly discussed.
+<p>
+Once the Feature Request has beeen adequately discussed, I will
+either reject it, approve it, or possibly request some
+modifications.  If you plan to implement the feature or donate
+funds to have it implemented, this is important to note,
+otherwise, the feature, even if approved, may wait a long time
+for someone to implement it.
+<p>
+Once the Feature request is approved, I'll add it to the projects
+file, which contains a list of all open Feature Requests.  The projects
+file is updated from time to time
+<p>
+The current (though possibly somewhat old) list of projects can also
+be found on the Web site by clicking on the Projects menu item.
+                     
 
 <h3>Feature Request Form</h3>
 <pre>