1 <? require_once("inc/header.php"); ?>
4 <td class="contentTopic"> Feature Requests </td>
9 In the past, users informally submitted feature requests by email, and
10 I collected them, then once a version was released, I would publish the
11 list for users to vote on.
13 Now that Bacula has become a bigger project, I would like to formalize
14 the process a bit more. The main change will be to require users
15 to carefully think about their feature, and submit it on a feature
16 request form. A mostly empty form is shown below along with an
17 exaple of an actual filled in form.
19 Once I receive and approve the Feature Request, possibly requesting
20 some modifications, I'll add it to the projects file, which contains
21 a list of all open Feature Requests.
23 <h3>Feature Request Form</h3>
25 Item n: One line summary ...
26 Origin: Name and email of originator.
27 Date: Date submitted (e.g. 28 October 2005)
30 What: More detailed explanation ...
32 Why: Why it is important ...
34 Notes: Additional notes or features ...
38 <h3>An Example Feature Request</h3>
40 Item 1: Implement a Migration job type that will move the job
41 data from one device to another.
43 Origin: Sponsored by Riege Sofware International GmbH. Contact:
44 Daniel Holtkamp <holtkamp at riege dot com>
45 Status: Partially coded in 1.37 -- much more to do. Assigned to
48 What: The ability to copy, move, or archive data that is on a
49 device to another device is very important.
51 Why: An ISP might want to backup to disk, but after 30 days
52 migrate the data to tape backup and delete it from
53 disk. Bacula should be able to handle this
54 automatically. It needs to know what was put where,
55 and when, and what to migrate -- it is a bit like
56 retention periods. Doing so would allow space to be
57 freed up for current backups while maintaining older
60 Notes: Migration could be triggered by:
64 Highwater size (keep total size)
73 <? require_once("inc/footer.php"); ?>