diff options
Diffstat (limited to 'template/engage.html.j2')
| -rw-r--r-- | template/engage.html.j2 | 48 |
1 files changed, 28 insertions, 20 deletions
diff --git a/template/engage.html.j2 b/template/engage.html.j2 index ceeff7b8..2fa2fe9d 100644 --- a/template/engage.html.j2 +++ b/template/engage.html.j2 | |||
| @@ -18,11 +18,14 @@ | |||
| 18 | </p> | 18 | </p> |
| 19 | <h4>IRC</h4> | 19 | <h4>IRC</h4> |
| 20 | <p> | 20 | <p> |
| 21 | Most of the GNUnet developers are on the <a href="ircs://chat.freenode.net:6697/#gnunet">IRC channel #gnunet on freenode</a>. Please be patient and stay around at least for some hours to get an answer for your request. <!-- There is also a Matrix bridge to the IRC where you can get a backlog without staying connected. --> | 21 | Most of the GNUnet developers are on the |
| 22 | IRC channel #gnunet on freenode (connect via | ||
| 23 | <a href="ircs://chat.freenode.net:6697/#gnunet">ircs://chat.freenode.net:6697/#gnunet</a>). | ||
| 24 | Please be patient and stay around at least for some hours to get an answer for your request. <!-- There is also a Matrix bridge to the IRC where you can get a backlog without staying connected. --> | ||
| 22 | </p> | 25 | </p> |
| 23 | <h4>Mumble</h4> | 26 | <h4>Mumble</h4> |
| 24 | <p> | 27 | <p> |
| 25 | We have a monthly get-together on mumble where we talk about recent developments, strategies, and politics ;-) <br> | 28 | We have a monthly get-together on mumble where we talk about recent developments, strategies, and politics.<br> |
| 26 | We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br> | 29 | We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br> |
| 27 | To connect just enter "gnunet.org" as server into your mumble client; leave everything else as default. | 30 | To connect just enter "gnunet.org" as server into your mumble client; leave everything else as default. |
| 28 | </p> | 31 | </p> |
| @@ -50,20 +53,22 @@ | |||
| 50 | </p> | 53 | </p> |
| 51 | <h2>Report bugs!</h2> | 54 | <h2>Report bugs!</h2> |
| 52 | <p> | 55 | <p> |
| 53 | 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: |
| 54 | <ul> | ||
| 55 | <li>Run 'gnunet-bugreport'</li> | ||
| 56 | <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> | ||
| 57 | <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li> | ||
| 58 | <li>Please inform us if your operating system applies any vendor changes to GNUnet which you know about (to exclude sources of problems introduced by your OS).</li> | ||
| 59 | <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this – responses may take a while.</li> | ||
| 60 | <li>Please follow up with eventual questions about the bug. </li> | ||
| 61 | <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> | ||
| 62 | </ul> | ||
| 63 | </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> | ||
| 64 | <h2>Contribute!</h2> | 67 | <h2>Contribute!</h2> |
| 65 | <p> | 68 | <p> |
| 66 | There are various ways to contribute. We especially need coders with C skills and knowledge of crypto – but supporting with this website, it's translations, the bibliography and our wide documentation efforts are most welcome, too. As we are delivereing a new version now regularly, some packaging skills (for any OS) would a great thing to have – and if you are a designer we would need a hand, too. | 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> |
| 70 | The core software of GNUnet used to be released with long breaks between releases. Since the 0.11.0 release we try to make releases more regularly. Therefore package maintainers who are interested in working together with an welcoming environment are invited to contribute packages of our software to any OS/PM and request help.<br> | ||
| 71 | Last but not least designers are welcome to contact us about projects which require help. | ||
| 67 | </p> | 72 | </p> |
| 68 | </div> | 73 | </div> |
| 69 | </div> | 74 | </div> |
| @@ -78,14 +83,17 @@ | |||
| 78 | <div class="col-md"> | 83 | <div class="col-md"> |
| 79 | <h2>Get together!</h2> | 84 | <h2>Get together!</h2> |
| 80 | <p> | 85 | <p> |
| 81 | We meet in meatspace occasionally, mostly in Germany and Switzerland. The usual occasions are: | 86 | Occasionaly we meet in "meatspace", mostly in Germany and |
| 82 | <ul> | 87 | Switzerland. |
| 83 | <li><a href="https://events.ccc.de/congress">Chaos Communication Congress</a> in Leipzig (DE), 27th-30th December</li> | 88 | The usual occasions are: |
| 84 | <li><a href="https://datenspuren.de">Datenspuren</a> in Dresden (DE), usually by mid/end of September</li> | ||
| 85 | <li>GNUnet Hackweek in Mont-Soleil (CH), usually by the end of June</li> | ||
| 86 | <li>Other meetings happening throughout the year: You’ll get to know about it on our Mailinglist (or propose them yourself).</li> | ||
| 87 | </ul> | ||
| 88 | </p> | 89 | </p> |
| 90 | <!-- ul must stand on its own. See html specs --> | ||
| 91 | <ul> | ||
| 92 | <li><a href="https://events.ccc.de/congress">Chaos Communication Congress</a> in Leipzig (DE), 27th-30th December</li> | ||
| 93 | <li><a href="https://datenspuren.de">Datenspuren</a> in Dresden (DE), usually by mid/end of September</li> | ||
| 94 | <li>GNUnet Hackweek in Mont-Soleil (CH), usually by the end of June</li> | ||
| 95 | <li>Other meetings happening throughout the year: You’ll get to know about it on our Mailinglist (or propose them yourself).</li> | ||
| 96 | </ul> | ||
| 89 | </div> | 97 | </div> |
| 90 | </div> | 98 | </div> |
| 91 | 99 | ||