aboutsummaryrefslogtreecommitdiff
path: root/template/engage.html.j2
diff options
context:
space:
mode:
Diffstat (limited to 'template/engage.html.j2')
-rw-r--r--template/engage.html.j220
1 files changed, 10 insertions, 10 deletions
diff --git a/template/engage.html.j2 b/template/engage.html.j2
index 6d2cadbf..2fa2fe9d 100644
--- a/template/engage.html.j2
+++ b/template/engage.html.j2
@@ -53,17 +53,17 @@
53 </p> 53 </p>
54 <h2>Report bugs!</h2> 54 <h2>Report bugs!</h2>
55 <p> 55 <p>
56 While using GNUnet you will find bugs. Here are some notes on how to do that the most effective way: 56 While using GNUnet you will find bugs. Here are some notes on how to do that the most effective way:
57 <ul>
58 <li>Run 'gnunet-bugreport'</li>
59 <li>Report the output into our <a href="https://bugs.gnunet.org/">bug tracker</a>. Add more details e.g. what happened and what you expected to happen. </li>
60 <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li>
61 <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li>
62 <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li>
63 <li>Please follow up with eventual questions about the bug. </li>
64 <li>Once a fix is there: Check if it's working as expected, so that we can properly close the bug report and/or give you credits :)</li>
65 </ul>
66 </p> 57 </p>
58 <ul>
59 <li>Run 'gnunet-bugreport'</li>
60 <li>Report the output into our <a href="https://bugs.gnunet.org/">bug tracker</a>. Add more details e.g. what happened and what you expected to happen. </li>
61 <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li>
62 <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li>
63 <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li>
64 <li>Please follow up with eventual questions about the bug. </li>
65 <li>Once a fix is there: Check if it's working as expected, so that we can properly close the bug report and/or give you credits :)</li>
66 </ul>
67 <h2>Contribute!</h2> 67 <h2>Contribute!</h2>
68 <p> 68 <p>
69 There are various ways to contribute. We especially need coders with C skills and knowledge of crypto. Development work on this this website, it's translations, the bibliography, our wide documentation, and other efforts are most welcome, too.<br> 69 There are various ways to contribute. We especially need coders with C skills and knowledge of crypto. Development work on this this website, it's translations, the bibliography, our wide documentation, and other efforts are most welcome, too.<br>