tcontribute.html - vaccinewars - be a doctor and try to vaccinate the world
(HTM) git clone git://src.adamsgaard.dk/vaccinewars
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
tcontribute.html (3220B)
---
1 <?xml version="1.0" encoding="UTF-8"?>
2
3 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
4 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
5
6 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
7
8 <head>
9 <title>How to contribute</title>
10 <meta charset="utf-8"/>
11 </head>
12
13 <body>
14 <h1>How to contribute</h1>
15
16 <p>dopewars is open-source software, meaning that it is free for anybody to
17 use. However, this also means that the quality of the software is dependent
18 in part on <b>you</b> the user. You <b>don't</b> have to be a programmer to
19 help out - in fact, dopewars currently needs people to produce sounds and
20 graphics rather than to write code.</p>
21
22 <ul>
23 <li><b>Sounds</b> are needed. dopewars-1.5.7 and later support sounds, but
24 don't contain sounds for every game event. If <b>you</b> can provide
25 copyright-free sounds, then short files are needed for various effects
26 in the game. For example,
27 gunshots, bullet hits, ricochets and subway trains are obvious candidates
28 for sound effects, although pretty much any event in the game that you can
29 think of can conceivably have a sound (e.g. when players join or leave the
30 game). These sounds should be in WAV format, and should probably be no more
31 than a second or two in length. Later versions of dopewars may also be able
32 to play longer repeating sounds (i.e. music) if you're interested in
33 contributing this. Please open a
34 <a href="https://github.com/benmwebb/dopewars/pulls">pull request</a>
35 to add sound files to dopewars.
36 <p /></li>
37
38 <li><b>Suggestions</b> for future improvements are always welcomed at the
39 <a href="https://github.com/benmwebb/dopewars/issues">issue tracker</a>.
40 These can be anything from "the game interface
41 is confusing" through "more game locations are needed" to "what about a
42 hospital". (I can't guarantee that such suggestions will ever make it
43 into dopewars, but it's a lot easier if I know they exist! Also, it's
44 far more likely to happen if you write the code - see the
45 <a href="developer.html">tips for developers</a> page.)<p /></li>
46
47 <li><b>Bug reports</b> are always useful. Register them with the
48 <a href="https://github.com/benmwebb/dopewars/issues">issue tracker</a>.
49 If I don't know the problem exists, I can't fix it...
50 The more information you can give here, the better. In particular, I need
51 to know your operating system - e.g. Linux or Windows. For Linux, gdb stack
52 traces of the core file are most useful.<p /></li>
53
54 <li><b>Configuration files</b> can be included in future distributions. If
55 you run a customised game, and think others might want to play with your
56 configuration, or at least use it as an example, then post it in the
57 <a href="https://github.com/benmwebb/dopewars/issues">issue tracker</a>.
58 <p /></li>
59
60 <li><b>Translation</b> of dopewars into your language will enable you to
61 play the game in your native tongue, and will also help others that speak
62 the same language. It's pretty easy, too - all you have to do is edit a
63 simple text file! See the <a href="i18n.html">i18n pages</a>.<p /></li>
64 </ul>
65
66 <hr />
67 <ul>
68 <li><a href="index.html">Main index</a></li>
69 </ul>
70 <p>
71 Last update: <b>05-12-2020</b><br />
72 Valid <a href="http://validator.w3.org/check/referer">XHTML 1.1</a>
73 </p>
74 </body>
75 </html>