|
pierre@0
|
1 There are many ways that you can contribute to the development of the ad
|
|
pierre@0
|
2 module:
|
|
pierre@0
|
3 1. Testing.
|
|
pierre@0
|
4 2. Documentation.
|
|
pierre@0
|
5 3. Code.
|
|
pierre@0
|
6 4. Money.
|
|
pierre@0
|
7
|
|
pierre@0
|
8
|
|
pierre@0
|
9 1. Testing
|
|
pierre@0
|
10
|
|
pierre@0
|
11 The ad project is a large and complex collection of modules. As new
|
|
pierre@0
|
12 features are added, unfortunately new bugs are sometimes added too. And
|
|
pierre@0
|
13 unfortunately these bugs can go undetected in my development environement.
|
|
pierre@0
|
14 By installing the ad module on your server, testing it, and reporting any
|
|
pierre@0
|
15 problems that you run into, you help to improve the project.
|
|
pierre@0
|
16
|
|
pierre@0
|
17 Before submitting bug reports, please be sure that you are running the
|
|
pierre@0
|
18 latest version of the code, as your bug may have already been fixed. Also,
|
|
pierre@0
|
19 please be sure to review the existing bug reports that other people have
|
|
pierre@0
|
20 already submitted so I don't have to waste time cleaning up duplicate bug
|
|
pierre@0
|
21 reports -- I maintain this project on a volunteer basis and already have
|
|
pierre@0
|
22 little enough time as is. Finally, be sure to review the included
|
|
pierre@0
|
23 documentation to be sure that you have properly installed and configured the
|
|
pierre@0
|
24 module.
|
|
pierre@0
|
25
|
|
pierre@0
|
26 Bug reports can be viewed and submitted at the following URL:
|
|
pierre@0
|
27 http://drupal.org/project/issues/ad
|
|
pierre@0
|
28
|
|
pierre@0
|
29
|
|
pierre@0
|
30 2. Documentation.
|
|
pierre@0
|
31
|
|
pierre@0
|
32 There is limited documentation built into the modules, and additional
|
|
pierre@0
|
33 documentation found in the documentation directory distributed with the ad
|
|
pierre@0
|
34 module. However, documentation can always be improved. You don't need to
|
|
pierre@0
|
35 know how to write code or create patches to help improve the documentation.
|
|
pierre@0
|
36 You can simply rewrite documentation files and attach them to the project's
|
|
pierre@0
|
37 issue queue at the following URL:
|
|
pierre@0
|
38 http://drupal.org/project/issues/ad
|
|
pierre@0
|
39
|
|
pierre@0
|
40
|
|
pierre@0
|
41 3. Code.
|
|
pierre@0
|
42
|
|
pierre@0
|
43 There are plenty of issues listed in the project's queue waiting until I
|
|
pierre@0
|
44 find the time to code up fixes. If you are a PHP coder yourself, it is
|
|
pierre@0
|
45 tremendously helpful if you track down bugs and submit fixes! It's most
|
|
pierre@0
|
46 helpful if you submit fixes for both the 4.7.x and 5.x versions of the
|
|
pierre@0
|
47 module.
|
|
pierre@0
|
48
|
|
pierre@0
|
49 In addition to fixing bugs, you are also welcome to contribute new
|
|
pierre@0
|
50 features. It's preferred when new features use the ad module's many hooks
|
|
pierre@0
|
51 and are implemented in external modules.
|
|
pierre@0
|
52
|
|
pierre@0
|
53
|
|
pierre@0
|
54 4. Money.
|
|
pierre@0
|
55
|
|
pierre@0
|
56 I maintain the ad module in my spare time. While cash donations are not in
|
|
pierre@0
|
57 any way required, they are certainly appreciated. The simplest way to donate
|
|
pierre@0
|
58 money is to use PayPal and send the donation to my email address:
|
|
pierre@0
|
59 jeremy@tag1consulting.com. If you are unable to use PayPal, drop me a note at
|
|
pierre@0
|
60 that same email address and we can work out something else.
|
|
pierre@0
|
61
|
|
pierre@0
|
62 I also offer consulting services, and can be contracted to add specific
|
|
pierre@0
|
63 functionality to the module. Contact me at jeremy@tag1consulting.com for
|
|
pierre@0
|
64 more information.
|
